Our office has twelve Media Composer systems connected to Interplay Production on ISIS storage. We are talking about having one of the editors work in an office in a different part of the country and we are trying to determine what his workflow would realistically be.
- The best option of course would be to use Media Composer Cloud (former Sphere) to facilitate access to our existing Interplay Production system. Since we do not have any plans to remotely connect more than a single user, this option would likely not be cost-effective.
- The safest option would be to segregate projects and media to the remote system. We would export and transfer (via Aspera) media that the user would need to edit locally and never bring his projects back to Interplay. If we originate a project at the remote location with media that has never been added to Interplay, I could see importing an AAF back to Interplay, however.
- What would be optimal would be to use a workflow that could allow the remote editor to utilize duplicates of media that exists in Interplay and return his timelines to Interplay and relink to the original media on ISIS storage. Based on my experience with the Interplay system, I imagine media could be "thrown over the fence" by copying the MXF OP Atoms right off Interplay and adding those to local storage at the remote site. Exchanging the media and projects in this fashion (if it would even work reliably) would seem to require a good deal of administrator support, where a user-servicable exchange process would be more desirable.
I have searched the Internet and briefly browsed topics in this forum to see if anyone has attempted media and project exchanges with Media Composer systems not connected to Interplay, with no luck. So I am looking for suggestions to see if there are even viable options to consider besides Media Composer Cloud (Sphere).