-
Media pending a loading way too long in my large project
Hi,
I’m in the middle of a pretty large project right now. Around 10000+ clips to load including proxies and pictures, different camera types and so on. The project opens right away but the loading time (media pending) is taking foreever (I mean 20mins or so but you get me).
I have multiple sequences each with different shooting day and I’m making some cutdowns (or what do you call these). From 5 hours down to 1 hour to work with. Taking out junk and so on. So basicly I have multiple sequences with some clips I’m intending to work with.
My question is:
Is there an easy simple way to somehow disable clips that I’m not using in any of these timelines to sort of not needing them to load? I’m looking for some one click option (disable loading for all unused clips in timelines). I don’t want to delete them from the project as I might need to come back to them or at least know they exist.
Disclaimer:
I know I can use multiple projects for different days and then import the cleaned footage to a completely different one where to do the editing. I actually do this already as the project is waaaay bigger than I mention earlier. It’s just that I’d like to keep some parts together thematicaly in one project.
Thank you for some of your tips or suggestions.
-
2 Replies
-
You should check out the new Productions workflow that allows you to break your overall project into smaller projects so you don’t have to load the whole “production” at once. It takes a bit to wrap your head around the new organization method, but it makes working with large projects like yours much more manageable.
Here’s Adobe’s overview on how to use it:
https://helpx.adobe.com/premiere-pro/using/production-panel.html
Best,
R
-
Sadly Pr is NOT very efficient. I know a software engineers at Adobe that works on the capture features of Pr. He’s a brilliant software engineer but has warned me about encoding/decoding problems they continue to encountered.
I’ve asked him several times why Adobe doesn’t leverage more RAM usage and he indicated there is “less risk” with less RAM usage, hence why Pr is still heavily I/O reliant. Regardless, the performance issues with Adobe are all about the encoding/decoding and the types of codecs used. Even “proxies” will not save the day.
I inquired about the usage of AVX instructions and he indicated they don’t use AVX (which seems odd to me). I haven’t confirmed but you can test for AVX usage by dropping the AVX offset in your BIOS/EFI (to some much lower value like 7 — 700Mhz slower when AVX is used) … disable speedstep so the CPU frequency is constant and note your “normal” frequency (i.e. 4.0Ghz). Run HWINFO64 and monitor CPU core frequency. Now run Pr and monitor HWINFO64 CPU frequency, if you see momentary CPU drops to 3.3 Ghz then you know AVX is being used, if no drops then AVX is not being used.
The performance problems I’ve noted with Pr:
1. Software bound (CPU side) and GPU usage is minimal and only helps in very specific use cases
2. Doesn’t use RAM efficiently … there is absolutely no need to have more than 64GB RAM (I have 128GB RAM which was a complete waste even for very large projects)
3. Doesn’t leverage AVX instructions
4. Encoding/Decoding isn’t optimized (Adobe seem lost in various codecs)
The only way I’ve been able to “marginally” tackle the performance problems with Pr is to:
a. Use proxies
b. Convert all my source to a format/codec that works well on my specific PC (you’ll have to experiment because it’s NOT the same for everyone)
I’ve tried tossing hardware at Pr and it made very little difference, very high speed M.2 drives, RAM drives, more RAM, better GPUs, faster RAM, different CPUs. The single key significant performance problem is Adobe’s encoding/decoding which they seem unable or unwilling to solve.
Cheers, Rob.
Reply to this Discussion! Login or Sign Up