karya VS textbeat

Here's the github page: https://github.com/elaforge/karya

https://github.com/elaforge/karya/blob/work/Util/Processes.hs#L146

I use a little library called "Then": https://github.com/elaforge/karya/blob/work/Util/Then.hs

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