Performance issue while rendering Vagap Pro 12 + Neat v3.4

resolve technical issues related to use of Neat Video
Post Reply
shali007
Posts: 1
Joined: Thu Jul 18, 2013 10:02 pm

Performance issue while rendering Vagap Pro 12 + Neat v3.4

Post by shali007 »

Hello I've just started using Neat video this week.

Rendering times have increased dramatically.

Is this expected ?

Video source is AVCHD 1080p , output is 1080p mp4
Rendering time have increased, I guess , about factor of 10.

What make me wonder is that I see in the performance monitor that cores are about 10-30 % loaded , while rendering without NeatVideo , I can see all 8 cores are at 100%.

Win7 Ultimate 64bit / i7-3770 @ 3.4 GHz/ 16 GB / GeForce GTX 670
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Post by NVTeam »

In general, yes. Neat Video is a very computation-intensive filter, it takes time to render.

Please open Neat Video's Configure window, then go to menu Tools > Preferences > Performance > Optimize, run the test and let me see the log from that test.

Thank you,
Vlad
BuDyNlan
Posts: 3
Joined: Tue Aug 27, 2013 6:57 am

Post by BuDyNlan »

Welcome. I have the same problem. Vegas Pro 11 and NV 3.4. running at about 30% of the computer performance. what to do to run at 100% of the computer?
NV settings on the CPU only.
NV settings for the CPU and GPU works the same way.

Now NV is working too slowly. Work faster!
Please Help!

I5 2500K/8GB DDR3 / Nvidia GTX 260

Image
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Post by NVTeam »

Which version of video driver do you run?

Thank you,
Vlad
BuDyNlan
Posts: 3
Joined: Tue Aug 27, 2013 6:57 am

Post by BuDyNlan »

Video Card Driver 320.49-desktop-win8-win7-winvista-64bit-international-whql

motherboard Asus P8P67 evo
Intel_Chipset_V9301019_XPVistaWin7

Working efficiently on CPU only. I use the CPU only.

Once NV worked faster. the same computer.
NVTeam
Posts: 2745
Joined: Thu Sep 01, 2005 4:12 pm
Contact:

Post by NVTeam »

That version of the video driver is known for creating such a problem. I recommend to either downgrade the driver to 314.22 (release version) or to upgrade to 326.41 (beta) or newer version. 314.22 did not yet have that problem and 326.41 seems to have it already fixed.

Hope this helps,
Vlad
Last edited by NVTeam on Tue Aug 27, 2013 10:51 am, edited 1 time in total.
BuDyNlan
Posts: 3
Joined: Tue Aug 27, 2013 6:57 am

Post by BuDyNlan »

ok I'll try.
Post Reply