This discussion is archived
2419 Views 2 Replies Latest reply: Aug 9, 2009 1:36 AM by simonblackledge
Currently Being ModeratedAug 8, 2009 8:16 PM (in response to simonblackledge)Yes. You'll want to reshare the edit proxy device read only, via AFP or NFS.
There are caveats - editing over ethernet cannot guarantee bandwidth and latency in the same way as fibre or direct of disk, so there might be occasional dropped frames. But for the purposes of editing with the proxies, this is not so much of a big deal - you'll be conforming with the hi-res media at a later point.
Depending on how many clients and streams per client would be using this, you'd need to have a think about the backend infrastructure. I've got a setup where I have the edit proxies device on an XSan and a dedicated XServe resharing the device as AFP (read only). That keeps the AFP I/O off the final cut server machine.
You can also do things like get a 4 port ethernet card and bond the network interfaces to give you more bandwidth from the xserve to the switch.
Currently Being ModeratedAug 9, 2009 1:36 AM (in response to Matt McM)Thanks Matt,
So from what I understand after re reading the manual over a few times. Editors can check out a project and choose orig media or Edit Proxies and both will edit in place as long as the drive where the media resides is mounted on that client, which it is.
The confusing part is the edit proxies appear to be in a .bundle :-/ how do I share that as a drive?
Or is the idea to create a new device for edit proxies at the start?
good point about setting it as read only..
Thanks for the help.
Message was edited by: simonblackledgeTo much !!!, Mac OS X (10.5.2), macpro 8core |5gig |8800GT|AttoR380|