jeb1138
Carioca
(I posted this in News & Rumors and then realized I should have posted it here. Please help!)
Um, does anybody out there have any experience with resource and data forks? I've got a large video project and I have messed up every single audio file in the whole thing because I used the Terminal to move the audio files once. The problem is with QuickTime and resource forks, I think, and I have no experience with resource forks.
I moved my audio files to a different folder and now the video files can't link to them anymore. You know how in QuickTime a file can link to other files to get audio or video? Mine can't. Everything was working until I moved my audio files to a different folder using the copy (cp) command in the Terminal. Oops. Now when QuickTime tries to load the video files it can't find the audio files. That's OK because it lets you "search" for the audio files. BUT, when I find the files they're grayed-out and I can't select them. I also found out that if I move the files to a Windows PC and use QuickTime for Windows to open the files I can select the audio files. All the data is still in the audio files, I just have to make QuickTime for OS X believe it.
I found out that if I copy an audio file using "ditto -rsrc" instead of "cp" it will work. That's why I think the problem is with resource files. Unfortunately I have already copied my 200+ audio files for this project using "cp".
Here's a link to 3 files -- a one-second video clip, a copy of its audio file made with "ditto -rsrc", and a copy of its audio file made with "cp":
http://homepage.mac.com/junk2755/FileSharing3.html
When you double-click the video file (Believers-av-0) it won't be able to find the audio file and will ask you if you want to search for it. If you do, when you find the "ditto -rsrc" copy you will be able to select it, but when you find the "cp" copy you won't be able to select it.
If anyone can figure out what needs to be tweaked on the "cp" copy to get QuickTime to like it please let me know. Or if anyone thinks they know what exactly is going on I would love to know. Thanks.
Um, does anybody out there have any experience with resource and data forks? I've got a large video project and I have messed up every single audio file in the whole thing because I used the Terminal to move the audio files once. The problem is with QuickTime and resource forks, I think, and I have no experience with resource forks.
I moved my audio files to a different folder and now the video files can't link to them anymore. You know how in QuickTime a file can link to other files to get audio or video? Mine can't. Everything was working until I moved my audio files to a different folder using the copy (cp) command in the Terminal. Oops. Now when QuickTime tries to load the video files it can't find the audio files. That's OK because it lets you "search" for the audio files. BUT, when I find the files they're grayed-out and I can't select them. I also found out that if I move the files to a Windows PC and use QuickTime for Windows to open the files I can select the audio files. All the data is still in the audio files, I just have to make QuickTime for OS X believe it.
I found out that if I copy an audio file using "ditto -rsrc" instead of "cp" it will work. That's why I think the problem is with resource files. Unfortunately I have already copied my 200+ audio files for this project using "cp".
Here's a link to 3 files -- a one-second video clip, a copy of its audio file made with "ditto -rsrc", and a copy of its audio file made with "cp":
http://homepage.mac.com/junk2755/FileSharing3.html
When you double-click the video file (Believers-av-0) it won't be able to find the audio file and will ask you if you want to search for it. If you do, when you find the "ditto -rsrc" copy you will be able to select it, but when you find the "cp" copy you won't be able to select it.
If anyone can figure out what needs to be tweaked on the "cp" copy to get QuickTime to like it please let me know. Or if anyone thinks they know what exactly is going on I would love to know. Thanks.