Tuesday, January 21, 2014

Re: [Avid-L2] Remote workflow best practices

 

I may have had a little trouble with that approach on a recent project where the media was going to systems with different versions of MC. 
 
We never really got to the bottom of it in the sense of replicating the error but rebuilding the databases on the new system fixed the issue we were having. 
 
It would seem prudent to allow a new machine to rebuild the databases when the drive first arrives by changing the folder name back to a number and then to something else after it rebuilds.
 
 
On Tue, Jan 21, 2014, at 02:52 AM, Job ter Burg (L2B) wrote:
 

 

 
Rename the mediafiles subfolder from 1 to 101 or somehting else, on both drives.
Anything you now import, render or create on one of them will go into a newly auto-created folder named 1.
 
Easy to detect, easy to sync.
 
Everything will not relink, as it will already be linked. You will not have to do anything besides adding media and bins. MC will rebuild the databases for any folders you add media to, and it will understand where things live.
 
J

On 19 jan. 2014, at 17:19, jesseg132001@yahoo.com wrote:



Hey folks -
 
 
I'm about to do a bit of remote work on a show I've so far been editing exclusively at the post facility. I just want to make sure I am following best practices so that when I go back for screenings it is seamless. 
 
MC 7.0.3
 
I have a drive of the entire show's media and project. Everything has reconnected on the remote system.
 
So I guess what I'm wondering is ... should I set the media creation settings to a DIFFERENT drive and then just copy that Avid MediaFiles/MXF/1 folder's contents back to the equivalent folder back at the mothership? I send myself the new updated bins and then ... will everything automatically re-link? How do I keep track of new media going forward? Is there a better workflow?
 
Thanks for your help.
Jesse
 

 

 

 

__._,_.___
Reply via web post Reply to sender Reply to group Start a New Topic Messages in this topic (7)
Recent Activity:
.

__,_._,___

No comments:

Post a Comment