It is very simple. I want to connect a MIDI program change to a shell script execution. For example, if MIDI program change 5 is detected, it would run a shell script that plays a file with ecasound or ogg123; if program change 2 is detected, a shell script would execute an ecasound chain. Four requirements: 1) Associate MIDI program change numbers with arbitrary files. 2) Listen on a MIDI channel for a MIDI program change event. 3) When a program change is detected, execute the file associated with the received program number. 4) After file is launched, return to listening mode and wait for another program change. To allow MIDI sequencer output triggered by a program change, it would be nice for the the listener on the MIDI-In be assigned a channel, but allow global playback of MIDI-Out on all MIDI channels. Why bash/shell scripts? I need the Linux distro to be small, fast, and able to run on recycled hardware or a flash drive. It may also run headless, or with a very small display. So far, the hardest part appears to be getting the MIDI Channel and program change info. --- Carlo Capocasa <capocasa(a)gmx.net> wrote: __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Cool... Okay I'm thinking this: You want to keep the C++ part as small as possible and do as much as you can in bash so you can have control even if you don't now C++. What do you think of a utility that listens for a MIDI program change on a MIDI channel you give it as an argument, then returns which change it was in the exit code? Should be doable under five kilobytes. Carlo

Emiliano Grilli wrote: Reading the output of "aseqdump" might be easier. HTH Clemens

Thanks, I'll try that. --- Emiliano Grilli <emillo(a)libero.it> wrote: __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com