Hello, very weird: 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. Connections have been set up using qjackctl. vkeybd->timidity works fine. The system is Musix0.50b12, realtime-kernel 2.6.15.4, with manually added MidiSport2x2 firmware. However, I don't think this is a typical "My-MidiSport-does-not-run-on-Musix" problem, as the firmware successfully loads and the MidiSport gets recognized as available device in ALSA. Even the data seems to arrive well as shown by "Rx bytes" (number of bytes per note-event is correct). What is wrong? Further information: cat /proc/asound/cards -> 0 [D3 ]: USB-Audio - Direct Mix USB 3 Aardvark Computer Systems Direct Mix USB 3 at usb-0000:00:07.2-1.3, full speed 1 [Solo1 ]: ES1938 - ESS ES1938 (Solo-1) ESS ES1938 (Solo-1) rev 0, irq 10 2 [M2x2 ]: USB-Audio - MidiSport 2x2 M-Audio MidiSport 2x2 at usb-0000:00:07.2-1.2, full speed cat /proc/asound/devices -> 16: [0- 0]: digital audio playback 24: [0- 0]: digital audio capture 0: [0- 0]: ctl 1: : sequencer 33: : timer 40: [1- 0]: raw midi 36: [1- 0]: hardware dependent 48: [1- 0]: digital audio playback 56: [1- 0]: digital audio capture 32: [1- 0]: ctl 72: [2- 0]: raw midi 64: [2- 0]: ctl cat /proc/asound/modules -> 0 snd_usb_audio 1 snd_es1938 2 snd_usb_audio cat /proc/asound/version -> Advanced Linux Sound Architecture Driver Version 1.0.10rc3 (Mon Nov 07 13:30:21 2005 UTC). Thanks for help, Jens