[Lee Adair]

OK, that makes more sense, and probably wouldn’t have worked out in my case. We often had all four of us editing at once, either on selects or actual deliverables, and Team Projects made managing that super-simple; just share changes every so often and they are available to everyone with no delay. Managing four versions of the project and making sure that they all got conformed into a master project would have been a much more difficult logistical challenge.

Thanks for the clarification!

[Lee Adair]

Honestly, other than the media cache issue we found it to be rather easy to use. Premiere seemed to crash a bit more than usual, but on the plus side every relaunch picked me up exactly where I had left off without asking me if I needed to open a recovery version of the project. Each night we would convert the day’s edits into a stand-alone project just to safeguard it, but we never needed to go back to one of them.

Just curious what your experience has been with Team Projects, Dave. What issues have you run into?

[Lee Adair]

Interesting, Oliver – we work off of shared storage, but have never had more than one editor working in the same project at the same time; didn’t think that was possible due to conflicts as each editor changes the project. As far as a local cache, we had the same thing at first, but each project “save” (or “share” in Team Project parlance) triggered new media with new cache files.

Will someone else confirm their experience with sharing a local Premiere Project at the same time? If that’s possible I’ll definitely rethink using a Team Project for such an event in the future.