MIDISend and MIDISendSysex semantics
MIDISend and MIDISendSysex semantics
- Subject: MIDISend and MIDISendSysex semantics
- From: "Paul D. DeRocco" <email@hidden>
- Date: Mon, 11 Nov 2013 19:37:44 -0800
A few interrelated questions, which Googling has not turned up any answers
to:
1) For MIDISend, it there a requirement that packet breaks not fall in the
middle of a message? I assume that one can use MIDISend to send very long
sysex messages, in which case one might have to break the sysex into
multiple packets, but what about regular Channel and System Common
messages? Can packet breaks fall in the middle of them without causing
problems?
2) Can one do running status suppression in the data given to MIDISend, or
does each message have to have a status byte? Or can running status be
suppressed within a packet, but not across packet boundaries?
3) Is it okay to give MIDISendSysex a buffer containing non-sysex data,
with status bytes other than F0 or F7? Do the bytes go out verbatim,
whatever they are, or does Core MIDI complain, or do something buggy the
way some versions of Windows do with midiOutLongMsg?
4) And finally, do the answers to these questions vary depending upon what
device driver is being used? For instance, USB MIDI would need to deal
with status byte regeneration, if it received data that had running status
stripped, because every non-sysex message goes out in a 32-bit USB packet.
--
Ciao, Paul D. DeRocco
Paul mailto:email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden