LitterPower
vst3_public_sdk
| LitterPower | vst3_public_sdk | |
|---|---|---|
| 1 | 2 | |
| 12 | 128 | |
| - | 5.5% | |
| 10.0 | 4.0 | |
| almost 7 years ago | 16 days ago | |
| C | C++ | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LitterPower
-
Declarative, non-intrusive, compile-time C++ reflection for audio plug-ins
If you wrote a software that worked with soundflower it means that at some point you used to call either the CoreAudio API directly or any abstraction on top of it (RtAudio, PortAudio, ...). Thus harder to port to another OS :-)
Here the idea is to write the algorithms in a way that is more future-proof, by not having them to depend on any run-time API, just a generic specification. This way the algorithms will still be useful in 10 years when everyone has moved to API N+1, unlike a metric ton of existing audio software which depends on a specific audio / media-object API for no good reason (today ! When they were written C++ wasn't advanced enough to allow this at all)
- all the objects in https://github.com/pcastine-lp/LitterPower for instance
vst3_public_sdk
-
How hard is it to make a VST plugin? Whether a instrument or effect.
This is an example of one source file in an sample VST - https://github.com/steinbergmedia/vst3_public_sdk/blob/master/samples/vst/note_expression_synth/source/note_expression_synth_processor.cpp
-
Declarative, non-intrusive, compile-time C++ reflection for audio plug-ins
> it does generate something compatible with VST2.x and I've been working on VST3 this week-end (and pulling a few hairs, that API is horrendous, the smallest example is a few thousand lines of codes).
Oh that is awesome!!!
If you want a tip about the smallest possible VST3 implementation, (and maybe you already know this) there is a class called "SingleComponentEffect", and an example called "AGainSimple" that uses it and is a fully self-contained single file full VST3 plugin:
https://github.com/steinbergmedia/vst3_public_sdk/search?q=s...
Also, I spent some time trying to get VST3 SDK usable with vcpkg so you could just do:
// vcpkg.json
What are some alternatives?
essentia - C++ library for audio and music analysis, description and synthesis, including Python bindings
delimited
q - C++ Library for Audio Digital Signal Processing
DPF - DISTRHO Plugin Framework
Fundamental
Vcpkg - C++ Library Manager for Windows, Linux, and MacOS
vst3sdk - VST 3 Plug-In SDK