I never developed an audio plugin (CLAP, VCV, or VST) so I don’t really know what I’m talking about. Given my ignorance, I am probably oversimplifying the process of VCV and CLAP plugin development. Hence the following question.
Is it feasible to imagine a future where we:
- Setup a build environment
- Create a collection of .svg files (layers, components, markers, etc.) that represent a rack version of a CLAP plugin that we want to live inside our VCV rack creations.
- Describe the GUI functionality of graphical items (states of lights, toggles, sliders, rotary things, I/O jacks, etc.) and the graphical components involved.
- Describe the relationships between these functions (scalar, boolean, enum, etc.) and the CLAP plugin’s parameters and I/Os.
- Describe the output plugin (slug, name, version, brand, etc.) in a manifest.
clap2vcv -i /path/to/clapplugin.clap -c ./config.json -m ./manifest.json -o "Tadaa!" --install
- Share this new plugin with my friends who also own that particular CLAP plugin
- Start vcvrack locally
And experience joy?