Productions feature vs. Team Projects

This is a user-to-user forum, with assistance and oversight by product support staff. We do get occasional product development staffers on here to assist. But it is not a normal place for direct discussion with development staffers.

Team Projects is good for those working in a wide-spread situation where you are in different places and cannot share stored media from the same servers. Mo is from Cape Town, I'm up on the US West Coast in Oregon, and we've had great success with Team Projects combining our varied talents. Mo ... well, good at most things, but his Ae and sound work are amazing. Color ... well, yea, that's my thing.

TP takes some experience as the media management is rather different than 'standard' and if not followed correctly one idiot can blow the whole project up for everyone if they add media incorrectly. Not that ... um ... oops ... I was that person ... um ... mind you ... just hypothetical here ... sigh.

But as long as you understand the protocols and follow them, it's amazing to work with.

Productions ... that is an awesome new way of working in Premiere, and I ... in my one-man shop ... totally work in a Production now. Why? Because all my complex template setups, all my b-roll, sound, graphics, everything that I've created or added for one project, is now available immediately in any other project without duplicating assets or slowing anything down.

Productions work can be done by major project, type of project, client, or time period.

You create an overall folder for the project. Within that folder you create a folder for your project assets, and then tell Premiere to create a Production folder in that same subfolder.

I recommend (as does the development team) that you build a subfolder structure in your OS file management for storing the project media assets in that Assests subfolder tree.

From the Productions panel in Premiere, you create subfolders for each of the project's sections, and in those subfolders, create one or more project to handle that bit of the project section. They recommend you use projects to house media in the same way we used bins within a project to house media.

You can work within any one project of that production, access any media, sequence, or asset of any other project ... but with only the overhead in RAM and cache from the small project you have open. It's quite wondrous that way.

But ... you do need to be on shared media/server typically when working with others.

So ... are you able to work shared media on a NAS/SAN system? Productions, definitely ... this isn't something for TP workflows.

Or ... do you people working remotely, have a massive project where you'll be shipping drives of media to everyone? Probably Productions still, as it handles massive assets better.

Are you remote, spread around the planet? And not a necessarily massive project? Then Team Projects is your thing. Probably. Note, everyone in a TP workflow has to have access to the media, but ... they can be proxies distributed by the project head and not full-res media.

And there is a dedicated forum for Team Projects questions ...

Team Projects

Neil

I have the same question and it's funny that Adobe representative doesn't care to reply?