VP17Edit versus VP18Edit for gaming videos.

dape wrote on 8/5/2020, 9:01 AM

So i just bought VP18Edit and configured just like VP17Edit. Having a 33,5 GB HEVC file (~ 65 Mbits of 1 hour and 10 minutes) generated by OBS on a RTX2080Ti i proceeded with encoding (AVC for YouTube: 1080p60, 12 Mbit, 192 Kbit) in both last versions.

Unfortunately not much difference on my system:

VP17 - CPU hovered around 25% (max 30%) - both versions had set 6 cpu threads in options and GPU was max 45%. Finished the rendering in 34 minutes.

VP18 - CPU almost the same and GPU was definately much lowered used.. maybe 35% iirc. Finished in..37 minutes and almost all the time told me it was using 2 gb of memory.

later edit: i see that VP18 has two pass for NVENC now.. will test it soon.

second edit for fr0sty: Ryzen 3900X + NZXT X62 280mm, 32 gb ram, 1 gb ssd, rtx2080ti.

Comments

fr0sty wrote on 8/5/2020, 9:13 AM

Here's my results: What are your system specs?

dape wrote on 8/7/2020, 5:38 AM

Well.. i installed Voukoder 5 with the VP18 connector and it seems quite fast! The cpu went to 40-45% while GPU seemed like with VP original encoder.

So.. VP17 34 min, VP18 37 min and Voukoder 22 min ! Visual result seems as good as Vegas' original encoded file, almost same size.

Former user wrote on 8/7/2020, 6:05 AM

later edit: i see that VP18 has two pass for NVENC now.. will test it soon.

I think it's look ahead mode, but that is automatic in high quality setting for Nvenc, so i'm not sure it does anything. Please test

andyrpsmith wrote on 8/7/2020, 6:22 AM

Here is my quick comparison. Project length 6mins 14sec, 39 clips 4K rendered to Bluray HD with sony AVC 24p GPU template, Intel 3rd gen ivy bridge proc i5 @ 4GHz, 16GB ram of which Vegas typically uses 7GB, GPU 1080Ti. V17 render = 9mins 40sec, V18 render 7mins 8sec.

RogerS wrote on 8/7/2020, 8:26 AM

@dape Thanks for sharing with Voukoder. Are you rendering to x.264 using one of the templates? I'm having issues using Voukoder with CPU mode- it's very slow and takes a few minutes just to close the render. For NVENC it's impressively quick.

dape wrote on 8/7/2020, 8:32 AM

@dape Thanks for sharing with Voukoder. Are you rendering to x.264 using one of the templates? I'm having issues using Voukoder with CPU mode- it's very slow and takes a few minutes just to close the render. For NVENC it's impressively quick.

Of course not x264... Time is money and i cannot afford to wait for cpu rendering even on my beast of PC. I used Voukoder NVENC AVC with High Quality and Bluray presets on a 1080p60 movie rendered for 12 Mbit for YouTube.