Activity › Forums › Apple Final Cut Pro Legacy › Installed 5.1.3 – Now Project is Corrupted!
-
Installed 5.1.3 – Now Project is Corrupted!
Oliver Peters replied 19 years, 2 months ago 10 Members · 27 Replies
-
Wes Plate
February 18, 2007 at 7:34 amDo 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.
Sorry, I don’t think I read that, or I forgot I did. Did you send the same file that had already been opened in 5.1.3, or a previous backup that still opened on your system in 5.1.2?
Do you think the illegal character would be the reason for this problem?
Anything is possible, but I would hope this isn’t the reason.
Finally, is there anyway to generate an XML file from a FCP Project file?
No.
— Wes Plate
Automatic Duck -
Walter Biscardi
February 18, 2007 at 1:21 pm[dkilgore] “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.”
Did you take the media offline like was already suggested on here? If FCP does not like the very first clip it’s trying to open, then your project will fail immediately.
Take your media offline and try opening the project. If that works, then yes, you do have a piece of media the new version does not like. You’ll have to re-connect the media in small batches until you find the piece of media that’s causing the failure.
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
-
Francois Stark
February 18, 2007 at 7:07 pmHi Walter
Some of us will never be in a position not to do upgrades mid-project.
We are now doing our new daily soapie on FCP, and will be moving our first daily soapie over (from AVID) within a month.
These projects have about 60 episodes in editing at any stage on our SAN – from digitising, off-line, 1st approval, final approval, subtitles, on-line and grading, playouts, audio mix, etc.
So, the only way we have to do upgrades, is to upgrade one system only, and test, test, test. Open finishes projects, digitise, playout, grade…
So even the “number one rule” has exceptions and workarounds…
Thanks
Francois -
Wes Plate
February 18, 2007 at 7:27 pmBut Walter is still right. If you have a system that works, leave it alone. Upgrading anything is always taking a chance. If you’re working on a 60-episode project, keep your system exactly the same for episode 60 as it was for episode 1.
Why do you think there are so many old Avids still working in LA? Partly because the systems haven’t changed in years.
— Wes Plate
Automatic Duck -
Shane Ross
February 19, 2007 at 12:16 amWhat Wes said. I occasionally work for a company that has Avid Meridians (v11) that are running on OS9.
Shane

Littlefrog Post
http://www.lfhd.net -
Dkilgore
February 19, 2007 at 2:24 amThanks everyone for your help. Unfortunately I was unable to get the project to open and spent the day reconstructing from scratch. I am almost back to the point of where I left off. Major headache, but fortunately happening on the project that it did I only lost about a day. Much of the work was AE composites and I was able to reference the last cut from a client approval DVD.
My advise and new workflow from now on will be to export projects and sequence cuts as XML backups. There is a lot more stability and ways to work with XML and it would be wise to not only backup working progress but also to archive XML with the project file. There are many solutions and ways to work with/troubleshoot an XML file but unfortunately with FCP projects it seems if there’s a problem your SOL.
It seems it would be a better option for Apple to set the auto-backups to the XML format or at least give the user the ability to choose.
-dk
Donald Kilgore
Image202 Entertainment -
Wes Plate
February 19, 2007 at 2:37 am -
Dkilgore
February 19, 2007 at 5:09 amdkilgore:
“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.”Wes Plate:
“Sorry, I don’t think I read that, or I forgot I did. Did you send the same file that had already been opened in 5.1.3, or a previous backup that still opened on your system in 5.1.2?”—
I assumed that since it would not open on another system with 5.1.2 that it would not work if I tried to go back. I was also afraid to waste more time on it and have to reinstall everything. I just figured I would be better off just getting back to it and learning from the experience.I did notice when starting over that Magic Bullet Colorista does not work with the new version. The cut I was working on did use Colorista on every clip. I’m assuming this could be another possible cause to the problem.
-dk
Donald Kilgore
Image202 Entertainment -
Wes Plate
February 19, 2007 at 5:29 amI read today on the FCP-L that Colorista is another casualty of 5.1.3. Hopefully Apple will have a fix soon.
— Wes Plate
Automatic Duck -
Oliver Peters
February 19, 2007 at 1:59 pmWes,
Apparently all plug-ins with a custom GUI as part of their controls are hosed. This includes Colorista and FxFactory (Noise Industries), among others. Obviously Apple really dropped the ball on this one by not even doing the most minimal beta testing with 3rd party products.
Has anyone found a location for a valid 5.1.2 update? The URL listed above only routes you back to 5.1.3.
Sincerely,
OliverOliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com
Reply to this Discussion! Login or Sign Up