Development - TheTechnobear/SSP GitHub Wiki
Overview
The Percussa allows for 3rd parties to develop modules for the SSP using the SSP-SDK.
Resources
- Github repo containing SDK
- SSP SDK Subforum
- Setting up a development environment
- How to build plugins
Expectations
- SSP is arm-based, so modules need to be compiled for ARM... so intel etc will not work.
- SSP has a hardware interface, that standard VST code cannot/doesn't support, sp VSTs will need some 'adaptation'
- The above resources, will only help you setup a development environment for building plugins, it will NOT teach you how to code plugins (see below)
Skills required for creating SSP Plugins
the following is a list of skills you (likely) need to create plugins for the SSP (actually for any platform)
- understand of how to create VSTs
- DSP
- C++/C
- build systems (cmake/make)
- Linux (to build and get around)
- Git (since you are going to want to store your code somewhere)
- Juce and/or VST SDK
Resources for learning to code plugins
The easiest way to get started to code plugins is to use JUCE, it is very powerful, cross-platform and also has a great forum for support from the community. see https://juce.com
Note: Juce is NOT completely free ! please checkout the licensing for complete details here
basically you have two choices:
- GPL - use for free, but make your code GPL - this means you MUST publish your source code
- Buy a JUCE license - then you do NOT have to publish your source code.
if you choose to use the GPL (Free) route, make sure you understand the implications eg. only using other code that are GPL compliant. its beyond the scope here, to cover all these details.