Slim 2010 Mac mini & Final Cut Studio 3

Hello all,
Is anyone running Final Cut Studio 3 on one of the new 2010 slim Mac minis or mini server? Is it really slow or is it running OK.
Thank you all very much.
Message was edited by: MLCinema

Some things to consider when you are deciding what to buy...
What are your needs?
Are you playing with FCS or will it be paying the bills?
If you are planning on doing a lot of work then you will need an additional hard drive to your system drive either internal or external.
Some machines don't allow for adding internal hard drives.
You will want at least 2G's of RAM to run FCS
Make sure you get a video card that can handle Motion if you plan on using that app.
There are plenty more gotchas that can pop up depending on what your plans are so think it through and remember sometimes going cheaper can cost you more in the long run than if you had just shelled out a little more in the beginning

Similar Messages

Mac Pro - Final Cut Studio 2 - Adobe Production Premium - NO FLASH PLAYING!

I recently purchased a Mac Pro with Leopard, Final Cut Studio 2, and Adobe Production Premium suite. I got everything setup yesterday, and I exported a Quicktime reference file from Final Cut, and brought it into Flash CS3 Media Encoder. The file seemed to encode fine, but when I try to open it, it shows that the Flash Player opens, but the video never actually opens. I also tired to import the FLV file into Flash Pro, and it acts as though it imports, but it does let me preview it. The ONLY thing that I think could have caused a problem is that I also have Sorenson Squeeze installed, which has its own On2 VP6 encoder. Again, this may have nothing to do with it since I copied the file to another Mac machine that did not have Sorenson on it, and downloaded the standalone Flash Player, and it acted the same. Any ideas on why FLV files would not play back would be greatly appreciated. I have ALL updates installed for OS X Leopard, as well as the CS3 collection. Thanks in advance.

After downloading an FLV player, and realizing that Adobe Flash Player will not work, all is swimming.

Is the JVC SR-DVM700 compatible with Macs and Final Cut Studio HD?

Hello all.
The company I work for is seriously thinking about purchasing the JVC SR-DVM700 next week (based on my recommendations). What I have discovered however is that there are very little user reviews and even less info on whether it is compatible with Final Cut Studio HD. Everything I have found 'seems' to indicate that it will work but I need a definite answer. The lack of user info makes me a little nervous.
Here are my questions:
If this system is incompatible, what would be a good alternative within the same price range?
What (if any), are the problems that crop up while using it and are they easily fixed?
What are your general thoughts on the system?
I really like the idea of a MiniDV, DVD and hard drive all in one machine but I need more info in case I need to put the brakes on this purchase.
Thanks for all your help.
Dual 2 GHz PowerPC G5 Mac OS X (10.4.4) 1.5 GB DDR SDRAM (working on getting more)

This is a FCP HD, but no Final Cut Studio HD
My guess is that you are trying to run FCP 4.5 HD on an Intel Mac.
It isn't reliable even if you could install it.
You need FCS2 -- at the upgrade price.

What's the right mac for Final Cut Studio?

Hi, I am a cameraman who wants to start learning final cut pro 5 to at first get a dvd together of my work (about 10 mins)and then maybe do some professional editing down the line. I am a bit lost with what mac I need to run studio on as I'm hearing conflicting voices. I can afford to buy an iMac G5 with 1.5 gig of ram. Will all the applications in studio run on this machine? should i bump up the hardrive to 250? Worst comes to worst should i wait and buy a power mac? Thanks for any help.
Imac g5 Mac OS X (10.4.3)

Let's get serious. You are trying to put together a short reel, not edit Cold Mountain.
If you believe you will make your living from this machine, get a professional grade box and all the bells and whistles to go with it.(max ram, multiple internal SATA drives, big monitors, etc)
If you want to get your feet wet, develop an understanding of the program and its basic operational structure, most anything that meets the minimum configuration will do. (Heck, you can edit on a powerbook...)
In the first case, (the professional box) if you spend 5 minutes rather than 15 minutes waiting for a render, it makes a differnece, time IS money. In the second case (learning curve), it doesn't matter. It's your time.
Cheers,
x
Do your part in supporting your fellow users. If a response has been Helpful to you or Solved your question, please mark it as such as an aid to other lost souls on the forum.
Also, don't forget to mark the thread Answered when you get enough information to close the thread.

Mac Mini - Final Cut Pro HD rendering

Hi
I have the late 2009 model mac mini, which I'm using to edit with final cut pro 7.
Up until recently I have always used DV footage, but I'm currently editing a project using HD footage from two cameras, one filmed at 720p the other with 1080p. The 720 footage is fine but the 1080 footage requires rendering each time I make any changes at all. I currently have the RT set to safe, and the playback set to dynamic. I've tried changing these settings which result in no change.
My question is - if I upgrade my mac mini to 8gb of ram instead of the 4gb currently installed, will this solve my issue?

NO. 8GB RAM is ideal for HD editing. But RAM isn't invovled in RT playback. The CPU and hard drive are. On an iMac you are stuck with FW800 external as your Scratch Disk, and this is just barely fast enough to deal with HD editing.
To make things run more efficiently, I'd make sure the codec of both camera footage match. That will save your CPU and hard drive a lot of work. I'm going to get the 720 is DVCPRO-HD and the 1080 is HDV? Any Long-GOP footage is going to bog down on FW800, so change it to either ProRes. Or if the 720 footage is Panasonic DVCPRO-HD then transcode it to that. That FW800 drive, and the GPU on that model of iMac are simply the best for HD video editing.
Set RT to Unlimited, Dynamic, you'll get the most playback out of it you can, once the codec issue is settled.

Not quite buyers remorse, but... Mac Mini, final cut pro x

Yesterday I bought my first mac, a late 2012 mac mini 2.3 GHz i7 with 4GB RAM. I do some very semi-professional video work and for years have been using a PC I built with Sony Vegas and it was time to get mac.
I know I took a chance with the mac mini, considering it doesn't have dedicated GPU, but it's not as snappy as I expected. To be fair, I've ordered RAM to get this machine up to 16GB, so maybe it will get better.
What I'm wondering is if there's any other mac mini users who have are using final cut pro x and adobe photoshop with similar specs?
I may be returning this and building my own PC again, I don't know. I really want this mac to be as awesome as I think it can be. Any experiences is appreciated.

Not FinalCut, but I do use Adobe Premiere, Encore and AfterEffects as well as PS, Dreamweaver and Audition.
PS was terribly slow with the OEM 4Gb. My Mini is a Corei5.
I first bumped up to 8Gb and that helped, but Premiere was still slow rendering. Photoshop worked well.
I have 16Gb now and I can run PS or Premiere with a Virtual Machine running too, and no lag at all.

Mac Mini & Final Cut Pro X: Intel Core i5 vs. Intel Core i7?

The Intel Core i5 is a dual-core, while the Intel Core i7 is a quad-core. Which one should I get and which one is more beneficial? Will I notice a difference in performance between the two? Besides FCPX, I'm also going to be listening to music, browsing the Internet, creating discs, and playing games. I know that the Macs no longer have a disc drive, but I am going to be buying an external disc drive.

Like woodmeister50, I generally buy the top of the model line (I have a late 2012 Mac mini with the 2.6GHz i7 processor, 16GB RAM, and Fusion drive) on the theory it will perform well enough to last through at least one more generation before I am longing for an upgrade. That said, given what you say you are planning to do with your Mac mini you are unlikely to notice a difference in performance between the i5 and i7 processors. However, you are likely to notice a difference between the model with only an HDD and one with a Fusion Drive. The Fusion drive will yield disk I/O performance that feels like a SSD but with the capacity of an HD. That could be a noticeable difference using FCPX.
NOTE: You mentioned games and with highly graphic intensive RPGs you may not be satisfied with the performance of the Intel video processor in the mini. If you are a serious gamer I would recommend you consider an iMac or even a Mac Pro for their superior video performance.

Question about Final Cut Studio 3/Final Cut Pro 7

Last year I bought Final Cut Studio 2 and got a student discount.
I was thinking about upgrading to Final Cut Studio 3, but I saw a post that said you can't upgrade if you have the academic version. First of all, is this true, and secondly how can I tell if I have the academic version?
If I can't upgrade, I can't afford to buy the whole package again. And surely I should have been informed of this! But can I edit a project on Final Cut Pro 6 and then work on it on Final Cut Studio 7, and back again? I presume not, but it's worth asking because I'm pretty much screwed if not and I can't get the upgrade.
Thanks

I want to upgrade because the macs at uni have upgraded, and I don't live near the uni I attend so it isn't practical for me to stay in their edit suites till late like everybody else does. I only bought the mac and final cut studio last year for this reason! So I prefer to edit from 2 machines: Mine, when I can, and the ones at uni when I'm collaborating with the 'crew'.
However, I cannot see academic version written anywhere. And I know this is going to make me sound even more stupid than I already do, but I can't remember if I got the student discount on Final Cut, or whether it was just on the mac. Does anyone know where I should be looking. I've checked the 'about final cut pro' details and looked through the packaging (and my emails for the receipt) but I cannot see anything.
Thanks

Does new MacBookPro 13" (Apr2010) run all Final Cut Studio applications?

Does the new MacBookPro 13" (April 2010) run all Final Cut Studio applications, and reasonably well?
I've looked at the FCS specs, CPU, RAM and hard disc minimums are more than satisfied with the MBP 13".
Now that the 13" has a discreet Nvidia (albeit sharing memory with main RAM) graphics card, that requirement is also satisfied.
The Color app needs a screen resolution of at least 1680x1050: Is this really a hard requirement?
i.e. will the Color app exit with an error message saying not supported at this resolution or will it work but with less space for items in its user interface? For example Adobe Premiere Pro 1.5 used to say minimum resolutions but I can run it on my Toshiba NB100 netbook at 1024x600 just fine. (BTW as an aside even this 200pound netbook has an eSATA port!)
Also I intend to use an external 23" 1920x1080 screen plugged into the MBP13" a lot of the time at home.
Also what about the Core 2 Duo on the 13" versus the i5 dual core hyperthreaded = 4 threads or i7 quad core = 8 threads on the new (Apr2010) 15" and 17" MBPs.
I intend to capture from solid state flash card, so dropped frames due to slow(is) internal 5400rpm non-raid hard drive capturing from real time playout of tape is not an issue.
Where would I notice the difference in speed? Where would the MBP 13" run noticeably slower compared with the new 15" and 17"?
I would expect the entry 2.4Ghz 13" Apr2010 model to run FCS/FCP reasonably well, given that people have coped with this sort of spec in the past.
As long as editing works reasonably smoothly on the 13" MPB, e.g. I can go backwards and forwards through my work, preview multiple tracks/effects (at lower resolution, if necessary - by using RTExtreme feature with ProRes422Proxy) and then leave it render to maximum high quality overnight, then I would be happy.
The smaller size of the 13" and lower cost make it more attractive to gain a more rounded cross platform skillset by entering into the Mac scene and for future opportunities requiring those skills.
The benefits buying a higher end notebook diminish against cost and increasing screen size (more to carry around), also that only the cumbersome (IMHO) 17" has ExpressCard34 for SATA input.

Thanks for your quick response and for the reassurance, my responses back...
{quote:title=NLEdit wrote:}
What sorts of things did you want to work on?
{quote}
Music videos, small projects to start with. I've come from working with Adobe Premiere Pro 1.5 on Windows XP on a 30minute documentary that took 18months part and fulltime to produce with 3 staff (http://www.youtube.com/mediamotioninvision for a clip of it). I feel the next level up would be to work with what many professionals are using: Final Cut Studio, as I was told at Cannes Film Festival in 2009. So to progress my craft I want to develop the skillset of the professionals.
{quote:title=NLEdit wrote:}
You also have to consider the i/o issue. How will you get footage in and out of the machine to an external drive and from a firewire camera if you go that route?
{quote}
Many film/video cameras, both low end/entry level consumer prosumer and higher end professional are recording onto solid state flash memory cards, e.g. SD. So transferring from that into the notebook is straightforward. This used to be more of an issue with tape-based cameras, as the footage transfer was real time and dropped frames could occur if the host recieving notebook could not handle the amount of data be sent from the camera, e.g due to slow hard drive/bus.
That said, even though solid state media eliminates the problem of dropped frames due to real time transfer of tape, it is a profound crying shame of a misguided decision that Apple decided to omit the ExpressCard34 interface (and therefore block high-speed eSATA/RAID hard drive options) from the 'Pro' range of 13" and 15" MacBookPros and reserve it for the 17", when the equivalent Windows notebooks have this for half the price.
So I'm reluctant to invest more money in a higher spec machine 1) because of limited budget 2) but also the higher spec 15" appears to be sadly unbalanced in that there is up to quad core of processing power etc but a lacking in external interfaces i.e. maximum of FireWire 800 for connecting external drives to. More better in my view to spend just enough on a 'sketch' grade notebook, for learning on and reasonable performance and benefit from the smaller size and cost.
Playback, previewing while editing the work may be a little compromised owing to the throughput of the internal harddrive, but, from my reading, I understand that RTExtreme and ProRes422Proxy technologies can help this situation of limited hard drive bandwidth/transfer rate whereby lower bitrates are used combined with reduction in preview quality to allow smoother playback. That is acceptable to me as long as I can get a good idea of how it looks. I intend to leave it running overnight to do the final maximum high quality render.

Final Cut Studio and Flash Macromedia 8

Hello everybody,
I would like to know if I can export swf files from Flash 8 (For MAC) to Final Cut Studio in order to convert them to Video files such as *.avi, *.mpg and to modify them. On Flash we can publish a flash file as quicktime file, but several effects included in Flash 8 are not available. We can to export it as AVI, but just from Windows, from Mac is not available, anybody knows why?
For this reason, I have:
1) to publish a flash file as SWF
2) to convert the file from SWF to AVI (with a program like Magic SWF2AVI (from Windows))
3) and it will be ready to work with it on Mac with Final Cut Studio.
If anybody knows how can I simplify it? and how can I work with Final cut from a Flash file using just a MAC?
Thanks a lot!
G5 Mac OS X (10.3.9)
G5 Mac OS X (10.3.9)

Yes. It is possible for you to create a *.avi if you have the source *.fla file. In Flash File menu > Export > Export Movie and in that you can choose avi, move, jpg sequence or anything like that. You need to ensure the *.fla file is created with right settings interms of Frames per second etc that is relevant to the settings you need it in FCP. Guess that is what you wanted !!!
Power MAC G5 Quad Mac OS X (10.4) Decklink HD Extreme

Final Cut Studio 3 on a 2010 Mac Mini?

Hi, I've searched the web high and low and can't find an answer to my question. Can the new Mac Mini dual 2.4 run Final Cut Studio 3? My main concern is the graphics card which SHARES 256mb ddr3 sdram. The Final Cut Studio 3 page says the hardware should be at least 128MB Vram. Is the shared 256MB SDram seen as "V"ram by Final Cut Studio?
If I'm reading the specs right the only thing the Mac Mini can't do is 4k & DPX rendering which requires 512MB Vram in Color (and I'm sure other intensive tasks would crawl).
Of course we would all like a Mac Pro, but my budget is tight.
Thank you so much for any feed back.

What do you mean by "Forget Color, forget Motion. There is no way to properly monitor what you are doing.
COLOR: I mean that to properly use COLOR you need a separate capture or video input/output device. One designed for video. Color will not send out a video signal via the HDMI port. That is, in essence, just another video out option...a video signal, via an HDMI port. So that you can connect the mini to an HDTV. But, it will mirror the desktop, send out an RGB signal, not a proper YUV video signal. For Color, you need proper monitoring. But you don't need to use Color...just saying.
and extended desktop is possible across the two for dual monitors, correct?
Yes, dual COMPUTER DISPLAYS...not proper video monitoring.
Color only requires 1680x1050)
For workspace...to use the interface. But to get a proper video signal you need a professional IO device. None works with the Mini. Well, there is the AJA IOHD, but that doesn't work with Color (firewire issue).
MOTION: Well, it might work. I just know that on the Mini I have it is a dog to work with. So I skip it. Let the kids edit on the BIG TV...they have fun with that.
Shane

Final Cut Studio 2 - not on Mac Mini?

I moved away from Mac towers around 12 months ago as I just didn't need the power and the Mac Mini has served me well since then, even running Final Cut Pro and DVD Studio Pro etc.
However, a worrying section of the spec requirements for Final Cut Studio 2 is 'An AGP or PCI Express Quartz Extreme graphics card (Final Cut Studio is not compatible with integrated Intel graphics processors)'
That basically means if you have a Mac Mini you are screwed, right? Therefore if I want to run Final Cut Pro 6 I need to get a tower? Crikey, that's bad news if that is the case...
As an aside - why the **** don't Apple release a 'Mac Middle' - a mini tower with space for two Sata drives and perhaps a maximum of 4Gb and a single Core duo. That way the Mac Pro is protected for the high end but the pro apps are far more affordable and worthwhile on a cheaper platform. Just my 2p worth!

Go to the individual applications page for detail and read the specs VERY closely. If it says it needs a video card or processor of a certain level - well - that's what it means. In years past, some hacks have been made but who knows if that is possible in the next generation. I certainly would not count on it.
x

Final cut studio 2 on mac mini

has anyone tried it on a mac mini?
i want to get a new mac pro but since the design is about to change sooner or later i prefer to get a desktop in the meantime.
does it run on a mac mini with that slow graphic card? what about color or motion?
thanks
mac mini Mac OS X (10.4.10)

http://www.apple.com/finalcutstudio/specs.html
"A Macintosh computer with a 1.25GHz or faster PowerPC G4, PowerPC G5, Intel Core Duo, or Intel Xeon processor
1GB of RAM
An AGP or PCI Express Quartz Extreme graphics card (Final Cut Studio is not compatible with integrated Intel graphics processors)
A display with 1024-by-768 resolution or higher."
That is the requirement to install all of the applications. Motion and definitely Color won't work.
You might be able to run DVD SP and FCP 6, however.
But then what do you capture video footage to?

Using final cut studio what the best way of getting a mini disc in to FCP?

I do some weddings and record some audio on to a mini disc recorder ( the small ones . On my avid liquid edit suite I just used to run it in live or ingest it on a 2 hour timer, and just record audio.
What the best way to do it with final cut studio and final cut pro?

Is there a reason you can't do the same on your mac system? What outputs does the audio recorder have?
Jerry

Final Cut Studio Fail After Pro Application Update 2010-1

Final Cut Pro crashes when loading project.
Motion crashes when loading project.
Compressor won't allow me to "submit" my batch from the 'name batch' stage.
I didn't try DVD Studio or Color.
Problems started as soon as I updated. Anyone else have similar problems? I tried dumping my system preferences but that didn't help. I haven't modified or customized FCS at all, I don't have any unusual plugins - I hardly even set up customized window configurations.
Using latest Final Cut Studio (MB642Z/A)
Final Cut Pro 7.0
Compressor 3.5
Motion 4
Running OS X 10.6.2
3.06 GHz Intel Core 2 Duo, 21.5" iMac
8 GB 1067 MHz DDR3
Thank you for any feedback. If others have similar problems, I can wait for next update (hopefully soon) otherwise I have no clue where to start.
--Doug

I should have known better, but new to the mac....dealt with death blows like this for a while....
Process: Final Cut Pro [1209]
Path: /Applications/Final Cut Studio/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 7.0.1 (7.0.1)
Build Info: FCPApp-910141802~4
Code Type: X86 (Native)
Parent Process: launchd [124]
Date/Time: 2010-03-25 01:06:44.195 -0500
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6
Interval Since Last Report: 3062 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 1939 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: 2739307A-393B-4135-A387-644DE9430D3D
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x00000000390302fe
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x90f1bb51 tinymalloc_from_freelist + 741
1 libSystem.B.dylib 0x90f1ab03 szonemalloc_shouldclear + 297
2 libSystem.B.dylib 0x90f1a988 malloczonemalloc + 81
3 libSystem.B.dylib 0x90f18a58 malloc + 50
4 libstdc++.6.dylib 0x91105617 operator new(unsigned long) + 36
5 com.apple.motion.TextFramework 0x24c54dab TXTextObjectRender::getHelium(LiAgent&) + 667
6 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
7 com.apple.motion.TextFramework 0x24c13829 TXTextLayout::buildHGNodeForFace(PCPtr<TXTextObject>, OZRenderParams&, LiAgent&, TXHeliumGlyph*, unsigned int, bool, PCMatrix44Tmpl<double>&, PCMatrix44Tmpl<double>&, PCMatrix44Tmpl<double>&, PCMatrix44Tmpl<double>&) + 4985
8 com.apple.motion.TextFramework 0x24c455ec TXCachedGlyphRender::getHelium(LiAgent&) + 940
9 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
10 com.apple.Lithium 0x248c4cda LiImageSoftClip::getHelium(LiAgent&) + 74
11 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
12 com.apple.Lithium 0x248c4cda LiImageSoftClip::getHelium(LiAgent&) + 74
13 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
14 com.apple.Lithium 0x248e0692 LiPolygonInstance::makeNode(LiClipSet const&) + 1682
15 com.apple.Lithium 0x24911111 LiRenderInstance::collectGeode(LiGeode*, LiCollectState&) + 929
16 com.apple.Lithium 0x24911f01 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 1521
17 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
18 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
19 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
20 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
21 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
22 com.apple.Lithium 0x249136a5 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 7573
23 com.apple.Lithium 0x249123a8 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 2712
24 com.apple.Lithium 0x249123a8 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 2712
25 com.apple.Lithium 0x249123a8 LiRenderInstance::collect3D(LiSceneObject*, LiCollectState&) + 2712
26 com.apple.Lithium 0x249144b5 LiRenderInstance::collectPolygons(LiSceneObject*, LiPtrArray<LiPolygonInstance>&) + 1509
27 com.apple.Lithium 0x24914d35 LiRenderInstance::collect() + 949
28 com.apple.Lithium 0x24914f91 LiRenderInstance::buildHeliumGraph(LiAgent&) + 529
29 com.apple.Lithium 0x24915a3e LiRenderInstance::getHelium(LiAgent&) + 270
30 com.apple.Lithium 0x2486bac3 LiRenderer::getHelium(LiAgent&) + 51
31 com.apple.Lithium 0x248ce715 LiAgent::getHelium(LiImageSource*) + 4789
32 com.apple.ozone.framework 0x238c4ebe GLRenderer::getSceneHeNodeFromLiWorld(OZScene*, OZSceneSettings const&, OZRenderParams&, PCPtr<LiGroup>, HGRenderer*, int, int, double, double, long*) + 2254
33 com.apple.ozone.framework 0x238c96e0 GLRenderer::getFrameNodeForSingleTime(OZScene*, OZRenderParams&, HGRenderer*, double, double, long*) + 880
34 com.apple.ozone.framework 0x238ca2ae GLRenderer::getFrameNodeIncludingFields(OZScene*, OZRenderParams&, HGRenderer*, long*) + 990
35 com.apple.ozone.framework 0x238ca894 GLRenderer::getFrameNode(OZScene*, OZRenderParams&, HGRenderer*, long*) + 164
36 com.apple.ozone.framework 0x238ce817 GLRenderer::render(OZScene*, OZRenderParams&) + 2583
37 com.apple.ozone.framework 0x2396fdd3 OZXGetFrame + 2755
38 com.apple.ozone.framework 0x23972406 OZXGetFrameAsTexture + 86
39 ...uartzComposer.QCMotionPatch 0x0d949c96 UserHasCancelled + 17982
40 ...uartzComposer.QCMotionPatch 0x0d9467ca UserHasCancelled + 4466
41 ...uartzComposer.QCMotionPatch 0x0d946428 UserHasCancelled + 3536
42 com.apple.QuartzComposer 0x91730396 -[QCPatch(Private) _renderAtTime:arguments:] + 111
43 com.apple.QuartzComposer 0x91739334 -[QCContext renderPatch:time:arguments:] + 809
44 com.apple.QuartzComposer 0x91738f9c -[QCGraphicsContext renderPatch:time:arguments:] + 96
45 com.apple.QuartzComposer 0x91737f53 -[QCOpenGLContext renderPatch:time:arguments:] + 565
46 com.apple.QuartzComposer 0x91737d16 -[QCPatch(Runtime) render:arguments:] + 92
47 com.apple.FinalCutPro 0x005196e9 RenderQCPatch + 1671
48 com.apple.FinalCutPro 0x00515c63 FCPQCMainEntry(long, long, KGDictInt*, void*) + 10083
49 com.apple.FinalCutPro 0x002ea236 pKGRunTransition(KGDictInt*) + 2182
50 com.apple.FinalCutPro 0x0045b5dc EffectRender(XXGlobals*, EffectTree*, long, long, Output*) + 5894
51 com.apple.FinalCutPro 0x0045e909 RenderFXTreeNode(XXGlobals*, EffectTree*, long, unsigned char, KGQTCanvasFormat, long, Output*) + 1497
52 com.apple.FinalCutPro 0x004614fb DecodeEffectFrameN(XXGlobals*, EffectTree*, long, unsigned char, Output*, bool*) + 2933
53 com.apple.FinalCutPro 0x004609ff DecodeEffectFrameN(XXGlobals*, EffectTree*, long, unsigned char, Output*, bool*) + 121
54 com.apple.FinalCutPro 0x004609ff DecodeEffectFrameN(XXGlobals*, EffectTree*, long, unsigned char, Output*, bool*) + 121
55 com.apple.FinalCutPro 0x00461893 DecodePipeTree(XXGlobals*, Output*) + 633
56 com.apple.FinalCutPro 0x0042bb15 FCPMediaHandler::RenderFrames(long long, bool) + 3981
57 com.apple.FinalCutPro 0x0042c17b FCPMediaHandler::Idle(long, long, long*, TimeRecord*) + 657
58 com.apple.FinalCutPro 0x0042d245 FCPMHIdle(FCPMediaHandler*, long, long, long*, TimeRecord*) + 45
59 ...ple.CoreServices.CarbonCore 0x92def72d callComponentStorage_44444 + 49
60 ...ple.CoreServices.CarbonCore 0x92de4474 CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
61 com.apple.FinalCutPro 0x00426009 FCPMHDispatch(ComponentParameters*, char**) + 59
62 ...ple.CoreServices.CarbonCore 0x92ddcb06 CallComponentDispatch + 29
63 ...ickTimeComponents.component 0x95ee4de7 MediaIdle + 61
64 ...ickTimeComponents.component 0x957673b6 doGenericIdle + 2991
65 ...ickTimeComponents.component 0x957691eb GenericMoviesTask + 357
66 ...ple.CoreServices.CarbonCore 0x92def72d callComponentStorage_44444 + 49
67 ...ple.CoreServices.CarbonCore 0x92de4474 CallComponentFunctionCommonWithStorage(char**, ComponentParameters*, long (*)(), unsigned long) + 54
68 ...ickTimeComponents.component 0x9576893e GenericComponentDispatch + 182
69 com.apple.FinalCutPro 0x00426025 FCPMHDispatch(ComponentParameters*, char**) + 87
70 ...ple.CoreServices.CarbonCore 0x92ddcb06 CallComponentDispatch + 29
71 com.apple.QuickTime 0x912b4083 MediaMoviesTask + 61
72 com.apple.QuickTime 0x912b2e33 TaskMovie_priv + 4783
73 com.apple.QuickTime 0x912c5b68 MoviesTask_priv + 101
74 com.apple.FinalCutPro 0x001bad50 DoMoviesTask(KGPlayerRec*) + 2388
75 com.apple.FinalCutPro 0x001cda79 DisplayMovie(KGPlayerRec*) + 2201
76 com.apple.FinalCutPro 0x001d1f70 pKGPlayerUpdate(KGPlayerRec*) + 196
77 com.apple.FinalCutPro 0x001bb045 DelayTimer(long, long, KGDictInt*, void*) + 89
78 com.apple.FinalCutPro 0x00150552 KGTimerInvoke(__EventLoopTimer*, void*) + 212
79 com.apple.CoreFoundation 0x900c1edb __CFRunLoopRun + 8059
80 com.apple.CoreFoundation 0x900bf864 CFRunLoopRunSpecific + 452
81 com.apple.CoreFoundation 0x900bf691 CFRunLoopRunInMode + 97
82 com.apple.HIToolbox 0x97feff0c RunCurrentEventLoopInMode + 392
83 com.apple.HIToolbox 0x97fefcc3 ReceiveNextEventCommon + 354
84 com.apple.HIToolbox 0x98177c02 _AcquireNextEvent + 54
85 com.apple.HIToolbox 0x9816dd5b _RunAppModalLoop + 101
86 com.apple.HIToolbox 0x9816e13b RunAppModalLoopForWindow + 86
87 com.apple.FinalCutPro 0x002a86b3 pKGDialogRun(KGPanelRecord*, unsigned char, unsigned char, KGDictInt*) + 755
88 com.apple.FinalCutPro 0x00285bf4 pKGNotifyFilesOffline(KGDictInt*, long) + 1990
89 ...FinalCutPro.Plugins.Browser 0x0bd0c914 BrowserOpenFile(KGFileRec*, unsigned char, unsigned char, KGDictInt**) + 5718
90 ...FinalCutPro.Plugins.Browser 0x0bd0f42d Browser(long, long, KGDictInt*, KGFileRec*) + 10299
91 com.apple.FinalCutPro 0x0018c870 CheckForOpenFile(KGFileSpec*, char*, unsigned char, unsigned char, KGDictInt**) + 488

Slim 2010 Mac mini & Final Cut Studio 3

Similar Messages

Maybe you are looking for