The Final Cut Pro X CRASH Thread

The thing that drives me crazy about this is that there are to many vairables that can cause crashing, to many things that "might work". That's beta testing. The thing I love about Apple is that it respects the creative flow meaning that you aren't spending alll your time trying to figure out why the product is not working. This is outside of the apple bussines model. If you told me I could buy a great new computer for a for or five grand that had the potential to edit fantastic videos with software for only a few hundre but I might find myself problem solving for weeks, losing sessions and hours of work I would have said no thank you. When people see an apple product, hardware or software they expect it to be functional. At least I do. I love my Mac Pro, my Ipad 2 my Iphone 4gs, mostly because of the functionality combined with the intelligent UI and the design element of al of the devices and software. This seems more like a third party application to me. To me its this simple, you buy it, you install it, you begin working on whatever project is at hand. That extra step of figuring out why its not working and why it keeps crashing and why you lost your edits....that's what beta testing is for an that should be completed prior to release. If its working for you great but if it works for 85% of the people is that sufficient?

Only for those 85% lol....I just want to create not problem solve... more ram, disable background rendering, throw away prefrences file. Switch to Avid...uggggg

The original codec is DVCPRO HD (1080i50), Linear PCM, Timecode.

But the problem was that within the compond clip There was a "ghost", blank audio clip in addition to the actual audio clip. The sound was record separately and consequently has to be sync'd as an audio file. Somehow another audio file got into the compound clip.

I then deleted the render files and hit "Render All" at which point just past the problem clip it crashed. I opened up again and starting from that location rendered clips individually to the end. No crashes.

Thanks for all the help. It is not what one would condsider intuitive.

And, I guess we're still waiting on a fix for the inabilityof the program to save text in the title templates athough I figured as long as I here I'll take a shot at rendering the titles separately. Just for fun :-P

I just started using FCP X this week, and while it hasn't crashed yet, I did lose my first night's work entirely. Everything was fine when I stopped working that night---no issues. But when I went to open it tonight, my project title/icon were visible, but there was absolutely NOTHING in the storyline--BLANK. I have restarted the computer, still nothing. Brand new iMac/Lion (last week).

Any suggestions?

Supposedly this known bug was fixed with the latest version of FCPX, at least that's what the forum pundits are saying.

Keep an eye on your UNDO menu entry, when that becomes unavailable FCPX is no longer auto-saving.

This bug has bitten many, many users.

Thanks for the reply. I just downloaded the latest version of FCP X this week-----it seems as if the bug still lives. I've always been an Apple lover. I can't afford this in my work, though. I downloaded the trial version of CS5.5 last night.

Did you lose work again in the new version?

I lost work just once--the only time I worked on a project in FCP x -- and yes, I was using the latest, updated version.

Wow, I'm in good company here.

I've started getting FCP crashes and freeze ups for the first time in 9 years of editing. I'm bummed. I was an early proponent of FCP X; I actually like the open timeline and don't give a **** about XML or multiclip. I started using FCP X because I thougth it'd be a good teaching tool. But after installing Lion over Snow Leopard, FCP X is crashing every 20 minutes or so. I haven't lost work, but the thought of not having a rock-solid editing environment is really making me apprehensive about continuing.

After a crash, I've found that I can relaunch FCP X and it will last for another half hour or so.

Specs:

OSX Lion 10.7.2

FCP X 10.0.1

Final Cut Studio 3 also installed (rock solid)

MacBook Pro 5,2

3.06GHz

NVIDIA GeForce 9600M GT 512MB

DVCPRO-HD codecs, rendering to ProRes

Fingers crossed that Apple will revive Final Cut Pro,

Andrew Burke

editor & educator

Your post caught my eye and while this may be nonsense, it's worth mentioning.

I was having crashes on my Mac Pro running Snow Leopard after migrating the FCPX app. from my MacBook Air which is running Lion.

I downloaded the trail version of FCPX directly onto my Mac Pro and haven't had a crash since. It sounds like you installed FCPX in Snow Leopard and then upgraded(?) to Lion so you might want to try a download of the trial version directly to Lion and see what happens.

Stranger things have happened.

I hear you Andrew. I want so much for FCPX to work well. I like the interface, the video scrubbing feature, and actually enjoy using it. I just get stuttering playback, I guess because of the background rendering (?). I'm using a 2011 15" Macbook Pro with top specs (best video card apple offers for that computer, 8gb of RAM, etc.), but still get the playback issue and spinning beachball lag. It does crash on occassion for me as well. I'm curious about something... Have you noticed that in demo videos (e.g., for training, effect plug-ins, etc.) FCPX seems to be responding nicely, and not acting like a beta program? I wonder if these people are using a Mac Pro, or an iMac for that matter. Seems like most people I've read online who are using the MacBook Pro are consistently experiencing these symptoms. I could be wrong. I'm holding on; I've purchased Premiere 5.5 and actually prefer FCPX, when it's working properly, but Apple's taking it's time to optimize this program!

Seems like the selling point of FCPX using all of the computer's resources (e.g., RAM, processing power, etc.) may be hindering things somehow. I notice, like others on this forum, that the RAM is hogged up, as a precurser to things acting funny in the program.

Anyway, all that to say, I feel your pain. I'm using this program now, even with its flaws, so that when Apple fixes its shortcomings, I'll have a good handle on how to use it (keyboard shortcuts and all).

Thanks Richard,

I think I will try trashing the App and re-downloading in Lion, as you suggested. That sounds reasonable. Here's to solid editing!

Thanks again,

Andrew

Thanks for your thoughts. Yes, isn't it fun to use when it's working well?

I think you're smart to get a handle of it now, while we all work out the kinks. Because, Apple has to further adjust FCP X to meet their customers needs.

Thanks,

Andrew

It's unfortunate becasue I do feel that this software is viable and I like it a lot.

I truly believe APPLE will solve this but like many have said "When - when will be the next update address the issue of frequent crashes".

I understand, like many, that any new software has glitches, bugs, freezes and crashes but it apperas from many therads that this occurs frequently for many people