A few weeks ago our production’s Mac Pro suffered a RAID5 failure. Fortunately the data was recovered and we began to reinstall the system and core software, namely Final Cut Studio 2 (Final Cut Pro 6.05). As we sorted through our recovered data we noticed a number of problems with Final Cut Pro.
Incorrect Type and Creator Flags
Final Cut Pro would not open our project files due to an error of “wrong type.” Apparently the Mac still uses Type and Creator flags to determine what application owns a particular file (and why file extensions are still optional in OS X).
For unknown reasons most of the recovered data had Type and Creator flags that were reversed. What should be FCPF was FPCF, AIFF was FFIA, and so on. Due to the number of buggered files we used Quick Change’s batch feature instead of the console application setfile.
The proper flags are listed below (format, type, creator):
- Final Cut Pro project / FCPF / KeyG
- AIFF audio file / AIFF / hook
- WAVE audio file / WAVE / TVOD
- MOV media file / MooV / TVOD
With the flags fixed Final Cut Pro opened our project file successfully but greeted us with another error.
This Project is Unreadable
Opening the project file resulted with “this project is unreadable or may be too new for this version of Final Cut.” I wasn’t surprised because we rearranged our volume structure during the recovery.
I’ve covered this issue before which is due to Final Cut Pro using absolute paths within the project file.
Opening the project using a different user account does work because Final Cut Pro ignores the bad paths when the project’s user account doesn’t match. The project was exported to XML which revealed the paths as:
file://localhost/Macintosh HD/Users/name/path/to/media
This URL should open the related media file in Safari but doesn’t. Interestingly, localhost is stripped which leaves the URL as file:/// (an empty host); remove the third / and it will open.
Resolving the “project is unreadable” error is simple: create a user account with a different name than what was originally used to create the project (if you created the “old” user account, delete it). Open the project and reconnect the media – done.
Even with this accomplished I still could not open the project under the old user account. I’m curious to know what else Final Cut Pro embeds which isn’t easily changed.
It seems that only rare and obscure software glitches come my way.
The final presentation at last night’s Tapeless Workflow seminar at the Editors Guild was a discussion of tape backup. Yes, there were chuckles about the irony of a “tapeless workflow” which still requires tape media.