Installed 5.1.3 – Now Project is Corrupted! - Apple Final Cut Pro Legacy

Apple Final Cut Pro Legacy

Installed 5.1.3 – Now Project is Corrupted!

Posted by Dkilgore on February 17, 2007 at 11:18 pm

After installing the software update for FCP 5.1.3 the project I was working on now crashes FCP when attempting to open. FCP also crashes on any of the auto save backups for this project as well. I’ve tried trashing FCP preferences and also tried opening the project from another user on the same machine…. No luck.

The crash log reports an error pertaining to framework. Below is a sample of the crash log, I’m not sure how to read this or what the important part is, posting the full report would be very large but if someone would like to see the full report I will email a text file.

Thanks for any help.
-dk

CRASH LOG SAMPLE

PID: 1701
Thread: 0

Exception: EXC_BREAKPOINT (0x0006)
Code[0]: 0x00000001
Code[1]: 0x92978120

Thread 0 Crashed:
0 com.apple.Foundation 0x92978120 _NSRaiseError + 264
1 com.apple.Foundation 0x92977e5c +[NSException raise:format:] + 40
2 com.apple.Foundation 0x92961eb4 _decodeObjectBinary + 1776
3 com.apple.Foundation 0x92961704 _decodeObject + 164
4 com.apple.ProFX 0x00c9efc0 -[PFXOpaqueData initWithStateValue:] + 100
5 com.apple.Foundation 0x92961f20 _decodeObjectBinary + 1884
6 com.apple.Foundation 0x92961704 _decodeObject + 164
7 com.apple.FinalCutPro 0x004e30a4 KGPortValueObject::Deserialize(CInputStream&) + 264
8 com.apple.FinalCutPro 0x003fc65c CSerializable::DeserializeObject(CInputStream&, CSerializable**) + 264
9 com.apple.FinalCutPro 0x003fe3c8 CInputStream::ReadObject(void**) + 120
10 com.apple.FinalCutPro 0x001367b8 ReadObject(void*, KGStreamRecord*, KGReferenceTableInt*) + 52
11 com.apple.FinalCutPro 0x00135e18 KGTypeReadValue + 160
12 com.apple.FinalCutPro 0x0002d378 KGDictReadHashCommon(KGDictInt**, KGStreamRecord*, KGReferenceTableInt*, KGDictInt* (*)(long)) + 304
13 com.apple.FinalCutPro 0x0002d464 KGDictReadHash + 32
14 com.apple.FinalCutPro 0x0011e1f8 KGDictReadInternal + 180
15 com.apple.FinalCutPro 0x0012f9c4 ReadDict(void*, KGStreamRecord*, KGReferenceTableInt*) + 96
16 com.apple.FinalCutPro 0x00135e18 KGTypeReadValue + 160
17 com.apple.FinalCutPro 0x0002d378 KGDictReadHashCommon(KGDictInt**, KGStreamRecord*, KGReferenceTableInt*, KGDictInt* (*)(long)) + 304
18 com.apple.FinalCutPro 0x0002d464 KGDictReadHash + 32
19 com.apple.FinalCutPro 0x0011e1f8 KGDictReadInternal + 180
20 com.apple.FinalCutPro 0x0012f9c4 ReadDict(void*, KGStreamRecord*, KGReferenceTableInt*) + 96
21 com.apple.FinalCutPro 0x00135e18 KGTypeReadValue + 160
22 com.apple.FinalCutPro 0x0002d378 KGDictReadHashCommon(KGDictInt**, KGStreamRecord*, KGReferenceTableInt*, KGDictInt* (*)(long)) + 304
23 com.apple.FinalCutPro 0x0002d464 KGDictReadHash + 32
24 com.apple.FinalCutPro 0x0011e1f8 KGDictReadInternal + 180
25 com.apple.FinalCutPro 0x0012f9c4 ReadDict(void*, KGStreamRecord*, KGReferenceTableInt*) + 96

Donald Kilgore
http://www.image202.com

Oliver Peters replied 19 years, 2 months ago 10 Members · 27 Replies
27 Replies

Walter Biscardi
February 18, 2007 at 12:05 am

Why did you update mid-project? Number 1 rule that all of the leaders on here have said time and time again, never update anything mid-project unless you’re having a ton of issues.

Run Repair Disk Permissions on the main hard drive. If that doesn’t work, get yourself a copy of Disk Warrior and run that on your main hard drive.

Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Food Network’s “Good Eats”
HD Editorial for “Assignment Earth”

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
Dkilgore
February 18, 2007 at 12:23 am

I know, but it is kind of hard not to update mid-project because I always have a few projects going at once and there almost never any downtime with no projects active.

I keep project files on a separate project drive with real time backup. The project raid is separate from the media raid and system drive. Which drive should I run disk warrior on and how do you think that would help? I’ve already repaired permissions and verified that all disks are in good conditions.

Could you provide more information on what disk warrior would be fixing?

thanks.
-dk

Donald Kilgore
http://www.image202.com
Ron James
February 18, 2007 at 2:05 am

Also, try taking all your media offline, then open the project. Just put an X at the end of your Capture Scratch folders, or something similar, so the material will show up offline when you open. It might be a render file problem. Wouldn’t be the first.
Wes Plate
February 18, 2007 at 3:01 am

If you reinstall 5.1.2 does your project (or one of your backed-up projects) open?

— Wes Plate
Automatic Duck
Dkilgore
February 18, 2007 at 5:33 am

I’m not sure how I can revert to 5.1.2 but I did send my project over to a friend who has not update to 5.1.3 and is still using 5.1.2 and he was unable to open the project as well. What really has me confused is why all of the auto save backups would also have the same problem, so it’s not simply 1 corrupt file, there is something in about that project which the new version does not like. I should also mention that it’s a rather large project with over 500 subclips created using MovieLogger and the project files is about 4MB.

-dk

Donald Kilgore
http://www.image202.com
Wes Plate
February 18, 2007 at 5:40 am

Maybe you haven’t archived your updaters, one thing I’ve learned to do only because I have to do a lot of installs, but I would reinstall 5.1 then update to 5.1.2.

— Wes Plate
Automatic Duck
Will Salley
February 18, 2007 at 5:44 am

Go to your Autosave vault (usually USER>DOCUMENTS>FINAL CUT PRO DOCUMENTS>AUTOSAVE VAULT) and COPY the last saved file to your current project folder.
Do not try to open the original file in the Autosave Vault, it may get corrupted as well and then you would lose even more work.

Open the copied backup in v 5.1.3. If it doesn’t work, you will need to re-install FCP from disk and do the update here:

https://www.apple.com/support/downloads/finalcutpro512.html

Before re-installing, go to ROOT>LIBRARY>RECEIPTS> and remove the file “FinalCutProUpdate5.1.2.pkg” and “FinalCutProUpdate5.1.3.pkg”.

System Info – G5/Dual 2 – 10.4.8 – QT v7.1.3 – 8GB ram – Radeon 9800Pro – External SATA Raid – Decklink Extreme – Wacom 6×8
John Pale
February 18, 2007 at 5:58 am

e-mail me the project and I will see if it opens here

pale.edit
AT
mac.com
Dkilgore
February 18, 2007 at 6:46 am

Wes,

Do you think going back to 5.1.2 on my system would work even if the project would not open on another system using 5.1.2? I tried sending it to a friend who has not yet updated and he was unable to open the project either.

Also, I’ve been researching this problem all night and looking into reasons projects get corrupt and one possibility could be that when logging the media using MovieLogger we created key terms based on the topics, problem may be we used commas to separate the keywords. I then created subclips from the logs. This resulted in apx 500 subclips many containing commas. Do you think the illegal character would be the reason for this problem?

Finally, is there anyway to generate an XML file from a FCP Project file? If I could could convert the project file to XML then maybe I could clean up and remove the illegal characters.

thanks for your help.
-dk

Donald Kilgore
http://www.image202.com
Dkilgore
February 18, 2007 at 7:04 am

John,

I emailed the project to you. If it works, export the project as XML and email that back over. Thanks for looking into it.
-dk

Donald Kilgore
Image202 Entertainment

Page 1 of 3

1 2 3 →

Reply to this Discussion! Login or Sign Up

Creative Communities of the World Forums

Installed 5.1.3 – Now Project is Corrupted!