Hello,

...

Does the same happen if you run "amidi -d -p hw:2,0" when no other program is connected?

amidi is not included in Musix, but alsa-utils-1.10rc3 can be compiled on Musix 0.39 (./configure, make). Running amidi -d -p hw:X successfully DOES dump the incoming midi data. However, even trying to simply play a .mid-file with aplaymidi fails, leading to this: cat /proc/asound/cardX/midi0 -> UM-1 Output 0 Tx bytes : 0 Mode : native Buffer size: 4096 Avail: 4045 (!!) Input 0 Ry bates : 0 To mention it again: this happens with the realtime-kernels of the GNU-Musix live-distribution, but not with the ordinary kernels. Hope this helps, Jens Clemens Ladisch schrieb:

Jens Gulden wrote:

...

cat /proc/asound/card2/midi0 ->

MidiSport 2x2

Output 0 Tx bytes : 0 Output 1 Tx bytes : 0 Input 0 Rx bytes : 1186 Buffer size : 4096 Avail : 1186 <--- ### SHOULD BE 0, NOT ==RX BYTES! ### Overruns : 0 Input 1 Rx bytes : 0

Instead of passing the data further to the connected timidity, it gets stuck in the receive-buffer. When 4096 is reached, overruns start to count up.

Does the same happen if you run "amidi -d -p hw:2,0" when no other program is connected?

Regards, Clemens