You own a terrific computer and a great graphics card that were really high performance four to five years ago. The only way to speed rendering would be to replace both or perhaps just the GPU. You can buy two GTX Titan cards today, which run circles around the K4000, for about what you originally paid for the K4000.
David Roth Weiss
Director/Editor/Colorist & Workflow Consultant
David Weiss Productions
David is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.
I used some clips from my canon 70D for testing the denier II in this way:
A- Color gradient, Levels, and shadows and highlight (ON ADJUST LAYER). This use de 100% of the CPU
B- Color gradient, Levels, and shadows and highlight (ON ADJUST LAYER) Denoiser II (ON THE CLIP). This use -25% of the CPU
C- Color gradient, Levels, and shadows and highlight, Denoiser II (ON ADJUST LAYER) This used -25% of the CPU
The problem is the Plugin it self, may be some of you can find why?
Re: Denoiser II by Chris Wright on Apr 30, 2016 at 6:45:35 pm
I haven't done extensive test, but a lot of people seems to have problems with denoiser and neatvideo not using cpu 100%
both denoiser and png images don't like multithreading so they choke.
neatvideo has an optimize button so that it doesn't run into this problem. it's a thread vs cpu/ram problem.
multithreading off may change your render speed. you can test this feature.
The most important thing is to denoise clips by themselves either before or after intermediate rendered clips and not
stack them with lumetri, special effects etc. The most recommended workflow is the smart rendering feature using supported filetypes.