Released Jamba 7.1.3 with the following changes:

• Use FetchContent_Populate/FetchContent_MakeAvailable with SOURCE_SUBDIR option (see CMake discussion)

Released Jamba 7.1.2 with the following changes:

• Migrated Jamba to use VST3 SDK 3.7.12 (release notes). Please check other release notes to see what has changed since 3.7.8 (the previous SDK version supported by Jamba).
• Fixed deprecated CMake warnings with FetchContent_Populate
• Fixes issues with some DAWs on Windows when using the bundle format
• Fixes the create-plugin.py tool on Windows

A new release is available: 7.0.0

• Migrated Jamba to use VST3 SDK 3.7.8 (release notes). Please check other release notes to see what has changed since 3.7.5 (last Jamba supported version).
• As explained in issue #16, Jamba is no longer supporting VST2
• Added a way to patch the SDK by defining the CMake cache string JAMBA_VST3SDK_PATCH_DIR (Jamba uses it on Windows/DLL build to fix an issue with win32resourcestream.cpp, but you can also use it for your own purposes): by defining this variable, 2 things happen
  • Jamba copies the SDK inside the build folder
  • Jamba copies all the files under ${JAMBA_VST3SDK_PATCH_DIR} on top of this copy while never modifying a local version of the SDK