Waves Plugin causes lag/crash in Vegas when plugin window is open

RobLundgren wrote on 12/30/2020, 8:25 PM

Hi, I just installed Vegas Pro 18 on a new PC. I also use the latest Pro Tools with Waves Plugs and they work great there. But in Vegas I noticed the waves plugs for example a limiter or RVox causes heavy lag and even crashed vegas when the plugin window is open. If I close the plug window but leave the plug active it's no prob. So it seems like there is some type of graphics issue. But I have well enough power (i7 10700K, GTX 1660 Ti , 16Gb RAM and SSD M2) to handle these things (new render time is awesome!). My older pc was way slower and I never had this issue. I have updated all drivers and the PC is running fine otherwise. Is there a setting I have missed or something? Thanks for any help!

Comments

fr0sty wrote on 12/30/2020, 9:48 PM

This is a known issue, hopefully we'll see it fixed when the team gets a bit to redo the audio engine... it needs to be updated to support things like VST3 as well, but they've been very busy trying to recode significant portions of VEGAS as well, and because they are a small team doing their best to completely overhaul VEGAS, it may take some time... please be patient.

Musicvid wrote on 1/1/2021, 3:39 PM

Yes, Vegas needs to support VST3. In the new batch from ToneBoosters, they have Barricade 4, which is a highly visual compressor, flexible limiter, and a set of LKFS meters. What a companion for Vegas that would be!

I have observed the "garbage with open plugin window" behavior, and I also assume it's graphics memory lugging down the processing.

rraud wrote on 1/2/2021, 9:43 AM

it's graphics memory lugging down the processing.

This is a common issue with the current generation of Waves plug-ins with Vegas and Sound Forge. My legacy Waves plug-ins do not exhibit this behavior.

Evan-Powell wrote on 3/25/2021, 8:54 PM

Waves has not supported Vegas since Waves V9.6. I tried installing these and they work fine.

https://www.waves.com/support/how-to-find-your-plugins-in-vegas-sound-forge

mortytemps wrote on 7/9/2021, 7:55 PM

I'm running Waves 9.2 (which predates V9.6 as discussed above) but still experiencing exactly the same problem (Vegas Pro 18.0). Any other solutions?

Evan-Powell wrote on 4/28/2022, 11:28 PM

@mortytemps Sorry. Just saw this. Did you make sure that you uninstall the latest versions of the Waves plugins? I've noticed that after 9.6, they start exhibiting this behavior. That being said, some of waves newer plugins do not go back that far. So I have to uninstall everything, pick and choose all that I can from 9.6 like how described in the link below, and then install the newer versions of the plugins that are not that old and deal with the issues. :P It kind of sucks.

https://www.waves.com/support/how-to-roll-back-to-waves-v9-6

If you are still running into this issue, then it probably just has to do with latency... not sure