-
Notifications
You must be signed in to change notification settings - Fork 32
Dplug VST3 Guide
This write-up describes the steps required to build a VST3 plug-in using Dplug.
Add a dplug:vst3
dependency in your plugin's dub.json
eg:
"dependencies":
{
"dplug:vst3": "~>8.0"
}
Add a configuration with a name starting with VST3
in your plugin project
"configurations": [
{
"name": "VST3-GOLD-EDITION",
"versions": ["VST3"],
"targetType": "dynamicLibrary",
"lflags-osx-ldc": [ "-exported_symbols_list", "module-vst3.lst", "-dead_strip" ]
}
]
You can find module-vst3.lst
in the given example in the distort
or clipit
examples.
If you use mixin(pluginEntryPoints!MyPluginClient);
you don't have anything to do.
Else, add the VST3 entry points in your main source file:
version(VST3)
{
import dplug.vst3;
mixin(VST3EntryPoint!MyClient);
}
Build with the right configuration:
$ dplug-build -c VST3-GOLD-EDITION
Such a VST3 cannot be distributed before you get an agreement and accept the dplug:vst3
licence.
This write-up describes the steps required to release a commercial VST3 plug-in using Dplug.
dplug:vst3
has a dual-licence that mirrors the one in the VST3 SDK.
Get a signed agreement for VST3 distribution with Steinberg. You can't ever release VST3 plug-ins without Steinberg's approval.
Use the VST3-compatible image in your documentation, binary distributions, and any material accompanying the VST3 plug-in.
Yes, if you want to distribute VST3 plug-ins. Do it.