-
FCP 5.1.2 Sequence corruption
I’ve never had this happen and can’t find any posts regarding this.
I had a three-week project finished and ready to print-to-tape via FW a to a DSR-45. When I switched the video playback device from the Decklink card to the Apple DV-NTSC firewire output, I got a “can’t locate” error, followed by an “out-of-memory” error. The sequence (the master on sequence) would not open. I went to the Autosave vault and opened the most recent save and the same thing happened. I suspected a bad piece of media but the sequence had played back fine before.
The timeline had been rendered including all effects. The only plug-ins used were the 3-WAY COLOR CORRECTOR and NATTRESS FILM 3.2 (or latest version). I removed the Nattress Effects and still got a corrupted sequence everytime.
I also tried reverting back to The Blackmagic card and it still corrupted.
Other actions taken:
-trashed FCP user settings
-trashed FCP prefs
-trashed Blackmagic Decklink settings
-trashed FCP thumbnail cache
-trashes FCP wavform cacheRe-installed 5.1.2 update.
Re-installed Quicktime.FYI- I just upgraded to FCP 5.1.2 two weeks ago and this is the first large project I cut since.
Any help would be appreciated.
System Info – G5/Dual 2 – 10.4.7 – QT v7.1.2 – 8GB ram – Radeon 9800Pro – External SATA Raid – Decklink Extreme – Wacom 6×8
-
5 Replies
-
Hi,
long shot for contact with your recorder:
You could try to load a easy setup with “dv ntsc” if your primary setting is BlackMagic.opening the project:
I now its boring to delete render files, however it could help…hope this helps you out!
the best,
Andreas -
This exact same error happened to me. Only prior to “not found” and “out of memory” error i was doing titles w psd files. the titles were jumping for what seemed like no reason. i removed all attributes and made the track invisible to reset the render file. when i made the track visible i got an error saying that playback had been disabled and to close my canvas window. i closed it and when i tried to open the sequence again i got “not found” & “out of memory.” i trashed all render folders and prefs. nothing worked. i had to rebuild from sequences in the auto-save vault.
What is going down? -
Similar Problem – we exported the sequence as an XML document and then imported it back in to the project. The sequence would then open. Does yours ?
-
Matt G’s suggestion about exporting at XML and reimporting sounds like a good suggestion, and can throw off the problems of internal corruption of your sequence/project. It would also be the steps I would take after troubleshooting your existing project, as described below:
I would also make a new project, in case it was more than just one sequence. I have successfully used the following technique in the past for a similar problem (which turned out to be a corrupted video file), using the “Divide and Conquer” method of troubleshooting a sequence:
1) Create a new project
2) Create a new sequence
3) Drop in some Bar and Tone and make sure this plays back OK, then delete this slug
4) Copy the contents of the problematic sequence to the new sequence
5) Close the old project
6) Test to see if the new sequence will play OK: if so then keep on going with the new project & sequence, otherwise continue.
7) If your sequence is still having problems then make a duplicate of this sequence
8) Open the copy of the new sequence
9) Select half of your timeline and delete it, unless you have only one clip left (and this should be the bad clip)
10) Try to play out what’s left
11) If it doesn’t play out, then go to step 7) above
12) If if does play out, then delete this sequence
13) Make a copy of your sequence
14) Delete the other half of the sequence you didn’t delete in step 9) leaving half of the clip untouched
15) Go to step 10)If you think you’ve identified the bad clip, try playing it in a sequence by itself.
Make sure that you’ve deleted all your render files before you start, in case it was a render file which was the problem.Bill Lee
-
I also exported to an XML. This was the workaround but I still lost several hours of editing as a result, but at least that’s better than several weeks. What’s scary is that it affected an autosaved file that, when it was saved, was fine.
I forgot to mention earlier that I did trash and re-build the render files. I also had some un-compressed footage that I was using on the timeline and I re-digitized that to the Blackmagic DV codec. Neither one of these actions prevented the sequence from corrupting.
Reply to this Discussion! Login or Sign Up