Creative COW SIGN IN :: SPONSORS :: ADVERTISING :: ABOUT US :: CONTACT US :: FAQ
Creative COW's LinkedIn GroupCreative COW's Facebook PageCreative COW on TwitterCreative COW's Google+ PageCreative COW on YouTube
SAN:SAN ForumSAN TutorialsApple Xsan Forum

Re: Avid Media Composer and sharing media on a SAN

COW Forums : SAN - Storage Area Networks

VIEW ALL   •   ADD A NEW POST   •   PRINT
Share on Facebook
Respond to this post   •   Return to posts index   •   Read entire thread


Bob ZelinRe: Avid Media Composer and sharing media on a SAN
by on Nov 11, 2011 at 3:52:12 am

Hi David -
everyone is being so nice and professional here. Well, of course, I will not be so nice and professional.

I know exactly what is going on here David - you want a cheap solution. You say "it's just a network - what's the big deal" - well, it's not just a network, and unless you buy AVID ISIS 5000, EditShare or Facilis Terrablock, you will either have to deal with workarounds, or you CANT HAVE SHARED STORAGE ! YOU AIN'T BUILDING THIS YOURSELF DAVID ! Do you understand me ?

Alternate solutions that work are using VOLUME BASED solutions - this means that you setup seperate partitions (or drive volumes) and only one guy can write to a volume at one time. This process works, and is successfully sold by Studio Network Solutions (SANmp) and Command Soft (Fibre Jet). Facilis until relatively recently, also used to only do Volume Based solutions for AVID, but relatively recently (a few years ago) they got file based working as well as EditShare. Other companies, like Small Tree and Maxx Digital are close to a working solution as well.

SO, why does this happen ? Because AVID writes a .msm and a .mdb file whenever you launch Media Composer, and if you are on one common volume or partition with two or more systems, the second (or third) Media Composer will overwrite the first guys .msm and .mdb file, and you will see MEDIA OFFLINE on your AVID on your edit 1 system. AVID (and others) get around this by using a METADATA SERVER to manage all of these files for each client. And companies that do VOLUME based solutions only allow ONE EDITOR to write to one volume or partition, so no one erases the .msm and .mdb file, because only one guy can WRITE to that volume. That's why it's called VOLUME BASED.

SO, why does AVID do this, and why doesn't AVID change this ? Because NO ONE WOULD BUY AVID ISIS OR UNITY if they made it easy, and would just buy cheap (or cheaper solutions). And brilliant companies like EditShare and Facilis have already figured out the successful solution for a file based workflow, and others (like me) are still struggling (but close) to a cheapo solution that works. And of course you can get a Volume based system right now from Studio Network Solutions and others.

but one thing for sure David - you ain't building this yourself to show your boss what a big hero you are.

Want shared storage for AVID Media Composer ? SPEND MONEY.

Bob Zelin



Posts IndexRead Thread
Reply   Like  
+1
Share on Facebook


Current Message Thread:




LOGIN TO REPLY



FORUMSTUTORIALSFEATURESVIDEOSPODCASTSEVENTSSERVICESNEWSLETTERNEWSBLOGS

Creative COW LinkedIn Group Creative COW Facebook Page Creative COW on Twitter
© 2014 CreativeCOW.net All rights are reserved. - Privacy Policy

[Top]