-
Yet another media puzzle
This as is as wierd as the wierd post below, and may be related.
I digitized several hours of footage to a FAT32 drive, which broke up the large clips as untitled-av, untitled-av-1, untitled-av-2, etc.
Due to fragmentation issues (I assume), it couldn’t play some of the clips without stuttering, so I copied all the folders and files off the drive onto a backup RAID striped as Mac Extended Journaled. I then reformatted the Fat32 drive as a Mac Extended Journaled drive, and copied all the original data back onto it.
However, now none of the broken up quicktime files will play on the freshly formatted drive. If I just select the untitled-av file, for instance, it will display as a sound file might, but no picture. If I open it up in Quicktime, it will display as an audio file might — no picture. When I pull up properties, it shows that it has several audio tracks and and a video track, but won’t allow me to enable them. The timecode track is the only thing being “displayed.” When I click on the resources tag, it shows where the current file is located, and then has a list of “unknown” under that.
Now, if I copy these files again (which work perfectly off the RAID) onto the drive, I see no change. Every fresh copy to this newly formatted drive yields the same results.
And the most ironic thing is that if I copy these non-working files to another volume ie. a SATA formatted as a Mac Extended Journaled drive, the files immediately work again, even though they were copied from the non-working directory on the freshly formatted drive.
Am I in that parallel universe where all the reasons I love Mac are backwards and obsolete? I hate it when that happens —Any help greatly appreciated . . .
Glen Hurd
-
3 Replies
-
OK, just stumbled across the solution. The name on the newly formatted drive had an apostrophe in it to match the name originally given the FAT32 formatted drive. On a hunch, I removed the apostrophe, and suddenly all is good.
I don’t know why this matters, so I’d still be curious if there are any opinions on why this didn’t matter with FAT32.
Confused, but happy …Glen
-
[Glen Hurd] “I don’t know why this matters, so I’d still be curious if there are any opinions on why this didn’t matter with FAT32.”
maybe ‘casue it is a legal character for file names in Windows but not under Unix?
Gary Adcock
Studio37
HD and Film Consultation
Chicago, IL USA -
The irony is that the mac was so much more forgiving about naming things than windows was. So I stopped paying attention. But when it comes to naming drives, there’s obviously something to watch for. Additionally, this issue doesn’t seem to matter in naming the folders used for storing the quicktime files — every folder name in the file’s heirarchy can have apostrophes, and the files behave normally. So if this is a Unix problem, it only seems to effect drive names.
Glen
Reply to this Discussion! Login or Sign Up