Hello, coming from WL11 to 13, I miss a function that was there previously. When using search (which is what I do 100% of the time to select a plugin), in previous version you had both 64F and VST3 icons to help you select the version you want. Now you only see the 64F icon, but can’t know which version is the VST3.
This search functionality has been improved in WaveLab 12, but nobody so far has reported the small issue you pointed out today . This will be fixed for WaveLab 13.0.10.
That said, I don’t recommend using both VST3 and VST2 plugins; use only VST3 plugins.
Yep I always want to load VST3 in priority. But disabling each plugin 2.4 version is cumbersome, and I though about disabling 2.4 entirely but I have a few plugins which don’t have a VST3 version.
I’m not sure if it’s something doable but an option that hides the 2.4 from the vst list if a vst3 version is detected could be very nice
Yep I saw that option. But I have a very short list of plugins that doesn’t play well with Wavelab’s master section in VST3 and cause no issue in VST2.4 (like Sonobus which can’t seem to setup in stereo on the master section in VST3 while it’s working perfect in vst2.4).
Edit : I just discovered that you can select multiple plugin at once to edit there appearance, that’s a nice touch
I have a few FLUX-IRCAM Plugins in both VST3 and VST2 versions but only the VST2 allow for saving Presets.
Hence, i have to use the VST2 version of the Plugin that is also available as a VST3.
With this i mean that every situation, system and setup may have its singularities and having “closed” definitions when “optional” definitions could remain or still be made available is extremely important for some users.
The actual method is perfect: it’s an Option.
Also, regarding distinction between VST2 and VST3 plugins, the Plug-In list under Preferences lists all the VST3 versions with three diagonal dashes /// (VST2 have no dashes) allowing the user to easily distinguish wich version of the Plugin he wants to enable.