-
This is kind of a wide open question…
Adobe on it’s own currently has no built in collaborative feature set.
No specific collaborative functions. Adobe did show some future Tech called “Anywhere” at IBC 2012. Its worth looking at just so you see where Adobe may be going, but it’s nothing you can implement today. so……Adobe’s tools are based on “Path to File” technology.
If the file can be found at the specified path, then it can be used.So…
The simplest implementation is simply to buy a NAS or SAN with enough spindle power behind it, a level of redundancy you are comfortable with and based on a connection topology that can deliver the number of streams your editors are requesting at high work volume + some overhead.I have used this type of collaboration in Library style collaboration.
Common Assets are shared in common assets folders on the NAS
Project specific assets are stored in Project specific assets on the NAS.Editor can work on Projects from any machine and Projects can be passed serially from one machine to another.
An important key about this is how your filesystem identifies the “path to file.” If you’re on the PC side and your common assets are on volume Z: (as understood by your PC), then you need to make sure that the common assets are seen as volume Z: on all the machines.
If you are using a UNC convention like \Common Assets, this can help to alleviate these types of issues.
Another Key aspect of making this work, is FILE ORGANIZATION. It’s really important to have a defined workflow for where files live and procedures for how editors are to create projects and access media. It can get out of control, and that can make relinking projects when you move from machine to machine tedious to say the least. People should be able to identify by folder structure and naming convention where to place/find things on the storage. Make it as logical to your content as you can.
NOW…that being said, there are some MAM’s (media asset mgrs) that are compatible with PPro. These types of tools sit on top of the OS and basically control workflow for asset check in, placing assets in appropriate places on the SAN. It also allows tagging and searching to find material based on metadata quickly. And editors should utilize the MAM interface and not the OS to find and access files. CatDV is one that comes to mind and they have a forum here on the COW.
Another IMPORTANT thing to consider about workflow procedure with Premiere in its current implementation is that segmenting projects across editors and then merging those editing projects into a master for finishing can cause project bloat. Where, when projects are merged, if multiple editors used the same asset, it will be merged into the project multiple times. So projects built this way can get bulky quickly, particularly if there’s a lot of back and forth with the editors and revisions. It’s not a deal breaker, but it is something you should be aware of.
Some turn key SANs are claiming collaborative workflows within Premiere Pro Projects. Facilis and Editshare are two that come to mind. While I have used Facilis, it was prior to this implementation, so I can’t speak to the functionality. I’ve never used editshare at all.
So….that’s about what I can add to this….I hope its helpful.
Alex Udell
Editing, Motion Graphics, and Visual FX