This FAQ relates to the Plug-in Compatibility for VST 3 toggle FAQ pages and further explains how some hosts are able to replace the EZbass plug-in without using the toggle.
Say that we used EZmix 2 in a DAW/host but we have upgraded to EZmix 3 and uninstalled EZmix 2. If your host can’t find the EZmix 2 plug-in, there is a chance that it can replace it with the EZmix 3 VST 3 plug-in using “IPluginCompatibility”.
The same feature solves the issue that normally needs to be worked around with the Compatibility toggle in EZbass.
Not all DAW developers have implemented this yet, but these are the ones we know about so far:
For most of these hosts, this just works. You load your old project and voila, Cubase has replaced the missing EZmix 2 plug-in with EZmix 3.
But for some hosts an additional step is required before the host recognizes the new, compatible plug-in. Select your host in the list below:
To our knowledge, Ableton does not support this feature.
Cubase should just replace the plug-in automatically, no additional steps needed.
To our knowledge, Digital Performer does not support this feature.
To our knowledge, FL Studio does not support this feature.
REAPER needs to re-scan and update its plug-in cache for it to be able to replace the old plug-in.
To our knowledge, Reason does not support this feature.
To our knowledge, Studio One does not support this feature.
Waveform should just replace the plug-in automatically, no additional steps needed.
