Ok, thank you. I'll check this. But I feel probably I'll keep my original plan, to have a bottom line for technologies I am going to use. So, with VST3, and leave VST2 in history. I want to develop another plugin, and I think I'll need to point to future.Kott wrote:Situation with VST2 is not pretty well.
You cannot distribute VST2 binaries if you haven't agreement with Steinberg, that agreement was available until November 2018 iirc.
Of course You can share your code (without VST2 SDK), which anyone "who has agreement" can compile against VST2 SDK.
Many windows DAWs supports VST3 now. In Linux there only Reaper and Bitwig and only u-he plugins works with VST3.
For VST3 probably the idea of Steinberg is to get permission if you want to distribute proprietary plugins/hosts. If you release under GPL than you can distribute and sell your plugins. If is not like this, than I will not develop any VST.
Update: From here I see it is dual license https://github.com/steinbergmedia/vst3s ... ICENSE.txt, so, you can distribute and sell VST3 plugins/hosts if you release them under GPL.