VST Dev Notes

Supported OS & Compiler
 OS: Windows 8.1 and Windows 10
 Compilers: Visual Studio 2017
 OS: 10.11 and higher
 Compilers: Xcode 7 and higher

Finding your Plugin
Open the compiler project for your newly generated project. You can now re-build the solution to finish the ported project.

Your project will be validated automatically with the validator project that is built-into your compiler project. If your plugin fails validation, the compiler will NOT create the final VST plugin. This is generally good as a plugin that fails validation will likely crash the VST client which may result in it being black-listed from future loads! Fix any validation problems (see the compiler output window).

Your finished plugins will be located in the following sub-folder:

VST_SDK/VST3_SDK/myprojects/(project name)/mac_build/VST3/(config)


VST_SDK/VST3_SDK/myprojects/(project name)/win_build/VST3/(config)

where (config) is either Debug or Release, depending on how you built the project.

Your VST2 and VST3 plugins are AUTOMATICALLY copied to the proper locations in your MacOS device:

VST2: ~/Library/Audio/Plug-Ins/VST/<plugin>.vst)

VST3: ~/Library/Audio/Plug-Ins/VST3/<plugin>.vst3)

You must manually copy the VST plugins to the proper locations - these will vary depending on your setup.

VST3: There are generally accepted "default" locations for 32 and 64 bit builds.
These are located in admin-protected folders and can't be copied programmatically. For VST3 plugins:

C:\Program Files\Common Files\VST3

You should copy your .vst3 plugin to the appropriate folder as well as any other DAW-specific VST3 folders that exist on your system.

VST2: There is no default location for VST2 plugins.

You should copy your .vst3 plugin into your VST2 folder(s) for your DAW(s). THEN, rename the suffix from ".vst3" to ".dll" to convert it from a VST3 to a VST2 plugin.