Note: this is currently still in development, don't use this in production yet!
- Fork this repository.
- Click on the "Actions" tab and enable github actions
- Add your patch files and plugin definitions to config.json.
- Wait for GitHub Actions to complete the build.
- Download your VST3 / AU / CLAP / LV2 / Standalone plugins!
Example:
[
{
"name": "N-SPEC COMP LITE 2",
"author": "Nasko",
"path": "Plugins/N-SPEC COMP LITE 2.zip",
"formats": ["VST3", "AU", "LV2", "CLAP"],
"type": "fx",
"version": "1.0.0",
"enable_gem": false,
"enable_sfizz": false,
"enable_ffmpeg": false
},
{
"name": "N-TILT",
"author": "Nasko",
"path": "Plugins/N-TILT.zip",
"formats": ["Standalone"],
"type": "fx",
"version": "1.0.0",
"enable_gem": false,
"enable_sfizz": false,
"enable_ffmpeg": false
}
]
Field | Type | Description |
---|---|---|
name |
string |
Unique name of the plugin. This is how it will appear in your DAW. Note: You cannot load two plugdata plugins with the same name. |
author |
string |
Name of the plugin's creator, displayed inside the DAW. |
path |
string |
Path to the patch location within the repository. Can be a folder or a .zip file. |
formats |
array |
List of plugin formats to build. Valid values: VST3 , AU , CLAP , LV2 , Standalone . |
type |
string |
Type of plugin: either "fx" for effects or "instrument" for instruments/synths. |
Field | Type | Description |
---|---|---|
version |
string |
Plugin version, new versions will not install correctly unless you increment this. Default: 1.0.0 |
enable_gem |
boolean |
Enables experimental GEM support Default: false |
enable_sfizz |
boolean |
Enables the [sfz~] object for SFZ sample playback. Default: false |
enable_ffmpeg |
boolean |
Enables FFmpeg-based audio objects. Recommended if your patch plays audio files. Default: false |
You can also run the build script locally instead of through github actions:
python3 build.py
You can use the --generator
flag to set the project cmake generates. Valid values are xcode
, visualstudio
or ninja
(default).
Aditionally, you can use the --configure-only
flag if you want to skip the build step.
After building, the original patch file you used is directly accessible via the “Info” menu in the plugin. This is required to comply with the GPL license (required by both plugdata and the JUCE GPL tier), as your patch could now legally be considered as "source code" of the generated plugins.