On Thu, Nov 07, 2002 at 01:50:29PM +0100, Clemens Ladisch wrote: > > So ALSA rawmidi works, too. > > Apparently, the bug only occurs if a rawmidi port is used through the > alsa-lib functions. (The subdevice checking code in rawmidi_hw.c did > change, but that was a bugfix. Hmmm...)
commenting out that new line doesn't help! > In former days I have had these lines in /proc/asound/seq/clients. There were two endpoints for each direction. Client 64 : "Evolution Electronics Ltd. MK-249C USB MIDI keyboard" [Kernel] Port 0 : "MK-249C USB MIDI keyboard Port 0" (R-e-) Port 1 : "MK-249C USB MIDI keyboard Port 1" (-We-) Now I have two endpoints in the messages, but a mixed entry in the clients list. Is this correct or do we have a multi endpoint problem? [...] Nov 7 14:18:55 tuba kernel: snd-usb-midi: detected 1 input jack(s) on endpoint 1 Nov 7 14:18:55 tuba kernel: snd-usb-midi: detected 1 output jack(s) on endpoint 2 [...] Today /proc/asound/seq/clients shows me only one port of my keyboard and the description doesn't has the port number included like above. tuba:~# cat /proc/asound/seq/clients [...] Client 80 : "External MIDI 2" [Kernel] Port 0 : "MK-249C USB MIDI keyboard Port " (RWeX) [...] I hope this can help martin -- "2b|!2b" ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
