commit 56e4b2a644be164c5d324e8bc9de55b964b0f102
parent d821ee66d0699386f29c28edd9a03c780458087e
Author: ygrabit <ygrabit@users.noreply.github.com>
Date: Thu, 19 May 2022 17:24:31 +0200
VST SDK 3.7.5
Diffstat:
5 files changed, 322 insertions(+), 314 deletions(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
@@ -1,5 +1,5 @@
-cmake_minimum_required (VERSION 3.4.3)
+cmake_minimum_required (VERSION 3.19)
#-------------------------------------------------------------------------------
# Options
@@ -21,7 +21,11 @@ include(SMTG_VST3_SDK)
#-------------------------------------------------------------------------------
# SDK Project
#-------------------------------------------------------------------------------
-project(vstsdk)
+project(vstsdk
+ VERSION 3.7.5
+ DESCRIPTION "Steinberg VST 3 Software Development Kit"
+ HOMEPAGE_URL "https://www.steinberg.net"
+)
smtg_setup_platform_toolset()
@@ -91,6 +95,10 @@ endif(SMTG_AAX_SDK_PATH)
set(SDK_IDE_HOSTING_EXAMPLES_FOLDER FOLDER "HostingExamples")
add_subdirectory(public.sdk/samples/vst-hosting)
+# Add utilities
+set(SDK_IDE_UTILITIES_FOLDER FOLDER "Utilities")
+add_subdirectory(public.sdk/samples/vst-utilities)
+
#-------------------------------------------------------------------------------
# Here is added your own plug-ins folder location
# (by default we add the HelloWorld included in my_plugins folder)
diff --git a/LICENSE.txt b/LICENSE.txt
@@ -1,44 +1,44 @@
-//-----------------------------------------------------------------------------
-// LICENSE
-// (c) 2021, Steinberg Media Technologies GmbH, All Rights Reserved
-//-----------------------------------------------------------------------------
-This license applies only to files referencing this license,
-for other files of the Software Development Kit the respective embedded license text
-is applicable. The license can be found at: www.steinberg.net/sdklicenses_vst3
-
-This Software Development Kit is licensed under the terms of the Steinberg VST3 License,
-or alternatively under the terms of the General Public License (GPL) Version 3.
-You may use the Software Development Kit according to either of these licenses as it is
-most appropriate for your project on a case-by-case basis (commercial or not).
-
-a) Proprietary Steinberg VST3 License
-The Software Development Kit may not be distributed in parts or its entirety
-without prior written agreement by Steinberg Media Technologies GmbH.
-The SDK must not be used to re-engineer or manipulate any technology used
-in any Steinberg or Third-party application or software module,
-unless permitted by law.
-Neither the name of the Steinberg Media Technologies GmbH nor the names of its
-contributors may be used to endorse or promote products derived from this
-software without specific prior written permission.
-Before publishing a software under the proprietary license, you need to obtain a copy
-of the License Agreement signed by Steinberg Media Technologies GmbH.
-The Steinberg VST SDK License Agreement can be found at:
-www.steinberg.net/en/company/developers.html
-
-THE SDK IS PROVIDED BY STEINBERG MEDIA TECHNOLOGIES GMBH "AS IS" AND
-ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
-IN NO EVENT SHALL STEINBERG MEDIA TECHNOLOGIES GMBH BE LIABLE FOR ANY DIRECT,
-INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
-LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
-OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
-OF THE POSSIBILITY OF SUCH DAMAGE.
-
-b) General Public License (GPL) Version 3
-Details of these licenses can be found at: www.gnu.org/licenses/gpl-3.0.html
-Please refer to the Steinberg VST usage guidelines for the use of VST, VST logo and VST
-compatible logos:
-https://developer.steinberg.help/display/VST/Steinberg+VST+usage+guidelines
-//----------------------------------------------------------------------------------
+//-----------------------------------------------------------------------------
+// LICENSE
+// (c) 2022, Steinberg Media Technologies GmbH, All Rights Reserved
+//-----------------------------------------------------------------------------
+This license applies only to files referencing this license,
+for other files of the Software Development Kit the respective embedded license text
+is applicable. The license can be found at: www.steinberg.net/sdklicenses_vst3
+
+This Software Development Kit is licensed under the terms of the Steinberg VST3 License,
+or alternatively under the terms of the General Public License (GPL) Version 3.
+You may use the Software Development Kit according to either of these licenses as it is
+most appropriate for your project on a case-by-case basis (commercial or not).
+
+a) Proprietary Steinberg VST3 License
+The Software Development Kit may not be distributed in parts or its entirety
+without prior written agreement by Steinberg Media Technologies GmbH.
+The SDK must not be used to re-engineer or manipulate any technology used
+in any Steinberg or Third-party application or software module,
+unless permitted by law.
+Neither the name of the Steinberg Media Technologies GmbH nor the names of its
+contributors may be used to endorse or promote products derived from this
+software without specific prior written permission.
+Before publishing a software under the proprietary license, you need to obtain a copy
+of the License Agreement signed by Steinberg Media Technologies GmbH.
+The Steinberg VST SDK License Agreement can be found at:
+www.steinberg.net/en/company/developers.html
+
+THE SDK IS PROVIDED BY STEINBERG MEDIA TECHNOLOGIES GMBH "AS IS" AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL STEINBERG MEDIA TECHNOLOGIES GMBH BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
+BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
+OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
+OF THE POSSIBILITY OF SUCH DAMAGE.
+
+b) General Public License (GPL) Version 3
+Details of these licenses can be found at: www.gnu.org/licenses/gpl-3.0.html
+Please refer to the Steinberg VST usage guidelines for the use of VST, VST logo and VST
+compatible logos:
+https://steinbergmedia.github.io/vst3_dev_portal/pages/VST+3+Licensing/Usage+guidelines.html
+//----------------------------------------------------------------------------------
diff --git a/README.md b/README.md
@@ -1,266 +1,267 @@
-<div style="text-align:center">
-<img src="https://steinbergmedia.github.io/vst3_doc/gfx/vst3_logo.jpg" alt="VST 3 SDK" /></div>
-
-# Welcome to VST SDK 3.7.x
-
-## Table Of Contents
-
-1. [The VST SDK package](#100)
-1. [System requirements](#200)
-1. [About VST plug-ins in general](#300)
-1. [About VST 3](#400)
-1. [How to build VST 3](#500)
-1. [Contributing](#600)
-1. [License & Usage guidelines](#700)
-
-<div id='100'/>
-
-## The VST SDK package contains
-
-- The VST 3 API
-- VST 3 Implementation Helper Classes
-- AAX, AU, AUv3 and VST 2 wrappers
-- VST 3 plug-ins Examples
-
-The full VST 3 SDK is available [here!](https://www.steinberg.net/en/company/developers.html). It contains :
-
-- a 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.
-
-<div id='200'/>
-
-## System requirements
-
-Supported Platforms:
-
-| Operating System|Architecture|Compiler | Notes|
-| :------------- | :----------: | :-----------: | :-----------: |
-|Windows 10 |x86, x86_64 |MSVC 2022, MSVC 2019, MSVC 2017 | |
-|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 | |
-|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|
-
----
-<div id='300'/>
-
-## 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.
-
-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:
-
-- On **Windows**, a VST plug-in is a multi-threaded DLL (Dynamic Link Library), recently packaged into a folder structure.
-- On **Mac OS X**, a VST plug-in is a Mach-O Bundle
-- On **Linux**, a VST plug-in is a package
-
-To learn more about VST you can:
-
-- subscribe to the [VST Developer Forum](https://sdk.steinberg.net)
-- check the 3rd Party Developer Support section at [www.steinberg.net](https://www.steinberg.net/en/company/developers.html)
-- check the online documentation under: [steinbergmedia.github.io/vst3_doc](
-https://steinbergmedia.github.io/vst3_doc)
-
- ---
-<div id='400'/>
-
-## About VST 3
-
-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:
-
-### 1. Improved Performance with the Silence Flag
-
-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.
-
-### 2. Multiple Dynamic I/Os
-
-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 busses after loading and even reactivate those when needed. This cleans up the mixer and further helps to reduce CPU load.
-
-### 3. Sample-accurate Automation
-
-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.
-
-### 4. Logical Parameter Organization
-
-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).
-
-### 5. Resizeable UI Editor
-
-VST 3 defines a way to allow resizing of the plug-in editor by a user.
-
-### 6. Mouse Over Support
-
-The host could ask the plug-in which parameter is under the mouse.
-
-### 7. Context Menu Support
-
-VST 3 defines a way to allow the host to add its own entries in the plug-in context menu of a specific parameter.
-
-### 8. Channel Context Information
-
-A VST 3 plug-in could access some channel information where it is instantiated: name, color, ...
-
-### 9. Note Expression
-
-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.
-
-### 10. 3D Support
-
-VST 3 supports new speaker configurations like Ambisonic, Atmos, Auro 3D or 22.2.
-
-### 11. Factory Concept
-
-VST 3 plug-in library could export multiple plug-ins and in this way replaces the shell concept of VST 2 (kPlugCategShell).
-
-### 12. Support Remote control Representation
-
-VST 3 plug-in can deliver a specific parameter mapping for remote controls like Nuage.
-
-### 13. Others
-
-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
-
----
-<div id='500'/>
-
-## How to build VST3
-
-### Get the source code from GitHub
-
-<pre>git clone --recursive https://github.com/steinbergmedia/vst3sdk.git
-</pre>
-
-### 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.
-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:
-
-<pre>
-cd TheFolderWhereYouDownloadTheSDK
-./copy_vst2_to_vst3_sdk.sh
-</pre>
-
-- for Windows:
-
-<pre>
-cd TheFolderWhereYouDownloadTheSDK
-copy_vst2_to_vst3_sdk.bat
-</pre>
-
-### Build the examples on Windows
-
-- Create a folder for the build and move to this folder (using cd):
-
-<pre>
- mkdir build
- cd build
-</pre>
-
-- Generate the Solution/Projects: provide the path of the Project where CMakeLists.txt is located:
-
-<pre>
- examples:
- cmake.exe -G "Visual Studio 17 2022" -A x64 ..\vst3sdk
- or without symbolic links
- cmake.exe -G "Visual Studio 17 2022" -A x64 ..\vst3sdk -SMTG_CREATE_PLUGIN_LINK=0
- or by using the local user program folder (FOLDERID_UserProgramFilesCommon) as VST3 folder
- cmake.exe -G "Visual Studio 17 2022" -A x64 -SMTG_PLUGIN_TARGET_USER_PROGRAM_FILES_COMMON=1
-</pre>
-
-- Now you can build the plug-in (you can use Visual Studio too):
-
-<pre>
- msbuild.exe vstsdk.sln
- (or alternatively for example for release)
- cmake --build . --config Release
-</pre>
-
-### Build the examples on macOS
-
-- Create a folder for the build and move to this folder (using cd):
-
-<pre>
- mkdir build
- cd build
-</pre>
-
-- Generate the Solution/Projects: provide the path of the Project where CMakeLists.txt is located:
-
-<pre>
- For XCode:
- cmake -GXcode ../vst3sdk
- Without XCode (here debug variant):
- cmake -DCMAKE_BUILD_TYPE=Debug ../
-</pre>
-
-- Now you can build the plug-in (you can use XCode too):
-
-<pre>
- xcodebuild
- (or alternatively for example for release)
- cmake --build . --config Release
-</pre>
-
-### Build the examples on Linux
-
-- Install the required packages [Package Requirements](https://developer.steinberg.help/display/VST/How+to+set+up+my+system+for+VST+3#HowtosetupmysystemforVST3-ForLinux)
-- Create a folder for the build and move to this folder (using cd):
-
-<pre>
- mkdir build
- cd build
-</pre>
-
-- Generate the Solution/Projects: provide the path of the Project where CMakeLists.txt is located:
-
-<pre>
- cmake ../vst3sdk
-</pre>
-
-- Now you can build the plug-in:
-
-<pre>
- make
- (or alternatively for example for release)
- cmake --build . --config Release
-</pre>
-
-### Build using cmake-gui
-
-- start the cmake-gui Application
-- "Browse Source...": select the folder vst3sdk
-- "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
-
----
-<div id='600'/>
-
-## Contributing
-
-For bug reports and features requests, please visit the [VST Developer Forum](https://sdk.steinberg.net)
-
----
-<div id='700'/>
-
-## License & Usage guidelines
-
-More details are found at [www.steinberg.net/sdklicenses_vst3](http://www.steinberg.net/sdklicenses_vst3)
-\ No newline at end of file
+<div style="text-align:center">
+<img src="https://steinbergmedia.github.io/vst3_doc/gfx/vst3_logo.jpg" alt="VST 3 SDK" /></div>
+
+# Welcome to VST SDK 3.7.x
+
+## Table Of Contents
+
+1. [The VST SDK package](#100)
+1. [System requirements](#200)
+1. [About VST plug-ins in general](#300)
+1. [About VST 3](#400)
+1. [How to build VST 3](#500)
+1. [Contributing](#600)
+1. [License & Usage guidelines](#700)
+
+<div id='100'/>
+
+## The VST SDK package contains
+
+- VST 3 API
+- VST 3 Implementation Helper Classes
+- AAX, AU, AUv3 and VST 2 wrappers
+- VST 3 plug-ins Examples
+
+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.
+
+<div id='200'/>
+
+## System requirements
+
+Supported Platforms:
+
+| Operating System |Architecture |Compiler | Notes|
+| :------------------------------------ | :-----------------------: | :-------------------------------: | :-----------: |
+|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 | |
+|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|
+
+---
+<div id='300'/>
+
+## 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.
+
+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:
+
+- On **Windows**, a VST plug-in is a multi-threaded DLL (Dynamic Link Library), recently packaged into a folder structure.
+- On **Mac OS X**, a VST plug-in is a Mach-O Bundle
+- On **Linux**, a VST plug-in is a package
+
+To learn more about VST you can:
+
+- subscribe to the [VST Developer Forum](https://sdk.steinberg.net)
+- check the 3rd Party Developer Support section at [www.steinberg.net](https://www.steinberg.net/en/company/developers.html)
+- check the VST 3 SDK online documentation under: [steinbergmedia.github.io/vst3_dev_portal](https://steinbergmedia.github.io/vst3_dev_portal/pages/index.html)
+- check the online documentation under: [steinbergmedia.github.io/vst3_doc](https://steinbergmedia.github.io/vst3_doc)
+
+ ---
+<div id='400'/>
+
+## About VST 3
+
+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:
+
+### 1. Improved Performance with the Silence Flag
+
+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.
+
+### 2. Multiple Dynamic I/Os
+
+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 busses after loading and even reactivate those when needed. This cleans up the mixer and further helps to reduce CPU load.
+
+### 3. Sample-accurate Automation
+
+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.
+
+### 4. Logical Parameter Organization
+
+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).
+
+### 5. Resizeable UI Editor
+
+VST 3 defines a way to allow resizing of the plug-in editor by a user.
+
+### 6. Mouse Over Support
+
+The host could ask the plug-in which parameter is under the mouse.
+
+### 7. Context Menu Support
+
+VST 3 defines a way to allow the host to add its own entries in the plug-in context menu of a specific parameter.
+
+### 8. Channel Context Information
+
+A VST 3 plug-in could access some channel information where it is instantiated: name, color, ...
+
+### 9. Note Expression
+
+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.
+
+### 10. 3D Support
+
+VST 3 supports new speaker configurations like Ambisonic, Atmos, Auro 3D or 22.2.
+
+### 11. Factory Concept
+
+VST 3 plug-in library could export multiple plug-ins and in this way replaces the shell concept of VST 2 (kPlugCategShell).
+
+### 12. Support Remote control Representation
+
+VST 3 plug-in can deliver a specific parameter mapping for remote controls like Nuage.
+
+### 13. Others
+
+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
+
+---
+<div id='500'/>
+
+## How to build VST3
+
+### Get the source code from GitHub
+
+```c
+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.
+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:
+
+```c
+cd TheFolderWhereYouDownloadTheSDK
+./copy_vst2_to_vst3_sdk.sh
+```
+
+- for Windows:
+
+```c
+cd TheFolderWhereYouDownloadTheSDK
+copy_vst2_to_vst3_sdk.bat
+```
+
+### Build the examples on Windows
+
+- Create a folder for the build and move to this folder (using cd):
+
+```c
+mkdir build
+cd build
+```
+
+- Generate the Solution/Projects: provide the path of the Project where CMakeLists.txt is located:
+
+```c
+// examples:
+cmake.exe -G "Visual Studio 17 2022" -A x64 ..\vst3sdk
+// or without symbolic links
+cmake.exe -G "Visual Studio 17 2022" -A x64 ..\vst3sdk -DSMTG_CREATE_PLUGIN_LINK=0
+// or by using the local user program folder (FOLDERID_UserProgramFilesCommon) as VST3 folder
+cmake.exe -G "Visual Studio 17 2022" -A x64 -DSMTG_PLUGIN_TARGET_USER_PROGRAM_FILES_COMMON=1
+```
+
+- Now you can build the plug-in (you can use Visual Studio too):
+
+```c
+msbuild.exe vstsdk.sln
+// (or alternatively for example for release)
+cmake --build . --config Release
+```
+
+### Build the examples on macOS
+
+- Create a folder for the build and move to this folder (using cd):
+
+```c
+mkdir build
+cd build
+```
+
+- Generate the Solution/Projects: provide the path of the Project where CMakeLists.txt is located:
+
+```c
+// For XCode:
+ cmake -GXcode ../vst3sdk
+// Without XCode (here debug variant):
+ cmake -DCMAKE_BUILD_TYPE=Debug ../
+```
+
+- Now you can build the plug-in (you can use XCode too):
+
+```c
+xcodebuild
+// (or alternatively for example for release)
+cmake --build . --config Release
+```
+
+### Build the examples on Linux
+
+- Install the required packages [Package Requirements](https://steinbergmedia.github.io/vst3_dev_portal/pages/Getting+Started/How+to+setup+my+system.html#for-linux)
+- Create a folder for the build and move to this folder (using cd):
+
+```c
+mkdir build
+cd build
+```
+
+- Generate the Solution/Projects: provide the path of the Project where CMakeLists.txt is located:
+
+```c
+cmake ../vst3sdk
+```
+
+- Now you can build the plug-in:
+
+```c
+make
+// (or alternatively for example for release)
+cmake --build . --config Release
+```
+
+### Build using cmake-gui
+
+- start the cmake-gui Application
+- **Browse Source...**: select the folder vst3sdk
+- **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
+
+---
+<div id='600'/>
+
+## Contributing
+
+For bug reports and features requests, please visit the [VST Developer Forum](https://sdk.steinberg.net)
+
+---
+<div id='700'/>
+
+## License & Usage guidelines
+
+More details are found at [www.steinberg.net/sdklicenses_vst3](http://www.steinberg.net/sdklicenses_vst3)
diff --git a/VST3_License_Agreement.pdf b/VST3_License_Agreement.pdf
Binary files differ.
diff --git a/index.html b/index.html
@@ -1,6 +1,6 @@
<html>
<frameset border="0" frameborder="0" framespacing="0">
- <frame src="vst3_doc/index.html">
+ <frame src="doc/index.html">
</frameset>
<body>
</body>
