I’m continuing to test JUCE’s VST3 implementation against a wide variety of VST3 plugins. Today I’ve been testing a variety of Waves plugins, and so far they all exhibit the same behavior:
Click a control to move it.
As you drag the control, the value changes both visually and audibly.
Release the control.
The control’s value drops to zero.
In addition, loading any preset will cause all controls to drop to zero, probably for the same reason. I’ve discovered that the plug-ins values don’t drop to zero until audio is processed through the effects – you can move any controls you want until audio is processed, and then that control (and any other controls that you’ve moved) will drop to zero.
You should be able to test this for yourself by downloading a demo of Waves C1, available here: http://www.waves.com/plugins/c1-compressor
Note that Waves plugins use a single shell .VST3 file to store all of your plugins. JUCE does an excellent job of pulling all the plug-ins out of the shell, and I’m able to load a specific plugin from the shell with ease!