FCP X crashes on large jobs

[Mathieu Ghekiere]

I used it on a project with about 750GB of Prores material, spread over 2500 clips in 3 Events. Not long form though, a half hour of edited material.

It could Be slow at times but I was editing on a 8GB RAM 13″ MBP from a 5400rpm FireWire800 drive.
Can’t Really remember it being so unstable, although the app had its moments.

I’m working now at work on a retina MBP and Pegasus R6 raids. Getting great performance.

[Oliver Peters]

[Mathieu Ghekiere] “I used it on a project with about 750GB of Prores material, spread over 2500 clips in 3 Events. Not long form though, a half hour of edited material. “

I’m not sure why on this one. I’m not even editing yet. Just organizing with keyword collections and selects assemblies, which I’m doing as compound clips in the event. However, I had crashes without any sequences at all. Typically 1 crash each day, a couple today. Maybe it will settle down from now on.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[T. Payton]

Oliver,

I haven’t specifically had problems with large projects but I typically see the following causing crashing:

Corrupted Media
FCP X is rather sensitive to bad clips. Video, stills (PDFs especially), a few random PSDs, MP3s and fonts. FCP X hits one of those and crashing happens. Isolating the problem is tricky, but is a good step to take.

Corrupted Prefs
I trash my prefs when crashing begins because crashing seems to lead to more crashing.

Third-Party Plugins & Tools
I’ve also had Third-Party plugins and A/V output (BlackMagic, AJA, Matrox) cause trouble. Sometimes in the Crash report the first few lines indicate what the app was doing when it crashed and I have seen third party tools specifically mentioned in the crash report.

Render Files (not just the timeline ones)
Another area that seems to cause trouble are the render files FCP X creates. Not just for a timeline, but an event will have caches for waveforms and thumbnails. You might try trashing “Peaks Data” and “Thumbnail Media” for the event in the “Render Files” folder. Or just trash the whole “Render Files” folder for the event, then restart and see if that helps.

Hope this helps.

——
T. Payton
OneCreative, Albuquerque

[Patrice Freymond]

Pre 10.0.6 I did have similar crashes in similar circumstances.

It seems that there was a “speed limit” to the skimming I could do in the browser. That was the cause of most crashes and those crashes were without consequences.

Event was roughly 800 GB of mixed media and I had, by the end, about 15 versions of the project, a half hour doc. with little effects or retimings.

I haven’t had a project that big since so i can’t compare with 10.0.7

[Jeremy Garchow]

Another vote for teaching peaks data and event render files.

It will take a while to rebuild though.

[Jeremy Garchow]

“Teaching” should have been trashing.

I blame society.

[Paul Jay]

Would be interesting to see if these type of projects also crash on AVX foundation supported iMacs with Ivy and Sandy bridge chips.

[Oliver Peters]

[Paul Jay] “AVX foundation supported iMacs”

Do you mean AV Foundation? AVX is Avid’s plug-in architecture. AV Foundation is the Apple media architecture that replaces QuickTime. It’s really an OS function and has nothing to do with the processor AFAIK. That’s what FCP X has been using since the beginning on all machines.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Chris Harlan]

[Jeremy Garchow] “”Teaching” should have been trashing.

I blame society.
“

So, this is another trashable moment?

[Jim Giberti]

Yes to graphic files and PSDs.
FCPX still seems to have real problems with basic graphics (imported).
I’m just finishing a short film and it wasn’t till the end when bringing in a few PSDs and Stills that it had issues.

One other issue that crashed my system twice during this project was I simply clicked the button at the bottom of the timeline to resize the clips in it.