This project is unreadable or may be too new for this version of Final Cut
Posted by Tim · 14 Comments
What bullshit.
I created this project file with this version of Final Cut Studio 2 almost a year ago, so it’s not too new, this is the most current version of FCS2 available, and on top of that I just opened this file successfully — without saving or modifying it in any way — just one week ago. And now the backup copy, archived on DVD, also isn’t working? You’re telling me it’s my file that’s the problem? I think not. The only thing that changed was… oh, it was that fucking QuickTime 7.4.1 (14) update that did it!
Fucking fix it, Apple.
UPDATE: I was able to open the files successfully on a system running 10.5.2, QuickTime 7.4.1, and the same version of FCS, so it looks like this is just an issue with OS 10.4.x.
Also, sometimes it hurts to get baited on your own site, even in jest. Looks like I owe someone a massive apology.
UPDATE TWO: I tried upgrading from 10.4 to 10.5, but the 10.5 installer required a GUID-formatted partition, which necessitated formatting my fucking hard drive. Talk about the cure being worse than the disease, which means I’ll be sticking with 10.4 for now, Coverflow be damned.
On the plus side, opening the same projects as a different user works. This is good for two reasons, the most obvious being that I can work in Final Cut again, and the second is the implication that my ‘too new’ project woes may be fixed by something as simple as deleting a file in my user preferences.
You never upgrade QT mid-project. Ever.
Sorry to offend your delicate Victorian sensibilities, m’lady.
Here’s the thing, I already completed these projects and from the same version of FCS, no less. Was it too much to expect FCS not to break my projects retroactively? If that’s going to be the case, when should I upgrade QuickTime? Never?
The fault lies with Apple and its shortsightedness for not checking this update beyond the bells and whistles it adds to the iTunes store.
No bother, I use those words too… I was just messing with you.
The situation with QT updates breaking stuff has been like this with FCP (and other apps) since FCP 1.0. If you could see the entire scope of QT development on updates you may not be so eager to simplify the process. Which would you rather have a security issue that might compromise a lot of things or the slight inconvenience of having to backtrack on your error to impetuously update and go back and downgrade? Apple is really good about getting fixes done. Compared to Microsoft?
What you may want to consider is going onto a site like 2-Pop.com or Creative Cow and check reports in those forums on updates before taking a plunge.
Yeah, I hadn’t had a problem this severe with FCP before, so it really blind-sided me. I’m going to try it on a friend’s machine to see whether it’s the QT update that broke it, my version of the OS or what …and of course hold off on the next QT update.
Thanks for the advice and the links!
We are in the same boat.
It fucking sucks.
I have researched the living shit out of this damn issue.
I HAVE TRIED EVERY FIX I HAVE READ relating to this issue.
We have now lost a client, as we missed the deadline due to this shit.
Fucking fix it apple!
Apologies for my ‘pottymouth’ – it is a way of me externalizing violence in a non physical form- saves me from throwing the Mac out the window!
J
Yeah, it’s maddening when your projects suddenly stop working, and it sucks even more that you lost a client over this sloppy update. Were you able to open the project as a different user?
Tried opening as a different user at the start – and no joy! Tried even going through the permissions of every relevent folder and file as well and gave ‘universal’ access to all users and accounts. I dont know quite what I hoped to get out of this process… but when your at the end, the brain makes some passionate attempts at lateral thinking.
The only real fix i have, which isn’t really a fix and certainly doesn’t work for us is using the XML export and unclicking all of the options on import. But this method trashes all the filters. Which really doesn’t help as that just puts us back a week and half with the no CC, no filters, (audio and video) and motion graphics.
Tim, i think we are gonna have to wait for some wiz kid apple technician to get back from holiday!
For us it didn’t seem to be a matter of QT but more so with leopard, as the file works fine on our G4 PB and intel imac both running 10.4 the problem has arisen with our purchase of the new MAc pro (8 core 3.0ghz) running on leopard. This computer is what we bought to finish this project and start a new one.
Your experience sounds different from mine; I wasn’t able to open projects at all in 10.4.11 with QT 7.4.1, but could on a system with FCS 6.0.2 and OS X 10.5.2. Apart from making sure everything is updated, or just reinstalling Final Cut… I’m out of ideas.
I agree, I can’t wait for the QT 7.4.2 update to fix this mess!
till then mate… good luck
I might have the same problem. Project gets saved to an external hard drive on a G5 Mac and cannot be opened on any of my other macs, although all macs have the same OS X (newest)and I am working with FCP 5.1.4.
I have a G5 PowerMac a new Intel iMac and an older G5 iMac. both iMacs get the same stupid message when trying to open the project. It doesn’t matter wether I copy aöl data before to another harddrive, so rights shouldn’t be the problem, I habve no idea but I am also short before collapsing…
I know how you feel!
A friend of mine had a similar problem he was able to fix by deleting his Final Cut User Settings in /Library/Preferences. I haven’t gotten around to testing it yet, but there’s another possible solution.
@Tim
I tried trashing the prefs with empty trash and restart. Still no solution, but thanks anyway. I found out so far that with one user on my maschine it worked. (User has the same name than the user on the maschine that created the file, no idea wether this can make the change?) With my own user account it doesn’t, so it seems not to be a matter of OS or of the file itself.
My Imac crashed in the middle of a rendering (fuck you Apple), then I restarted and I got this fucking message.
Even the autosaves can’t be opened.
what the fuck?
I’ve had this problem with FCE 3 and 4 — using both Tiger and Leopard.
My very crude workaround: leave the computer and FCE running until current project has been completed…