Hi Tim,
> Python won't fly supersonic anyway; so as long as you're not expecting
> sub-millisecond latency from your MIDI -> X signal path I don't see
> why it shouldn't work. However, binding to certain widgets might prove
> hard if they don't come with their own X Window ID.
Quick update: I've
Hi Tim,
> >In the meantime, I've put together a little MIDI routing module for
> >Python and ALSA. I'm tentatively calling it pyseq, and you can find
> >it at
> >http://www.math.tu-berlin.de/~brinkman/software/pyseq.tgz
> >if you're interested. I'm using ctypes to expose the snd_seq_event
> >
[me]
>Ah, an interesting little piece of code. There seems to be a memory
>leak in startMidiLoop() -- the pfds are never free()'d.
My bad. All this c++ made me forget what alloca() does. Sorry.
Cheers, Tim
Hi Peter,
>I remember that I looked at nam a while ago, but I must admit that I
>didn't get very far with it. When I looked at your page again just now,
>I noticed that the tar ball nam*.tgz has disappeared.
Sorry, my fault. It's up now FWIW.
>In the meantime, I've put together a little MIDI rou
Hi Tim,
> I've worked on something that has many parts of what you are looking
> for, but it won't run if compiled with g++ 3.0 or later. The project
> is discontinued, but the sources are here: quitte.de/nam.html if you
> happen to feel adventurous.
I remember that I looked at nam a while ago, b
