Martin Langer wrote: > On Thu, Nov 07, 2002 at 01:50:29PM +0100, Clemens Ladisch wrote: > > 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!
It fixed a bug. Without that line, opening a specific input-only rawmidi subdevice with a subdevice number would fail. > 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-) Having seperate ports for each endpoint was a side effect of the endpoint handling code. Using rawmidi had the side effect of fixing this. :-) > 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? It's correct, and I consider it more correct than one port for each direction, from a usability point of view. > ... the description doesn't has the port number included like above. > > Client 80 : "External MIDI 2" [Kernel] > Port 0 : "MK-249C USB MIDI keyboard Port " (RWeX) The sequencer allocates 64 bytes for port names, but rawmidi ports have only 32 bytes (including the terminating zero). You should've bought an MK-249 instead. ;-) Regards, Clemens ------------------------------------------------------- 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
