You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

📢 Newsroom Update

Final Cut Pro 11 begins a new chapter for video editing on Mac. Learn more >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Final cut keeps crashing on export. Urgent help needed!

I tried deleting preferences. Tried restarting. Played the movie in Final Cut and there were no issues. I see no problematic clips with bright red exclamation point. When I try to export, it says "preparing to share" with a progress bar, then crashes. Tried a few different formats, no luck. Mac Studio, OS 12.6.3, FCPX 10.6.5

Mac Studio (2022)

Posted on Mar 10, 2023 2:14 PM

Reply
Question marked as Top-ranking reply

Posted on Mar 11, 2023 2:33 AM

Give the Verify Project option a shot.

Make the Project ACTIVE.

Hold the Option Key, then click the Clip Tab in the menu.

Verify and Repair Project feature will appear.

You may get some info as to what is wrong:



Al

12 replies

Mar 11, 2023 1:35 PM in response to terryb

Shame this forum only lets you hit "helpful" twice. Getting warmer. Pasting into a new project didn't help. After deleting all effects, it did export.


It'd be great if we could get a list of plugins used in a project along with timestamps. Does such a thing exist? Or some other efficient way to find a problematic plugin in a large project?


Maybe I should try rendering the whole thing first? I have background rendering off.

Mar 10, 2023 3:41 PM in response to jacksonsg

How much free space on the drive that you're exporting to? You need a minimum of 15%-20% free.


If you have plenty of space, maybe the cache is corrupt? Or the library is corrupt. Or a piece of media is corrupt.


Select the library in the browser and choose File->Delete Generated Library Files... Choose All Render files.

Manage render files in Final Cut Pro - Apple Support  Any change to the export behavior?


Create a new library and import one of the clips used, then create a simple project and try to export. Does that work?


Post a report from https://etrecheck.com using the "Additional text" button below in your reply.

Mar 11, 2023 3:02 PM in response to jacksonsg

One way to see all applied effects is to select all your clips, then choose Clip>Show Video Animation or Control-v. Scroll through the timeline and see what effects are applied and pick one that could be a suspect (probably a 3rd party effect) and disable it in the clips in the first half of the timeline. Try an export of the first half of the timeline (set in and out points).



If it fails, uncheck another one and try again until you find the culprit.

Mar 11, 2023 2:06 AM in response to terryb

Some more info... I have plenty space. Also tried exporting to an external, no luck. Deleted render files, no luck. Opened a different, much smaller and simpler project and was able to export fine. So it seems the issue is with this project. Anything I should look for in or around the project? Since I'm not getting any exclamation marks anywhere or blank clips or error messages.

Mar 11, 2023 12:07 PM in response to jacksonsg

Open the problematic project and select all, then copy. Create a new project with the same project properties and paste. See if this new project will export. Sometimes there's subtle project corruption that can be fixed by pasting it into a new, empty project.


If this new project also crashes, select all in the new project and remove all effects with Edit > Remove Effects (or press Option-Command-X). See if it exports. If it does there's a clue.


Report back with your findings.

Mar 11, 2023 9:28 PM in response to terryb

FINALLY was able to export this thing from within FCPX. Not sure why it works now, but here are more things I did:


I put Neatvideo's noise reduction plugin on a clip in a tiny project that normally takes half a minute to export. It took a half hour. So I figured that was the culprit and disabled all instances in the big project. Didn't work.


Disabled Filmconvert Nitrate. Didn't work.


Replaced a lone instance of the built-in noise reduction with Neatvideo. Didn't work.


Then I did a few things together that worked. (I should've tested after each of these, sorry!) Deleted a few titles, out of dozens, that were already disabled. Deleted a few adjustment layers, out of dozens, copying their lone hue/sat curves to the clips themselves. And "finalized audition" on the few clips that had them. Export then worked. And of course I might've done something else without realizing it.


Fwiw, exporting in Compressor worked throughout this ordeal, though it took nearly a half hour to do the small project with Neatvideo in it. The big project takes maybe 10 minutes? Can't explain it.

Mar 12, 2023 9:29 AM in response to jacksonsg

Glad you got the project to export. So were you able to add back all the effects? Neat Video can be an extremely CPU intensive effect.


Maybe someone else with a better understanding of what happens under the hood can chime in with theories about why an export could fail in FCP but work by sending to Compressor.

Final cut keeps crashing on export. Urgent help needed!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.