Trouble Rendering/Exporting Neat Video Noise Redcution Plug-in

[Joe Barta iv]

We apply Neat Video and render the entire timeline as ProRes. That way we know the plugin has been applied and has rendered correctly. Then on Media Export choose ProRes to match the rendering of the timeline and then select Use Previews. After we have an exported ProRes then we use Encoder to make whatever file we need.

Bars & Tone
SALUTE!

[Rex Polanis]

Thanks for the advice, I’ll give that a try.

One man with courage makes a majority.

Canon 7D
Adobe CC Master Suite
Digital Juice
Video Copilot

[Jeff Pulera]

Hi Rex,

You won’t have the ProRes option on the PC. You might try installing the FREE Lagarith codec and then export only the Neat sections of timeline as .avi files using Lagarith. The quality is lossless. If the export works, then drop the new clip(s) onto a higher track in the sequence directly over the originals, then export the whole works to format of choice.

I don’t use Neat – I have Red Giant DeNoiser II – but due to extreme render times and such, I do pre-render those segments rather than trying to “do it all at once”.

Of course, one could simply use the ENTER key to render parts of the timeline from red to green, then in AME check the box for “Use Render Previews”, however most sequences will use “MPEG I-Frame” as the preview format, with no way to adjust the quality at all, so who knows what quality you would get. I just position the work area bar in the timeline and manually export (render) what I want to and import the results. I do have the Matrox MXO2 hardware and generally use the Matrox codec, but Lagarith comes in handy as well.

Thanks

Jeff Pulera
Safe Harbor Computers

[Rex Polanis]

Thank you guys with the help. I was curious if anyone else was having this issue.

I did post on the neat video forums and I got a response that has helped me narrow down the issue.

As noted, the neat video noise reduction plug-in is processor intensive as it requires a lot of power to cleanly remove noise and produce a quality image.

Part of my issue is that my processor (AMD FX 8150 over clocked to 4.6Ghz) over heats from the intense processing required. This overheating is the result of a combination of how hard I push the processor and the algorithm neat video uses to remove noise.

The second part of the problem is that there appears to be a driver issue with my video card: AMD FirePro v7900. The neat video plug-in is not able to detect the Open CL ability of my card and therefore places all the plug-in computation on the processor.

One solution that has worked, yet doubled the render times of clips using noise reduction, is to reduce the number of cores the plug-in uses to remove noise from 4 to 2.

My next steps to correct the problem is to resolve the driver issues with the AMD video card.

I’ll post my solutions once I get everything worked out.

Thank you guys for responding.

One man with courage makes a majority.

Canon 7D
Adobe CC Master Suite
Digital Juice
Video Copilot