Best Practices - Project Size/Number of Assets per project.

[Alex24473624titx]

Simple question but hard to find an answer. Does anyone know for best practices how larger a project size should be? Is there a set number of assets you should not exceed per project?

Thanks all. 

[R Neil Haugen]

Not really. There are things to be aware of though.

For instance, all metadata of assets/sequences is essentiallly loaded into RAM/cache files on opening a project, so the larger the project's assets base, the more RAM/cache it takes. Past X point, which will vary by machine, it starts to get slower in response.

The old methods of working around that were to set multiple projects for sections of a large project, with one over-all project file that you then duped your sequences to ... which also duped the media into that project ... so it sorta worked better.

But multiple open projects can be a nightmare for cross-duped things you didn't intend also.

They now have the Productions mode, which I've gone to even as a solo operator. You create a Production, which Premiere does with both an on-disc folder to house it, and a Production file in that folder.

From that Production panel, you create additional folders for parts of your project or workflow, and within those organizational subfolders as needed. Which Premiere actually creates as folders on disc.

Within the folders/subfolders, you create project files ... for actually working in. They suggest thinking of projects within Productions as essentially bins within an old standalone project.

And so you can have say a folder of broll, with subfolders for different types or subjects of broll footage. Then within those subs, you create project files and import that type of media.

They suggest building a parallel folder structure for your media to actually live in on-disc, as they prefer it not be within the Production folders.

The metadata for all imported assests is only 'filed' in the original project file you imported in ... no matter where else you use it in the Production. It simply references where in the Production the meta is housed. No duplicated assets and meta files. So vastly less gets stuffed into RAM/cache files while working.

I have subfolders for my main workflow areas ... within those, for specific clients, and within those, specific jobs.

My broll, audio library, templated seqeunces & such are available to all projects in the entire shebang. And it works sweet ...

Neil

[Alex24473624titx]

Afternoon Neil,

Thanks for your informative response, I wasn't aware of productions mode which could benefit from some of our larger projects here. We came across some projects with well over 15k+ assests per project and my thinking that seemed a bit high for a single .prproj. Our issue came across when we took our mezz footage off the NAS we lost links between our proxy files(Not all but roughly 30% of the proxies became detached). The assets still showed the proxy's file location but when the project reopened I think there was just to much for the computer to handle with reattaching to them, seeing that not all came back attached. 

[R Neil Haugen]

Definitely those are projects that should be handled as Production. There are some online presentations by Karl Soule on YouTube about Productions, go watch some. And they do have some info on their online help.

Including a very useful around 22 page pdf file I downloaded and printed out.

Neil

Neil