Thoughts on Steinberg's VST SDK

I have looked through the VST SDK and all I can say is that it is a convoluted mess. There are like 100 C++ classes but a base API specification of nowhere to be found. Has anybody had any experience with using the SDK? I think that Steinberg approached this from the wrong angle. Instead of focusing on defining the API, they “coded” a bunch of utility code.

Thank you for your thoughts. You may like to read the documentation here:

1 Like

Have you looked in the “pluginterfaces/” directory? That’s the actual API, and I know a couple of people who have just implemented those interfaces and bypassed all the “public.sdk” stuff .

Although the wording of the original post might be a bit harsh, I would tend to argue that the VST3 SDK is a bit intimidating for newcomers.

As pointed out by @signalsmith the true API is the folder pluginterfaces which is actually a repository on its own: GitHub - steinbergmedia/vst3_pluginterfaces: VST 3 API (as you can see the description of this repo is VST 3 API)

But because it is bundled with the SDK which is a rather large collection of “a possible implementation of the API”, and it is not clearly separated, it is hard to see where the boundary is. The true API also contains some conventions (like the bundle format, the location where hosts can find plugins, etc…)

I also wished that the API was truly promoted and distributed as such and the VST3 SDK was clearly promoted as an “implementation of the API which happens to bundle the API”.

The fact that the SDK and the API are even having the same version number is somewhat on an issue. For example when a new version of the VST3 SDK is released, it contains many changes in the SDK itself (including VSTGUI, etc…) and hardly any to potentially none in the API itself but since it is bundled, technically it is also a new version of the API…

I think as a simple measure, it would help tremendously if, in the release notes for the version, there was a clear separation between what has changed in the API vs what has changed in the rest of the SDK.

And BTW, the API (pluginterfaces) depends on the SDK which is definitely wrong: vst3_pluginterfaces/CMakeLists.txt at master · steinbergmedia/vst3_pluginterfaces · GitHub


# ...

	get_target_property(PLUGINTERFACES_SOURCES pluginterfaces SOURCES)
	add_library(pluginterfaces_ios STATIC ${PLUGINTERFACES_SOURCES})

both smtg_target_setup_universal_binary and smtg_target_set_platform_ios are used in the API CMakeLists.txt but are defined in the SDK…

Thanks for the detailed description. We will take this into account in our discussions here.