http://www.apple.com/final-cut-pro/whats-new/ There is a brief description about halfway down this page. Hopefully it's what you're after.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple's Professional Video Apps Final Cut Pro, Motion, and Compressor Updated
- Thread starter MacRumors
- Start date
- Sort by reaction score
http://www.apple.com/final-cut-pro/whats-new/ There is a brief description about halfway down this page. Hopefully it's what you're after.
You are quite correct however - just an opinion, Apple does a miserable job of maintaining most of its own apps. Aperture went from elating photo enthusiasts to being another 'rotten Apple' experience.
Personally, I don't use Aperture but I know lots of people who do and this now short life product was a total waste of their time and the learning curve to fully exploit it. - It could have been spent on Lightroom or another product. While I might loathe Micro$oft's behaviors and business, I find Apple too has become another giant that generates "issues" for end users and it is no wonder that many people (like myself) wonder why many 3rd party applications have a longer life than Apple's software and with more effort to have meaningful updates.
I am not upset as this is nothing new for Apple and glad I am not caught in this mess.
------------
Capture One Pro, Photoshop 6, and other photo related apps that are not Apple.
hey guys, i just downloaded new fcp x update and ran a quick test using my finicky mid-2010 MBP w/ GT330M. first try, after laying down video clips i added light effect transition. worked on one clip then i added a 2nd light effect transistion, which then caused my MBP to KP. same gpu-related KP as usual. i tried it again after reboot and this time w/o doing any effect transistions. just straight video clips and then shared it or exported it. the 3:30m video exported. it's AVCHD 1080P/23.9FPS video from a sony-nex 6 camera.
i don't know what is effin wrong w/ this MBP. but, i obviously can use it but if i push it too hard w/ transistions, titles, it inevitably causes a KP.
wtf Apple!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
i don't know what is effin wrong w/ this MBP. but, i obviously can use it but if i push it too hard w/ transistions, titles, it inevitably causes a KP.
wtf Apple!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Actually, the white paper on that page you linked is even more specific!
http://images.apple.com/final-cut-pro/docs/Apple_ProRes_White_Paper.pdf
Well, from the naming of other prores codecs, it's not difficult to interpret. A 4K extra or extreme quality as opposed to SD or HD standard, low or high quality.
Most? I might agree with some of the consumer apps like the iLife and iWork stuff but what other pro apps have been neglected? A number of those were just updated.
I'd say with Apple it has tended to be pretty obvious which apps they were intending to keep updating and which they were intending to dump. Which has been the case with many other companies, it's not unusual for one app to stop getting updates while the others have obvious development.
We'll maybe you shouldn't comment if you haven't kept up. Final cut x was released in June 2011.
Bwhahahahhahahah Thanks Kid. Editing user share, is Avid 35% Fcp7 30% Premiere CC 18% and FCP x at17% Now So BWHAHAHAH
Final cut 7-x make up more of the market then any other, and FCP7 is losing users to FCPx so lol Avid has not gained much market share lol and premiere has not gained much more market share either so..
where does one get fcp 7 these days? fcp x is unuseable for me since i have a weird latent defect on my mid-2010 15" MBP. but, i have tried going back to OS X lion and i can use fcp express 4 (or whatever the last version of it is) no problem and os x lion seems more stable for my MBP. i would like to downgrade to fcp 7 and to os x lion for my particular situation. not sure tho if it will cost too much dough.
What about exporting OMF or AAF files?
As a sound professional, my clients need to buy X2Pro to export a AAF file if they are using FCPX. To me, it's remarkable that a major update doesn't include the ability to export audio in a format that ProTools can open.
As far as I'm concerned, it's not Pro yet.
As a sound professional, my clients need to buy X2Pro to export a AAF file if they are using FCPX. To me, it's remarkable that a major update doesn't include the ability to export audio in a format that ProTools can open.
As far as I'm concerned, it's not Pro yet.
Pro Tools is an Avid product, right? So you're complaining that Final Cut doesn't automatically support a competing product? How about being mad that Pro Tools doesn't support a format that Final Cut exports?
Final Cut 7 exported OMF files. This feature was one of the biggies that was missing in FCPX.
I can't speak to how well FCPX exports for use in Logic, but this doesn't change my mind. ProTools is the de facto industry standard for post production audio editing and mixing. Until FCPX lets an editor export an AAF file, I refuse to think that FCPX is a "complete" professional product.
Hey, Apple! Can you update my Final Cut Express please? I mean, it's probably better than Final Cut X.
LOL...this statement is so false.
Tons use FCX in TV and Film and those that don't moved to Premiere, not Avid.
ok. no mention of "addressed replicate-able gpu-related kernel panics in mid-2010 mbp's w/ gt330m dGPU"
If you get repeated issues like this, make sure you let apple know at http://www.apple.com/feedback, the FCPX team do listen & will try to fix the problem in the next update if it's software related.
----------
You're correct - just like Adobe Encore was dropped & there's no viable mac replacement (any suggestions welcomed other than Toast)!
ok. i went to the website and tried to tell my story. unfortunately, they limit your feedback to only so many words.
"I'm writing to you guys as a last resort since I don't know where else to turn or whether there is even a place for me to make a turn. I'm sort of stuck on a street with dead ends on both sides, if you know what I mean. The only bright side to it is that the computer, which you guys made is the one stuck on this street and not me (I think). But, it is still my computer and the only one I will have for a while. So, I'd like it to be able to get out of this jam. To make a long story short, my computer is a Mid-2010 Macbook Pro, which I think is afflicted with the dreaded "Latent Manufacturing Defect." Now, I have had Apple Geniuses diagnose my computer about 2 or so months ago and my computer failed the Apple Video Systems Test. But, I just can't afford anything, right now. What should I do?"
do you guys think this letter is effective? it sucks that you're limited to how much you can write. i couldn't even get to the actual issues i am encountering.
GPU might not be broken
Here is a quote from another Apple discussion board.
Hello guys,
what fixed the issue of "recurring GPU panics at random times" for me was to alter the Configuration.plist file located in "/System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphi cs.framework/Resources/".
Just copy that file to the Desktop and edit it with XCode.
Where it sais "ForceSessionDrawsVirtualFramebuffer" change "NO" to "YES"
-> This setting will force the GPU to write data only to the main memory instead of using the VRAM.
Note: i assume this fix only works for GPU panics caused by read access failure (see what your panic dump says).
Note: do not use these settings if you're low on memory.
~
I did this to my 2010 17in MBP and when I upgraded to Mavericks I had random shutdowns and the likes. Fortunately I was within my warranty, so they replaced the logic board, because of power related issues. When i got my laptop back I had the same issues even on reinstalling mavericks. It would just occasionally restart 1-2 times maybe every 3 days. So I tried this fix and my MBP hasn't had a problem since. I've done this to about 6 other 2010 MBPs 15inch and 17inch. Hope this helps some people.
That's a common problem with Mid 2010 MacBooks Pro. In other words, your Mac's NVIDIA GPU is damaged
Here is a quote from another Apple discussion board.
Hello guys,
what fixed the issue of "recurring GPU panics at random times" for me was to alter the Configuration.plist file located in "/System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphi cs.framework/Resources/".
Just copy that file to the Desktop and edit it with XCode.
Where it sais "ForceSessionDrawsVirtualFramebuffer" change "NO" to "YES"
-> This setting will force the GPU to write data only to the main memory instead of using the VRAM.
Note: i assume this fix only works for GPU panics caused by read access failure (see what your panic dump says).
Note: do not use these settings if you're low on memory.
~
I did this to my 2010 17in MBP and when I upgraded to Mavericks I had random shutdowns and the likes. Fortunately I was within my warranty, so they replaced the logic board, because of power related issues. When i got my laptop back I had the same issues even on reinstalling mavericks. It would just occasionally restart 1-2 times maybe every 3 days. So I tried this fix and my MBP hasn't had a problem since. I've done this to about 6 other 2010 MBPs 15inch and 17inch. Hope this helps some people.
How about graphic distortions? My 2010 15" just started doing this recently. Apple had a recall, but they would only cover within 3 years of purchase so I am SOL. Does this help with those problems too?
You also recommend not doing this on systems with low memory. The 8GB max in these models is pretty low memory for FCPX. Does this have any impact in your experience?
here is my dump:
Fri May 30 19:53:34 2014
panic(cpu 0 caller 0xffffff7f9d62ef7c): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff81373e9000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.5.26/src/AppleMuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 0), Frame : Return Address
0xffffff8125b3b140 : 0xffffff801b222fa9
0xffffff8125b3b1c0 : 0xffffff7f9d62ef7c
0xffffff8125b3b290 : 0xffffff7f9bd05e7b
0xffffff8125b3b350 : 0xffffff7f9bdcf46a
0xffffff8125b3b390 : 0xffffff7f9bdcf4da
0xffffff8125b3b400 : 0xffffff7f9c04e056
0xffffff8125b3b530 : 0xffffff7f9bdf2b09
0xffffff8125b3b550 : 0xffffff7f9bd0c8cd
0xffffff8125b3b600 : 0xffffff7f9bd0a3d8
0xffffff8125b3b800 : 0xffffff7f9bd0b356
0xffffff8125b3b8e0 : 0xffffff7f9cc479c2
0xffffff8125b3b920 : 0xffffff7f9cc5737f
0xffffff8125b3b940 : 0xffffff7f9cc8533b
0xffffff8125b3b980 : 0xffffff7f9cc8539b
0xffffff8125b3b9c0 : 0xffffff7f9cc5ce15
0xffffff8125b3ba10 : 0xffffff7f9cc28b5e
0xffffff8125b3baa0 : 0xffffff7f9cc24ae7
0xffffff8125b3bad0 : 0xffffff7f9cc22636
0xffffff8125b3bb00 : 0xffffff801b6ce0a3
0xffffff8125b3bb90 : 0xffffff801b6cff9f
0xffffff8125b3bbf0 : 0xffffff801b6cdabf
0xffffff8125b3bd40 : 0xffffff801b2b66a8
0xffffff8125b3be50 : 0xffffff801b226bf1
0xffffff8125b3be80 : 0xffffff801b2139f5
0xffffff8125b3bef0 : 0xffffff801b21e043
0xffffff8125b3bf70 : 0xffffff801b2c989d
0xffffff8125b3bfb0 : 0xffffff801b2f3c76
Kernel Extensions in backtrace:
com.apple.driver.AppleMuxControl(3.5.26)[B67CD59F-1344-37BC-8A9A-46D6D3DCA13D]@0xffffff7f9d620000->0xffffff7f9d633fff
dependency: com.apple.driver.AppleGraphicsControl(3.5.26)[C0F9A79F-167E-3A68-873C-5CE17B97FB11]@0xffffff7f9d618000
dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xffffff7f9bb6d000
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff7f9b8be000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0xffffff7f9bc63000
dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[E04639C5-D734-3AB3-A682-FE66694C6653]@0xffffff7f9d61b000
com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[6EB3FF52-A4F6-3496-AE9C-D89B00FDE504]@0xffffff7f9bcb6000->0xffffff7f9bf1efff
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff7f9b8be000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[B93BBFC9-9ED5-3DDD-8CED-5EDA081BB997]@0xffffff7f9bca6000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0xffffff7f9bc63000
com.apple.nvidia.classic.NVDANV50HalTesla(8.2.4)[B0E6AAA7-E970-3D81-8B43-145D56A3A4AC]@0xffffff7f9bf29000->0xffffff7f9c1d2fff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[6EB3FF52-A4F6-3496-AE9C-D89B00FDE504]@0xffffff7f9bcb6000
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff7f9b8be000
com.apple.GeForceTesla(8.2.4)[24ED915E-02F3-3A31-8502-6AA41FFCA420]@0xffffff7f9cc07000->0xffffff7f9ccd1fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff7f9b8be000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[B93BBFC9-9ED5-3DDD-8CED-5EDA081BB997]@0xffffff7f9bca6000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0xffffff7f9bc63000
dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[6EB3FF52-A4F6-3496-AE9C-D89B00FDE504]@0xffffff7f9bcb6000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
13D65
Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
Kernel slide: 0x000000001b000000
Kernel text base: 0xffffff801b200000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 397836666227109
last loaded kext at 397631734858683: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f9d7af000, size 49152)
last unloaded kext at 397772241251490: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f9d7af000, size 32768)
loaded kexts:
com.apple.driver.Oxford_Semi 3.4.1
com.apple.filesystems.smbfs 2.0.2
com.apple.driver.AppleHWSensor 1.9.
panic(cpu 0 caller 0xffffff7f9d62ef7c): "GPU Panic: [<None>] 3 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff81373e9000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.5.26/src/AppleMuxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 0), Frame : Return Address
0xffffff8125b3b140 : 0xffffff801b222fa9
0xffffff8125b3b1c0 : 0xffffff7f9d62ef7c
0xffffff8125b3b290 : 0xffffff7f9bd05e7b
0xffffff8125b3b350 : 0xffffff7f9bdcf46a
0xffffff8125b3b390 : 0xffffff7f9bdcf4da
0xffffff8125b3b400 : 0xffffff7f9c04e056
0xffffff8125b3b530 : 0xffffff7f9bdf2b09
0xffffff8125b3b550 : 0xffffff7f9bd0c8cd
0xffffff8125b3b600 : 0xffffff7f9bd0a3d8
0xffffff8125b3b800 : 0xffffff7f9bd0b356
0xffffff8125b3b8e0 : 0xffffff7f9cc479c2
0xffffff8125b3b920 : 0xffffff7f9cc5737f
0xffffff8125b3b940 : 0xffffff7f9cc8533b
0xffffff8125b3b980 : 0xffffff7f9cc8539b
0xffffff8125b3b9c0 : 0xffffff7f9cc5ce15
0xffffff8125b3ba10 : 0xffffff7f9cc28b5e
0xffffff8125b3baa0 : 0xffffff7f9cc24ae7
0xffffff8125b3bad0 : 0xffffff7f9cc22636
0xffffff8125b3bb00 : 0xffffff801b6ce0a3
0xffffff8125b3bb90 : 0xffffff801b6cff9f
0xffffff8125b3bbf0 : 0xffffff801b6cdabf
0xffffff8125b3bd40 : 0xffffff801b2b66a8
0xffffff8125b3be50 : 0xffffff801b226bf1
0xffffff8125b3be80 : 0xffffff801b2139f5
0xffffff8125b3bef0 : 0xffffff801b21e043
0xffffff8125b3bf70 : 0xffffff801b2c989d
0xffffff8125b3bfb0 : 0xffffff801b2f3c76
Kernel Extensions in backtrace:
com.apple.driver.AppleMuxControl(3.5.26)[B67CD59F-1344-37BC-8A9A-46D6D3DCA13D]@0xffffff7f9d620000->0xffffff7f9d633fff
dependency: com.apple.driver.AppleGraphicsControl(3.5.26)[C0F9A79F-167E-3A68-873C-5CE17B97FB11]@0xffffff7f9d618000
dependency: com.apple.iokit.IOACPIFamily(1.4)[045D5D6F-AD1E-36DB-A249-A346E2B48E54]@0xffffff7f9bb6d000
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff7f9b8be000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0xffffff7f9bc63000
dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[E04639C5-D734-3AB3-A682-FE66694C6653]@0xffffff7f9d61b000
com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[6EB3FF52-A4F6-3496-AE9C-D89B00FDE504]@0xffffff7f9bcb6000->0xffffff7f9bf1efff
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff7f9b8be000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[B93BBFC9-9ED5-3DDD-8CED-5EDA081BB997]@0xffffff7f9bca6000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0xffffff7f9bc63000
com.apple.nvidia.classic.NVDANV50HalTesla(8.2.4)[B0E6AAA7-E970-3D81-8B43-145D56A3A4AC]@0xffffff7f9bf29000->0xffffff7f9c1d2fff
dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[6EB3FF52-A4F6-3496-AE9C-D89B00FDE504]@0xffffff7f9bcb6000
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff7f9b8be000
com.apple.GeForceTesla(8.2.4)[24ED915E-02F3-3A31-8502-6AA41FFCA420]@0xffffff7f9cc07000->0xffffff7f9ccd1fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[244D4E48-78E6-3369-8D76-285C66EF9BF4]@0xffffff7f9b8be000
dependency: com.apple.iokit.IONDRVSupport(2.4.1)[B93BBFC9-9ED5-3DDD-8CED-5EDA081BB997]@0xffffff7f9bca6000
dependency: com.apple.iokit.IOGraphicsFamily(2.4.1)[B889D3AB-CCC0-3FCD-A83E-D2E3E4CB537B]@0xffffff7f9bc63000
dependency: com.apple.nvidia.classic.NVDAResmanTesla(8.2.4)[6EB3FF52-A4F6-3496-AE9C-D89B00FDE504]@0xffffff7f9bcb6000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
13D65
Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
Kernel slide: 0x000000001b000000
Kernel text base: 0xffffff801b200000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 397836666227109
last loaded kext at 397631734858683: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f9d7af000, size 49152)
last unloaded kext at 397772241251490: com.apple.driver.AppleIntelMCEReporter 104 (addr 0xffffff7f9d7af000, size 32768)
loaded kexts:
com.apple.driver.Oxford_Semi 3.4.1
com.apple.filesystems.smbfs 2.0.2
com.apple.driver.AppleHWSensor 1.9.
where/how do i find the read/access error?
yes, like poster above says, does this workaround allow you to use fcp x? how is performance in fcp x with this? thanks.
P.S. -- do you think the "latent defect" are bad GDDR5 VRAMS for the GT330M? i'm asking b/c of the workaround you mention making the dGPU use the main RAM. is this what the workaround is doing?
Last edited:
No, it would be for 4gb systems. I have 8GB RAM and have no issues. And you can try. If it doesnt work, you can change the setting back. You arent really going to damage anything in trying. Also, my graphics switching still works fine.
----------
I use FCPX and PPro CC and AE without any problems. Obviously, performance wise, it's not my mac pro, but it is still pretty good.
Aperture is completely out. Final Cut went to the "X" version which started out to be wretched. People were beyond frustrated with Apple's decisions on this product. Various other pro apps have had hiccups and over due upgrades. As I said, nothing new here for Apple.
so, your MBP got its logic board replaced and you still had the KP issue? and this is the only solution? is it bad VRAM? so the VRAM's on my MBP will no longer be used if i do this? why do you think this method is working? sorry if i am asking too many questions. just wanna try to understand what the thing does before i try to do it.
thanks.
PS--on your post above, you mention random KP's. My MBP has that, too. But, when i use FCP X, the KP is not random but imminent. i mentioned above how adding transitions to video clips triggered the KP for me. and then after my computer rebooted again, i didn't add transitions and laid down just clips up to 3:30m or so and i exported w/o a problem. so, i guess my question is if you could KP your MBP using FCP X before this workaround?
I agree the feedback system for Apple is poor, limited to 800 characters, this is simply unacceptable for a company as diverse as Apple.
I have tried through various forums to get a contact within Apple, as there are aspects that I feel are not being addressed, almost reaching a point of being forgotten, or swept under the carpet.
Please Apple update and modernize your feedback pages!!!
I thought it was only me having random kernal panics and pauses... Good to know I am not alone in this, would you happen to know if there is a support group for "Sufferers and Survivors of Apple Kernal Panics.."
I have tried through various forums to get a contact within Apple, as there are aspects that I feel are not being addressed, almost reaching a point of being forgotten, or swept under the carpet.
Please Apple update and modernize your feedback pages!!!
I thought it was only me having random kernal panics and pauses... Good to know I am not alone in this, would you happen to know if there is a support group for "Sufferers and Survivors of Apple Kernal Panics.."
I don't think it's bad VRAM, it is more likely OS X (Rather, the new versions) not being efficiently coded to include.... "old equipment" I never had a problem under snow leopard, but under Mavericks, I had plenty of restarts. I tested that theory by running various programs under 10.6.8 and didn't have a single crash, but when I slapped my 10.9 ssd in, boom, random restarts. So, I came across this fix, it's worked a treat, I don't have any problems or performance issues. So I've not really come up with a detailed analysis. FCP 7 and FCP X were fine under 10.6.8, under 10.9, they would occasionally restart. But after the fix... I have a rock solid machine with no random restarts.