Upgrading from Vegas 17 to 19/20 stability and audio plugins

flyerstl wrote on 7/27/2022, 1:19 PM

For audio-only sessions (mixing, sweetening/sound design, VO recording to picture), I'm still using Vegas 11 32bit b/c it works okay with WAVES audio plugins. Anything past that (64bit) doesn't play nicely with WAVES. This has been a known issue since Vegas 12. I also use ProTools when I have to. I currently use Vegas 17 for video sessions, and for when I need to import ProRes files into an audio session. Here's my questions:

1. If I upgrade from 17 to 19/20, it claims "Increased performance & stability". So, what does that mean? Have they worked on the audio plugins stability issue at all? Does the thing crash less? today it crashed three times when instantiating a VU meter plugin on the master bus for no apparent reasons.

2. When writing audio automation does the upgrade actually change the audio level in real time rather than currently (it doesn't change audio levels until playback for some odd reason even tho it's writing fader movements with my Faderport).

2. I missed the 149.00 upgrade price, but it's currently 199 for vegas pro 17 --> 19/20 so that's not bad. Not a question, but ya'know.

3. After my three crashes today, I decided to "SEND" the crash info to their server. Then I got a link "for more information click this link" It started downloading the installation .EXE file for Vegas 17.00.xx.452, but I'm already on build 455, so what's that all about?

Cheers and thx if you have any thoughts on these issues.

jmm in STL (system info in signature)

 

 

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

Comments

fr0sty wrote on 7/27/2022, 3:37 PM

VEGAS 20's VST engine has been overhauled, it now supports VST3 and the VST bridge got updated so that older VST plugins should also work ok. There will be a demo at launch you can try out to see for yourself.

flyerstl wrote on 7/27/2022, 3:42 PM

@fr0sty 

Good to know, but this is true of V20 but not 19, correct?

jmm in stl

Windows10 with Vegas 11 Pro (most recent build). Intel Core i7-3770 @ 3.40GHz 3.90 GHz, 32GB ram, separate audio and video disks. Also Vegas 17 Pro on same system. GPU: NVDIA GeForce RTX 2060 SUPER. Dynamic RAM preview=OFF.

fr0sty wrote on 7/27/2022, 3:46 PM

Yes, 19 does not have these audio updates. 20 isn't far off. It'll launch soon.

Last changed by fr0sty on 7/27/2022, 3:47 PM, changed a total of 2 times.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

LanceMGY wrote on 7/29/2022, 3:23 PM

VEGAS 20's VST engine has been overhauled, it now supports VST3 and the VST bridge got updated so that older VST plugins should also work ok. There will be a demo at launch you can try out to see for yourself.

Well this is great news if true! This is basically the single bug fix I've been waiting for since 32bit Vegas, like the OP says audio plug-ins (any 3rd party, not just Waves) does not work when used on buses and master fx, they do work better when used on a track but not much better. I saw they incorporated VST3 and a better audio engine in Soundforge and Acid I believe, was hoping they could make that work in Vegas eventually.

If 3rd party audio VST plugins work in Vegas 20 as they should (flawlessly in 32bit Vegas versions), then they can have my money. Will get the demo when available to confirm this. Thanks!

Evan-Powell wrote on 7/29/2022, 6:36 PM

I have this same issue with Waves plugins. The only real work around at the moment (at least for up to Vegas 19) is to use Waves Version 9.6 or earlier. I posted about this too a while back...

https://www.vegascreativesoftware.info/us/forum/severe-lag-audio-cutout-when-waves-plugin-s-gui-are-visible--128080/#ca796463

Scott-Reams wrote on 11/4/2022, 1:17 PM

VEGAS 20's VST engine has been overhauled, it now supports VST3 and the VST bridge got updated so that older VST plugins should also work ok. There will be a demo at launch you can try out to see for yourself.

Well this is great news if true! This is basically the single bug fix I've been waiting for since 32bit Vegas, like the OP says audio plug-ins (any 3rd party, not just Waves) does not work when used on buses and master fx, they do work better when used on a track but not much better. I saw they incorporated VST3 and a better audio engine in Soundforge and Acid I believe, was hoping they could make that work in Vegas eventually.

If 3rd party audio VST plugins work in Vegas 20 as they should (flawlessly in 32bit Vegas versions), then they can have my money. Will get the demo when available to confirm this. Thanks!

I just upgraded to Vegas 20.0 upon reading this, and it does finally fix the Waves plugin issue. I've been waiting a decade for this to be addressed... so great to finally be able to use my plugin suite in this software!