FCPX Export disapears no failed export notification

First, whenever there is a crash or the application behaves unexpectedly, you must delete its preferences. To delete preferences, hold down command and option while starting the application and click Delete Custom Settings. The application will start with default settings and open an “Untitled” library. Adjust the settings, reopen the library you were working, and see how it works now.

Also: there was no mention of your mac model, OS version, FCP version or what kind of media you are using.

And often problems are due to other stuff that is installed automatically may cause a conflict.

Please run Etrecheck and post its full report here.

Use the “additional text” button and paste the report into the text box.

FCP may be crashing due to an unhandled exception. Please run the MacOS Console app, click "Crash Reports" in the left sidebar, and look for FCP crash reports. For each one found, right-click>Reveal in Finder. Upload all of those to the below folder, and I will analyze them.

If none are found, look in the "retired" folder and see if any FCP crash files are there. They will usually have an .ips file extension.

https://we.tl/r-kHxPjDoriH

The only thing that jumps out from the report is the dreaded Google updater and keystone software. Follow https://chromeisbad.com for instructions to completely remove. After removal it's best to reinstall a fresh copy of FCP from the AppStore.

Are you using any plugins? What version are you on?

What I've done in the past is make a compound clip of my whole project. Then export to 4444 prores in parts, paying attention to where it's failing. I'd export whatever 5% of your total time is, then another 5%, then another 5%, then do it in 30s-1minute blocks if all is good.

if it keeps failing at a certain part, a hack is to make a cut on the frame it's failing on, or a bunch of different cuts over the top of the compound clip. You don't have to alter the clip, just cut over the compound clip with the blade tool. Don't know why this works but it does.

I think I used this tutorial to help me: https://www.youtube.com/watch?v=11wqQhrFbhQ&t=89s

then once you have everything in 4444 parts, put the exported versions in a timeline and export again.

i'm curious to hear about what effects you've used in this project.

I've been trying to navigate what causes my crashes and I think for me, it's these effects or a combination of them together or in the same timeline together.

ReelSmartMotionBlur

Dehancer Film Emulation

Some music video plugin that rotates in a circular movement

Hope this helps!

Wait!

How is that external drive formatted? I just noticed that the report does not mention.

If you are exporting or storing your library in an ExFAT drive then that might explain it...

Have you explored a Mac hardware failure?

If MacBooks get dust and debris buildup on the fans/vents overheating is a possibility.

Bad RAM is another culprit.

Al

Matthewgre wrote:

Hey i replies with all the information you requested still looking for answers. I tried using my inter hard drives instead of my external ssd and still failing to export.

I understand the frustration, but I also live in a different timezone, and, like all others here, try to help on my spare time...

As terryb already said, the keystone things by google are dreadful and should be removed.

Other than that, I don't see anything of note in the report.

If you clear preferences once again, make a new library, a new project add some clips and export, does it fail also?

I use Ryan Nangle too and I have endured this issue too.

Did you try exporting in 20s incriments?

How did this go?

Please show me a screenshot of the error message. The media may be corrupted, please share the media with WeTransfer for verification.

I’ve already sent the footage to someone else and they were able to get exports off with the clips.

No one in the community here has verified your media. Not sure if it's exportable.