VST3 support and glitchy VST2 plugins

SilentNight wrote on 2/17/2021, 11:23 AM

Hey everyone I was just wondering if Magix is planning on adding VST3 support any time soon?

Almost all VST2s I've tried on Vegas projects have worked initially but sometimes certain plugins glitch out when loading the project again and cause Vegas to crash on open. Waves Vocal Rider and iZotope Ozone are examples that have caused this for me before (but sometimes the project loads fine with them on so idk).

Additionally a really important plugin I use, Slate Virtual Mix Rack, can't save its settings when used in Vegas. This is a known issue by the plugin devs but it doesn't look like they can do anything to fix it without rewriting the plugin due to some incompatibility with the Vegas VST2 engine. I have the Slate VMS ML-1 so this plugin is pretty essential to making the mic sound like it's supposed to and dialing in the settings again every time I go to export is very annoying.

If Magix is planning on supporting VST3 then maybe that will solve some of these issues I've been having and also allow me to use some VST3 only plugins I have. If not does anyone know if Magix are looking into the VST2 issues I've described?

Comments

rraud wrote on 2/17/2021, 12:57 PM

Waves plug-ins in Vegas are kn.own to cause odd behave when the window is open.
VST 3 support is planned AFAIK
Don't know about VP 17 & 18 but all iZotope plugs I have (including Ozone and RX) run normally for me in VP-16. They load slightly slower than some others though.
 

Gregory-Mead wrote on 3/17/2021, 8:07 PM

VST3 support, along with an improved/updated audio processing engine would be appreciated in a HUGE way! I've been using Vegas since its inception as an audio-only application, even contributing to the informal beta testing community at the time. I stuck with it for all these years partly because it was the only professional video editing application with professional multi-track audio editing capabilities to match. Over the past few years, this has become less and less possible.

Here in 2021, none of my VST3 plugins work, and it's the ONLY application I use that doesn't support them. It sputters and spits with even a single audio track when modest audio FX (VST2) are applied. It's not my audio hardware or the settings. I have the same problems on all of my systems, using a variety of hardware, and only in Vegas. I have no such issues with any other software, including Magix's own ACID 10, which really proves they CAN make the audio engine work properly.

I've been working professionally in music and video production for 30 years... and it saddens me that the Vegas audio engine just isn't up to the task anymore. I have to edit audio tracks completely outside Vegas in another app, then bring the final mix back in to render. I never had to do that before approximately five years ago. I've been hoping Magix would get it together, but it's still not happening in this latest update. I don't really want to purchase the next version if this isn't resolved. Audio technology has advanced up and beyond what Vegas can handle... I hope it gets resolved soon. I know I'm not the only user who feels this way. Thanks for listening! 🙏

Dexcon wrote on 3/17/2021, 8:55 PM

@Gregory-Mead  ... you may want to add a VST3 and audio engine request to the Vegas Pro 19 wish list - https://www.vegascreativesoftware.info/us/forum/vegas-pro-19-feature-requests--123432/?page=9#ca795316

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 15, 16, 17, 18, 19, 20, 21 & 22, HitFilm Pro 2021.3, DaVinci Resolve Studio 19.0.3, BCC 2025, Mocha Pro 2025.0, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 11, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

JMacSTL wrote on 3/6/2024, 11:27 AM

@Gregory-Mead  sounds like we're in the same boat. I've been using Vegas since the very early days in the early 2000s as an audio-only application, since at that time, ProTools wasn't nearly as robust. I still prefer Vegas to ProTools for many of my projects, but this VST3 issue (currently running Vegas 20) and the fact that many Waves VST2 plugs still cause issues, is troublesome. I still love Vegas, however, even with the workarounds on plugins. Cheers.

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.

RogerS wrote on 3/6/2024, 8:44 PM

sounds like we're in the same boat. I've been using Vegas since the very early days in the early 2000s as an audio-only application, since at that time, ProTools wasn't nearly as robust. I still prefer Vegas to ProTools for many of my projects, but this VST3 issue (currently running Vegas 20) and the fact that many Waves VST2 plugs still cause issues, is troublesome. I still love Vegas, however, even with the workarounds on plugins. Cheers.

@JMacSTL Which plugins specifically do you have issues with? The audio engine was revamped in VP 20 so referencing posts from VP 18 isn't really relevant. VEGAS now has VST3 support and an improved audio engine.

VP 21 further refined VST support with a number of bug fixes; you might try a trial and see if it is now better for you.

JMacSTL wrote on 3/7/2024, 11:17 AM

@RogerS  I use many Waves plugins, not all of which cause issues. If I try to load a VST3 plugin from Waves, it often spins for awhile, then crashes. I had to turn most of the WAVES vst3 plugins off (Prefs>VSTEffects> unchecking boxes) so I don't accidentally do that. All my RX10 plugs are vst3 and cause no issues. The ones that are especially troublesome: (all Waves, all vst2):

Anything API, anything CLA, Rchannel, anything SSL. The issues with some are just sluggish behaviour when the plugin window is open and you're adjusting whilst playing back audio (even in a simple timeline with only one track soloed), and on dialog especially, stuttering upon playback of the beginning of a cue.

As to Vegas21, I didn't note any significant audio changes from v20, so I haven't upgraded to that yet.

jmm

 

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.

RogerS wrote on 3/7/2024, 9:43 PM

@JMacSTL Can you create a new thread and describe exactly which plugin you are using and what problems you see? That would help others replicate it.

I also use some Waves plugins and mostly VST2. They were not really usable for me in earlier versions in VEGAS (I'd head over to Fairlight to get some audio work done). 20 was somewhat improved but there's some lag and visual tearing. Izotope also had issues (I'm on RX9 all 64-bit VST2).

The audio engine development that started in 20 made good strides in 21. (full release history here). If we can demonstrate that there are still issues that should help the developers get to the bottom of it.

mark-y wrote on 3/8/2024, 10:40 AM

The last version of Waves plugins that were certified to be compatible with Vegas and Sound Forge was version 9.6.

That was 2017, about the time of Vegas Pro 14. There was a big disclaimer on their website, but even that seems to have disappeared.

 

VEGASDerek wrote on 3/8/2024, 10:42 AM

We do have several fixes for the VST engine, including fixes related to the Waves plugins, coming in the next update of VEGAS Pro 21. We are wrapping up things on this update and hope to have it available in the next 4 or 5 weeks.

RogerS wrote on 3/8/2024, 6:20 PM

I think the loss of Waves certification was due to their shift to VST3 which VEGAS only began to support with version 20. They do function again (at least the few I own).