Hi all, I know this point has been mentioned before but I'd like to stress it again in an extra topic to increase visibility and encourage more people to join in.
Axoloti is an absolutely great project (congrats, Johannes!) and for me the final killer aspect is the possibility to add your own custom dsp objects. (Personally I'm dealing with physical modeling and simple amp modeling kind of stuff, but I'm sure there are so many more very individual and specific algorithms people would want to run on the Axoloti Core hardware, which can't be realized well, or not at all, just by patching, without writing actual C/C++ code.)
Therefore I'm sure I'm absolutely not the only one who would appreciate a guide on adding your own custom DSP objects. I was very positively surprised how easy it was to add a dsp object by copying and modifying an existing .axo file but I'm sure a quick dedicated guide would help the Axoloti community to be more productive and grow. Some aspects which spontaneously come to my mind, to include in a guide on custom objects are:
* Correct generation of UIDs and SHAs
* Data types, fixed vs. floating point computation
* Best practices for structuring code with includes, inline directives, etc. ...
I'd like to encourage everyone interested in this topic to add her/his questions.
I totally understand that writing a guide to custom objects is currently not the top priority for those involved with getting Axoloti to take off. But maybe a quick summary of some main points could still be done. And anyway it would already be good to know if any such documentation is planned and when we might expect something like this...