Try a test with 21 build 208. It should work as fast as you remember.

Since you are using Google Drive 😎, upload a short zipped project with assets. You can easily do this with File->Export

@Gastor Hi, I downloaded those files from Google Drive, there's loads of files missing or mislabelled making the .veg useless.

Have you included your project file of VP22?

I just added this - thanks for the call out.

@Gastor Hi, I downloaded those files from Google Drive, there's loads of files missing or mislabelled making the .veg useless.

there was a small jpg missing - thanks for catching that. I've added that now. The other 2 files are videos and are in the google folder under the same name. Maybe the project is trying to locate them in the location that they are in on my computer, but they should replaceable by the 2 files in the folder. - Thanks for your helps!

Since you are using Google Drive 😎, upload a short zipped project with assets. You can easily do this with File->Export

Thanks for the suggestion. Here's a direct link to download the files as a Zipped project https://drive.google.com/file/d/17W4Qp1urfymUKccy45FYNqHDmlM0zxGd/view?usp=sharing

Try a test with 21 build 208. It should work as fast as you remember.

In attempting to do this - I uninstalled my Vegas 21.315 and when installing the 208 it informed me that I was already installed on my laptop and desktop and thus couldn't reinstall it to a "3rd" system - even though this would be the same desktop that has Vegas 22 and is being counted as one of the 2 systems it list.

Also - if this fixes the render speeds issues, wouldn't this cost me access to the current updates in Vegas 22? Is this the solution you're currently using? I know you're one of the more informed members of the forums.

Try a test with 21 build 208. It should work as fast as you remember.

In attempting to do this - I uninstalled my Vegas 21.315 and when installing the 208 it informed me that I was already installed on my laptop and desktop and thus couldn't reinstall it to a "3rd" system - even though this would be the same desktop that has Vegas 22 and is being counted as one of the 2 systems it list.

Also - if this fixes the render speeds issues, wouldn't this cost me access to the current updates in Vegas 22? Is this the solution you're currently using? I know you're one of the more informed members of the forums.

Credit where it's due. @RogerS as always - you were right! I recreated the project in 21.208 and it worked like normal, rendering it in 17 minutes. What's different between this and 22? Am I stuck using 21.208 for now? I have the smart scription so I'm invested in the long-term of the program. I will say - I had to make a new project for this test, as it wouldn't let me open any of the two previous test vegas projects since they were made in newer versions of Vegas. I'll be adding this test project file(which does use the same files as the other two test) to folder linked above - just incase someone can point out something I'm doing different that I can do to make 22 run like this. (Couldn't add it to the Zip File as it's already uploaded as a single item in google drive.)

Thanks again to everyone for your efforts so far. I edit a few podcast and comedy clips, and I had to use DR for the week to meet deadlines, but I hate the workflow. I'll use 208 for now.

@Gastor Hi,

I ran it in VP22, Magic AVC (NVENC)

It estimated 40mins which I believed as the render progress was slow but steady.

VP21 the render was very slow, I took this pic when it said 59mins, I let it run a bit longer but progress had hardly moved & the time had gone up to 1hr 20mins, I stopped rendering.

VP22 with Legacy AVC in Preferences ticked render was a bit faster but not much. Again I believed it as the render progress was slow but steady.

-----

PS. I don't know why Magic AVC (NVENC) does this to my CPU in VP21 & is so slow 🤷‍♂️

@Gastor Hi,

I ran it in VP22, Magic AVC (NVENC)

It estimated 40mins which I believed as the render progress was slow but steady.

VP21 the render was very slow, I took this pic when it said 59mins, I let it run a bit longer but progress had hardly moved & the time had gone up to 1hr 20mins, I stopped rendering.

VP22 with Legacy AVC in Preferences ticked render was a bit faster but not much. Again I believed it as the render progress was slow but steady.

-----

PS. I don't know why Magic AVC (NVENC) does this to my CPU in VP21 & is so slow 🤷‍♂️

Thank you for running the test. I can't figure out what's different between 21.208 and 21.315/22. I just ran the same file I mentioned in the post above yours, where I got a 17 minute completed render in 21.208, and it's still rendering now in 22.

@Gastor 👍

I've no idea, or why my VP21 is the opposite to yours & so slow, 🤷‍♂️

Your 17min with the Intel + the RTX 4090 is impressive. My 40mins-ish AMD with no integrated graphics + RTX 3090 is about right, although I think I would expect it to be faster with a fairly simple 1920x1080 project 😒 I might try later to recreate your project using my own files or maybe prerender/convert yours with an external converter.

Can you share your render option & settings?

---------

Can you click your icon at the top of this page - My Profile & fill in your Signature with the full name of your CPU, GPU & amount of RAM, also inc the Windows & Vegas version, this will then show at the bottom of your comments,👍

@Gastor 👍

I've no idea, or why my VP21 is the opposite to yours & so slow, 🤷‍♂️

Your 17min with the Intel + the RTX 4090 is impressive. My 40mins-ish AMD with no integrated graphics + RTX 3090 is about right, although I think I would expect it to be faster with a fairly simple 1920x1080 project 😒 I might try later to recreate your project using my own files or maybe prerender/convert yours with an external converter.

Can you share your render option & settings?

---------

Can you click your icon at the top of this page - My Profile & fill in your Signature with the full name of your CPU, GPU & amount of RAM, also inc the Windows & Vegas version, this will then show at the bottom of your comments,👍

first is the settings from 22 the second is the settings from 21208

The new video engine is still a work in progress with issues like the GPU dropping out over long projects, and not everything that was GPU accelerated in 21.208 still is. For the benchmark I manage of a VP20 ad my render times doubled since then, for example. For the time being I'd work in 21 and test out patches to 22 to see when it's ready.

Feel free to try both benchmarks in my signature with your new and old builds and see how it changes.

Thank you for the project. I think, that was very helpful for testing Vegas. Recommend you to watch what will come up here.

For the time being I'd work in 21 and test out patches to 22 to see when it's ready.

This is much too pessemistic I think.

I only give advice to others that I follow myself. I am mainly using VEGAS Pro 22 build 208 for multiple reasons.

I only give advice to others that I follow myself. I am mainly using VEGAS Pro 22 build 208 for multiple reasons.

You mean VP21? I didn't know VP22 was at B208! 😉

For sure a typo. I for my part have switched immediately to VP93. Has still some issues like the increased render times, but there are also some advantages (like improved stability).

@Gastor

I rendered your project with the machine in my signature on Vegas Pro 21-315 using Magix AVC/AAC with default settings, Voukoder with my preferred settings and Intel QSV. I have no Nvidia or AMD add-in card in my machine.

Magix AVC/AAC was the slowest at 20.29 FPS. Voukoder and QSV were both around 22.7 FPS. This more or less results in a CPU-only render time of 49 to 56 minutes.

Anyone else can use this information as a data point of all the possible machine results.

On a personal note, I was put off by your social media links covering your face. I created a transparent PSD to show how I would like to see the links and logos arranged.

@Gastor

I rendered your project with the machine in my signature on Vegas Pro 21-315 using Magix AVC/AAC with default settings, Voukoder with my preferred settings and Intel QSV. I have no Nvidia or AMD add-in card in my machine.

Magix AVC/AAC was the slowest at 20.29 FPS. Voukoder and QSV were both around 22.7 FPS. This more or less results in a CPU-only render time of 49 to 56 minutes.

Anyone else can use this information as a data point of all the possible machine results.

On a personal note, I was put off by your social media links covering your face. I created a transparent PSD to show how I would like to see the links and logos arranged.

that looks great - good call on the socials! I'll make that change in the next recordings episodes.

In 21.208 I'm able to get rendering to average 75-80 FPS. with 22, it starts at around 60 and seems to have a "half-life" where it continues to slow down in rendering rate, getting to as slow as 6 FPS before I've given up, 2 hours into rendering a clip that's roughly 40 minutes long, and doesn't have heavy edits or use a ton of FX's.

with 22, it starts at around 60 and seems to have a "half-life" where it continues to slow down in rendering rate, getting to as slow as 6 FPS before I've given up

Have you noticed if your GPU's VRAM is full and 'shared gpu memory' is filling up when that happens?

The 6fps is familiar to me, or exactly 6.5fps. Nvidia GPU's get very slow when they have to use shared gpu memory, Not sure if that's your problem, but if it is , nothing you can do, but wait for it to be fixed and keep using VP21b208

edit: I see GID has same problem with slowness but has 100% CPU use which is crazy for his powerful CPU, and that's while using NVENC. At this point it's a game of 'choose your bug' to win, Just don't use VP22 at this point while you have VP21b208

with 22, it starts at around 60 and seems to have a "half-life" where it continues to slow down in rendering rate, getting to as slow as 6 FPS before I've given up

Have you noticed if your GPU's VRAM is full and 'shared gpu memory' is filling up when that happens?

The 6fps is familiar to me, or exactly 6.5fps. Nvidia GPU's get very slow when they have to use shared gpu memory, Not sure if that's your problem, but if it is , nothing you can do, but wait for it to be fixed and keep using VP21b208

edit: I see GID has same problem with slowness but has 100% CPU use which is crazy for his powerful CPU, and that's while using NVENC. At this point it's a game of 'choose your bug' to win, Just don't use VP22 at this point while you have VP21b208

I haven't checked that but I will on my next render test.

When you say wait for it to be fixed - do you mean by Vegas in a future update or in a future update to our GPU's?

@Gastor Vegas bugs in VP22 causing slow down, not a GPU driver problem