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 :-)
More baroque, for sure. More future-proof? Only if this is the one true form of reflected code that gets adopted.
> This way the algorithms will still be useful in 10 years when everyone has moved to API N+1
Actually, this way algorithms are not useful today since nobody writes them this way, and in 10 years, whoever writes this way right now will probably have moved on.
Now, if some small community (like C++-reflection-and-audio-buffs) commits to this, then maybe it makes sense for them. But not generally. General reflection (not to mention runtime reflection) is probably the way to go.
ah, actually not :) the library tries to do things in two steps in many places:
1/ map the user's code to a proxy depending on which concepts it conforms to: for instance whether your audio processing function is written per-sample (that's still in progress tho):
float operator()(float input) { return input * 0.5; }
or per-buffer: void operator()(float** inputs, float** outputs, int frames) { for(each channel, each sample) { ... } }
2/ the back-end accesses the class through these proxies to do whatever it needs to do.this means than if tomorrow we get reflection and metaclasses (I hint to this in the readme), and that we can write the "ideal" struct which (to me) would look like
struct my_effect {
[[name: "Main inputs"]]
audio_input main_input;
[[name: "Main outputs"]]
audio_output main_input;
[[range: {20, 20000}]]
[[unit: hertz]]
slider frequency;
// will create an appropriate message in max / pd with the name some_function
void some_function(int, std::ranges::view<std::variant<float, int>> list_of_stuff);
auto operator()(std::floating_point auto in) { return in * gain; }
};
the only thing that one will have to do is map the new "shape" in these proxies (which are as far as possible doing their stuff at compile-time) and all the existing backends will keep working with the algos defined in the better way.of course the existing algorithms will stay uglier, but they'll also keep working with new environments (and, as far as possible, without a runtime perf. hit)
> General reflection (not to mention runtime reflection) is probably the way to go.
yes, we all want that !
In the audio space I can imagine Concepts' Duck-typing is probably fairly effective for this work, you're rarely going to have something that looks like this flavour of duck but is not, in fact, a duck. It has been many years since I wrote LADSPA plugins, but there I'd guess the only confusion might be that there's deliberately no API difference between PCM data and CV, a reasonable strategy if you're building a modular synth but probably not what you want to listen to as output. Such differences are expressed only in metadata.
On the other hand, the same thing that presumably made this an attractively simple project for C++ 20 features also makes its practical utility very limited. Over the years what seems to matter to musicians is mostly the packaging, not the algorithms. The same exact algorithm exists for twenty years and then somebody famous calls it "Wonky-smog-burble", paints it fluorescent purple and presents the control parameter as an integer between 3 and 17 - suddenly it is this week's hot new sound. Which is fine of course, but the API doesn't matter at all to such fashions.