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 (given as a set of C++20 concepts). 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
- all the algorithms in https://github.com/MTG/essentia/tree/master/src/algorithms
- ditto for https://github.com/cycfi/q/tree/master/q_lib/include/q
- ditto for all the VCV algorithms: https://github.com/VCVRack/Fundamental/tree/v1/src
- ditto for all the Bespoke objects: https://github.com/BespokeSynth/BespokeSynth/tree/main/Sourc...
- ditto for all the LMMS plugins: https://github.com/LMMS/lmms/tree/master/plugins
etc etc, there's a couple hundred of those, which always depend on some API and are thus not easily portable across environments: if tomorrow you want to make an audio software and want to use one of the, say, VCVRack plug-ins you're going to have to bring the whole VCV run-time API along.
Related projects are Faust (https://faust.grame.fr/) and SOUL (https://juce.com/discover/stories/soul-first-public-beta-rel...) but they both are domain-specific languages with their own compilers. I wanted a pure-C++ thing instead, which allows to call directly native code, and enables more than just generic audio processing: unlike Faust and SOUL (last time I checked) it's possible to make a message-based object for Pd or Max, not just an audio filter or synthesizer.
My end goal for this is that when I make an object for the main software I'm developing, ossia score (https://ossia.io) then the whole media arts community can benefit :-)