SONY VEGAS + i7 2600K + 8GB RAM + NEAT VIDEO = SLOW RENDERING?!

[Demetris Christodoulides]

Btw, i wanted to add the following:

This is the card i am talking about ASUS – Graphics Cards- ASUS GTX680-2GD5 https://www.asus.com/Graphics_Cards/NVIDIA_Series/GTX6802GD5/ will i see any worthy difference or will it be money thrown away? Would it be better strictly for video applications (i am not dealing with graphics or animation) to opt for quadro? ‘Cause sony shows otherwise in their gpu benchmark site which i linked above.

Thanks a lot!

[James Wilhelmi]

Demetris christodoulides – What am i doing wrong?

Nothing. From what I’ve read on a previous post, neat video takes an extremely long time to render even with a super-fast processor. Considering your timeline is 2hrs, it may just be the nature of the beast. I would render a 10sec test clip to make sure it will look the way you expect it to, check your timeline to make sure everything is correct, then render away. Good luck!

James

[Demetris Christodoulides]

Thank you, already did and i tested it, looks great but kills the pc! So opting for a much more expensive gpu won’t do any trick you say? thanks!

[James Wilhelmi]

Sorry,I don’t believe it would.

James

[Bryan Powers]

V3 renders faster than V2 but it’s still pretty slow. It took 5hrs for a half hour project. Neat video works great though but the render times are killer.

[Mikhail Petrushin]

If you render your project using 2 passes encoder’s settings that you can try to reduce your render time almost twice by spliting the render into 2 steps:
1. Render the project into temp file using loseless codec (lagarith for example).
2. Open the resulting file in Vegas and render it with settings that you need.

NeatVideo plugin is extremely slow (and very effective as well) and if you render with 2 passes encoding it does its job twice.
If you render it to a temp file (loseless) it will work only once.
Unfortunately, you need a huge amount of free space for the temp file.

P.S. This is just an idea, I haven’t tried it yet 🙂

[Scott Francis]

Neat video processes EVERY frame of video when it is used, removing or adjusting the noise in each….this is extremely processor and time intensive…..but a stated above….works really well!

Scott Francis
Mind’s Eye Audio/Video Productions

[Demetris Christodoulides]

Indeed, and i have no problems with it. But cpu usages is continuously at 30-40% and ram is at 40% all the time so this is why i assumed it has something to do with the gpu. But it seems it doesn’t?

Also, maybe i should mention that i haven’t messed anything in the settings of the programme, the dynamic ram preview is by default set to 200 and maximum number of rendering threads is at 16. I generally read that by messing with those, you usually get negative results so i left them untouched.

Thanks guys

[Scott Francis]

What are you rendering too as far as format? If I am rendering to any form of AVCHD I turn OFF GPU under the rendering settings….if it is set to automatic I find it takes quite a bit longer to render a file….

Scott Francis
Mind’s Eye Audio/Video Productions

[David Lightman]

The key omission from your setup list at the top is version of Neat Video you’re using.

As Bryan mentioned Version 3 (or now 3.1) is a much faster than version 2. Version 3 is at least 2x as fast as V2 (2.6 etc) when only using your CPU. Version 3 (released last winter) also now supports CUDA GPUs for another 2x to 4x speed boost (Version 2 didn’t use GPUs at all)

It does add a lot of time to renders but the difference between version 2 and 3 is huge. Using only Neat Video HD projects in the 1.5hr range could take 30+hrs to render on my i7 2600 + 560TI. With version 3 the same projects take 6 to 8hrs to render (usually just run them overnight).

If you’re using V3 there’s a benchmark tool located in Tools/Preferences/Performance . That’ll show you the FPS for each frame radius setting using different number of CPU cores and w/ or w/o GPU. Pick the setting that yields the highest FPS.

Based on those benchmarks you can also lower (or disable) the Temporal Filter radius. The default is one frame but if you change that to 0 rendering will definitely speed up. Depending on the project the temporal filter might not make all that much difference anyway.

Hope this helps a bit.