-
Strategies for keeping externally source media in check?
In our office we have a server which we do most of our motion graphics and VFX work from. Clips from FCP or Avid get exported out to the server, and then rendered shots get put on the server when they’re done.
When using these shots in FCP I don’t want to import directly from the server as it results in media being played across the ethernet, which is sub-optimal. So I copy it to a local drive.
However this is an issue with keeping files in Sync this way as potentially new versions or revisions are made, I have to make sure I copy them to the local drive and have the latest version imported.
Anyone have any useful strategies for ensureing things are in sync between a network (SMB in this case) location and a local mirror of the same stuff?
Currently I’m experimenting with using an Rsync utility to manage the process, which seems to work okay – it will overwrite files locally if they’ve changed on the remote side, and will pull down anything new.
Another thought I’ve had, but never really tested, is using a SVN (version control, typically for software development) to manage a respositry like this – it might be more efficient as it only needs to transfer file differences rather than whole files in the case of changes.
-
1 Reply
-
It’s an issue all FCP-based multiple-seat houses must eventually face so I hope some of the big dogs will respond. It’s all about communicating with each other, deliberately moving obsolete versions to an obscure location, and developing and enforcing a file naming convention that encourages participation and use instead of rebellion.
FC Server may be a viable investment for your shop. The return on investment in content management tools is usually realized in the first project when a client approval stage is met because everyone is using the same versions of everything.
Hoe you get more specific advice soon, stay tuned. Good luck and please consider coming back some day to explain how you solved this in your shop.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
Reply to this Discussion! Login or Sign Up