Participant

Question

'Replace with After Effects Composition' exponentially increases render time?

Forum|Forum|7 years ago
June 29, 2018
2 replies
484 views

I am editing concert footage from a 3 camera shoot. No 4k files, just 1920x1080. Computer is a new build, i7-7820, 32gb Ram, Evo 970 M2 SSD for OS drive and 950 SSD for Scratch disk drive where files are located.

I have a 9 minute excerpt, all edited up. If I only am using Premiere Pro CC, the render time is about 14 minutes and all works flawlessly (using the Youtube 1080 preset). I have done dozens of videos so far, the system is very quick.

Recently I've tried to utilize the 'Replace with After Effects Composition' on some of the clips to remove grain in AE. No animation, etc., just removing grain, and only on one clip of about 8' in length. However when I do this, it exponentially increases the render time in PP to 38 hours. Also, playback back in PP comes to a virtual standstill. I've tried to 'render and replace' the clip back in PP but it just appears to hang on "Analyzing project...". Perhaps it is similarly doing some processing, but if so that is also taking an inordinately long time, and I always need to cancel.

Based on my understanding of the workflow between PP and AE, I don't think this is standard, and would love any advice you might be able to offer. Thank you.

This topic has been closed for replies.

E

excited_Genie16B8

Legend

One thing you have to consider is that AE comps rendered out of AE are multi-threaded. AE comps in PP are processed on a single thread, so...much slower.

R Neil Haugen

Legend

Thanks for the comment, Jim ... I always forget that bit, and well ... kind of a crucial thing, isn't it?

Neil

Everyone's mileage always varies ...

B

benwinter

Inspiring

To avoid going to AE for footage noise reduction, I've started using the Neat Video denoiser plugin natively in Premiere. It does take some time to render as any denoise might, but wow is it a magic wand, and also GPU accelerated.

R Neil Haugen

Legend

Video noise reduction is some of the most intense resource-heavy computing out there. Yea, depending on how you set it, that can really kick up the export time.

Especially when other effects such as color, Warp Stabilizer, such things are applied to the sequence.

Which is why many editors will say do a first pass of noise reduction (if they know significant nr will be required) in AfterEffects, then export those clips into a "digital intermediate" or "mezzanine codec" like Cineform, ProRes (if on Mac) or DNxHD/R, and then import those clips into PrPro to completely replace the original media, and then do the general editing process and export the final deliverables.

And the noise-reduction export can be done overnight of course, so you don't sit & wait for it.

Especially if that media is from DSLR/Mirrorless cameras, long-GOP H.264, your export times with noise reduction are going to be extreme. Due to the nature of that media, where there's only a real frame of video every 9-30 or more frames, and in between are only data-sets of pixels that have changed since the last complete or i-frame, will change before the next one, and/or both. That forces the CPU to constantly create & store frames, pull up data, recall a frame or two, compute the changes to create a new frame, store ... recall ... compute ... rinse and repeat for every frame.

That chip of yours is only a 4-core rig and unless you've severely over-clocked it, supposedly running a bit under 3Ghz. Long-GOP media requires 8-10 cores running close to 4Ghz if not over, with around 10Gb RAM per core, for best running in an NLE. Or so say a number of experts, and from my experience, that's about right.

Would I wish it were otherwise? Oh, of course. But in the world as it exists, this app & that computer, you may need to split off the n-r work and export that into your project for decent export of the final project files.

Neil

Everyone's mileage always varies ...

rumiatesAuthor

Participant

Thanks for the quick reply. I made a mistake in specifying my processor: it's the i7-7820x. This is 8 core/16 thread, I believe, in case this information changes the expectation of rendering times, etc.

R Neil Haugen

Legend

Yea, that changes things a bit doesn't it? 8 cores at base of 3.6Ghz, you're right, significantly a better CPU. There, the bottleneck will be the RAM, as that's only 4GB per core, less than half the recommendation for long-GOP processing. Still, better than the first numbers!

Which means that yea, it is better than I thought, but ... still ... video noise reduction is a massive process. Especially if you've got much temporal work involved, going 3 or more frames either side for checking the file, which is really what gives the best quality noise reduction. I tend to go to 5 frames at times, and wow ... going from 2 to 5 frames in the temporal setting vastly increases the render time. But ... also the quality.

So I'd still suggest trying to export a clip from Ae with full n-r applied, imported into your project and worked, then export that out of PrPro. See if the times are more workable.

And ... yea, I need n-r at times for entire shoots. Those run over-night to prep for working the project.

Neil

Everyone's mileage always varies ...

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded