FCP quit unexpectedly…won’t open project

[Loanne Do]

Although this post is 2 years old, I’d thought I’d contribute because I’m one of those people that update software versions VERY LATE in the game (to avoid bugs).

I recently updated to FCP v.6 and most of my files updated normally to v.6 but my bigger projects (about 130 MB in size) refuse to load and just QUITS during the updating process. I tried numerous times and tried some of the tricks on this site: which didn’t work.

So I did a very interesting thing:

I just clicked “update” and although under the Force Quit window I see the message in red “Final Cut (not responding), I ignored it and went on to do my other business online.

After ignoring the message for about 10-15 minutes: the whole file loaded correctly!

I think that in my case, the file was not corrupt but that it was just VERY LARGE so it took awhile. My project had a million fine cuts in it (for a 2 hour project).

Summary: so although some projects “hang” and seem to crash the program, it could be that the software is taking longer ot read it.

Hope this helps.

my hardware specs: OS 10.5.7/ Leopard/ Macbook Pro/ 4 GB ram

[Mahala Morris]

I think you will just have to redo the corrupted file again. mine seems to happen quite a lot when using motion and final cut together…does anyone know how this can be avoided in future or why it actually happens? its incredibly time consuming.
Mala

[Dylan Haley]

You saved my ass. I love you! I think I lost a few years off my life. My client upped the deadline and I promised a deliverable product and then couldn’t open the project. Your response is the only one that saved me. If you are ever in Santa Barbara, the beer is on me. Seriously, thank you.

[Patrick Sheehan]

very glad to hear that it helped you out… turns out that desperation is the sister of invention