[sdiy] MIDI spec
Colin f
colin at colinfraser.com
Mon Dec 2 12:39:53 CET 2002
----- Original Message -----
From: "Paul Maddox" <P.Maddox at signal.qinetiq.com>
To: "charlie lamm" <charlie at www2.charlielamm.com>;
<synth-diy at dropmix.xs4all.nl>
Sent: Monday, December 02, 2002 9:22 AM
Subject: Re: [sdiy] MIDI spec
> if its just the Midi codes you want, take a look at this ;-
> http://www.midi.org/about-midi/table1.htm
>
> its well burried on the MMA site, I guess they'd rather you buy the book.
> It doesn't go into massive amounts of details, but its more than enough to
> get you going.
Note that this table is not quite up to date.
System Common message F1 is listed as undefined, but it's the midi timecode
quarter frame message status byte, and is followed by a data byte. If your
parser just ignores F1 and retains it's running status, you're going to get
some weird shit if you start sending MTC.
Also F4 and F5 are undefined bytes, but should reset running status. F9 and
FD are also undefined, but should *not* affect running status. (i.e. system
common resets running status, system realtime doesn't, even for undefined
bytes)
See http://crystal.apana.org.au/~ghansper/midi_introduction/contents.html
for more useful info.
Colin f
More information about the Synth-diy
mailing list