-
FCPX crashes immediately when selecting share master file
Hi,
I am at the end of my project and need to export master files. I am working HD 25p. When I click share/master file FCPX crashes immediately. I don’t even get to the export dialogue box. I have a simple 3 min sequence of shots with a few titles and no effects at the moment.
I have already tried trashing prefs, reinstalling FCPX, deleting 3ivx component and exporting a simple alternate sequence with unrelated media.
I have used FCP7 for years but this is my first project with FCPX and the first time I have tried to export master files from it.
Any help would be greatly appreciated as I have to deliver the files on Wednesday.
Bex
Running OSX 10.7.5 and FCPX 10.0.7
-
24 Replies
-
Did the other sequence crash as well or is it only this one?
-
All of them crashed
-
I’ve had this issue intermittently. Try this:
Delete both the event and project render files. Then duplicate the project file. Select that to export, after letting it render the whole timeline first.
Sometimes a corrupt render file can gum up the works.
Try this too: select another formate to see if it’s just the master file format that is giving you problems. Or changes the specs in the settings (e.g., 444 not 222) etc. to see if that helps.
Officially, if you are still having issues, Apple will tell you to delete FCPX and then re-install. But that’s a pain. I’ve had this problem twice and was able to resolve with out reinstalling.
FWIW, most of the time, FCPX works really well for us.
Good luck.
-
Thanks so much for your reply. I managed to fix it about an hour ago by deleting some quicktime components that were conflicting with FCPX. Trial and error, but I got there in the end!
All the best,
Becky
-
Great! It can be very frustrating.
I forgot to mention I wholeheartedly recommend the maintenance pack from Digital Rebellion. The crash log analyzer is very useful and has helped me identify similar conflicts in the past.
Also, the Pro Versioner utility is a must with FCPX (which doesn’t have an autosave vault–it updates the same backup every 15 minutes). Another must: Event Manager.
That said, I can’t imagine going back to 7.
-
[Rebecca Way] ” managed to fix it about an hour ago by deleting some quicktime components that were conflicting with FCPX.”
Do you know which ones? That’s good info.
Jeremy
-
Thanks for the tips! I’m still using both 7 and X, so it’s great to get some advice.
Cheers,
Becky
-
kind of went a bit mad a deleted 3 or 4 as I was getting desperate, so i’m not sure which one yet. I have to repeat the process on my Mac Pro, so will be a bit more controlled and report back!
-
[Rebecca Way] “kind of went a bit mad a deleted 3 or 4 as I was getting desperate, so i’m not sure which one yet.”
Cool.
It’s the first I’ve heard of a QT Component interfering with X.
Thanks for any details.
Jeremy
-
[Jeremy Garchow] ”
It’s the first I’ve heard of a QT Component interfering with X.”I’ve had problems specifically with Perian and ScreenFlow, but never with FCPX. I keep Perian off now and just turn it on when I really need it and then re-boot. Before doing that, I was getting a lot of the “blue screen of death” that would happen randomly.
Dave
Reply to this Discussion! Login or Sign Up