q
LitterPower
Our great sponsors
| q | LitterPower | |
|---|---|---|
| 2 | 1 | |
| 1,071 | 12 | |
| - | - | |
| 8.6 | 10.0 | |
| 6 months ago | almost 7 years ago | |
| C++ | C | |
| MIT License | - |
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.
q
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
What are some alternatives?
KFR - A benchmark for comparison of FFT algorithms performance
essentia - C++ library for audio and music analysis, description and synthesis, including Python bindings
inspectrum - Radio signal analyser
DPF - DISTRHO Plugin Framework
eos - A lightweight 3D Morphable Face Model library in modern C++
Fundamental
DaisySP - A Powerful DSP Library in C++
delimited
libnop - libnop: C++ Native Object Protocols
vst3sdk - VST 3 Plug-In SDK
gensound - Pythonic audio processing and generation framework
vst3_pluginterfaces - VST 3 API