commit 358b72ee61bc67fb4592b0d492e0c6a1211ebf11
parent 56a6b78ea3e9fae4ea71fcf1793c34a5408adc8b
Author: ygrabit <[email protected]>
Date: Mon, 12 Dec 2022 14:48:19 +0100
VST SDK 3.7.7
Diffstat:
3 files changed, 28 insertions(+), 22 deletions(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
@@ -1,13 +1,19 @@
cmake_minimum_required (VERSION 3.19)
+# Specify the minimum version of the target platform
+if(NOT DEFINED ENV{MACOSX_DEPLOYMENT_TARGET})
+ set(CMAKE_OSX_DEPLOYMENT_TARGET "10.13" CACHE STRING "macOS deployment target")
+ message(STATUS "[SMTG] macOS Deployment Target: ${CMAKE_OSX_DEPLOYMENT_TARGET}")
+endif()
+
#-------------------------------------------------------------------------------
# Options
#-------------------------------------------------------------------------------
-# Add VST3 Plug-ins Samples
-option(SMTG_ADD_VST3_PLUGINS_SAMPLES "Add VST3 Plug-ins Samples to the solution" ON)
+# Add VST 3 Plug-ins Samples
+option(SMTG_ADD_VST3_PLUGINS_SAMPLES "Add VST 3 Plug-ins Samples to the solution" ON)
-# Add and use VSTGUI (enable VST3 Plug-ins Samples using VSTGUI)
+# Add and use VSTGUI (enable VST 3 Plug-ins Samples using VSTGUI)
option(SMTG_ADD_VSTGUI "Add VSTGUI Support" ON)
#-------------------------------------------------------------------------------
@@ -22,7 +28,7 @@ include(SMTG_VST3_SDK)
# SDK Project
#-------------------------------------------------------------------------------
project(vstsdk
- VERSION 3.7.6
+ VERSION 3.7.7
DESCRIPTION "Steinberg VST 3 Software Development Kit"
HOMEPAGE_URL "https://www.steinberg.net"
)
@@ -36,12 +42,12 @@ set(SDK_ROOT "${ROOT}")
set(public_sdk_SOURCE_DIR ${SDK_ROOT}/public.sdk)
set(pluginterfaces_SOURCE_DIR ${SDK_ROOT}/pluginterfaces)
-# Disable all VST3 samples when using SDK as subdirectory
+# Disable all VST 3 samples when using SDK as subdirectory
message(STATUS "[SMTG] CMAKE_SOURCE_DIR is set to: ${CMAKE_SOURCE_DIR}")
message(STATUS "[SMTG] CMAKE_CURRENT_LIST_DIR is set to: ${CMAKE_CURRENT_LIST_DIR}")
if(NOT ${CMAKE_SOURCE_DIR} STREQUAL ${CMAKE_CURRENT_LIST_DIR})
- message(STATUS "[SMTG] Disable all VST3 samples")
+ message(STATUS "[SMTG] Disable all VST 3 samples")
set(SMTG_ADD_VST3_PLUGINS_SAMPLES OFF)
set(SMTG_ADD_VST3_HOSTING_SAMPLES OFF)
set(SMTG_ADD_MYPLUGINS_SRC_PATH OFF)
@@ -60,10 +66,11 @@ include_directories(${ROOT} ${SDK_ROOT})
# From Here this is optional...
#-------------------------------------------------------------------------------
-# CORE AUDIO SDK, AAX SDK
+# CORE AUDIO SDK, AAX SDK, JACK SUPPORT
#-------------------------------------------------------------------------------
setupCoreAudioSupport()
setupAaxSupport()
+setupJackSupport()
#-------------------------------------------------------------------------------
# Projects
@@ -78,17 +85,17 @@ add_subdirectory(public.sdk)
add_subdirectory(public.sdk/source/vst/interappaudio)
#---Add Wrappers (AU, AAX)-----------------------
-if(SMTG_COREAUDIO_SDK_PATH)
+if(NOT "${SMTG_COREAUDIO_SDK_PATH}" STREQUAL "")
add_subdirectory(public.sdk/source/vst/auwrapper)
-endif(SMTG_COREAUDIO_SDK_PATH)
+endif()
-if(SMTG_AAX_SDK_PATH)
+if(NOT "${SMTG_AAX_SDK_PATH}" STREQUAL "")
add_subdirectory(public.sdk/source/vst/aaxwrapper)
set_target_properties(aaxwrapper
PROPERTIES
${SDK_IDE_LIBS_FOLDER}
)
-endif(SMTG_AAX_SDK_PATH)
+endif()
# Add hosting examples, it includes the validator (must be done before any plug-ins to support running the validator after building)
set(SDK_IDE_HOSTING_EXAMPLES_FOLDER FOLDER "HostingExamples")
@@ -103,7 +110,7 @@ add_subdirectory(public.sdk/samples/vst-utilities)
# (by default we add the HelloWorld included in my_plugins folder)
#-------------------------------------------------------------------------------
if(SMTG_ADD_MYPLUGINS_SRC_PATH)
- set(SMTG_MYPLUGINS_SRC_PATH "${CMAKE_CURRENT_SOURCE_DIR}/../my_plugins" CACHE PATH "Here you can add Your VST3 Plug-ins folder")
+ set(SMTG_MYPLUGINS_SRC_PATH "${CMAKE_CURRENT_SOURCE_DIR}/../my_plugins" CACHE PATH "Here you can add Your VST 3 plug-ins folder")
if(EXISTS ${SMTG_MYPLUGINS_SRC_PATH})
message(STATUS "[SMTG] SMTG_MYPLUGINS_SRC_PATH is set to: " ${SMTG_MYPLUGINS_SRC_PATH})
@@ -118,7 +125,7 @@ if(SMTG_ADD_MYPLUGINS_SRC_PATH)
endif()
endif(SMTG_ADD_MYPLUGINS_SRC_PATH)
-#---Add VST3 examples (plug-ins and hosting)-----
+#---Add VST 3 examples (plug-ins and hosting)-----
if(SMTG_ADD_VST3_PLUGINS_SAMPLES)
set(SDK_IDE_PLUGIN_EXAMPLES_FOLDER FOLDER "PlugInExamples")
add_subdirectory(public.sdk/samples/vst)
diff --git a/README.md b/README.md
@@ -25,8 +25,7 @@
The full VST 3 SDK is available [here!](https://www.steinberg.net/en/company/developers.html). It contains :
- VST 3 plug-in Test Host Application/Validator,
-- the **Steinberg VST 3 Plug-In SDK Licensing Agreement** that you have to sign if you want to develop or host VST 3 Plug-Ins.
-- VST 3 Project Generator
+- the **Steinberg VST 3 Plug-In SDK Licensing Agreement** that you have to sign if you want to develop or host **VST 3** plug-ins.
<div id='200'/>
@@ -38,8 +37,8 @@ Supported Platforms:
| :------------------------------------ | :-----------------------: | :-------------------------------: | :-----------: |
|Windows 10/11 |x86, x86_64, arm64 |MSVC 2022, MSVC 2019 | |
|Windows 8.1 |x86, x86_64 |MSVC 2019, MSVC 2017 | |
-|macOS 10.13, 10.14, 10.15, 11.0, 12.0 |x86, x86_64, Apple Silicon |Xcode 7, 8, 9, 10, 11, 12, 13 | |
-|iOS 13, iOS 14 |arm64 |Xcode 11, 12, 13 | |
+|macOS 10.13, 10.14, 10.15, 11, 12, 13 |x86, x86_64, Apple Silicon |Xcode 10 - 14 | |
+|iOS 13 - iOS 16 |arm64 |Xcode 11 - 14 | |
|Linux - Raspberry Pi OS (Buster) |arm32 |GCC 8.3 and higher |Visual Studio Code|
|Linux - Ubuntu 18.04 LTS |x86, x86_64 |GCC 8.3 and higher |Visual Studio Code, Qt Creator|
|Linux - Ubuntu 20.04 LTS |x86, x86_64 |GCC 8.3 and higher |Visual Studio Code, Qt Creator|
@@ -49,9 +48,9 @@ Supported Platforms:
## About VST plug-ins in general
-A VST plug-in is an audio processing component that is utilized within a host application. This host application provides the audio or/and event streams that are processed by the plug-in's code. Generally speaking, a VST plug-in can take a stream of audio data, apply a process to the audio, and return the result to the host application. A VST Plug-in performs its process normally using the processor of the computer. The audio stream is broken down into a series of blocks. The host supplies the blocks in sequence. The host and its current environment control the block-size. The VST Plug-in maintains the status of all its own parameters relating to the running process: The host does not maintain any information about what the Plug-in did with the last block of data it processed.
+A VST plug-in is an audio processing component that is utilized within a host application. This host application provides the audio or/and event streams that are processed by the plug-in's code. Generally speaking, a VST plug-in can take a stream of audio data, apply a process to the audio, and return the result to the host application. A VST plug-in performs its process normally using the processor of the computer. The audio stream is broken down into a series of blocks. The host supplies the blocks in sequence. The host and its current environment control the block-size. The VST plug-in maintains the status of all its own parameters relating to the running process: The host does not maintain any information about what the plug-in did with the last block of data it processed.
-From the host application's point of view, a VST plug-in is a black box with an arbitrary number of inputs, outputs (Event (MIDI) or Audio), and associated parameters. The host needs no implicit knowledge of the plug-in's process to be able to use it. The Plug-in process can use whatever parameters it wishes, internally to the process, but depending on the capabilities of the host, it can allow the changes to user parameters to be automated by the host.
+From the host application's point of view, a VST plug-in is a black box with an arbitrary number of inputs, outputs (Event (MIDI) or Audio), and associated parameters. The host needs no implicit knowledge of the plug-in's process to be able to use it. The plug-in process can use whatever parameters it wishes, internally to the process, but depending on the capabilities of the host, it can allow the changes to user parameters to be automated by the host.
The source code of a VST plug-in is platform independent, but the delivery system depends on the platform architecture:
@@ -149,7 +148,7 @@ git clone --recursive https://github.com/steinbergmedia/vst3sdk.git
### Adding VST2 version
-The VST2 SDK is not part anymore of the VST3 SDK, you have to use an older version of the SDK and copy the vst2sdk folder into the VST_SDK folder.
+The **VST 2 SDK** is not part anymore of the **VST 3 SDK**, you have to use an older version of the SDK and copy the vst2sdk folder into the VST_SDK folder.
In order to build a VST2 version of the plug-in and a VST3 at the same time, you need to copy the VST2 folder into the VST3 folder, simply run the following commands:
- for macOS:
@@ -207,9 +206,9 @@ cd build
```c
// For XCode:
- cmake -GXcode ../vst3sdk
+cmake -GXcode ../vst3sdk
// Without XCode (here debug variant):
- cmake -DCMAKE_BUILD_TYPE=Debug ../
+cmake -DCMAKE_BUILD_TYPE=Debug ../
```
- Now you can build the plug-in (you can use XCode too):
diff --git a/VST3_License_Agreement.pdf b/VST3_License_Agreement.pdf
Binary files differ.
