Best practice on a SAN with Team Projects
Hello all-
I am excited that Adobe has added the start of Node-based project management with the new 2017 Team Project feature.
So my question is..
Is there a video or tutorial with "Best Practice" setup for this type of edit?
We have 3 new Apple Cylinder editing workstations on a 10 GB/s SAN network, with 500/Mbps tested off of the server, which is SSD. We are editing 22 minute episodes of 2K footage in rendered TIF sequences.
We have seen a LOT of curious behavior when working on 2015.3 in the same scenario, and have yet to be able to determine what the best practice is for performance in this scenario.
For instance,
-Where do we set the cache? Right now we are setting it locally on each machine to a dedicated thunderbolt SSD. The thinking being that we don't want to use any network bandwidth to edit the TIF sequences, which are quite large, around 128 GB per 11 minutes.
If we put the projects on the server, will it automatically detect a team edit? Can you make a team edit on the same sequence at once?
Do we set the scratch disks for previews and such on the server or locally as well.
Do projects carry these settings internally? We noticed that if we had a machine with Premiere loaded on it fresh, and the machine had set its' intermediate time database as 29.97 fps, then if it loaded up a project that had a hundred TIF sequences originally imported at 24 FPS, the NEW machine will open the OLD project using 29.97 fps. We then have to go back and manually link re-interpret each of the sequences... VERY ANNOYING!
Any overview of working off of a SAN and Team Projects would be greatly appreciated. It is a nice feature, but it (like so many things ADOBE) is released with a seeming VACUUM of information on how to best setup the technical side.
Thanks
Chapman
