Exporting FCPXML Crashes FCP 12.0

Question

Level 6

13,474 points

Exporting FCPXML Crashes FCP 12.0

Exporting FCPXML Crashes FCP 12.0. I've reported to Apple and to the developer of ScriptStar. Deleting prefs allows me to export and FCPXML once, then it starts to crash again. And I can't keep resetting my Settings and everything all over again. Seems more gets reset now with FCP 12 when deleting prefs than used to. Just posting in case others may have this issue, or similar. Just posting to inform, not ask any questions, as there's no questions to ask at this point. And yes, I know many of you don't have this issue. Just saying, FCP 12 has a number of bugs, we need a bug fix soon.

Posted on Feb 20, 2026 6:36 PM

Reply

Answer 1

Top-ranking reply

BenB Author

Level 6

13,474 points

Feb 23, 2026 6:30 AM in response to BenB

I tested some other (older, pre-12) projects, and they all export just fine. From the same TV show, same title templates, same fonts, etc. And some from other shows I still produce. They all exported fine.

This particular episode is very long, hour and a half. It was edited in its entirety, then duplicated into two other projects. Each having either the first half or second half deleted and then conformed to the "two part" format. Seems those duplicates that were edited had issues.

Copied contents of those to two fresh, new projects, they export fine.

I did find two other more recent projects that crash when exporting FCPXML. Did the same, created new projects, copy/paste content to new projects, the export FCPXML just fine.

So, same footage, same title templates, same fonts, same everything, new project, works fine. I question the stability of an FCP project now in version 12. Especially now seeing a post for crashing when using beat detection.

Reply

Answer 2

joema

Level 4

1,395 points

Feb 23, 2026 7:31 AM in response to BenB

Ben, I can't remember your configuration. Are any of those libraries on a NAS?

Over the years we've seen a few cases of apparently damaged project timelines that work OK if the contents are copied to a new project. It's fairly rare except in cases like a NAS or ExFAT drives that disconnect during editing.

If you have a project where FCP crashes when exporting FCPXML, can you try selecting the project icon and doing OPT+Clip>Verify and Repair Project? Does that show any problems?

There were definitely a lot of code changes between 11.2 and 12.0. In general, the more changes, the greater the chance of bugs. The framework that handles XML is called "Interchange." It had several additional methods added. If you send me your crash file I could possibly analyze that to determine if the crash was related to those source code changes.

Overall the data and project integrity of FCP is very good, and far better than Resolve. Even during normal operation, FCP is constantly running various integrity checks. In some cases, it will automatically use the SQLite PRAGMA integrity_check command to verify database consistency. But it's not perfect.

Reply

Answer 3

joema

Level 4

1,395 points

Feb 21, 2026 6:33 AM in response to BenB

Ben, if you can send me a couple of your FCP crash logs, I'll study them. Using the Console app select Crash Reports in the left sidebar, then for each crash, do right-click and "Reveal in Finder." They will each be an .ips file.

Just upload 2 or 3 of those to the below link.

https://we.tl/r-bAQQU51kIi

Reply

Answer 4

Feb 21, 2026 1:44 AM in response to BenB

I have not tried this in FCP 12 yet, and I can see how awful this is.

As a stopgap solution one might consider this: make a copy of a known good plist file after you have it set exactly as wanted; instead of the usual command and option start that deletes the corrupted plist, run a tiny script that copies the good version over the bad one. Again, this is only meant to lessen the hassle of resetting preferences, as only Apple can fix the bugs.

Reply