Hi,
The 64 bit vst engine is a huge step forward, but I have grave issues with VST3 effects.
I've refreshed VST plugins directory, but the problem still persist. I cannot load single vst3 effect - every time Vegas 20 crashes. Also, if by chance some plugins do load, after saving and restarting Vegas, VST3 plugins lose all settings/preset values that I've entered.
Someone have a solution?
Thank you in advance.
Not all VST plugins necessarily work or have been tested in Vegas. I have dozens of VST3 plugins from reputable makers working "as expected" as Effects in Vegas Pro 20 build 214.
Waves Platinium plugins not working as expected. Crashes, settings resetting after loading the project etc.
The message about Waves compatibility with Vegas is to be found on their website:
https://www.waves.com/support/how-to-find-your-plugins-in-vegas-sound-forge
Going forward, the Forum Search feature will get you many answers to your questions, as they have often been asked before.
I was able to get Clarity to work in Vegas and the new VST 3 functionality was supposed to help it work in Vegas.
Were there particular ones that failed or just all the ones you tried?
I assume you are on build 214 and not 139 of VP 20.
The message about Waves compatibility with Vegas is to be found on their website:
https://www.waves.com/support/how-to-find-your-plugins-in-vegas-sound-forge
Going forward, the Forum Search feature will get you many answers to your questions, as they have often been asked before.
I am with waves 9.6:
"Waves plugins v9.6 is the last version supported in Sony Vegas and Sound Forge applications. "
I'm testing with 14 myself.
The Vegas and Soundforge VST engines are new so that may no longer apply (though old VSTs really should still work).
From Waves website re supported hosts, Waves 9.6 lists host compatibility as being Vegas Pro 12 - 14:
https://www.waves.com/support/tech-specs/supported-hosts#version-9-6
Vegas Pro 14 was the first release of Vegas Pro under the MAGIX corporate umbrella and since then there have been many coding changes in Vegas Pro's coding to eliminate references to Sony. I'm only speculating, but perhaps those coding changes have affected plugins like Waves which may have been based on 'Sony' coding in Vegas Pro. It certainly did with FXHome's Ignite Pro FX video plugin package with the release of Vegas Pro 17 (I think it was 17) when FXHome had to release an update (v4.1) to enable it to work in VP17 by updating coding references from Sony to MAGIX/VEGAS coding.
I think the difference may have been that Waves migrated to 64-bit hosts after 9.6 and support on the Vegas/Soundforge side was lacking. https://www.waves.com/support/tech-specs/supported-hosts#version-9-92
It's just a VST so don't think Sony coding would be an issue here.
But the notes in Waves 9.6 state:
Exceptions & Notes:
32/64 bit: Version 9 supports all audio hosts above in 32-bit, and 64-bit where available.
If I remember correctly, there was on the forum years ago a conversation where Waves said it was up to Vegas to update its VST coding to accept Waves but Vegas was of the opinion that it was up to Waves to update its coding to allow Vegas Pro functionality for Waves. My thought is that if Waves was 'open' VST 32 or 64 technology, there should not be a problem in Vegas Pro or any other NLE/DAW with accepting Waves 32 or 64 plugins and Waves therefore should not need a compatibility list on their website. To my mind, that Waves has a compatibility list strongly suggests that it does code for specific programs.
But the notes for Waves 9.96 states:
"32/64 bit: All of the above-listed hosts (except Sound Forge) are supported in 64-bit only."
They may have cut loose the Magix products as a legacy 32-bit compatibility issue, or perhaps there is something that needed to be coded specifically for it.
I don't have so many VST hosts but Waves 14 seems to work in Fairlight and at least Clarity Vx in Vegas Pro 20 (the VST 2 mostly works in 19). Would be interested in more detailed tests with 20.214 and VSTs.