VST 3 is a general rework of the long-serving VST Plug-in interface. It is not compatible with the older VST versions, but it includes some new features and possibilities. We have redesigned the API to make it not only far easier and more reliable for developers to work with, but have also provided completely new possibilities for Plug-ins. These include:

Processing can optionally be applied to Plug-ins only when audio signals are present on their respective inputs, so VST 3 Plug-ins can apply their processing economically and only when it is needed.

VST 3 Plug-ins are no longer limited to a fixed number of inputs and outputs, and their I/O configuration can dynamically adapt to the channel configuration. Side-chains are also very easily realizable. This includes the possibility to deactivate unused buses after loading and even reactivate those when needed. This cleans up the mixer and further helps to reduce CPU load.

VST 3 also features vastly improved parameter automation with sample accuracy and support for ramped automation data, allowing completely accurate and rapid parameter automation changes.

The VST 3 Plug-in parameters are displayed in a tree structure. Parameters are grouped into sections which represent the structure of the Plug-in. Plug-ins can communicate their internal structure for the purpose of overview, but also for some associated functionality (eg. program-lists).

VST 3 defines a way to allow resizing of the Plug-in editor by a user.

The Host could ask the Plug-in which parameter is under the mouse.

VST 3 defines a way to allow the host to add its own entries in the Plug-in context menu of a specific parameter.

A VST 3 Plug-in could access some channel information where it is instantiated: name, color,...

VST 3 defines with Note Expression a new way of event controller editing. The Plug-in is able to break free from the limitations of MIDI controller events by providing access to new VST 3 controller events that circumvent the laws of MIDI and provide articulation information for each individual note (event) in a polyphonic arrangement according to its noteId.

VST 3 supports new speaker configurations like Ambisonic, Atmos, Auro 3D or 22.2.

VST 3 Plug-in library could export multiple Plug-ins and in this way replaces the shell concept of VST 2 (kPlugCategShell).

VST 3 Plug-in can deliver a specific parameter mapping for remote controls like Nuage.

While designing VST 3, we performed a careful analysis of the existing functionality of VST and rewrote the interfaces from scratch. In doing so, we focused a lot on providing clear interfaces and their documentation in order to avoid usage errors from the deepest possible layer. Some more features implemented specifically for developers include:

• More stable technical Host/Plug-in environment
• Advanced technical definition of the standard
• Modular approach
• Separation of UI and processing
• Advanced Preset System
• Multiple Plug-ins per Library
• Test Host included
• Automated Testing Environment
• Validator (small command line Test Host) and Plug-in examples code included

git clone --recursive https://github.com/steinbergmedia/vst3sdk.git

mkdir build
cd build
cmake ../vst3sdk
make  (or alternatively cmake --build .)

mkdir build
cd build
cmake -GXcode ../vst3sdk
xcodebuild  (or alternatively cmake --build .)

mkdir build
cd build
cmake.exe -G"Visual Studio 15 2017 Win64" ../vst3sdk
msbuild.exe vstsdk.sln   (or alternatively cmake --build .)

* start the cmake-gui Application
* "Browse Source...": select the folder VST3_SDK
* "Browse Build...": select a folder where the outputs (projects/...) will be created. Typically a folder named "build"
* you can check the SMTG Options
* Press "Configure"
* Press "Generate" and the project will be created