Comments on: This project is unreadable or may be too new for this version of Final Cut http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/ Lookout honey, 'cuz I'm using technology. Thu, 19 Jan 2012 21:36:11 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Tim http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-5538 Tim Fri, 27 May 2011 18:17:03 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-5538 Hey Paul, Have you tried deleting the Final Cut preferences in /Library/Preferences or logging on as a different user? There are a lot of helpful tips in the comments! Hey Paul,

Have you tried deleting the Final Cut preferences in /Library/Preferences or logging on as a different user? There are a lot of helpful tips in the comments!

]]> By: paul http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-5537 paul Fri, 27 May 2011 17:20:28 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-5537 A project i just finished a week or two ago won't open now! same computer, no updates, did shut computer down once or twice... now what? A project i just finished a week or two ago won’t open now! same computer, no updates, did shut computer down once or twice… now what?

]]> By: k-day http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-3133 k-day Fri, 01 Aug 2008 08:30:20 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-3133 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... 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…

]]> By: Fucking fuck http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-2335 Fucking fuck Fri, 30 May 2008 10:54:45 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-2335 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? 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?

]]> By: Oliver http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-1603 Oliver Fri, 28 Mar 2008 13:54:30 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-1603 @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. @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.

]]> By: Tim http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-1598 Tim Thu, 27 Mar 2008 02:02:45 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-1598 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. 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.

]]> By: Oliver http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-1583 Oliver Tue, 25 Mar 2008 21:30:29 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-1583 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 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…

]]> By: Fix it... http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-1528 Fix it... Sun, 16 Mar 2008 18:06:23 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-1528 till then mate... good luck till then mate… good luck

]]> By: Tim http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-1527 Tim Sun, 16 Mar 2008 16:36:13 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-1527 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! 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!

]]> By: Fix it... http://www.timtoon.com/2008/03/16/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/comment-page-1/#comment-1526 Fix it... Sun, 16 Mar 2008 16:16:11 +0000 http://www.timtoon.com/2008/03/06/this-project-is-unreadable-or-may-be-too-new-for-this-version-of-final-cut/#comment-1526 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. 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.

]]>