-
file attribute mismatch
Hello
My editor and I share the same exact media on duplicate drives. We are both running 6.0.2. She sends me project files of her work. When I attempt to reconnect her project file to the duplicate media on my drive I get the File Attribute Mismatch dialogue box. Media Start and End is mismatched.
We are working on merged clips. The video portion of these clips reconnects with no problems – however if I continue regardless of the File Attribute Mismatch warning the audio portion reconnects without its In Point. So the merged clip is now merged with the beginning of the audio clip as the In Point rather than the original In Point. As a result the the merged clip is now out of sync.
Anyone have any thoughts what is going on here?
Thanks
Andy
-
4 Replies
-
Andy,
I’m having a very similar problem.
Working with ProResHQ video and BWF audio and merged clips.
Whenever i need to relink the audio files, i get the attributes mismatch error (Media Start and End, Rate).
Sometimes i can get away with clicking “continue”, but, for some clips, i can’t.
Those get chopped down to a single frame in the edited timelines, and are completely out of sync.
Please let me know if you find out anything -I’ll do the same.
Thanks!
Guy Ross
creativeco [at] guyross [dot] com -
This is the exact problem I have been having. I am very surprised that theres not more on here about this. You should be able to have a project on multiple systems with the exact same media copied over without this kind of a problem. Maybe this message will open this discussion back up. Thanks in advance.
-
I have the “Media Start and End” msg after having made a back-up to a G RAID2 drive. I used Finder to copy the folders.
After capturing, nothing has been dragged to the timeline yet. Already reconnect issues? I’m using FCT 6 on a Mac Pro, captured format: ProRes (HQ).
When I reconnect the media files, the start and end times change with a few seconds.
What the h*ll is going on?Thanks, experts! Sorry for my frustrations!
-
This is an old thread, but apparently Apple hasn’t addressed the issue. While researching a similar problem, I found a fix thanks to a discussion on Apple’s site:
The best way I’ve found to share a project is to make sure the file directory structure and drive name match exactly on both systems. That way there are no reconnect issues at all. Cloning the drive is the easiest way to do it and then simply rename the drive to match the original drive. I usually add an x to the end of the drive name so that there are no problems caused by having to identical drives on the same system. And then I remove the x from the drive name when I connect the drive to the other system (but before I launch fcp).
This instantly fixed the problem for me. I didn’t even clone the drive – I just changed the drive’s name. Not sure why FCP thinks the rate has changed when all I did was copy the file…!
Reply to this Discussion! Login or Sign Up