extempore VS textbeat

I've use a few "live coding" programming environments focused around audio programming where this is also the norm. Extempore ( https://github.com/digego/extempore, https://www.youtube.com/watch?v=yY1FSsUV-8c ) is a great example of this.

I grew up in the 70s with the term cybernetics from Norber Wiener, and I liked it before Gibson's Neuromancer in the 80s, so I guess I was inoculated before the pandemic use of the word. Cyber-Physical Systems (CPS) is a term being bandied about a bit now (reading Logical Foundations of Cyber-Physical Systems, and it is pretty cool [1]; Andrew Sorensen's Extempore as a CPS environment [2]). I also attended the first HOPE in 1994 in NYC and although the press abused the term cyber, it's still cool to me! But the Papa John's stuff was funny.

[1] https://link.springer.com/book/10.1007/978-3-319-63588-0

[2] https://github.com/digego/extempore

Check out https://github.com/digego/extempore by Andrew Sorenson

Extempore

I'm really fond of the idea of writing music like this.

From all available implementations of the idea, I probably like Extempore (https://github.com/digego/extempore) the most. Extempore provides a low-level C-like language (xtlang) which compiles into LLVM and can be meta-programmed from a variant of Scheme (TinyScheme I believe). This arrangement makes it possible to generate the code for the audio graph from Scheme, compile/optimize it via LLVM, then drive it in a live-coding fashion from Emacs. Best of both worlds (high and low).

My personal, much simpler attempt in this space is Cowbells (https://github.com/omkamra/cowbells) - with this one you can live-code FluidSynth (MIDI soundfonts) from Clojure + CIDER + Emacs, representing musical phrases either via Clojure data structures or an alternative text-based syntax (which is translated into the former by a compiler).

I tried it on textbeat which is in python and it wasn't understanding too much, with the exception of how the callstack worked in the parser. My questions may have been too usage-specific and not enough about the internals but I used up all my free usage credits so I couldn't continue.

My text-based music sequencer has some music theory support and it also has a REPL:

https://github.com/flipcoder/textbeat

I haven't worked on it in a while, but you might like textbeat (https://github.com/flipcoder/textbeat). It's a midi tracker and REPL that lets you type in music theory-like terminology and plays it. It's nowhere near a modern DAW but it's cool for tinkering and learning.

I've used Bitwig as a plugin host for textbeat before and it was quite fun. Textbeat is a project of mine that lets you write music in "plain text" with notation for chords, scales, and articulations. I haven't worked on it in a while though.

I love these text-based languages for music composition. Its something that is approaching a gap in music composition in real-life vs via computer. In real-life you can tell your bandmates to "just play a I V IV in C" and they get it. But we are still not quite at a place where we can tell a computer that exact phrase and get something useful. I love how close these text-based languages are getting though!

I've actually made my own musical language too - called miti [1], which is just one of many others including textbeat [2], foxdot [3], sonic-pi [4], chuck [5], and melrose [6]. Each has their own goals and capabilities.

- [1] https://github.com/schollz/miti

- [2] https://github.com/flipcoder/textbeat

- [3] https://foxdot.org/

- [4] https://sonic-pi.net/

- [5] https://chuck.cs.princeton.edu/

- [6] https://github.com/emicklei/melrose