Questions about receiving SysEx, compared to old OMS way
Questions about receiving SysEx, compared to old OMS way
- Subject: Questions about receiving SysEx, compared to old OMS way
- From: Stephen Kay <email@hidden>
- Date: Sun, 23 Apr 2006 00:10:54 -0400
I'm at the point in the porting of a Classic OMS app to Mach-0/CoreMIDI
where I'm reworking the SysEx handling code.
I have a MOTU FastLane USB I'm using for testing at the moment, and if I
dump an example program from one of my Korg keyboards into it, I see that it
gets broken into a large number of single packet MIDIPacketLists, with each
of them containing 32 Bytes, followed by whatever is left over at the end
containing a 0xF7.
Questions:
1. Is this behavior determined by the interface, the interface's drivers,
the Korg, CoreMIDI, what? - who is deciding that these packets are 32 Bytes
long? Do different drivers/interfaces do it differently? I don't have any
other OSX compatible interfaces at the moment....
2. How is one supposed to handle and assemble this stuff, these days? In the
"old day", there were contFlags that told you how to put things together. Do
I simply assume that anything that isn't a complete MIDI message is part of
a SysEx dump, and watch for the 0xF0 and 0xF7's?
Thanks,
- Stephen
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Stephen Kay
Karma Lab - developers of KARMA
http://www.karma-lab.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________
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