-
iMac Pro thoughts
-
I had it twice with large projects last year where the library of footage (all red 8K and 6K raw) when imported to a cc project would slow the project to a crawl when saving, opening, closing or importing new footage. The library was around 7TB in size – contacted adobe support (which is dreadful) and they said to reduce the size of the library by either working in proxy and relinking for final export or to edit chunks together and compile at the end. Didn’t seem viable so worked in FCPX instead.
Perhaps it was a freak, but it seemed to be an acknowledged problem at the time from Adobe; storage was fast and had plenty of space, as did scratch disks and cache so I couldn’t figure out what was causing it other than a software problem.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
[Tom Sefton] “I had it twice with large projects last year where the library of footage (all red 8K and 6K raw) when imported to a cc project would slow the project to a crawl when saving, opening, closing or importing new footage.”
I really haven’t run into that and over the past year we’ve had about 7 editors on various machines running some pretty large projects.
Premiere has to go through a “conforming” process with audio on various media types. When you first import media, this happens in the background and slows everything down. But once down, standard operation is pretty fast. It’s generally advisable to not have this cache on a shared storage volume, so we save those files locally. This means that if you open the project on a new machine at any point, those files have to be created again locally on that machine. That’s the only annoyance we have routinely run into. However, waiting the first time is about the same as waiting for FCPX to write all the waveform cache files, which is essentially the same process.
The other thing that can balloon project files sizes in Premiere is if you have media, like Alexa Log-C, where Premiere automatically applies a built-in LUT. In your case with RED files, maybe there’s a slowdown because of RAW, but I would think only if you’ve changed the RED settings away from “as shot”. Just a thought.
– Oliver
Oliver Peters – oliverpeters.com
-
[Oliver Peters] “I really haven’t run into that and over the past year we’ve had about 7 editors on various machines running some pretty large projects.”
I’m working with a company that has two docs in PPro and each doc has about 20TBs of media in it and I haven’t heard them complain about slowness when opening or saving the project.
-
That may have been a localized problem. I’ve worked on multiple projects that have involved over 5 terabytes of media and there’s been no noticeable lag. I’m also working on a PC though so maybe it’s been a mac bug.
I Hate Television. I Hate It As Much As Peanuts. But I Can’t Stop Eating Peanuts.
– Orson Welles -
[greg janza] “That may have been a localized problem. I’ve worked on multiple projects that have involved over 5 terabytes of media and there’s been no noticeable lag. I’m also working on a PC though so maybe it’s been a mac bug.”
Same here (on PCs) – but my projects and media are on local storage.
Shawn
-
[Andrew Kimery] “I’m working with a company that has two docs in PPro and each doc has about 20TBs of media in it and I haven’t heard them complain about slowness when opening or saving the project.”
Slowness is the in the eye of the beholder. Isn’t that how the saying goes?
-
[Jeremy Garchow] “Slowness is the in the eye of the beholder. Isn’t that how the saying goes?”
It is, though when I’ve been opening, saving, ingesting, etc., into the projects I mentioned in the previous post they do so quickly and not “horribly slow” like Tom has experienced. Sure, it’s all relative, but I doubt my ‘quickly’ and Tom’s “horribly slow” are the same speed. ????
On my current gig we generate about 80TB of media each week (11 video feeds running for 90min stretches, three times a day, four days a week). All of that footage ends up in PPro and the projects open and save in a few seconds. Importing media is a little slower than I’m used to, but it still happens in seconds, not minutes (and I’m used to importing files that are much shorter than 90min so my point of reference isn’t really comparable).
-
Nahhhh, this was beach balls for 30s whilst trying to import a single jpeg to a project that had been worked on for days. I think it was more to do with the compatibility between cc and red helium footage.
Co-owner at Pollen Studio
http://www.pollenstudio.co.uk -
[Andrew Kimery] “It is, though when I’ve been opening, saving, ingesting, etc., into the projects I mentioned in the previous post they do so quickly and not “horribly slow” like Tom has experienced.”
Is it 6k and 8k red raw footage like Tom is using, though?
-
[Jeremy Garchow] “Is it 6k and 8k red raw footage like Tom is using, though?”
No, but the original talking point was that 5TB of media was the max PPro could handle w/o slowing down and my responses have been to that point. Factoring in codecs, HD vs 6K/8K, specific machine hardware, etc., are obviously different variables that can play into what Tom is seeing.
I don’t work with 6K/8K red raw footage, so I can’t comment specifically to that workflow, but I do work with large amounts of media and don’t experience Tom’s problems so that can help eliminate variables with regards to trouble shooting and workflow development. To that point (and the most recent post from Tom), the problem sounds specific to the footage he is using, as opposed to using large amounts of media in general.
Reply to this Discussion! Login or Sign Up