The optional processing can only be applied to plug-ins if audio signals are present at their respective inputs, so that VST 3 plug-ins can apply their processing cost-effectively and only when they are needed. You can share the open source license of your VST 3 plug-in/host, including the VST 3 SDK sources that are subject to GPLv3. @Anthony_Nicholls Yvan said they tested all the hosts they could and didn`t find any problems. The Irritation Of Contents/Win32 is specific to VST2 I think VST3 uses unique identifiers to tell the difference between plug-ins. I will report my results here when I have updated my constructions. OK, I have it, it`s in the VST_SDK 3.6.10 here, in the VST2 folder: download.steinberg.net/sdk_downloads/vstsdk3610_11_06_2018_build_37.zip The open source license, you can share the source code of your VST 3 plug-in/host, including VST 3 SDK sources that are submitted to GPLv3. Note that VST 2 sources are NOT part of GPLv3! For more information about GPLv3, please visit this link. In addition, you can modify and modify the sources of SDK VST 3 as long as you release your changes and make them available to everyone (z.B on an internet hosting service like GitHub). Note that you must follow Steinberg VST`s rules of use.
VST 3 is a general follow-up of the long-lived VST plug-in interface. It`s not compatible with older versions of VST, but it contains some new features and possibilities. We have reorganized the API to not only make it much simpler and more reliable for developers, but also to offer new possibilities for plug-ins. This includes: The VST 3 plug-in library could export several plug-ins and replace the VST 2 shell concept (kPlugCategShell). Are you saying that a user of the proprietary license may not share the source code for their project? I think anyone, the VST-Plug-Ins or hosts, for profit or not, can share their source code if they wish. My company has developed a VST3 plugin that we want to distribute in binary form. We are now ready to distribute our plugin. I understand that my company must use the Proprietary Steinberg VST3 license. We printed and signed the contract by hand, then again scanned and sent to the reception at steinberg dot. We sent it on 24.07.2017, but we have not yet heard a response from Steinberg. How long does it usually take to get a response from Steinberg? Plugin developers who have already signed a VST2 licensing agreement with Steinberg could continue to develop VST2 after October 1, 2018. The purpose of this agreement consists of the Steinberg VST PlugIn Software Development Kit Version 3.6.10 The SDK VST2 is no longer part of the VST3 SDK, you must use an older version of the SDK and copy the VST2_SDK folder in the VST_SDK folder.
To create a VST2 version of the plug-in and a VST3 at the same time, you must copy the VST2 folder into the VST3 folder, simply execute the following commands: The VST 3 Licensing Issues document in steinbergmedia.github.io/vst3_doc/ says: 3.3. I want to sell my plug-in/host in binary form. If you work for profit and distribute your plug-in/host in binary form, you must choose the Proprietary Steinberg VST3 license. In the online VST3 documentation, you`ll find questions about licensing: developer.steinberg.help/display/VST/VST+3+Licensing This means we need another license file related to VST2. It would be nice if @ygrabit could get one as quickly as possible.