Vst3

[Shelly Takacs]

Iam trying to build a simple VST created with Projucer. In the Projucer Project settings, Enable Plugin Copy Step is by default enabled, and VST3 binary location is correctly pointing to my default VST3 folder location on my Mac, aka $(HOME)/Library/Audio/Plug-Ins/VST3.

After saving settings and successfully building in Xcode, with my Build Scheme set to All, no Vst3 is created at the location. It does not work either when changing the scheme to vst3.

Hi everyone! There have been a lot of conversations about the vst3 issues (especially with iZotope Ozone 9 and RX 8 Elements) since 16.1 and later...the issue is quite easy to resolve. The problem is that due to the re-hauling of the VST3 Engine, our vst3 plugins are assigned new plugin IDs in our registry, so it looks like many of our VST3 plugins won't load. All we need to do is re-scan our plugins manually. You can do this by clicking Options > Preferences > VST Plugins and click Refresh. Keep in mind that this scan will take some time, as again most of the plugins are being given new plugin IDs, but after that initial scan, your plugin scan at startup should be faster than they've ever been in SF. I hope this is helpful for you all!

Because of the statement in this thread that the horrific problem that causes SFPro 16 to be unusable has been resolved, I re-accomplished the steps that reportedly resolve the problem. They still don't resolve the problem. SFPro 16 still crashes upon attempting to use VST3, no matter how many times one Refreshes the Options>Preferences>VST Plugins.

hi! wow...this is strange, as i have tried this on every system i have access to and it worked every single time, plus i asked each user who filed a ticket in the last week to try it and so far it has also been successful for all that have responded back. is it possible for you @walter-howerton and @john_barr to perhaps send a video showing your manual rescan, and then the error with selecting a vst3 plugin? this would be most helpful, as i could get this to the developers and we can determine if there is another issue happening as well. also, if you need, i'm happy to get you an installation file for build 16.0 build 106, which was the last build before the vst re-haul.

Step two: Close Sound Forge Pro 16.1

Step three: Reboot the computer

Step four: Open Sound Forge Pro 16.1, and any audio file, then try to apply any VST3 plugin...

Note that I have also tried uninstalling and reinstalling, both Sound Forge Pro and ALL my third-party plugins (which are iZotope, if that's relevant).

Hi @john_barr thank you, that's great info! I just updated to Waves 14 and I can see that all of the individual plugins that are updated to Waves 14 only show in VST2. All of my other Waves plugins that run on 13 and earlier show up and work in VST3 without a problem. I've written with a few guys that are running studios and using Sound Forge and this is their experience as well. It seems (at least, at the moment) that the issue isn't a problem with all VST3 plugins, as all of our other VST3 plugins seem to be working great...but, the problem can be narrowed down to Waves (in particular, the plugins that are updated to Waves 14).

Before I updated my Waves to version 14, all of my Waves vst3 64 bit showed up and worked...so I believe it's an issue with Waves version 14 plugins...please let me know if that's not your experience, as I will talk to the developers today and if your experience is different then they will need to know what else to look for. Thanks again for your feedback, it really helped to narrow it down!

hi @john_barr. Thanks for the additional info! I spoke with the developers and they think they have identified the issue with the Waves 14 plugins, and they will work on that specifically so our Waves users (of which there are many!) can use their vst3 Waves 14 plugins again. Thank you again for the great info!

I disagree. There are thousands of VST-2 plugs-ins that would no longer run in Sound Forge. Many do not have VST-3 versions or equivalents, Not to mention the cost and time finding a 'suitable' VST-3 replacement Many of my 'go-to' plugs are VST-2 (not to mention Direct X).

@john_barr This just means that Steinberg no longer provides support for developers who use the VST2 SDK to develop plugins. As long as no Windows update breaks VST2 plugins there should be no problem in using them.

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?

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.

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! ?

@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.

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.

@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):

3a8082e126