@enkiv2 @drwho
Thanks for posting this.
I am going to run it later today.
@20Hz @drwho NP. I should note that I know nothing about music theory, so results are questionable. But I'm proud of having written something that makes it comfortable to compose music from the command line with sox.

@enkiv2 @drwho
I also use this
#pyosound:
PYO
dedicated Python module for digital signal processing

http://ajaxsoundstudio.com/software/pyo/

@20Hz @drwho I remember looking into that a year or two ago and having a lot of trouble getting it working.

Do you know of a usable python midi library? That stuff is a minefield of broken/outdated projects with portability issues, & it doesn't make much sense.

@enkiv2 @20Hz @drwho

It seems to work pretty well for me. The midi library in it is pretty good as well. If I were you I would give it a shot again as it is the best imo package for music and sound available for python

@chaotic_signals @20Hz @drwho I probably had trouble with pyo because I'm on a weird fringe source distro. Basically anything where the binary is listed before the source gives me lots of trouble. I'll give it another try though.
@enkiv2 Yeah that is possible, that may be the problem. try it again as it is very useful and you can design instruments with a gui. Which increases accessibility
@enkiv2 @20Hz @chaotic_signals What distro are you using?

@drwho @chaotic_signals @enkiv2

I have an installation on ubuntu studio 14.04(need to update)

And on OS X 10.8

@drwho @chaotic_signals @20Hz
I'm running Lunar.

The Lunar maintainers have a policy of never writing their own patches -- all packages are just build scripts for official sources. Avoids the debian-breaking-ssl issue.

Unfortunately, official QT source releases don't work with the latest libjpeg, which breaks not only all KDE apps but also WXWidgets; I can't build PYO because I can't disable GUI support for it.

@enkiv2 @chaotic_signals @drwho

What is your reason for picking that distro over the others?

@20Hz @drwho @chaotic_signals
Within reason, all problems on it are things I can fix, if I put in the work -- even if I have to edit the source to do so. (This is not true of binary distros.)

Any bug I find is actually an upstream bug, not a distro bug, so I can submit patches for my fixes. (I almost never do, but I could.)

The default package set is very small, so I can keep my system lean. My newest computer is 5 years old so this is important to me.

@chaotic_signals @drwho @20Hz
Now, occasionally I run into issues like large bloated libraries that won't build & are too big for me to debug (QT), but I take it as a sign that I don't want to be using such a library anyway -- if I can't even get it to build, it's large enough that serious quality control on it probably isn't possible.

Most problems on lunar are actually just bad assumptions being made by build scripts -- easily identified & fixed.

@enkiv2 @20Hz No. Kinda wish I did. I had an idea for an XMPP-to-MIDI bot as an art hack, but never worked on it, just made some notes.
@enkiv2 @20Hz I don't remember any music theory (grew up playing a few instruments, stopped for health reasons). Mostly I play around until I get something that sounds and looks interesting.

@enkiv2 @20Hz Cool! I'll check that out.

I've been considering building a Markov bot, feeding it a few hundred tablitures, and then seeing what comes out of it.