Q: The Final Cut Pro X CRASH Thread

Bit of a crash then! Not had FCPX for very long, but every time I have tried to import some video files it crashes, regardless of the size and type of file. Luckily I still has the files on my camera (a Panasonic HS300), and they imported directly from the camera almost instantaneously. So thats one reason for crashing solved, still waiting for a solution to all the others....

Tom Wolksy helped me in a similar situation--I think. When importing, be sure you are optimizing all media. If you're working in high res, and want to be able to work the timeline effectively without lots of RAM, also select proxy on import. Once imports are complete, go to preferences and select proxy playback until you're ready to export at full res. Hope this helps!

Oh, the other ting is this. Get Event Manager X2 to select only events and project files you need for the particular job you're working on. http://assistedediting.intelligentassistance.com/EventManagerX/

If you're still having crashes, throw away preferences and reboot. This is handy for that: Preference Manager:

http://www.digitalrebellion.com/prefman/

I's also a big fan of CleanMyMac http://macpaw.com/  for regular maintenance. Also, defrag, etc.

Good luck!

Thanks. Looks like its another one of those situations where you need to know what you are doing before you do it! I have tried switching to proxy playback once I have imported to try and speed things up, but all the footage disappears. I'll remember for the next project!

There is a way to make proxies of the events once they're already imported. Look in the help manual. I think you select them in the bin and right click. But check it. Happy editing!

This worked, thanks. Would give you some points but the option to hasn't appeared!

Why not report the crash? Well, I did it around 20 times. This is to report Apple that there is a problem, but not to get immediate help. Sometimes people in the forum find a workaround for a bug long before Apple analyses the issue.

In my case, there has been no problem for months. Now, I cannot even lauch FCPX. Apparently, the application is OK.

It is really a shame that these solutions aren't ingrained with in the program. Especially when they are tedious steps as above that need to be repeated over and over again. Isn't that what computers are for? and further more isn't it more Mac like to have all these things streamlined for you?

In any case, my FCPX also crashed on startup like 7 or 8 consecutive times, likewise, after a couple of months of smooth editing.

My suspected culprit: I have the hidden files in my OS non-hidden. I seem to recall there being some hidden files visible in the trash. I deleted them as I was emptying the trash....is this it?

Does FCPX make temp files in the trash?

Whatever the case may be - the fact that I had to trash my project and me loosing a days of work - is completely unacceptable.

My last chance is the next major update. Ill hang in there until the next major update and if things dont smooth out then. I hope that I was loyal enough....till then which I honestly hope doesn't happen. It would be great it Apple could turn this thing around....

I have been editting a very complex video with FCPX and Snow leopard, and no crashing at all! Lots of effects, text generators etc. I do also have FCP7 installed on the same volume....But at home on Lion, this would be crashing all the time. Not really sure what the deal is, but that my 2 cents, stick with Snow Loepard.

I have an ill-informed theory as to why FCPX behaves much better under Snow Leopard. The auto-save function baked into Lion uses the Core Data layer within the OS. Core Data takes care of both the undo and auto-save function and marshalls data to one of several persistence layers. FCPX uses the sqlite persistence mechanism, which you can explore if you copy and *.fcpproject and *.fcpevent files and open them with an sqlite browser. This layer also manages the coherency between the state of objects in memory with its persistent counterparts on disk. Perhaps the memory leak in Lion is due to "unhealthy" relationships between the RAM-resident objects and their representation in sqlite.

Snow Leopard; however, does not have this auto-save functionality built-in, so the developers must have had to provide the FCPX auto-save functionality using a different method, one that is apparently much more reliable than they way they are doing it in Lion.

I'm sure this doesn't help anyone with their specific FCPX issues, but I offer it as a software developer and video editor trying to guess as to what could be causing the gnashing of teeth  due to these issues. I said ill-informed in my first sentence, because I'm not a Mac developer by any stretch of the imagination.

As soon as I start seeing mischief with FCPX in my project, I'll seriously consider downgrading to Snow Leopard from Lion, no matter what the cause, as long as late-2011 model MBPs work under Snow Leopard.

It does not generate any files in the trash. It just fades away.

FCPX continues crashing after the last step in launching. I have checked all my drives, repaired the preferences, started the machine many times, and reinstalled the program. I have also disabled Resume.

If I launch FCPX as a new user without any assets, it will start properly.

bill33 wrote:

 

Whatever the case may be - the fact that I had to trash my project and me loosing a days of work - is completely unacceptable.

 

My last chance is the next major update. Ill hang in there until the next major update and if things dont smooth out then. I hope that I was loyal enough....till then which I honestly hope doesn't happen. It would be great it Apple could turn this thing around....

It's not about being "loyal enough"... that's merely a way to let Apple off the hook. Software should not be released in this condition, you are being taken advantage of.. you are a "paying" beta tester for Apple. Unless you complain and complain loudly enough you will continue to be taken advantage of.

Treat Apple like you would any other company that took advantage of you, if you don't it will get worse, not better.

You have a corrupt Event/Project or clip within an Event/Project. Remove all Events & Projects from the Events and Project folders and place them back 1 by 1 until you see the crash again. That will be the problem child.

hope that helps

best

Brooklyntreez

kirkilj

Sounds like some logical thinking. Please tell Apple.

I agree, and Apple shouldn't be let off the hook. I voted like I would with any other company, after I also lost work, time, and spent hours troubleshooting many issues, I ditched FCPx, purchased Premiere, and will using FCP 7 while I migrate all new projects to Premiere and After Effects. They really slapped everyone in the face on this fiasco, and I voiced my opinion and let them know how I felt. Luckily, Avid and Adobe are both there to make the fall from grace easy I'll check back in a few years, but my guess is by them I'll have ammassed a set of tools. plugins, and spent time and money on retraning everyone that moving back won't make any sense, even if I wanted to.