- Posts: 85
- Thank you received: 2
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
FCPX crashing on every Master export
Any ideas? Never had a a probem exporting before. Thinking it might be one of the grading plugins so I'm going to remove them one by one and see if that helps!?!
Please Log in to join the conversation.
Not sure what to try next. Like I said, I've never not been able to export before so it's a bit of a head scratcher.
It exports to Vimeo but not to MXF or Prores. Very annoying. Tried ditching prefs and exporting without the grade and transferring the edit to a new library.
Please Log in to join the conversation.
Try deleting all render files, then select the entire timeline, render it with CTRL+R, then if rendered OK try exporting.
If it still crashes, right before you export, stop and restart FCPX, do nothing else then try to export.
If it still crashes, right before you export, restart macOS, then bring up FCPX and export.
You shouldn't have to do any of these, but I had an intermittent problem like this once and restarting FCPX before the export was a workaround. I don't remember the details but it finally quit happening all by itself.
Also verify you have plenty of extra hard disk space on the export drive, also on your system drive.
Please Log in to join the conversation.
Please Log in to join the conversation.
I've managed to get a prores 422 version out but it won't do MXF or anything higher than 422.
I'm going to transfer the project to my laptop and see if that makes any difference.
Please Log in to join the conversation.
Reinstall from scratch.
If you still have issues, it's hardware.
Take it to the nearest Apple retail store to have it diagnosed.
Please Log in to join the conversation.
What a massive load of (&£^$&£^%*&^%(£&$*&^
Please Log in to join the conversation.
BJansch wrote: Yes I think the graphics cards could be an issue, wish I knew how to check!...
I suggest following FCPX.guru's advice.
Also you can try running Apple Diagnostics, but it's not guaranteed to find all problems. If it finds a problem you definitely have a hardware issue. If it does not find a problem that is no "clean bill of health", it only means this simple test didn't find anything. However it's available and easy to run: support.apple.com/en-us/HT202731
At the Apple Store they have much more extensive diagnostics, including overnight or multi-day "bench diagnostics".
Please Log in to join the conversation.
BJansch wrote: Just loaded the Library onto my Macbook Pro, but it won't export from there either!
What a massive load of (&£^$&£^%*&^%(£&$*&^
What version of FCPX are you on, and what was the year, model and specs of the Mac where this library was created?
Can you post the thread stack of the crashing thread? Not the entire crash report, just the crashing thread stack.
Please Log in to join the conversation.
Please Log in to join the conversation.
There is no crash report because FCPX just hangs on the 'preparing media....' message
Please Log in to join the conversation.
If this is a managed library, and you copied that or connected an external hard drive to the MBP, the cache and render files are still there. Can you create a test library on a separate hard drive, copy just the project itself to that library, and answer "no" the dialog about copying render or proxy files? Then consolidate that library, disconnect the other drives and verify the test library will load. Then try to render the timeline with CTRL+R, if that works then try to export to the problem codec. This copies over just the media for the project, and leaves behind any render, scratch or proxy files.
It's important to determine is it crashing in the render phase or the encode phase. If the timeline is not fully rendered, then exporting does both render plus encode, so we don't know which phase it crashed in.
A variation of the above is progressively cut down the project and see at what point the export stops hanging. This could help isolate it to a single clip or at least a small collection of clips.
If that still fails evaluate what plugins you have, whether applied or not. If you are using FxFactory run that and update it. Some possible steps:
1) Open the FxFactory application.
2) Select the "Show FxPlug Plug-Ins in Finder" command under the "Actions” menu:
3) The Finder will open a folder on your system that contains all legacy plug-ins for Final Cut Pro and Motion.
4) Look at each file in the folder, especially for items like these:
- BCC9FxPlug_x64.fxplug
- Fc7FxPlugPro.fxplug
- FilmConvertPro2.fxplug
- Imagenomic/Portraiture.fxplug.bundle
- Imagenomic/RealEffects.fxplug.bundle
- mMorphCut.fxplug
- NeatVideo4.fxplug
- Separator.fxplug
- VTwinFx FCP 7.fxplug 2.8.3
- ZBCC 3D Objects.fxplug
Remove those that you no longer need/use, and contact the original vendor if you plan on continuing to use these plugins.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
- Jonathan Levin
-
- Offline
- Platinum Member
-
- Posts: 786
- Thank you received: 21
Please Log in to join the conversation.
BJansch wrote: I also tried exporting just a single clip with no grade or fx applied and that failed too.
OK, I know this is frustrating but those are all useful tests and help narrow down the problem. If you cannot export even a single clip with no fx, that makes further isolation easier.
E.g, can you import that same clip to a new fresh library, and does export still fail? If so that eliminates the possibility of corrupt data within your existing library. If it works there's something in your original library causing the problem.
If it fails with a freshly imported single clip in a test library, then examine the codec of that clip. Does if fail with any clip or just clips using that codec. If you import a non-MXF ProRes clip, or other various H264 clips, does it hang on export to MXF?
If no, we need to examine the original clip characteristics. If yes, the next step is evaluating what export codecs it hangs on. You previously said MXF and ProRes above 422. Is that consistent? Are you certain you've installed the latest Apple Pro Video Formats?
MXF is a container format that can include various codecs. As Jonathan said, does it hang when exporting to a ProRes 422 (or higher) master in a non-MXF format? If no can you then convert an exported ProRes master to MXF with Compressor? That's not a long term solution but might help isolate the problem area.
We previously had a report of a problem specific to interlaced MXF 25i material on 10.4. It wasn't a crash or hang but how interlacing was handled. Is your imported clip MXF 25i, or does the export hang with any clip which you export to MXF? www.fcp.co/fcp-forum/4-final-cut-pro-x-f...in-10-4?limitstart=0
Please Log in to join the conversation.
I created a custom MXF profile in compressor and then added that in FCPX. That has worked, using the AVC Ultra 100 setting.
Many thanks for all your help!
Please Log in to join the conversation.
- Irishrebel
-
- Offline
- New Member
-
- Posts: 2
- Thank you received: 0
I then came across this article! blog.frame.io/2016/09/13/recognize-fix-common-problems-fcpx/
Symptom #2... I downloaded that Preference Manager app, selected FCP in the menu, and trashed the preferences. Problem solved. That was it!
Please Log in to join the conversation.




