Premiere Projects take forever to open on NAS when switching computers.

Cool thread!

🙂

It wasn't Team Projects you needed to adopt, but the Productions workflow. I've worked extensively with both.

TP is great for linking people for remote work, but you're still working within a single massive database/cache for the entire project, which Premiere has to load into RAM/cache files to operate. Horribly for massive projects, as you've noted. You can use Linked Projects within TP, but it still has limitations.

Productions works completely differently, and it takes a bit of thinking, including dumping many of your normal practices. But when applied, it's comparatively blazingly fast to load and operate.

In Premiere, create a New Production. Premiere actually creates a new folder on-disc and puts inside that folder the Production file.

And now the major differences begin ... right-click on the Production panel, and Create New Folder ... which again, will be a folder on disc. Create a folder structure for your project, similar to how you created Bins before.

Say you have a Media bin, and within that bin you have sub-bins for Day 1, Day 2.

For a Production then, you would probably have a Media folder, and subfolders for Day 1 and Day 2.

Now the really weird begins!

In the Day 1 folder, right-click Create Project. In that new project, import/ingest ONLY the Day 1 media.

Do the same in the Day 2 folder ... create a Day 2 Media project, with only the Day 2 media.

Do the same for other assets, like Sequences, Audio files, Graphics, Stills, whatnot. Each gets a folder within the larger folder tree, and within folders, its own project file.

What this accomplishes is separate the storage of Premiere's "Master Clip" data into very usable bits, that are all tied together through that Production file uptop. But Premiere only needs access a small part of the total data at any one point. And once you've used it, you never, ever want to go back to single project file operation.

When you open the Production to work, you can access any and all of the project files within that production. It uses the Premiere collaboration tools for mulitple users working within the production, and while one is working with a sequence another can open the sequence but can't change it. But you can open a sequence in-use, copy things as it is showing on your screen, and then add that copied bit to another sequence you're working on.

Drag/drop clips from their 'bin' project to a 'sequences' project, and it does NOT duplicate the Master Clip data within that project ... it just accesses the needed data from the project where that media now 'lives'.

It's how the "Hollywood" unit sets up the major movie and broadcast productions for those clients. And now available for all.

You can also take your current project, add that to a Production, and separate the bits out into a full Production workflow.

• Create a new Production folder.
• Add the current Premiere Pro project to that production.
• Create the folders, subfolders and projects, as essentially a duplication of the organization within the current project.
• Drag/drop assets from the current project to their new homes.
• When done emptying that project, just delete it.

That is what you need to do. Yea, waiting for HOURS for Premiere to load all that data is painful. But now, totally unnecessary.

Neil

Premiere Pro Productions Introduction

Using Productions in Premiere Pro

Productions Workflow for Long Form & Episodic PDF

I have worked as an editor from my share of servers but let me quickly say that I don't have direct experience with this setup. It obviously doesn't sound right, but let me ask a couple questions even if that helps someone else more network-savvy if they see this.

Are the project files stored locally? I could see that causing a big issue with load times as it may see it as a drive letter change. (I believe in any situation I've been in when working from a server the media cache was local, so I don't necessarily think that's an issue, but again--I yield to the more server-savvy)

I'm also curious about whether or not you have a project without the dynamic linking that you could test to see if that works any better. Any production company or agency I've been at where multiple people are sharing a project has not used dynamic linking outside of to send a shot to AE, but after that the link is broken. It's convenient, but it's an extra layer of stuff to go wrong. It's not my place to change your workflow, that's just what I've seen and worked with as an editor in team/server environements.

The other thing I'm curious about is if you've tried a different version of Premiere, like maybe rolling back to 14.4?