Vegas 18, does anyone max out pc performance with gpu encoding?

RealityStudio wrote on 9/14/2020, 3:00 PM

I know this question has been coming up for over decade now, but I wanted to follow up since we have a new version of Vegas out. Just curious, is anyone able to get Vegas 18 to fully use their pc? I have a 12 core AMD 3900X Ryzen cpu along with an NVidia 1080ti, and from the performance charts I attached my pc is basically snoozing when Vegas 18 renders, it just doesn't use much of it at all. It still *much* faster than without gpu assist (I've timed it) but still, it would be great to know of there is some setting that would let Vegas actually take full advantage of my pc to speed up render times. For reference my videos are very simple, a single 4k file from a Sony A73 camera, a single watermark applied, and a single Film Convert visual effect applied which supports gpu, that's it. Note the gpu graph trails off at the end because the encode had just finished.

 

Comments

RogerS wrote on 9/14/2020, 9:16 PM

I assume you are using a NVENC render template? I rarely see above 20% on my 1050, so I think Vegas is working as designed.

VCC wrote on 9/14/2020, 9:25 PM

Does anyone here know of a site where we can post our video to get feedback on becoming better at our craft? DP Review does photos, but who does video?

RogerS wrote on 9/14/2020, 9:31 PM

@VCC Maybe you should start a new thread with this question? It will get lost here.

RealityStudio wrote on 9/14/2020, 9:47 PM

I assume you are using a NVENC render template? I rarely see above 20% on my 1050, so I think Vegas is working as designed.

Yeah using NVENC template, would be a shame if that is normal performance. Anyone know if other video editing programs have the same limit to where they can't use more than 20% to 40% of the gpu? That's basically the range mine bounces between, hence the spikes on the performance graph. I think the NVidia 30xx cards have a newer generation of NVEnc/Dec so I'll have to try those as well when they are available.

lenard-p wrote on 9/14/2020, 10:04 PM

Nvidia 3000 series have the same NVENC encoder as 2000 series. The problem is not the hardware encoder though. VegasPro can not serve it rendered frames fast enough for it to encode. Try Handbrake transcoder to see if that uses more CPU or GPU

RealityStudio wrote on 9/14/2020, 10:51 PM

Nvidia 3000 series have the same NVENC encoder as 2000 series. The problem is not the hardware encoder though. VegasPro can not serve it rendered frames fast enough for it to encode. Try Handbrake transcoder to see if that uses more CPU or GPU

Ah ok that makes some sense as when I watch it, it will render a bunch of frames, then stall, then render some more, stall, and keep doing that for the duration of the encode.

I've avoided using Handbrake + Vegas because I've seen so many people have issues with it, and I use Vegas for my business so I just need things to work 100% of the time, I don't have time to tweak and fiddle with stuff anymore alas.

Oh well I guess it's something I'll have to live with.

RealityStudio wrote on 9/14/2020, 11:11 PM

Any idea what holds Vegas back from generating the frames? It doesn't seem to be my cpu as it's mostly sleeping during rendering, and likewise for the gpu it's also mostly asleep. So I'm curious what the bottleneck is and can it be corrected. I know NVidia has their Gpu Direct Storage that lets a machine shuffle data from m.2 storage right to the gpu bypassing the cpu completely, maybe Vegas supporting something like that would help?

RealityStudio wrote on 9/14/2020, 11:13 PM

Read this thread for more comments.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-barely-using-available-system-resources--121256/#ca755285

Cool I'll check it out.

EDIT: I took a look but didn't see anything useful there aside from running multiple instances of Vegas. That's not applicable to me as I do one project per video shoot (for a bunch of reasons I won't go into) so I can't run multiple instances of Vegas.

lenard-p wrote on 9/14/2020, 11:52 PM

Any idea what holds Vegas back from generating the frames? It doesn't seem to be my cpu as it's mostly sleeping during rendering, and likewise for the gpu it's also mostly asleep. So I'm curious what the bottleneck is and can it be corrected.

Software not optimised for processors of today. Have you tried voukoder, it's a free 3rd party plugin that adds Voukoder to your render options. It speeds up encoding for me by more than 20%. It has a number of encoding options including x264 and NVENC hardware encoding

 

RealityStudio wrote on 9/15/2020, 12:27 AM

Any idea what holds Vegas back from generating the frames? It doesn't seem to be my cpu as it's mostly sleeping during rendering, and likewise for the gpu it's also mostly asleep. So I'm curious what the bottleneck is and can it be corrected.

Software not optimised for processors of today. Have you tried voukoder, it's a free 3rd party plugin that adds Voukoder to your render options. It speeds up encoding for me by more than 20%. It has a number of encoding options including x264 and NVENC hardware encoding

 

Hmm I haven't, I wonder if it plays nicely with Vegas scripting. Like I have a script I wrote which when I run will render every clip on my project timeline, make directories for each clip with correct names, render various versions into those directories, etc. Guess I'll test it and find out.

EDIT: Actually going to wait on that for now. I checked the Voukoder forum and there seem to be issues with it and Vegas as Voukoder for Vegas 18 is still in beta. I'll just stick with what I have, it's slow but reliable so it'll have to do for now. Thanks everyone!

RogerS wrote on 9/15/2020, 1:20 AM

Voukoder is great, I use it and help bug test it. I am not aware of current issues with it beyond one user crash report, and Voukoder 6.2 with the new connector is a stable release. It's worth a try.

Anyway, if you decide to compare software, rendering times and quality are more important than GPU % utilization. Someone here once compared it to focusing on your car engine's RPMs rather than how fast you are getting to your destination.

andyrpsmith wrote on 9/15/2020, 5:14 AM

Voukoder is great, I use it and help bug test it. I am not aware of current issues with it beyond one user crash report, and Voukoder 6.2 with the new connector is a stable release. It's worth a try.

Anyway, if you decide to compare software, rendering times and quality are more important than GPU % utilization. Someone here once compared it to focusing on your car engine's RPMs rather than how fast you are getting to your destination.

One issue I have with Voukoder (using default for H264) is the rendered image has slightly less colour saturation than Magix AVC and Sony AVC encoders.

Marco. wrote on 9/15/2020, 5:20 AM

Mine match the source. Are you sure this isn't a full/limited range thingy?

andyrpsmith wrote on 9/15/2020, 5:27 AM

I will have another look but I think the project was set as 8 bit full range with the settings also set for this on template tab in Sony/Magix encoders. Voukoder is very fast when using GPU fast option though.

andyrpsmith wrote on 9/15/2020, 5:48 AM

Yes I forgot to change the project tab in Voukoder to full - oops. Thanks

RealityStudio wrote on 9/15/2020, 4:16 PM

So I did end up trying Voukoder. It is indeed a little quicker mostly because the stalls are removed, but the machine still for the most part sleeps, both gpu and cpu aren't used much. I did a 4k 30 second encode as a test and tweaked the Voukoder setting to get the file size to be fairly close to my Vegas encoder sizes. It took Vegas 37 seconds to encode it, and Voukoder took 32 seconds. So a little quicker but my pc is still mostly unused.

The other issue I saw, or at least I could not find the setting for it, is to have Voukoder render out at different resolutions. For example, my Vegas script renders out multiple versions of every video on my timeline in named folders at certain resolutions, but I couldn't see how you can have similar multiple encoding templates with Voukoder to where I could mod my script to output various resolutions of the videos.

In any case I think I got the info I need, I'll just stick to stock Vegas for now. Maybe one day they can figure out how to use current hardware to it's full potential.

lenard-p wrote on 9/15/2020, 4:28 PM

There are lots of people like you that have AMD CPU's 12-16 core cpu's that see exactly the same problem as you, but I could swear some people also have screenshots of their cores mostly utalised at a high percentage. If you turn off GPU processing and do a software encode, will it use much more of your CPU?

Not a solution, just wondering

RealityStudio wrote on 9/15/2020, 5:22 PM

If I turn off gpu encoding then it will peg my 12 core cpu at 100%, but it's much slower than using the cpu+gpu in spite of both of them being heavily underutilized.

RogerS wrote on 9/15/2020, 9:17 PM

Voukoder follows project settings. You can also go into the Voukoder dialog and add a "zscale" filter and change the resolution.

RealityStudio wrote on 9/15/2020, 10:07 PM

Voukoder follows project settings. You can also go into the Voukoder dialog and add a "zscale" filter and change the resolution.

Unfortunately that wouldn't work for me as I heavily use scripting, so I need to be able to save multiple presets right in the Vegas render dialog box so that Vegas scripting can call on them as needed. No biggie, I figure one day the Vegas crew will fix the bottleneck.