-
Disk Array Repaired/Returned But FCP files unuseable
This may be slightly off topic. I had a disk controller problem with my harddisk array and the repairs went fine with the unit being returned to me last week. In my first attempt to hook up and use the array, 99% of the Final Cut-related captures and WAVs, Photoshop files, QT movies, etc are highlighted in red and none of these can be viewed or played. If I try to double click a QuickTime file that ordinarily would play fine, I see a message with the QuickTime logo saying “QuickTime cannot open the file: “xxx.mov” it is no a file that QuickTime understands (-2048)”
Is this a Mac permissions problem or just what? I tried to repair permission as best I understand the process, then rebooted and got the same results. When right-clicking and looking at the file info, it shows that I have read/write permissions in all cases. If I can’t remedy this I’ll have to lose all and reformat, I guess. For some reason just two (both QT) of the several hundred media files WILL play. There is nothing unique about these that I can determine, but they play.
If I open a prior FCP project, the files in the Browser appear to be online and normal, but if I click on one of them I get an error message “General Error 34” and then a message saying “Error: Out of memory”
I haven’t trashed preferences yet simply because all of these problems also happen OUTSIDE of FCP while simply looking at the files in Finder.
Remember that there are JPEGs that won’t open along with MP3 files, AIFFs, etc. The file sizes, dates, etc. look right. The array capacity and used space look correct, too. I’m not Mac savvy enough to know the ropes here. I’d be grateful for your wisdom and experience.
Greg Golden
Power Mac G5 with 10.3.9 OS, FCP 4.5
1.5 Gigs RAM, Blackmagic Design DecklinkSP
MediaVault 1.8 Tb -
4 Replies
-
Sounds like the resource fork for the files has been lost. This is common with reconstructions.
Try versiontracker.com and look for resource fork. There are some products that can determine and reattach the fork.
Ooh, ooh! You could also try to rename the files yourself. Just change the extension to what you think it should be and see what happens.
I hope you get it fixed, sorry I cannot give you a better or more definitive answer. You might also try the OS10 forum here on the cow but please include that you have crossposted.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
I’d post this in the Huge forum (that’s the array that was repaired, correct?). They will help you.
-
Call Huge. I am sure they have seen this before and they have great customer support. Your first move should be contacting them, not posting here.
-
They suggest to repair permissions — that was their only suggestion. I tried that and it didn’t help, so I took the next step. Thanks.
Reply to this Discussion! Login or Sign Up