Curious which ProRes format you are using... ProRes422 HD doesn't usually need a proxy for editing. In any case, the native Vegas-created proxies are bypassed for rendering. Just choose a render template for Nvidia encoding. Such as a Magix template marked "(NVENC)" like this:

The equal signs on the left mark the templates that match the frame-rate of the project. You can verify gpu usage by looking at Windows Task manager performance charts:

If that shows the gpu being used for rendering, the slow render rate is due to something else. ProRes XQ 4444 media?

from a Prores 1920x1080 50p clip. 

"from" is not the question.

What exactly are you rendering "to?"

Unless you are rendering "to" a GPU-accelerated encoder template, it will not utilize any GPU acceleration.

If you mean you are rendering a Vegas Proxy file, that is MPEG-2 XDCAM-EX, which is not a GPU-accelerated format; instead, it is 20 year old software encoding technology, one of the faster ones from that era.

If you want a GPU-accelerated "proxy," which should be entirely unnecessary on your system, render normally to one of your Nvidia AVC/HEVC templates. Simple.

@P0rp01s31954 said: “... currently rendering a proxy file @ 0.77 fps! from a Prores 1920x1080 50p clip.”

Proxy shouldn’t be necessary for that media

Hi John,

Thanks for your input.

That's what I thought but for some reason, the approx. 15 minute ProRes 422 HD clip isn't playing nice on the timeline. Yet hardly any resources are being used. That's why I thought I'd render an mp4 as a proxy to edit with. I just can't fathom what the issue might be.

Normally, an Nvenc MP4 would render in next to no time but it took hours (with hardly any resources being used!).

I'd consider opening the problem file in another application to see if it also struggles with it. Shutter Encoder can process Pro Res to other media types, including Pro Res.

Maybe it will clean it up if the source file is corrupt.

I don't use NVENC, but Pro Res to QSV. (Something I also never do.)

Hi - an update to this issue:

I have absolutely no idea what the problem was but having come back to this project after getting on with other stuff, whatever the issue was, seems to have fixed itself??!!?? Plays perfectly on the timeline and renders in just ove 6 minutes. (45 minute talking-head clip).

However, I have a different issue which has raised its ugly head (+ another 3 clips of roughly the same length from the same shoot) and it seems to be an issue woth frequency of the led ceiling down-lights causing a strobing effect (10 second clip attached)

and I can't seem to find any relevant tool in Vegas for fixing it.

Had several issues on the day of the shoot with sound and lighting and am trying to do the best of a substandard shoot. (No control over sound or lighting)

My system is set up as 50Hz PAL (UK) but I suspect the LEDs may have been at 60Hz?!

Does anyone know if there is a way to fix this, or will they just have to live with it?

@P0rp01s31954 Hi, try Vegas Flicker control - Flicker reduction

@P0rp01s31954 Hi, try Vegas Flicker control - Flicker reduction

That's brilliant - thank you!

I don't suppose you could provide the settings you used... 😁

@P0rp01s31954 👍

They're the default settings. this is that picture that I posted, I cropped it to make it easier to see, there's nothing to the right that is set.

PS. It's customary to mark the persons comment that provided the solution not your own, but seeing as this post is titled 'GPU rendering' & your problem fixed itself maybe there shouldn't be any comment tagged as the solution.

My RTX4090 renders a particular 4K project in 33 minutes using the NVIDEA template while it takes on 18 minutes for the Intel Template. Seems that with the Intel template both video processors are used.

My RTX4090 renders a particular 4K project in 33 minutes using the NVIDEA template while it takes on 18 minutes for the Intel Template. Seems that with the Intel template both video processors are used.

Your are right - you can utilize the intel GPU especially for decoding (part of many CPUs today) and an nvidia GPU for the effect calculation in Vegas.

My RTX4090 renders a particular 4K project in 33 minutes using the NVIDEA template while it takes on 18 minutes for the Intel Template. Seems that with the Intel template both video processors are used.

@Bofus Nvidia encoding is slow on Vegas, it's been like that since 2017, it stops and starts. You don't have 2 Intel hardware encoders, if you had an intel cpu with an IGPU and an Intel GPU it would work how you have described. Intel template doesn't use Nvidia encoder at the same time as Intel encoder.

Your 4090 has 2 NVENC video encoders of it's own, not sure if Vegas uses them. Nvidia only uses the dual NVENC's for HEVC and AV1. What you've done is created a hypothesis based on your results which does not factor in that Vegas doesn't properly utilize the Nvenc encoder. It has to start and stop constantly. Also Nvidia decoder is faster than Intel.

The difference between your intel and Nvidia hardware encoding is much larger then I would expect to the point that this may be another VP21b315 issue, Is that what you're using? Have you looked at task manager while using the Nvidia Nvenc encoder, is there activity in 'Video Encode'

Feel free to try the benchmarks in my signature and play close attention to the settings. NVENC and QSV shouldn't be so different in time if the settings are similar.

@Bofus Nvidia encoding is slow on Vegas, it's been like that since 2017, it stops and starts.

I'd love to see improvements on this, I have an AMD CPU with no integrated graphics.

00.52sec UHD CFR event.

Vegas Magix HEVC - 26secs to render,

Voukoder - 20secs to render, the progress flows along fairly smoothly

& just for the hell of it - Intel QSV - 59secs

The third one isn't actually QSV it's the CPU doing all the work as your graphs show.

Voukoder isn't that much faster than the "slow" native implementation of NVENC.

@RogerS I was just calling it by the name in the render options,

& Voukoder on that very quick test is 1/5th faster, I'd need to a longer test but if a Magix render takes lets say 30mins, Voukoder would be n the 24min range,

----------------------

The same 13mins of UHD CFR events.

Magix HEVC (NVENC) - 8.22mins

Voukoder - 5.07mins

@Gid Out of curiosity, when you click on the HEVC (QSV) template does the encode mode say QSV or Mainconcept HEVC? I'd assume the latter for a non-Intel system but don't know as both my systems have QSV.

@Gid Out of curiosity, when you click on the HEVC (QSV) template does the encode mode say QSV or Mainconcept HEVC? I'd assume the latter for a non-Intel system but don't know as both my systems have QSV.

@RogerS I don't use this one so it'll be at it's defaults i assume

---------------------

I just changed it to Mainconcept, I used to change it to that if there were pictures/text along with video in the project because NVENC sometimes used to put those pictures/text in the wrong place in the rendered out file, I haven't noticed that recently so I use NVENC or Voukoder now. (I've never really used the QSV option as I don't have intel or Integrated GPU 🤷‍♂️)

This is the 13min test with Mainconcept. - 9.11mins

--------------------

But don't get me wrong, I'm not complaining,

My projects are often simple events with a 12frame crossfade, I used MMS (Magix Movie Studio) for many yrs & when they added the Infusion Engine export times were incredible, I upgraded to VP18, then 19, 20 & now 21, but with 18 & 19 I found myself going back to MMS to do these simple projects & using Vegas for effects/Mocha etc., At the end of a night's editing a 20min project the difference was something like 18mins with Vegas & only 8mins with MMS, I often then wanted to upload to YT that night for it to be ready the next day to publish & make public. So that 10min difference was a lot esp if I had to fix a mistake & render again after watching/reviewing the rendered project.

But I've seen significant improvements with VP21, render times are faster & stability is next to spot on, I can't remember the last time I had a crash (I like to play with Boris's fxs that would crash previous versions often).

This is MMs exporting those same 13mins events. 5.30min compared to Vegas's 8mins or Voukoder's 5mins is not a massive difference, I very rarely open MMS anymore.

I assume the QSV on an AMD CPU and Mainconcept is the same thing and takes the same time but odd VEGAS says QSV.

I believe the out of order text/picture issue with NVENC was fixed with build 300 or newer- I haven't seen it anymore.

I agree VP 21 is catching up in terms of performance, stability and GPU support and hopefully will be on par with MMS before long. I just want all the upsides without any annoying downsides that waste my time.

I assume the QSV on an AMD CPU and Mainconcept is the same thing and takes the same time but odd VEGAS says QSV.

Yeah I don't understand that bit.

I believe the out of order text/picture issue with NVENC was fixed with build 300 or newer- I haven't seen it anymore.

Yep, it did seem to go away about that time.

I agree VP 21 is catching up in terms of performance, stability and GPU support and hopefully will be on par with MMS before long. I just want all the upsides without any annoying downsides that waste my time.

👍👍

I've been playing with the File I/O options, I even reverted back to (208) for a bit to see the difference, I'm now back on (315)

My files are HEVC, every CFR shows unquantified ends & sometimes at the starts of the event, it doesn't matter which Project setting is used, Experimental HEVC doesn't create or show these unquantified frames but the File IO plugin in the file's properties changes, 🤷‍♂️

This is render to a new track with nothing ticked in File I/O, unquantified frames start & finish.

When I'm editing my clips get trimmed start & finish which removes these partial frames so it's not a big deal but I would like this resolved before the 22 release would be nice, you can't just move on to the next version after leaving the previous version's builds in such a state, & there's been pretty much 0 feedback from the few @Vegas....'s that comment on here.

I simply don't know which option or build no' to choose so I've stuck with the latest with nothing ticked in File I/O🤷‍♂️

The unquantized frames, unread video levels metadata, occasional garbled decoding with NVDEC, state of speech to text, etc. has me back on 208 though I very much see the promise of 315.

 

@Bofus Nvidia encoding is slow on Vegas, it's been like that since 2017, it stops and starts.

I'd love to see improvements on this, I have an AMD CPU with no integrated graphics.

00.52sec UHD CFR event.

Vegas Magix HEVC - 26secs to render,

Voukoder - 20secs to render, the progress flows along fairly smoothly

@Gid I haven't been using Vegas lately, but if I recall correctly largest slow down is with 720P, followed by 4K, with 1080P the least amount of slow down. They started enhancing decoding and playback in VP21, by the look at things at this late stage they'll still be doing that in VP22, buy hopefully optimize NVENC encoding too.

The speed issue with Vegas mostly annoys me when I do multiple re-renders the native Hardware encoders are slow, and Voukoder is faster, but even voukoder encoding is slow compared to how fast some of the codecs playback in Vegas now,

Resolve vs Vegas, playback is often just as good on both now(speed wise) but for a given HEVC 5K 10bit file I get 125fps encoding to HEVC Nvenc on Resolve and 55fps on Vegas, both via Voukoder encoding to 4K. It's like they have left so much performance on the floor because both NLE's playback fine at 4x 120fps in best quality/resolution but all that speed is lost going to the encoder.

@Todd-AO 👍 Do you have Adobe PP? I used to have AE, however much people hype about it playback wasn't great until it prerendered, that prerender works in two directions at the same time, backwards & forwards from the cursor/marker doubling the speed of the prerender, this is auto also so no Shift+B etc. needed, it just does it itself. + I'm fairly sure this prerender is used in the export, I can't remember so I might be wrong? Resolve also has a Smart cache option,