Disc Z and the GPU are at 100% so they appear to be your bottleneck.

I can't tell you how to render faster as you didn't click on either of these in the video and only showed details for the CPU.

Try a template with NVENC (MagixAVC with NVENC) if you aren't already. Beyond that certain Fx aren't well optimized so may slow things down a lot.

Media is another factor- VEGAS has to read the file to write it. What media are you editing?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

If you'd like to try a benchmark feel free to try one in my signature and report your results.

I did your benchmark, the results are there.

What I notice is that when there is more editing that actually weighs, this bottleneck does not occur, it has a more constant framerate.

here is performance information of all task manager performance monitor

here is performance information of all task manager performance monitor

I noticed that in my normal videos (without much editing) it renders 60 frames and stops for half a second and then renders another 60 frames.

This break bothers me a little, is there a way to resolve it?

Could it be due to a lack of video memory?

the GPU at 100% is because of the recording

The benchmark times look fine for 21.315 which is a slow build for certain Fx. Media decoding is better in 21.300 and 315 but certain Fx don't seem to be GPU accelerated so are slower.

The video recording here looks normal- both the GPU and CPU are working hard. I see decoding, encoding and 3D calc activity on your GPU so all looks good.

Unless you make dynamic ram previews I'd set it back to 5% and free up ram for other purposes.

I'd say the bottleneck is something specific to your project. For me 208 was the fastest build of 21 (but didn't work so well with NVIDIA decoding). 22 is overall better performing than 21.315 so I'm using that now (22.239 is the latest).

The benchmark times look fine for 21.315 which is a slow build for certain Fx. Media decoding is better in 21.300 and 315 but certain Fx don't seem to be GPU accelerated so are slower.

The video recording here looks normal- both the GPU and CPU are working hard. I see decoding, encoding and 3D calc activity on your GPU so all looks good.

Unless you make dynamic ram previews I'd set it back to 5% and free up ram for other purposes.

I'd say the bottleneck is something specific to your project. For me 208 was the fastest build of 21 (but didn't work so well with NVIDIA decoding). 22 is overall better performing than 21.315 so I'm using that now (22.239 is the latest).

So, I wanted to use version 22, but it's very expensive for someone living in Brazil. It costs 600 BRL (a half of minimum wage) just for the upgrade. There should be a way for me to exchange my version 21 for 22 without having to pay. From the beginning, I actually thought it was...

But thank you for your attention and your benchmark!

If you get the VEGAS subscription you always have the latest version. You're right that if you have the perpetual/one-time purchase license that you have to pay to upgrade from 21 to 22.

The BRL price seems similar to the US one in absolute terms, which is unfortunate as US salaries are far higher.

@zBicudin have you tried Voukoder plugin? I believe that might be the answer for eveyone who renders large video files. The plugin is now discontinued after initial release for vp22 but the vegas pro 21 and older works perfect. It has been an essential part of my workflow as I don't have to switch between laptop and pc anymore while my pc used to render as I did the editing on my laptop.

@zBicudin have you tried Voukoder plugin? I believe that might be the answer for eveyone who renders large video files. The plugin is now discontinued after initial release for vp22 but the vegas pro 21 and older works perfect. It has been an essential part of my workflow as I don't have to switch between laptop and pc anymore while my pc used to render as I did the editing on my laptop.

No, I will test to see if it improves these pauses in the render.

Voukoder Classic doesn't have the render pauses so is somewhat faster but I think you have other bottlenecks before the encoding stage, so I'd be surprised if you see a large difference.

@zBicudin @BiswasArt Yes Voukoder is now only Voukoder Pro but Voukoder classic can still be downloaded &
works in VP22...

choose - Voukoder 13.4.1 msi (Windows installer package)

& the connector connector-vegas22-1.0.0 or connector-vegas21-1.7.1

This solved my problem, the videos I usually render are no longer pausing while rendering.

Voukoder Classic doesn't have the render pauses so is somewhat faster but I think you have other bottlenecks before the encoding stage, so I'd be surprised if you see a large difference.

@RogerS I agree with you, but in most cases, I render videos with little editing and effects, so my computer has some spare capacity.

Render without voukoder NVENC h264

Render with voukoder in the same settings (NVENC h264)

@zBicudin Hi, glad that helped, can you open this drop-down in the render window to show the final rendering duration? How long it took between the two when completed?. 👍

@zBicudin Hi, glad that helped, can you open this drop-down in the render window to show the final rendering duration? How long it took between the two when completed?. 👍

I separated a 1-minute part of the video and rendered it again in both.

VOUKODER H264 2k60fps NVENC

MAGIX AVC H264 2k60fps NVENC