I tried to open a Waves audio plugin which led to Vegas crashing. This seems to be the case with all my Waves plugins. If I try to open an old Vegas 21 project that has Waves plugins Vegas 22 opens it WITHOUT the Waves plugins. In Vegas 21 (and everywhere else Waves plugins work normal)
Please specify which plugins? Not seeing an issue here with the two I have.
The ones that I have tried are: Aphex Vintage exciter, Abbey Road Chambers, DBX-160 and RVox.
And I am on Windows 10.
Waves Plugins haven't been certified to be compatible with Vegas for a long time, although some users have reported success. I know of no change in that behavior: it's posted somewhere on the Waves website.
Maybe file a support request to Magix (head back to the top of this page) and make sure they're aware of this.
VocalRider and Clarity work fine now that Magix has support for VST3s (since VP20). The reason VEGAS was dropped as a supported host was because Waves moved over to VST3s which didn't work in VEGAS then.
The new Waves Plugins are sometimes problematic for Vegas Pro and other VST hosts. Personally, they have become a bit too bloated and requires too much unnecessary processing for what its suppose to do, and that is what causes instability at times.
I dropped them some years back for better options that are out there now, both in quality and price.
Thank you for your replies. I have done some more testing and it seems indeed that there are a lot of problems/crashes with Vegas and Waves plugins. It appears that I was kind of lucky with the plugins that I used in Vegas 21. Some seem to work and some don't. When I started this thread I also made a support request at the same time. That was almost a week ago. Unfortunately I haven't heard back from Magix yet :o(
I guess I'll just not use Waves plugins inside Vegas any longer. I usually don't do audio editing in Vegas anyway.
If there's any good news, it is that VEGAS has an audio engineer who has fixed a lot of issues with VSTs since VP 20. It's great you sent the Waves issues to support and hopefully it will make it to engineering before long. If you discover issues with other plugins please send those in, too.
@captain-coyote In the meantime check out Voxengo line of audio plugins. They are very versatile, 100% stable and incredibly effective in what they do. That and BorisFX Crumple Pop Audio Restoration plugins are my everyday go to audio solution.
Actually, the responsibility for compatibility of VST plugins in Vegas, and there are a LOT of pitfalls, lies with the plugin author to ensure compatibility with the host, not the other way around.
The only exception I know of are Vegas' commercially partnered addons, where plugin developers such as New Blue, are given pre-release access to the builds and releases.
You can think of it this way -- if the Vegas team set out to tailor the software to every Tom, Dick, and Harry plugin, which do not undergo industry vetting or standards compliance testing, there would never be another consumer release of Vegas Pro.
At least Waves has announced and published its intentions to not "guarantee" compatibility with Vegas Pro, quite unlike the unwashed kiddos out there who claim their first written VST plugin is all things to all people, a tendency that is quite pervasive, and almost always wrong. 😏
Do check out the Toneboosters Audio Plugins, which for pro use are a step above anything out there. I have never had a V3 or V4 Toneboosters plugin fail to open in any recent version of Vegas, and the big advantage is that you can run them in Demo Mode forever!
Well, as I said, I usually avoid doing audio inside Vegas if I can (and I usually can!!!). However, I am not so sure about who is actually responsible for "making it work" if something goes wrong. The way I see it is this: If there is a VST standard (I suppose that because Steinberg at some point created the technology and by that laid down the rules that became that standard) both, plugin manufacturers AND VST host manufacturers have to follow these rules. If Vegas crashes, how can I know for sure whether it was bad programming on Waves' or Magix's side (or maybe something completely different)? I'm sure they will both be claiming that the other side caused the crash?!
Of course I too don't know what caused the crashes, it is just my (limited) experience that I have never had any problems of Waves plugins crashing their VST hosts (in my case Cubase and Wavelab).
By the way, I still haven't heard back from Magix.
I'd just keep reporting it as some that had issues like ClarityVx now work well without glitches and lag.
There are absolutely no professional membership requirements or dues, no enforceable compliance standards or industry-wide testing for plugins, period. That is the first, and most important thing to understand.
It is helpful to know the difference between industry-regulated compliance with a set of international standards that all technology producers must adhere to, and open-source technology, which is up to the plugin author only, and no one else.
That is why Vegas is not obligated to comply with every thirteen-year-old kid with a computer and a bright idea.
Going forward, your best bet is to communicate directly with the plugin authors you would like to become compatible with Vegas, rather that the owner of the host application.
Welcome to the discussions.