On Wed, 12 Feb 2003 21:41:50 +0100 (CET) Jaroslav Kysela <[EMAIL PROTECTED]> wrote:
> It seems that mtpav don't remeber the old status byte for each > channels. If it's true, then we need to take care about the expansion > in the mtpav driver, because the sequencer MIDI driver removes > duplicated status bytes to opmitize throughput. Yes! this works! (Or basically the equivalent does.) Now, from looking at things, it seems like the MTPAV treats a device change like another midi message... basically using 0xF5 as a midi system message to change device. According to the references I'm looking at, 0xF5 is left undefined. This means technically the mtpav isn't wrong, just strange. ;-) For a somewhat elegant solution, it may be possible to have the mtpav track the last device and running status. I initially thought this would be impossible, but it looks like it could be done in snd_mtpav_output_port_write() (mtpav.c:298). I will work on this and submit a patch shortly, unless someone suggests a better solution. > To test this behaviour, please, try this patch: <snip> Thanks :-) -- Ryan Pavlik <[EMAIL PROTECTED]> "I distinctly remember dancing on your grave." - 8BT ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
