FCP Bug?
by Baz Leffler
on
Jun 26, 2009 at 12:15:48 am
I have a very stable MacPro Octocore running FCP 6.0.5 for some time now. But I can make it crash everytime. This is how...
I have to check 1000+ clips in a sequence to make sure the broadcast filter is the last on each clip. So I select the first clip in the viewer and look at the filters. Then I use the arrow down key to jump to each clip which then displays it in the viewer. This way I can rapidly check the whole sequence.
Problem is that after a while (about 200 clips) FCP becomes unresponsive for about 5 seconds then 'POOF' - its gone! It happens every time. And everytime it happens it offers me to report it to Apple which I do. But that is like talking in a one person conversation. Can anyone else here reproduce this bug?
I am amongst other things a software engineer and this reeks of a massive memory leak. And the 'poof' thing brings back bad memories of when I use to edit with Adobe Premiere.
Re: FCP Bug? by Baz Leffler on Jun 26, 2009 at 3:19:40 am
Thanks Shane - I am suspecting it only occurs with HDV as I tried it with a HDCAM (uncompressed 8 bit) sequence and it was fine. Also, sometimes when in the 5 sec frozen mode the image on the sequence viewer goes into strange colour mode indicating it couldn't decode the HDV frame.
Re: FCP Bug? by Baz Leffler on Jun 26, 2009 at 7:33:27 am
OK so here is an update - I just updated to 6.0.6 and can't make it crash... maybe its going thru an incredibly stable stage at the moment - one hopes it lasts forever.
Now lets hope they have fixed the export to tape bug thats been there since way back when....
I was troubleshooting a large and complex project that kept shutting down halfway through the session. It turned out that the editor had his levels of undo set to 99. I changed that and restarted the computer and Final Cut and the problem went away, never to return. I suggested to him that if he needed to go back 99 levels of undo, he would be better off going into his autosave vault and opening up his project from approximately where he was when he was where he started.
Re: FCP Bug? by walter biscardi on Jun 26, 2009 at 1:38:31 pm
[Sam - Senior Editor]"I suggested to him that if he needed to go back 99 levels of undo, he would be better off going into his autosave vault and opening up his project from approximately where he was when he was where he started. "
I leave Undo set to 50 and never use AutoSave.
Walter Biscardi, Jr.
Biscardi Creative Media HD and SD Production for Broadcast and Independent Productions.
Thanks for the quick reply. I set mine to 30 and leave the autosave turned on. If I was just editing myself, I'm with you and turn it off but I work at a place where the skill set of the editors range from novice to fully experienced, so for their sake I tell them to leave it on and they are protected when they edit on their own.
For me personally (editing at home), I just do a save project as a few times during my edit session but at work I leave it on for the benefit of the other editors or producer/editors as we trade projects back and forth. I guess that it's a personal preference of mine.
Re: FCP Bug? by Scott Allen on Jun 30, 2009 at 3:26:30 pm
I'm sorry, I'm new here (how many times has THAT been said before) -- but it's still not clear to me what's wrong with leaving AutoSave on? What's gained by turning it off?
Re: FCP Bug? by Baz Leffler on Jun 30, 2009 at 11:47:45 pm
On large projects autosave in FCP happens in the blink of an eye. But in Adobe Premiere you have time to go get a coffee.
Maybe some fear it from their Adobe days.
