There are 2 filters you can use that each take a VERY long time to render…and you are using BOTH of them, and on an older computer. Nice specs when it was new, not so much 6 years later. Plus also doing Keying and Color Correction as well.
Using either DeNoiser or UnSharpMask can take 18-24+ hours EACH per hour of video on an older machine, in my experience. Sometimes when effects are combined, it actually takes much longer to render them all at once than it would to do them in separate passes.
What I often do with DeNoiser it run that FIRST (overnight export) to create a new intermediate file (ProRes for instance). Then use that new, clean, denoised file to edit with and add more effects to. One reason is that with DeNoiser added, one cannot even scrub or play for any kind of decent preview as it bogs down so bad. So I do that before even beginning to edit.
I can’t speak for AE, but here’s what I have done in the past with Premiere projects. I might completely edit a long-form video like a wedding ceremony, then decide I really should’ve used DeNoiser (but maybe didn’t want to delay starting the edit, so had skipped it).
I can run DeNoiser on the raw footage clip, exporting as “filename_DN.mov” and then in Premiere use REPLACE and all my prior edits remain intact, but original media is replaced with the CLEAN footage.
Another way aside from using “replace” is to rename the original clip, and give new DeNoised file the name of original clip, then when you re-open Premiere it doesn’t know the difference and just references the new clip thinking it’s the old clip. Of course, clip duration must match exactly, as it will if you process and export original clip without altering.
So that’s why I might try, if estimated render time is like 3 days or something. DeNoise first, then start adding other effects. UnSharp is actually more render-intensive than DeNoiser, it’s bad!
Thanks
Jeff