In MIDI systems, the activation of a particular note and the release of the same note are considered as two separate events. The messages in this category are the Note On, Note Off, Polyphonic Key Pressure, Channel Pressure, Pitch Bend Change, Program Change, and the Control Change messages. Channel Mode messages affect the way a receiving instrument will respond to the Channel Voice messages.Ĭhannel Voice Messages are used to send musical performance information.
Channel Voice Messages carry musical performance data, and these messages comprise most of the traffic in a typical MIDI data stream. System messages are not Channel specific, and no Channel number is indicated in their status bytes.Ĭhannel Messages may be further classified as being either Channel Voice Messages, or Mode Messages. Channel messages are those which apply to a specific Channel, and the Channel number is included in the status byte for these messages. At the highest level, MIDI messages are classified as being either Channel Messages or System Messages.
There are a number of different types of MIDI messages. MIDI is also being used for control of devices where standard messages have not been defined by MMA, such as with audio mixing console automation.Ī MIDI message is made up of an eight-bit status byte which is generally followed by one or two data bytes. MIDI Machine Control and MIDI Show Control are interesting extensions because instead of addressing musical instruments they address studio recording equipment (tape decks etc) and theatrical control (lights, smoke machines, etc.). So over the past 20 or more years, companies have enhanced the original MIDI specification by defining additional performance control messages, and creating companion specifications which include: The first specification (1983) did not define every possible "word" that can be spoken in MIDI, nor did it define every musical instruction that might be desired in an electronic performance. Other MIDI messages include selecting which instrument sounds to use, stereo panning, and more. You can also adjust the overall loudness of all the notes with a Channel Volume" message. For example, to sound a note in MIDI you send a "Note On" message, and then assign that note a "velocity", which determines how loud it plays relative to other notes. It was designed for use with keyboard-based musical instruments, so the message structure is oriented to performance events, such as picking a note and then striking it, or setting typical parameters available on electronic keyboards. MIDI is a music description language in digital (binary) form. I didn’t get any further to figure out how you would use graph nodes to generate what is probably a log calculation, but the bottom line seems to be the node is expecting a frequency not a MIDI note number.The MIDI Message specification (or "MIDI Protocol") is probably the most important part of MIDI. To use a trigger counter to generate octaves, the step count would have to multiply the current value by 2 each repeat and could then produce octaves (e.g., if you want to produce A octaves A4=440, A5=440x2, A6=(440x2)x2 etc). It appears the node expects a frequency and its function is to quantize that to the nearest note in a tempered scale (possibly provided through the array pin?). If you were to somehow increment by 523 (resulting in 1046) on the C5 value (the third time through), you’ll get roughly a C6. If you change the trigger counter start value to 261.63 (middle C) and step increment to 261, the first two notes will be (roughly) C4 and C5. The problem is it is expecting a frequency. Hopefully someone else will weigh in who is good with Log functions, but I can shed a little light on what the trigger counter is producing versus what the Midi Quantization is expecting.