JUCE 5.4.1 and VST3

[t0m]

@Rory

why would I need the VST2 SDK?

Have you investigated the JUCE_VST3_CAN_REPLACE_VST2 preprocessor flag? It’s explained in much more detail in those links.

@Rory

And on a side note, can people continue to build VST2 plugins for as a long as they like if they just stick with JUCE 5.3.2?

No. The JUCE license and Steinberg’s VST2 license are different things.

Steinberg closing down VST2 for good

“From October 2018 onward we are closing down the second version of VST for good. While the VST 2 SDK has been unavailable, and so have maintenance and technical support, the subset within the VST 3 SDK will also be omitted.” - Steinberg. https://www.steinberg.net/en/newsandevents/news/newsdetail/article/vst-2-coming-to-an-end-4727.html

The future of VST2 support in JUCE

Steinberg is promoting VST 3 and deprecating VST 2, and there’s been some unofficial discussion on the forum, but we wanted to let you know what that would mean for your active JUCE projects that use VST 2. Here’s a summary of what we’re planning to change in JUCE, to give everyone a heads-up how it might affect your projects (spoiler: not very much!) Step 1: add VST 3 and VST 2 headers to the develop branch (today) We’ll push a new version of JUCE on the develop branch, in which: We remove…