This part is not available in the 3.6.9 license agreement, it is at 1.6 in the 3.6.10 License Agreement The purpose of this agreement is the Steinberg VST PlugIn Software Development Kit version 3.6.10 This agreement does not apply to the development or hosting of VST 2-Plug Ins. With the open source license, you can share the source code for your VST 3 plug-in/host, including the VST 3 SDK sources that are subject 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. I`m going to catch up with him. I don`t have a licensing agreement with Steinberg, but from what I collect, I can download the SDK, fill out the license form, email it to Steinberg, and then I can publish vST2 plugins after October? You can choose between the Proprietary Steinberg VST 3 license or the “Open-Source GPLv3” license based on the distribution of your VST 3 plug-in/host. This license is available in www.steinberg.net/sdklicenses. 3.1. I want to share the source code of my plug-in/host on GitHub. You can choose the GPLv3 license and share the source code for your plug-ins/hosts, including the VST3 SDK sources on GitHub. But that`s a big question. Why not have the VST2 files gPL? I do an open source GPL3 synthesizer (tytel.org/helm) and unable to redistribute VST2 files makes the construction process really difficult.
There are also a whole series of other logistical problems that arise because these (3?) The files are still proprietary licensed. The Proprietary Steinberg VST 3 license allows you to distribute your VST 3 plug-in/host in binary form. However, plugin developers who have already signed a VST2 licensing agreement with Steinberg can continue to develop VST2 after October 1, 2018. 3.2. I want to distribute my plug-in/host as a freeware. You can distribute your plug-in/host in binary form. This always requires you to choose the Proprietary Steinberg VST3 license. Even if you distribute your plug-in/host in freeware, you must meet the requirements of the Proprietary Steinberg VST3 license.
That`s where it gets tricky. You can no longer download Steinberg`s VST2 deal, and Steinberg has just cleaned up as much as they can find of its existence recently online with DMCA Falls. (Note that the link above to the VST2 license is a 404) That would mean that you are not covered by the current VST3 agreement if you did not sign a VST2 agreement years ago that relates specifically to VST2? “You can distribute your plug-in/host in binary form. To do this, you must always choose the Proprietary Steinberg VST3 license. It says here that you can distribute it in binary form if the source is under GPLv3? 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? For more information, see the Proprietary Steinberg VST 3 licensing agreement. If you accept it, please enter all the necessary information, sign it and send it back to us, either by land mail (at the Steinberg address listed in the license), or by e-mail (email@example.com.-stei.nosp-m.nber.nosp-m.g.de) or by fax (49 (0) 40 210 35-300).