Are you using the color grading panel? That's known to be much slower in 21.300 than 20 or older versions.

Beyond that the video engine has changed in 21 from 20 and should be faster but struggles with some media. Try NVIDIA decoding in preferences, file io and rendering to NVENC instead of QSV.

Feel free to try the benchmarks in my signature and we can see if performance is as expected vs similar hardware (great system, btw).

Nope, no color grading. I ran your benchmark project and no matter what the settings it's taking around 3 minutes for the render when most people on the spec sheet are getting around 1:30. Is it a Win 11 thing? Here's screen shots of all info I can think to provide. It's also strange that task manager shows 80-100% cpu usage when I NEVER had that rendering QSV previously, yet cpu usage from Vegas is showing only 10-20%. I also did another fresh install of windows today just to be safe. Literally nothing installed but windows, nvidia drivers and vegas. Something has to be off. One thing the benchmark sheet doesn't seem to have is what version of windows everyone is on.

Even ran Cinebench JUST in case to make sure everything's clicking right and yes it matches stock 13900K performance

PLEASE I'm in dire need of help as my wedding season begins tomorrow. Upgraded from windows 10 to 11 and from version 20 to 21 (300) All same hardware. 13900K, 64GB, 3080ti. I'm rendering 4K 10bit HEVC footage and rendering Magix AVC/AAC Intel QSV. Project properties just 8 bit (I know 32 bit is extremely slow) On Windows 10 and VP 20 I'd get around 20fps and 40-60% CPU usage. Now I get 90-100% CPU usage and 9-10fps. SAME timelines, same effects. Same thing with no effects. I've tried EVERYYYTHING I could think of. Checking/unchecking legacy avc hevc decoding, rendering other formats. Please, any help would be appreciated, this is mind boggling and disappointing.

If you have a Nvidia GPU try fully uninstalling the driver software using this Display Driver Uninstaller (DDU) download version 18.0.7.5 (guru3d.com) and the re-install

I had an issue like this about two years ago and it fixed the problem

Are you using the color grading panel? That's known to be much slower in 21.300 than 20 or older versions.

Beyond that the video engine has changed in 21 from 20 and should be faster but struggles with some media. Try NVIDIA decoding in preferences, file io and rendering to NVENC instead of QSV.

Feel free to try the benchmarks in my signature and we can see if performance is as expected vs similar hardware (great system, btw).

Nope, no color grading. I ran your benchmark project and no matter what the settings it's taking around 3 minutes for the render when most people on the spec sheet are getting around 1:30. Is it a Win 11 thing? Here's screen shots of all info I can think to provide. It's also strange that task manager shows 80-100% cpu usage when I NEVER had that rendering QSV previously, yet cpu usage from Vegas is showing only 10-20%. I also did another fresh install of windows today just to be safe. Literally nothing installed but windows, nvidia drivers and vegas. Something has to be off. One thing the benchmark sheet doesn't seem to have is what version of windows everyone is on.

My desktop is Windows 11 (look for RogerS) so no particular issues there as far as I'm aware. You can also see the performance drop from 208 to 300 for projects like this that use multiple Fx (I did tests with both my systems).

For VP 21.300 I'd try NVDEC decoding over QSV unless you are editing 10-bit 422 HEVC. If you are, keep it on QSV and check "enable legacy AVC decoding) in preferences, file io.

I'd also test NVENC and see if you get better performance than QSV. I'm seeing a slowdown with Intel decoding in general with build 300 but have not tested QSV encoding.

Are you using the color grading panel? That's known to be much slower in 21.300 than 20 or older versions.

Beyond that the video engine has changed in 21 from 20 and should be faster but struggles with some media. Try NVIDIA decoding in preferences, file io and rendering to NVENC instead of QSV.

Feel free to try the benchmarks in my signature and we can see if performance is as expected vs similar hardware (great system, btw).

Nope, no color grading. I ran your benchmark project and no matter what the settings it's taking around 3 minutes for the render when most people on the spec sheet are getting around 1:30. Is it a Win 11 thing? Here's screen shots of all info I can think to provide. It's also strange that task manager shows 80-100% cpu usage when I NEVER had that rendering QSV previously, yet cpu usage from Vegas is showing only 10-20%. I also did another fresh install of windows today just to be safe. Literally nothing installed but windows, nvidia drivers and vegas. Something has to be off. One thing the benchmark sheet doesn't seem to have is what version of windows everyone is on.

My desktop is Windows 11 (look for RogerS) so no particular issues there as far as I'm aware. You can also see the performance drop from 208 to 300 for projects like this that use multiple Fx (I did tests with both my systems).

For VP 21.300 I'd try NVDEC decoding over QSV unless you are editing 10-bit 422 HEVC. If you are, keep it on QSV and check "enable legacy AVC decoding) in preferences, file io.

I'd also test NVENC and see if you get better performance than QSV. I'm seeing a slowdown with Intel decoding in general with build 300 but have not tested QSV encoding.

I think I've already tried all this. I'll try again tomorrow along with the above person's suggestion to fully uninstall and reinstall video drivers (though I'm 99% sure this has nothing to do with it but I'll try). All I work with is 10bit 422 HEVC unfortunately. I do Indian weddings and often need to render a 3 hour wedding ceremony. And with this slow speed and the rate at which Vegas crashes I may have to go have to Windows 10 and VP20. UNLESS it's rock stable. I don't mind slower renders if it doesn't crash every other render though I think that's a pipe dream. It's a shame because VP21 in W11 feels smooth and snappy. Other than this issue. I'll report back with anything tomorrow.

If I were you I would use Windows 11 and VP 20.411 or 21.208. I would not use build 300 with an Intel iGPU for decoding and legacy AVC unchecked. My recommendations for you are all based on controlled tests.

You can download 208 from here.

There are the issues I've found with 300 so far: https://www.vegascreativesoftware.info/us/forum/vegas-pro-21-build-300-general-thread--145190/?page=1#ca909791

I'd test 21 again once a patch for 300 is released and when you're not on a tight deadline for your projects.

If I were you I would use Windows 11 and VP 20.411 or 21.208. I would not use build 300 with an Intel iGPU for decoding and legacy AVC unchecked. My recommendations for you are all based on controlled tests.

You can download 208 from here.

There are the issues I've found with 300 so far: https://www.vegascreativesoftware.info/us/forum/vegas-pro-21-build-300-general-thread--145190/?page=1#ca909791

I'd test 21 again once a patch for 300 is released and when you're not on a tight deadline for your projects.

Ok good to know. I'll try those versions tomorrow!

 I'm rendering 4K 10bit HEVC footage 

Which camera do you use? What type of 10bit footage is it - 4K 10bit 422 or 4K 10bit 420?

And have you tried to render with another encoder, instead of AVC? HEVC for example?

 I'm rendering 4K 10bit HEVC footage 

Which camera do you use? What type of 10bit footage is it - 4K 10bit 422 or 4K 10bit 420?

And have you tried to render with another encoder, instead of AVC? HEVC for example?

Yes sir. The footage I use I listed above but it doesn't really matter because it's rendering EVERYTHING twice as slow as before lol. I'm going to try the other versions/builds of VP tomorrow and see if that changes anything in Windows 11

No, it have not seen an answer it it is 4K 10bit 422 or 4K 10bit 420 footage. I have not seen any other information about the footage. A slow render process can result from different aspects:

• the decoding of the footage can be slow - that is why we ask for the footage typicall
• effects - for example denoising or the CGP - can slow down the process. Or a lot of transitions
• the render process itself - here you stated that it is the Magix AVC/AAC Intel QSV. But what happens if you choose the NVEND (if available) or the GPU rendering only? Roger has suggested to try to use the NVENC - but what is the answer to that
• What is the utilization of you GPU/i-GPU? You show the CPU only

Win11 will not be the issue for VP 21 - compared to Win10.

If I were you I would use Windows 11 and VP 20.411 or 21.208. I would not use build 300 with an Intel iGPU for decoding and legacy AVC unchecked. My recommendations for you are all based on controlled tests.

You can download 208 from here.

There are the issues I've found with 300 so far: https://www.vegascreativesoftware.info/us/forum/vegas-pro-21-build-300-general-thread--145190/?page=1#ca909791

I'd test 21 again once a patch for 300 is released and when you're not on a tight deadline for your projects.

OMG going to 208 fixed the issue. My own person project went from rendering at 11fps to 25fps. And the benchmark project went from 3:00-3:30 to 1:34-1:38 depending on settings. THAT seems a lot more on par with the other results. THANK YOU! One quick question. For the benchmark project, I don't have the AI modules installed because I don't use them. Does that mean my render results are currently showing faster or slower for the benchmark? Just asking out of curiosity, just so I have an idea of where my system and its results stands in that list. Thanks.