3 ms·

I fully agree. We saw one here yesterday (my timezone), actually. In that thread, another HN commenter posted this: https://en.m.wikipedia.org/wiki/List_of_a

I fully agree. We saw one here yesterday (my timezone), actually. In that thread, another HN commenter posted this: https://en.m.wikipedia.org/wiki/List_of_audio_programming_languages https://en.m.wikipedia.org/wiki/List_of_audio_programming_la... I used ChucK in college, and considering its functional use in performance art of many kinds, I'm seeing a lot of these proverbially "reinventing the wheel" in different syntax....ad nauseum. Where I see the real potential is using the native language of DAWs (digital audio workstation) like Protools, Ableton, and leveraging their native languages to write new scripts and library extensions for hardware.

zebproj 11y ago
> Where I see the real potential is using the native language of DAWs (digital audio workstation) like Protools, Ableton, and leveraging their native languages to write new scripts and library extensions for hardware. Most of these DAWs are written in C/C++. In many cases, things are really closed down (looking at you ProTools), so its difficult/impossible to write extensions unless you intend to sell it commercially. Renoise has a pretty good API in Lua for building plugins, which I thought was kind of neat. Ableton has Max4Live which I think counts for an extension language. As far as "native" code goes, I've been working a library of high quality DSP modules that you can use to build plugins called Soundpipe: http://www.github.com/PaulBatchelor/Soundpipe.git http://www.github.com/PaulBatchelor/Soundpipe.git