Re: MIDI packet processing
Re: MIDI packet processing
- Subject: Re: MIDI packet processing
- From: Scott Ruda <email@hidden>
- Date: Tue, 14 Sep 2004 08:53:02 -0700
From: Doug Wyatt <email@hidden>
Multiple events per packet ARE allowed. You WILL receive them (e.g.
from a USB MIDI interface) and you may create them.
Just don't use running status when writing a packet, or put realtime
in between the bytes of a non-realtime message (except sysex). And you
can make those assumptions when you parse packets.
I'm a bit confused now. According to the comments in the header file:
"In the case of system-exclusive messages, a packet may only contain a
single message, or portion of one, with no other MIDI events."
That seems to conflict with your post saying that realtime events can
be embedded in a sysex message packet. Or are you saying a realtime
'packet' can be embedded within a series of sysex packets like:
<sysex status + data>
<continuation data>
<realtime message>
<continuation data>
<continuation data + eox>
It seems a shame if it's true that realtime messages can be embedded
within a single sysex packet. That means you would have to scan each
packet's bytes and copy byte by byte instead of doing a block move. Is
that what you are saying?
-s
_______________________________________________
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