Jamba is currently working on the following platforms:
Visual Studio 16 2019)
Visual Studio 17 2022)
cmakeexecutable must be in your
New since 5.1.2, Jamba supports building universal plugins on macOS with XCode and Apple Silicon chipset!
On macOS, it is likely possible to use an earlier version (of the OS and Xcode) but it has not been tested
Linux is currently not supported (could be added if there is demand).
Jamba can automatically download the SDK for you but it is strongly recommended to install the SDK as the cloned repository is quite large (over 100MB) and would have to be downloaded again if you delete the build folder.
You can clone the SDK from Github
# using the branch name (simpler but use less safe tag) git clone --branch v3.7.8_build_34 --depth 1 --recursive https://github.com/steinbergmedia/vst3sdk.git # using the git hash (more complex but use safer hash) git clone --recursive https://github.com/steinbergmedia/vst3sdk.git cd vst3sdk git checkout --recurse-submodules 0041ef2c879c3c54c03d33cdc11a97eaebfb5752
Jamba currently uses 3.7.8 which corresponds to the tag
0041ef2c879c3c54c03d33cdc11a97eaebfb5752 commit hash).
|Jamba||VST||VST2||VST SDK Git Hash||VST SDK Download|
|1.0.0 - 4.5.0||3.6.9||Yes||
Jamba lets you configure the location of the SDK via the
VST3_SDK_ROOT CMake cache variable which can be set via any means available to CMake or set via the
--vst3 option when running the
configure.py script. If you do not want to have to worry about it you can also install it (or create a link) to a default location:
C:\Users\Public\Documents\Steinberg\VST_SDK.3.7.8) or the path provided via
--vst3, corresponds to the folder called
vst3sdkin the zip file.
Since Jamba version 7.0.0, Jamba no longer supports VST2. This section is left in this documentation in the event you are using a prior release of Jamba!
If you want to wrap your VST3 plugin into a VST2 plugin you will need the VST2 SDK. Unfortunately Steinberg is no longer distributing it officially and you need to get access to it. Once you get access to it, Jamba lets you configure the location of the SDK via the
VST2_SDK_ROOT CMake cache variable which can be set via any means available to CMake or set via the
--vst2 option when running the
If you download an old version of the VST3 SDK (like 3.6.9 (shasum 256 =>
7c6c2a5f0bcbf8a7a0d6a42b782f0d3c00ec8eafa4226bbf2f5554e8cd764964)) it contains the VST2 SDK at the root and this is what you need to copy or link to.
If you donwload the latest VST3 SDK zip file it does contain a
VST2_SDK folder at the root but it is an incomplete VST2 SDK distribution. Only older versions of the VST3 SDK (like 3.6.9) contains a valid VST2 SDK distribution.