Does temporarily setting dynamic ram preview to 0MB help? 17 had some issues around that and GPU acceleration.

Question, do you have your GPU listed in Options>Preferences>File I/O, and Video>GPU acceleration of video processing? If so, change the settings to "Off" and see what happens.

Does temporarily setting dynamic ram preview to 0MB help? 17 had some issues around that and GPU acceleration.

I will try this and see if it fixes it.

Question, do you have your GPU listed in Options>Preferences>File I/O, and Video>GPU acceleration of video processing? If so, change the settings to "Off" and see what happens.

 

This is what my File I/O settings tab looks like, I don't see anything with GPU acceleration.

Also to update this issue, I did some more investigating and it seems to happen when I exceed a certain amount of separate elements with "eFX Vocal Strip" on them. I haven't tested to see if it happens with other audio FX as well but I will be able to look into it once I can.

GPU acceleration is under preferences/ video.

Hardware decoding says Intel QSV here.

GPU acceleration is under preferences/ video.

Hardware decoding says Intel QSV here.

I set this to AMD then I presume.

@Klush what build of Vegas 17 are you using?

@Klush what build of Vegas 17 are you using?

I'm using 455

@Klush From your screenshot, the blue color also appears in the meters of Audio Track 8. What, if anything is on Track 8?

@Klush From your screenshot, the blue color also appears in the meters of Audio Track 8. What, if anything is on Track 8?

Track 8 is empty, I have a tendency to always start my project with 4 video and 4 audio tracks. I did try to import everything into a new project with only the necessary tracks, but the issue persisted.

Look at recent changes to the system from Windows Updates, etc. using View Reliability History

Suspect video driver. The latest driver is not always the best driver for old software. I recently had a case open with Intel for two months until they announced that they just weren't going to fix the problem that killed my ancient software on Windows 11.

Look at recent changes to the system from Windows Updates, etc. using View Reliability History

Suspect video driver. The latest driver is not always the best driver for old software. I recently had a case open with Intel for two months until they announced that they just weren't going to fix the problem that killed my ancient software on Windows 11.

So I'm guessing the only solution if I don't find a fix is to buy Vegas 23 then. I tried messing with drivers once on this device and it bricked my windows, rendering my PC inoperable. Gonna avoid anything to do with drivers going forward.

@Klush said: "Gonna avoid anything to do with drivers going forward."

If that's your preference, you should plan to give up editing video or pay someone else to worry about drivers for you.

@Klush said: "Gonna avoid anything to do with drivers going forward."

If that's your preference, you should plan to give up editing video or pay someone else to worry about drivers for you.

One can be a an exceptional mechanic, but that doesn't mean he should know how to forge his own spanner. Sure I can get someone to do it, but telling someone with over 10 years experience in video editing to give up is a bit extreme, no?

@Klush Try a "Factory reset" as it can sometimes fix bizarre problems. Instructions here https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/ Make sure to tick the box to clear the cache.

@Klush said: "telling someone with over 10 years experience in video editing to give up is a bit extreme, no?"

The fact that you own a Radeon RX 9070 XT and expect to benefit from the hardware assist that it brings exposes you to the very great likelihood that you will have a driver issue at some point in your career. You will also experience hardware failures and software incompatibility over a long career.

My Standard Warranty Information

All my posts on this and other fora come with a double your money back guarantee.

PS

My Vegas Pro 17-455 test system on Windows 11 Pro works OK.

@Klush said: "I tried messing with drivers once on this device and it bricked my windows, rendering my PC inoperable."

A ten-year veteran video editor should have an image backup so that he/she can deliver on time in spite of "messing with drivers once on this device and it bricked my windows". Bricking one of my Windows installations is a five-minute inconvenience for me because I have system image backups.

Macrium Reflect | Free 30-Day Trial

@Klush said: "telling someone with over 10 years experience in video editing to give up is a bit extreme, no?"

The fact that you own a Radeon RX 9070 XT and expect to benefit from the hardware assist that it brings exposes you to the very great likelihood that you will have a driver issue at some point in your career. You will also experience hardware failures and software incompatibility over a long career.

My Standard Warranty Information

All my posts on this and other fora come with a double your money back guarantee.

PS

My Vegas Pro 17-455 test system on Windows 11 Pro works OK.

This machine is used for more than video editing. We're going to start doing 3D stuff soon so having something that can handle graphics and animation very well and be future proof for a long time was necessary. To give the extent of my knowledge of computer parts, I don't know how powerful the 9070XT is in relation to other parts. What I told my builder was that I just needed something very powerful with good rendering capabilities. I never expected Vegas 17 to work with any newer hardware to begin with seeing as they never existed on the market at the same time together. That's why I'm not that upset if I have to get Vegas 23 instead for better compatibility, I had already accepted this in case it turned out that 17 didn't work, which it has done up until this point. If there's a way to turn off this hardware assist then that'd be great, to see if that's what might be causing it.

For your test, these settings should banish GPU hardware involvement as much as possible.

This issues described in the original post should have nothing to do with the GPU or video drivers. Those components are using raw Win32 GDI drawing code (which does not use the GPU). This is very likely a drawing resource leak. We had a few of them at various times back in the VP 16 - 19 time frame, all of which had been corrected. I do not recall any at the end of the VP 17 development cycle. It is very strange that this is happening with a relatively simple timeline. We may have still had a resource leak the audio bus on the timeline, but that does not appear to be open here. I am not sure what advice to give on this one...it has been a long time since VP 17 was touched and we have not seen any related issues coming in from users of VP 17 that look like this.