Re: MIDISendSysex?
Re: MIDISendSysex?
- Subject: Re: MIDISendSysex?
- From: Kurt Revis <email@hidden>
- Date: Mon, 23 Jun 2003 20:29:13 -0700
On Monday, June 23, 2003, at 06:54 PM, Geoff wrote:
MIDISendSysex() is more convenient in many cases
Would you mind sharing some examples of this? In particular would they
relate to situations like when the data packet is so huge that you
might want to use the CompletionProc to know when its finished before
doing the next relevant thing to that data transmission? Also, what
about examples of reasons for setting the .complete flag to true
before the transmission is complete. That would have to be with large
packets as well wouldn't it otherwise the time interval within which
you would interrupt it would be quite small?
You pretty much hit the nail on the head :) Sending sysex over MIDI
can take a considerable amount of time -- remember that normal MIDI
sends at most 3125 bytes/second, and it's not unheard of for sysex
dumps to be 64 KB or more (potentially much more).
Because of this, you might want to show the user how things are
progressing, and perhaps let the user stop the send before it is
complete. It entirely depends on your application.
My original point was: there's nothing magical about MIDISendSysex().
It just splits up the sysex message into smaller chunks, and sends them
out when appropriate, using MIDISend(). You could do it yourself if
you wanted to.
--
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.