Martin Langer wrote:
> tuba:/usr/local/src/alsa-cvs/alsa-lib/test# ./rawmidi -v -I /dev/midi2
> Using:
> Input: /dev/midi2
> Output: NONE
> Read midi in
> Press ctrl-c to stop
> read fe
> read fe
> ...

> tuba:/usr/local/src/alsa-cvs/alsa-lib/test# ./rawmidi -v -I /dev/snd/midiC2D0
> Using:
> Input: /dev/snd/midiC2D0
> Output: NONE
> Read midi in
> Press ctrl-c to stop
> read fe
> read fe
> ...

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...)

And I'm still not able to reproduce it on my machine. I'll test with a
fresh checkout and the official rc5 tonight.

Did anybody test with a non-USB device?


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

Reply via email to