Code is a terrible way to learn DSP.
Audio programming is mostly math.
Most programming languages aren't suitable for audio DSP.
Offline first, then real-time.
Avoid plugins for a while.
Avoid FAUST for a while.
@paul this is something I see people ask about a lot, I'm sure it will be useful for many! are you looking for feedback or opinions?
@paul cool, I'll send an email later!
@icedquinn yup. getting into that kind of stuff is just not what most people signed up for.
@icedquinn I mean, at some level I suppose. But for me that just sounds like more brittle layers of complexity. The thing is, software doesn't actually seem to work most of the time. I tend to want less of it, not more of it.
@icedquinn I've not used it myself, but I've definitely seen stuff like it. Enzien audio made heavy, which was open sourced and abandoned when the company tanked. That converted PD patches to code. STM had a proprietary patcher thing for their boards. The teensy audio board has a rather rudimentary patching web interface I think? I also remember seeing some random hardware startup at SXSW a few years ago doing that as well.
Is the axolotl patcher thingy open source?
@icedquinn I don't really miss operator overloads for audio programming. I do for graphics though.
From what I can tell, Nim seems suitable for realtime, sometimes. Maybe things have changed, but don't you have to pass some extra options to get it to work?
Welcome to post.lurk.org, an instance for discussions around cultural freedom, experimental, new media art, net and computational culture, and things like that.