This is exactly the same problem I have. It crashes while rendering, then have to force quit FCPX 10.0.6 then suddently the OS becomes unresponsive and I have to whole computer crashes (MBP17" 10.7.5). Everything was working perfectly fine until I upgraded. So, I don't think there's a corrupt vidoe file or anything wrong with my computer. It was working beautifully before. I'm tempted to uninstall and reinstall. How to do that cleanly?
BTW, my footage is not the problem. I unhooked my external scrtch drive and had the same problem on the main drive with brand new footage I downloaded and uploaded and converted to optimized media and then did some effects and waited to render. Help!!
I have finally fixed it (at least I've been working on it for half an hour now )
what I did was:
go to User/movies/final cut events/
and I deleted (moved somewhere else) the folders: "Effect Browser Thumbnails" and "Render FIles"
and it's working now
I wonder what those folders are for and if FCPX will generate them again...
I had the exact same experience as Endoman99 and it was not due to corrupt files or footage and not computer hardware. Strangely enough the App Store informed me that FCPX needed upgrading again to the same version, 10.0.6.
At first I ignored it as a glitch, it's not first time it's happened to be honest. Howe er in my desperation and thinking this coul t get worse I did indeed press upgrade and now everything works.
FCPX had definitely upgraded the first time, I checked the version. I can only assume it installed wrong.
All other methods to fix the problem previous to this eg uninstall and re install the software, trashing all render files, repairing permissions and disk came to nothing.
This was my experience and it seems others share it.
Tom Wolsky wrote:
"uninstall and re install the software"
This puts in a completely fresh copy of the new version of the software. I cannot see how this is any different from running the update again. I suspect you repeatedly were getting bad downloads, one of the downsides of web delivery.
I agree that installing a completely fresh copy or upgrading again should be the same. However one worked the other didn't. As I said, it is strange.
I did think that software from the App Store, particularly Apple software, was safe to download. Am I being naive? Or can it become corrupted during the download?
After all, we have no other option with this upgrade.
I can only open the application once per boot-up. If I close the application to "manage my folders" to work on one project at a time and open a different project. I get the message:
The storage location "user" on this computer is already in use by "user" on "My-Mac-Pro". To access the location, quit Final Cut Pro on "My-Mac-Pro" or remove the location.
I only have one user on my computer, me. I have to restart my computer to reset this error code to open FCPX. Annoying! This is what I really dislike about this software. I just want to manage my client projects in my own local folders without it serching every one of my harddrives.
jeff Leyshon 66 wrote:
...I did think that software from the App Store, particularly Apple software, was safe to download. Am I being naive? Or can it become corrupted during the download?
After all, we have no other option with this upgrade.
Hmm, no.. and if you are running on 10.7+ the app should be signed and checked. If just one bit is wrong, it should not open..
Having the same problem here. Worked fine until rendering. I was ok with it slowing down quite a lot when setting up 3rd party plugins settings for the colour grade (Magic Bullet Looks and Beauty Box), but it was still useable. Once done I set it to render.
Only made it a 1/4 of the way thru, FCPX had quit in the morning.
Set it to continue. Came back, locked in screen saver.
Loading up the whole thing is unresponsive, beach balls etc. If I stop the render (eventually it lets me) then it comes back to life. Including being reasonably ok with render frames as I scrub including the plugins. Wish there was an easy way to temporarily not render plugins on playback just so you can view and edit still.
Anyway. Am trying some things on this post. App Store was still saying to update 10.0.6 because I'd copied 10.0.06 from my macbook pro to save on downloads. So am trying that. Can't imagine why that would be a problem as it's been working fine until rendering.
Next will be trying to delete all my render files and thumbnails as above - I think this is a good idea. I'm also getting that weird black frame in some renders that other people have noticed in the past in earlier versions. Shame.
I wasn't really using FCPX before 10.0.6 as I shoot Red Epic. So yes, I'm using all 5K R3D's. It's worked amazingly up to now. I'm on 10.8.2, I have a 6 core and 64GB Ram with an 512GB SSD and 12TB RAID all running at 400/600MB/sec respectively.
So no issues there. All hardware tested ok and running great (I did have a bad memory module before causing kernel panics, but now have replaced and all is perfect - except now renders in FCPX)
Oh and I also have it causing Safari to be unusable over here. I KNOW that applications aren't supposed to mess with other applications when they crash, but for whatever reason, Safari didn't work properly once FCPX had slowed/quit/done whatever it's doing to itself/the system.
Even when FCPX wasn't rendering anymore (after it had given up) and Activity Monitor no longer showed excessive CPU usage, the whole system was unresponsive including Safari. I had to restart to get functionality back.
Arguing with people's experience like (FCPX can't cause Safari to do that) is silly - something is going on that is causing some common problems when rendering in FCPX.
I have since read on this post (hadn't read it all before) that MB Looks is a potential problem but others haven't been using ANY plugins so I'm inclined to believe it's FCPX itself. 10.0.6 was a big update as someone said, so there are bound to be some problems. Just hope Apple can fix it up.
I don't think it's bad clips by the way - if it was working for you in 10.0.5, logically it's not bad clips. And it's also silly to keep suggesting that.
Was wondering whether to get rid of all MP3 files out of the project though...
Re-installing from app store (and deleting as per Apple's instructions) has done the trick. So far anyway. I have NOT tried to finish the rest of my renders yet, just a couple here and there as I was changing things. Whole thing is a bit snappier now and hasn't slowed down as much, even attempted to play the sequence (sorry, project) in areas that weren't rendered and didn't do too bad a job! (even 2 or 3 seconds I got a frame and sound continued to play).
Will post either way once I try finishing off all the rest of the renders.
Free RAM has nothing to do with it. I have 64GB in my system, Final Cut is only using about 7gb even whilst doing the huge renders, Safari about 100 or 200MB.
48GB free. It's a work machine so I don't run much else, everything else I do on my macbook pro.
For a complicated project, still getting nowhere near any sort of physical limit on RAM.
It's going a bit better now, it's chugging away on the render, at 61% (after a few hours) and is not beach balling or quitting anymore.
mp3's clearly aren't a factor therefore either.
Something else was going on that was causing FCPX to render the system unresponsive. The reinstall has solved that for now. We'll see how we go ongoing.
Many thanks Tom.
There it goes again. At 63%, tried to scroll to the right in the timeline (I had thumbnails off and just viewing the clips without any pictures to save it having to render all those and interrupting the main render), and now it won't switch to activity monitor and is beachballing constantly. 49GB of RAM FREE, the CPU has cycled down, the fan has slowed, nothing is happening. It's just caused an entire system to come to a halt.
Similar amount of effects and stuff in FCP7 would be done by now. Granted everything else FCPX has been a huge time saver and it's wonderful I can edit natively with Red footage. But this is a killer.