t0m
November 16, 2018, 10:23am
6
A JUCE_VST3_CAN_REPLACE_VST2 configuration option has been added to the Projucer. This defaults to 1 , meaning that existing projects will be unaffected by this change (aside from requiring a VST2 SDK), but this option will be set to 0 for new projects. When this option is set to 0 then the VST2 SDK is not required to build VST3 plug-ins (which will work out-of-the-box with JUCE) but plug-ins built in such a way will not be able to “override” VST2 plug-ins. Changing the JUCE_VST3_CAN_REPLACE_VST2 option changes the form of the plug-ins saved state, so any previous state saved in a host by an older version of the plug-in will be incompatible. This means that hosts will fail to load the new version of your plug-in on an existing track. Therefore, leave this flag unchanged if you want to maintain backwards compatibility.
You need to set JUCE_VST3_CAN_REPLACE_VST2 to 0 if you don’t want a dependency on the VST2 SDK. This will, however, break compatibility with previously released VST3 plug-ins.
