Re: Sysex MIDI Packets
Re: Sysex MIDI Packets
- Subject: Re: Sysex MIDI Packets
- From: Kurt Revis <email@hidden>
- Date: Wed, 11 Feb 2004 00:28:16 -0800
On Tuesday, February 10, 2004, at 12:09 PM, Doug Wyatt wrote:
On Feb 10, 2004, at 0:09, Rib Rdb wrote:
Another developer on my project is interpretting the documentation
differently than I am on what can be in a MIDIPacket, and I wanted to
try to figure out what's right. Our confusion is with Sysex messages
that are mixed with realtime messages. We're trying to figure out if
it would be possible to recieve a packet with data like this:
{ 0xf0, 0, 1, 2, 0xfe, 3, 5, 6, 7, 8, 0xf7 }
or maybe two packets like
{ 0xf0, 0, 1, 2}, { 0xfe, 3, 5, 6, 7, 8, 0xf7 }
or if it will always come with the realtime message in it's own
packet:
{ 0xf0, 0, 1, 2 }, { 0xfe }, { 3, 5, 6, 7, 8, 0xf7 }
thanks for your help.
The latter, with the realtime message in its own packet. If any one is
producing packets differently, it's a bug.
As usual, you should listen to Doug, not to me! He's definitely right,
and my previous message was wrong. I apologize for the misinformation.
That said -- it's not unheard of for MIDI devices, interfaces, and
drivers to have subtle bugs when dealing with sysex, especially if you
throw something else into the mix (like realtime messages). So if it's
easy for you to handle a data stream that theoretically shouldn't
happen, I say, go for the more robust solution.
Doug also pointed out, offlist, that what he's saying only applies to
the MIDIPackets that come from CoreMIDI. If you're dealing with a raw
MIDI stream (like if you're writing a MIDI driver), you still have to
be prepared to get realtime messages at any place in the stream.
--
Kurt Revis
email@hidden
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.