Subject: Re: [linux-audio-dev] Midi Mapper???
From: Phil Kerr (phil_AT_plus24.com)
Date: Sat Jan 05 2002 - 05:17:45 EET
Yes, all the real time messages can interleave with other MIDI data without
problem, from the specs:
Real-Time messages are intended for all units in a system.
They contain Status bytes only -- no Data bytes. Real-Time
messages may be sent at any time -- even between bytes of a
message which has a different status. In such cases the
Real-Time message is either ignored or acted upon, after which
the receiving process resumes under the previous status.
From: http://www.alsa-project.org/archive/alsa-user/msg02667.html
Phil
martijn sipkema wrote:
> > i can't find my copy of the MIDI spec right now, but MIDI clock (0xF7)
> > is the most obvious example. There are several others relating to the
> > song position pointer that are all single byte, plus MIDI time code as
> > well, plus active sense. in addition, though i don't swear by this, i
> > think that you need to be able to handle a sysex message at any point
> > as well (ie. sysex can interrupt a regular message; in a MIDI Machine
> > Control system, there will be a *lot* of sysex messages running around
> > some of the time, since MMC is all implemented using sysex).
>
> I don't have the MIDI spec (I probably should) but i'm pretty sure that
> this is not the case. As far as I know only realtime MIDI bytes can
> interleave other MIDI messages.
>
> --martijn
This archive was generated by hypermail 2b28 : Sat Jan 05 2002 - 03:13:57 EET