The way Premiere is built, for "stand-alone" projects, the ones most of us have typically used, it's prone to this on larger projects. The reason is that all metadata of every asset of the project is loaded into the RAM/cache system to load the project. It's called the "Master Clip properties."
If you've a massively powerful system, it's not ... too ... bad.
The new Productions mode is designed to get around this. You create a new Production, which is a folder on-disc that Premiere creates, and a production file inside it.
Within that folder in Premiere you right-click and create additional folders to organize your project as you would have created bins in a single project. In each of those folders you right-click create a new project that holds only bits of the total production job.
So you have project sub-folders for media, sequences, other assets or however you decided to set it up. In the Media subfolder, you may have additional subfolders to organize your media, or just create additional projects in those folders to hold the media assets themselves. So you have say a project file that is all your RED media, or the media from day 1 of the shoot, and on through.
And the only thing those projects are used for is storage of assets.
Now you create another project for sequences. You add media from the projects that store media as needed. Premiere then loads only the metadata into RAM/cache of that opened sequence, it can reference the Master Clip properties of all the media involved without having to store that to RAM/cache.
So your computer's workload is a lot less.
I'm a solo shop, and I'm using a single production to house all my jobs for this year's version of Premiere Pro. It's great ... all my 'template' projects, b-roll, audio assets ... everything is quickly usable in other projects without a) slowing anything down or b) duplicating assets in project files.
Neil
Using Productions in Premiere Pro
Productions reference pdf
5
Replies
AdChoices