My project is cursed...
...at least that's the only explanation I can think of for the trouble this project has been giving me.
I'm editing a feature film. I inherited the rough cut from another editor and was supposed to do the final cut and fine tuning.
For about 3 days everything went fine, then FCP started to crash. A lot. It got so bad that It would crash as soon as I opened the project file.
So I downloaded the demo version of FCS Maintenance Pack and the Crash Analyzer told me that the crashes were caused by the XDCAM footage. I personally think this is BS, since the original editor had been working with that very XDCAM footage for months without problems, but whatever. So I converted everything to ProRes 422 and relinked all the media.
This got rid of the crashing-on-opening thing, but the project still manages to bring FCP down in flames frequently.
The crashes usually happen when I come across specific clips in the timeline. Then the preview image starts to violently strobe and stutter, then the left half of the image turns green and then FCP crashes.
I can sometimes avoid the crash if I close the sequence and re-open it, but that doesn't always help.
Also, once the stuttering starts, the whole sequence will stutter, even if i jump to a part in the timeline that previously played back fine.
I investigated some of the stutter-inducing clips and they look completely normal. They play back fine with Quicktime, VLC and even when imported into a new, empty FCP project.
Besides, we edited a trailer from the same footage (though in a new project), which worked fine. Only the main project seems to be cursed.
Unfortunately my demo version of FCS Maintenance Pack expired by now, so the current error logs don't really tell me much. Several hours of googling didn't help either.
There is no XDCAM footage remaining in the project. The old and busted XDCAM footage is on an entirely different harddrive than the new ProRes hotness and opening the project with the XDCAM disk unmounted works fine, no media missing.
The project doesn't use any plugins, Motion stuff or exotic fonts.
I do not have any exotic video hardware, besides I don't really think this could be hardware related, since this is the only project giving me grief. Everything else works fine.
Things I tried so far: Trash preferences, check hard drives and permissions, reset P-RAM, completely removed and reinstalled FCP, copied and pasted the main sequence into a new project, exported the main sequence via XML and reimported it into a new project.
And now I'm out of ideas.
The only option left seems to be to start over from scratch, which i really really want to avoid.
Here are my hardware specs:
2 x 2.4 GHz Quad-Core Intel Xeon
16 GB 1066 MHz DDR3 RAM
2 x ATI Radeon HD 5770
And here is one of the most recent error logs:
I had a similar headache on a large documentary project. Like you I got fcs maintenance pack, I ended up
My issue was with a few jpegs in the sequence. Is the project file massive ? You did mention that you copied and pasted the sequence into a new project which should counter the big project file issue.
What about creating an offline version of the project file then relinking the media? Thats worked for me in the past.
Anyway I feel your pain by the end of my feature length doco edit I was ready to buy a copy of premiere.
The original project file is 208.7MB, the copy&pasted sequence is 36.3MB.
I'll try the offline thing next.
Is the copy and pasted sequence in a new project ? Id the project file contains too many sequences that can I think cause trouble.
Others have noted the XDCAM issues with FCP before. I've argued that this is common on all projects in FCP with large numbers of media items - so this can happen with P2, XDCam, or even converted ProRes files. Large project files also cause instability.
To me - this is a clear indication that FCP has a problem managing a lot of individual media items in a single project. Previously, when people imported tape reels, rather than 200 individual items, this was less of an issue.
I would suggest you cut your timeline up into individual sections, and manage the media as best you can into smaller blocks - 'reels' if you see what I mean, as individual projects. This should cure the problem.
Edit Out Ltd
FCP Editor/Trainer/System Consultant
EVS/VT Supervisor for live broadcast
RED camera transfer/post
Makes sort of sense, as the project is indeed using a massive amount of files (about 120 hours of footage iirc).
But it does not explain how the original editor was able to work with it (even using the original XDCAM footage) for several months even though his system was a couple of orders of magnitude inferior to mine.
Oh well. It's something I haven't tried yet, so I'll try it and see if it helps. :-)
Large Proj. files have been a prob w/ FCP for as long as I can remember.
Like suggested, try managing in smaller chunks.
You may a currupt file somewhere.
There are many that do not have problems working with FCP so keep in mind it is not just the APP. itself.
Video Atlanta LLC
Green clips inexactly and casually indicate some sort of corruption somewhere.
I'd buy FCS maintenance pack and run corrupt clip finder.
Your initial post gave your computer info and said 2 x ATI cards. Are you running two cards? If so then take one out and see if that helps stability.
FCP is not designed to use two graphics cards and it has been reported here often that setups with two cards are inherently unstable.
Slashdot tonight has an item about crashing Macbook Pros -
Like someone before mentioned - if you're running 2 graphics cards, don't. Take one out.
Next you might want to try losing RAM. I know, counter intuitive. But I've tried it and it seems to work. I think this instability is a RAM issue within FCP, and for some reason minimising RAM actually seems to help stability issues in the machines I've tried it on.
Before you criticise a man, walk a mile in his shoes.
Then when you do criticise him, you'll be a mile away. And have his shoes.
*the artist formally known as Jaymags*
All NLE's start having problems as you get into really large projects (even Avid with a database to an extent). We all try some of the same things (trash prefs, import sequence to a new project, trim project) and you are right that the number of individual items in a project is a contributing factor since you use a little bit of memory for indexing each item.
For Adobe, when we went to 64-bit, we had another thing we could throw at the problem - RAM. I've had a number of customers with problems that have solved their problems by adding more memory. If the next version of FCP involves 64-bit, you'll be able to address the problem in the same way.
Dennis - Adobe guy