Had my first play with the Productions workflow this morning. I followed the very clear guidelines on coverting an existing (27MB) project into a production. It worked a treat and the resulting (5MB) 'Current Edit' project is wonderfully responsive. Brilliant.
Am wondering now if and how I might best incorporate productions into our existing workflow long term with respect to archiving old projects. My existing process in that regard would include creating a copy of the full organised project file, albeit removing any unneeded sequences, and saving that master project file alongside the programme masters. The original media would be archived separately. But with the productions workflow, short of manually constructing a single master 'project'... exactly like converting an existing project to a production, but in reverse... are there any guidelines?
I can see that I can create a standalone project from a sequence, and use 'Generate Master Clips for Media' to populate it with master clips based off the sequence contents... but if I understand correctly, that means I get only the sequence contents, not the full project media... and the master clips generated will not be organised in any way (ie not in bins per production organisationl structure).
Apologies for thinking out loud, but I suppose zipping up the entire production, and archiving that zip file along with my masters, is probably my easiest soultion for effectively replicating my existing workflow... and it's quick and easy ... but an option to allow users to export an entire production, or parts thereof, as a single standalone project (where that project would replicate the production's full/targetted content and organisational structure using bins) might be a useful feature to consider. Maybe a 'Production Manager' is needed?
[Edited post's 'Subject' line to avoid confusion]
Yes, I have read that but it doesn't address my post ... hence my post.
Have edited the 'Subject' line to better reflect the question.
I'm puzzled at the idea, actually. I just don't get the "why".
The entire point of a Productions workflow is to split things up so the entire job works better. That's if you work one job per production. It's a reorganization model, one built to scale from medium to massive jobs. And the organization model of a Production simply cannot be replicated in a single project file.
Why would you want to combine everything?
Lol. I actually spelt out the why in the original post Neil 🙂
Totally appreciate that not everyone may want or need to do it ... but I dare say the same could be said of any feature. For those that might need and use it, the organisation model of a Production could be replicated in a standalone project easily, effectively the same way we have been working without Productions for years, mapping Production > Project, Folder > Bin, Project > Bin, Bin > Bin. Hopefully the scripting API will eventually allow for it.
What, specifically, does the scripting model not currently allow?
I also don't understand what one might gain, by cramming a Production into one amalgamated project...
Thanks for the reply and apologies for the unintended shade! I blindly assumed support for Productions in the API would be limited by it being so new ... hadn't even looked. Thats my bad.
I just had a quick browse : Production.path gets me to the production folder (so I can easily discover structure and all contained projects - and thus open those as necessary) and Production.projects returns an array of all currently open projects. Assuming its possible to move projectItems between open projects then it looks like it could already be pretty straightforward to automate. I haven't tried it yet (as per my original post, I'm really just thinking out loud, I haven't convinvced myself I need to do it at all) but is moving items between projects really as easy as currentProject.projectItem.moveBin(targetProject.targetBinItem)?
If so, two thumbs up for rootItems!
I haven't tested trying to use moveBin() to move an item to a different project...Let me know if it works!
Yep. Just tested, works perfectly. Thanks again.
I still don't get the why ... and I did understand the bit about archiving. I just didn't understand what you expected to gain by reducing a Productions process into a Project file. There's a lot of differences there that aren't necessarily obvious. I can't see any 'saving' to be had by the time spent working on it.
One of the expectations with a Production workflow for those using them as a single-job process, is that you simply move the Production folder to the archiving location.
That's why I asked.
Part of the question about this may lie in assumptions or expectations.
It took some time of working within a Productions workflow for me to fully realize how massively different this process is. It isn't just a 'take the organization from a project and put some in folders and link the projects' bit of sleight-of-hand, based on the old stand-alone project files. If it were, then I suppose "shrinking" a production back into a project file would seem like a natural reversal.
Productions and stand-alone processes and workflows are different from the very core of each process.
You do have to accept that statement, and completely abandon the concepts used in stand-alone project workflows while working in Productions. And to get "there", I suggest thinking about this from the concept of The Job, not The Project.
Define The Job ... whether it is a single specific job for a specific client, all jobs for a specific client for a year perhaps, or all jobs for a small shop for a year. Create your Productions organization to best work within the Job as you have defined it.
And none of the above paragraph was ever possible with an old-style stand-alone project file/process.
Stand-alone projects are based on the metadata within the project file.
Within the old-style stand-alone process, the entire organization of the Job you are working on is based on two things: the organization you created in setting up bins for assets within the project, and the metadata that Premiere gathers from your bin organization and from ingesting those assets. None of that information is available outside that project file.
This is why when you have two project files open and drag/drop something from one project file into another, Premiere completely duplicates all of the copied assets and all metadata for them from the one project file into the other.
Production Jobs are built on the on-disc organization of the folders within the top level Production folder, combined with the linked metadata of all project files included in that top-level production folder.
In a Productions process, Premiere is not dependent on the metadata within each project file of that process to encompass all metadata for that entire process ... that Job. The metatdata is spread around through all the linked folders and project files of that productions process.
Remember, we are actually now working with project files that are the equivalent of a single bin in a stand-alone project file process. So even a medium sized Job can have 50 project files between those used as simple bins and those actually housing sequences. Where you had a top-level bin for Media with maybe 10 sub-bins, now you have an on-disc folder for Media project files ... and that folder includes ten project files, each holding only what each sub-bin had held before.
This enables the program to run with far less metadata loaded to memory/cache at any one moment. And at the same time, allows for a far deeper and broader organization of an editor's work within Premiere.
But there is no natural route for migrating all that diverse and diffused data down into one old-style project file. How would it have any idea which project files should become bins? Which project file should be the job project file? There are so many ways each user can organize their work, and can organize different parts of a job differently.
And as the entire approach to working within Premiere is changed, so is the archiving process.
Yet in some ways, it's the same. You archived a Job before, when each Job was it's own project file. Now you archive the Job as a Productions folder-set. You're still archiving The Job. But that Job is structured differently.
I'm glad to hear your first test with Productions went well!
The process of migrating a Production back down to a single project should actually be pretty straightforward. Here are the steps I would take:
The only need to use the Generate Master Clips command would be if you realized you forgot some clips that are in a timeline, but technically if you are thorough on steps 3 and 4 that won't be a problem.
Let me know if that works or doesn't make sense. The key is as long as you do all that combining while all the projects are open, Premiere will take care of essentially undoing all the links across projects and you will end up back with a single self-contained project. It's essentially the reverse of the steps in the documentation to break apart an existing project, but you can selectively leave behind old dupes of sequences, etc, that you don't want to combine.
Thanks Matt, yep thats the process I arrived at too. Appreciate the confirmation.
Will follow up with Bruce re scripting too.