On Thu, 13 Feb 2003 17:27:25 +0100 (CET)
Jaroslav Kysela <[EMAIL PROTECTED]> wrote:
<snip>
> Unfortunately, the patch is not perfect. I think that we need to
> buffer the whole MIDI message and send it after completion, because
> it's possible, that you'll get only partial MIDI message from the
> rawmidi API or at buffer overrun / full.
<snip>
Actually I have thought of this off and on, and figured that it
would probably be a Bad Thing:
1) It'd be painful to implement. The mtpav driver would need a
full understanding of MIDI, which means reimplementing things
that are already there at higher levels.
- You need to know the length of each message
- You can't rely on finding the next status & 0x80, because
it might not arrive right away
- Buffering large Sysex dumps would suck ;)
- "Other" messages you don't understand might not get through
2) More importantly: buffering would increase latency, which is
always the reason I don't sit down and start coding.
It's true that it would be nice to be able to send partial messages,
though, but most things use the ALSA sequencer API anyway.
--
Ryan Pavlik <[EMAIL PROTECTED]>
"Oh for the love of evil, not this again." - 8BT
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
