Comment by xrd

Comment by xrd a day ago

5 replies

Reading this article makes me want to point out the difference between commercial music software and open source software.

What stands out here was that Eno used very simple sounds and looped them. This was not a complicated rube-goldberg machine he built to finally get to these masterpieces. It was simple recordings of voices, looped.

Reggie Watts makes incredible, and non-traditional, electronic house music, basically just his voice and looping machine (granted he does have a 4 octave range, but...). So organic and human.

Same for Matthew Herbert, see his manifesto: https://prruk.org/personal-contract-for-the-composition-of-m.... It is all organic.

This is what makes me a little sad when I play with all the amazing open source tools on Linux. Ardour is great. Hydrogen is great. Sonic-PI is incredible.

But, the UI's are not the best. Getting started requires a ton of reading and researching. It is a long way to just "play" (I mean playing like a child, not playing piano).

For example, I wish Sonic-PI had a better way of writing music than JUST writing out ruby. I like ruby as a language, and I'm surprised there is not a way to easily extend the Sonic-PI tool so I can plugin my Novation drum pad and easily trigger samples and notes. I can absolutely watch for MIDI notes from Novation, and take actions in ruby code, but it kills my creativity to do it that way. I wish I could build a tiny set of buttons that shows me that which is not a stream of logs. I never feel like Sonic-PI puts me into a creative mode. It feels like trying to jam the beauty of a harp into emacs. And, I love emacs.

Open source music software could have bespoke custom UIs for any user. I'm a command line guy so I'm part of the problem. But, these tools should be customizable to make our own bespoke UIs which match the beginner level, or the advance level, or anything in between.

PaulDavisThe1st 20 hours ago

> But, the UI's are not the best.

Try jumping into any DAW without "a ton of reading and researching".

Granted, there are hardware drum machines and sequencers that you can "play" with as a completely fresh user, but these tend to be the exception rather than the rule. The newer generation of hardware sequencers (say the Elektron series) are quite impenetrable without spending a significant amount of time learning about what they can do and how to do it.

> Open source music software could have bespoke custom UIs for any user.

from the voice of experience, I'll tell you that this makes user support almost impossible, or at least, extremely difficult and frustrating.

  • xrd 18 hours ago

    I 100% agree with everything you said.

    But, when I use open source, I assume user support == "me supporting it". That often means reading the docs, reviewing source code, (and lately, asking claude...)

    I'm just saying I want to be permitted to build my own UI, easily. I think that should be front and center in the design decisions. I sheepishly think of Sonic-PI, and how incredibly hard Aaron has been working for years and know he was rightly focused on the backend pieces, which are incredibly complex. I don't think he should do the "UI-only-for-me-and-not-for-thee" work, but maybe as a community we can start doing better about making bespoke UI possible.

    • snypher 12 hours ago

      >we only have three colour themes - standard, dark and high contrast.

      >Theming Sonic Pi beyond this is only possible by hacking the source code and it’s not something I’ve had the time to make user friendly. However, if others would like to work on this, I’m happy to consider contributions.

      This seems like a pretty reasonable statement from him; I'm sure others would appreciate the work, if you have the time.

barfoure a day ago

You think open source has a UX problem? Try learning to play a guitar. It’s so bad it makes some people’s fingers bleed. People spend years learning how to play and they still say they have a long way to go!

soulofmischief 20 hours ago

You should check out Andrew and Ben's work, Extempore.

There is definitely a learning curve, but after reading the basics and poking through the examples, you realize you can do anything.

Lots of C libraries have wrappers already written and you can also write your own. I wrote a curl wrapper and pulled live data from sources such as weather APIs, assigned different facets of the data to different instruments and dynamics. You can write GL shaders and generally create your own interfaces.

It's also fully networked with sample-accurate synchronization, so that it's very easy to construct distributed computation and physical interaction. This is where the cyberphysical programming aspect comes into play.

Extempore has support for MIDI devices, and I've really pushed my gear to the limit with it. It is also very low level; you even write your own DSP. But you create libraries over time so that spontaneous jams don't require twenty minutes of fiddling first.

It took a lot of time to feel comfortable in the environment when I first got into it years ago, but with modern agentic IDRs such as Cursor, you should have a much, much easier time. It's great for writing algorithmic music and really great for freeform jam sessions. Lots of built in goodies that will really inspire you.

Also it's LISP.

https://extemporelang.github.io/