Activity › Forums › Avid Media Composer › MORE LIKE TRANSFER
-
MORE LIKE TRANSFER
Posted by Nicholas Toth on September 20, 2006 at 3:17 pmHey guys, I’m not an Avid poster (hahaha get it?!?!?!), I’m usually in the AFX forum.
We’re trying to transfer 3 timeslines from an old media composer (os 10.3), to a much faster Adrenaline (windows).
Any advice? We tried consolidating media and had NO SUCCESS. I’m thinking maybe an embedded omf.The timeline is about half an hour or so a piece, so it will be a monster.
Nicholas Toth replied 19 years, 11 months ago 2 Members · 4 Replies -
4 Replies
-
Michael Hancock
September 20, 2006 at 3:27 pmWhen you say you had no success, what does that mean exactly? You couldn’t get the timeline to consolidate? You couldn’t get the timeline to relink? The Adrenaline system wouldn’t read the timeline at all? Give us some more details of your workflow–what you’ve done, and what didn’t work.
Otherwise duplicate the timeline you want to transfer, consolidate the media to an external drive, plug that drive into your Adrenaline box and transfer the media files on it (in the OMFI MediaFiles folder at the root of the drive) to the OMFI MediaFiles folder of your Adrenaline’s media drives. Delete the database files of your Adrenaline’s media drives. Start your Avid and it will rebuild your databases.
Copy the bins from the Old Media Composer to the Adrenaline. Start a new project in the Adrenaline of the exact same name as the project on the Old Media Composer, import just the bins from your project. They should relink to the consolidated media you transfered over. If it doesn’t automatically recognize the link, select your clips and go to Bin–>Relink (I think it’s under the Bin command–not at the system right now). They should relink now.
Don’t try to bring the whole project up–just import the bins. Also, make sure you put all of the media in the OMFI MediaFiles folder–no other subfolders/etc… If the media isn’t in the OMFI MediaFiles folder at the root of your drives the Avid won’t see it.
Any of this help? Let us know!
Mike.
-
Nicholas Toth
September 20, 2006 at 4:31 pmIs it a problem that the adrenaline is trying to read the firewire drive as a media drive?
The house we’re working with isn’t transfering it to their hard drive.The audio imported PERFECT, but the video was off by quite a few frames.
You’re saying we should just copy/relink the media directly onto the hard drive….?
-
Michael Hancock
September 20, 2006 at 4:55 pmThe avid might have trouble using the firewire drive as a media drive, but you might be able to edit off of it depending on the resolutions of the media and complexity of the edit.
If it isn’t recognizing the drive then go to your Media Creation settings and uncheck Filter Drive Based On Resolution. Then do a File–>Mount All. This will allow the Avid to recognize the firewire drive as a media drive and to read and write from it. I would still suggest transfering your media off the firewire drive to the media drives of the Adrenaline if the folks you’re working with are ok with that. Don’t transfer the media to the system drive–only to their media drives, and again–drop all of your media files right into the OMFI MediaFiles folder (if you’re only dealing with OMF files–if you’re dealing with MXF files that’s different).
Also, you say the video is a off by quite a few frames. What do you mean? Is the Adrenaline recognizing the media on the firewire drive but the timeline seems to have shifted all the video layers by a few frames? Or is it a playback problem where the video lags? And when you say the audio imported perfectly, are you actually importing it? When you transfer the media files from one system to another you shouldn’t be importing anything–just relinking.
Mike.
-
Nicholas Toth
September 20, 2006 at 6:38 pmIt was strange —
We consolidated and just re-opened the avid project on the Adrenaline. The video wasn’t lining up, and some of the video was actually running at double speed. There were no issues with the audio timeline, it imported perfectly. We had no continuity, which is why it is tough isolating the problem. We wound up exporting quicktime movies and .omf audio sequences. This is a ghetto approach, but we are still trying to figure out the problem.
thanks again for your help Mike
Reply to this Discussion! Login or Sign Up