CoreMIDI behavior?
CoreMIDI behavior?
- Subject: CoreMIDI behavior?
- From: Stephen Davis <email@hidden>
- Date: Mon, 7 Jan 2002 01:23:18 -0800
Just wanted to ask a question or two about current/future behavior of
the CoreMIDI framework with regard to a MIDIReadProc().
Excluding SysEx, so far I've noticed that I only get full MIDI messages
in the call back (status byte + 1/2 data bytes). Usually one per packet
but sometimes two. Either way, it's always whole messages, i.e. no
fragments. Then again, I don't have a wealth of instruments I can test
with to see what happens. Obviously, if one can depend on this
behavior, then that makes packet parsing simpler. The example code
seems to assume this. I'm wondering if it's safe to assume that this
will always be the case. Again, SysEx packets are an exception. One
other notable exception might be real-time SysEx messages. What happens
with them?
Also, running status is not supported in the MIDISend() function but
does CoreMIDI do anything with running status on the inputs? Does it
add the status byte for me or do I need to watch out for running
status? If the status byte is not added, does that my break my above
assumption that packets will always contain complete messages?
stephen