MIDI (Musical Instrument Digital Interface) is a communication protocol — not audio — that transmits performance data such as note pitch, velocity, timing, and control changes between instruments, controllers, and DAWs. Introduced in 1983, it lets a single keyboard trigger any software instrument or hardware synth. Because MIDI carries instructions rather than sound, the same MIDI region can drive an orchestral string library one moment and a trap 808 the next.
Updated May 2026 — MusicProductionWiki.com
If you have ever clicked a piano roll in Ableton, tapped a pad on a controller, or seen a DAW track labeled “MIDI,” you have already worked with MIDI without necessarily understanding what it is. This article breaks down the protocol from first principles so you can use it with intention rather than guesswork.
What MIDI Actually Is
MIDI stands for Musical Instrument Digital Interface. It is a serial communication protocol and file format first standardised in 1983 by a consortium of synthesiser manufacturers including Roland, Yamaha, Korg, and Sequential Circuits. The goal was simple: let instruments from different brands talk to each other using a common language.
Critically, MIDI is not audio. A MIDI signal carries no sound whatsoever. It carries instructions — think of it as sheet music your computer can read in real time. Those instructions tell a sound engine what note to play, how hard to hit it, when to stop, and dozens of other performance parameters. The actual sound is generated by whatever instrument or plugin receives those instructions.
Because MIDI stores instructions rather than audio, a single MIDI region is completely non-destructive. You can change the tempo, transpose every note, swap the instrument, or quantise the timing at any point — with zero quality loss. Compare that to audio, where time-stretching or pitch-shifting degrades the signal.
The Anatomy of a MIDI Message
Every MIDI event is a small packet of digital data. The most common message types producers encounter daily are:
| Message Type | What It Sends | Practical Use |
|---|---|---|
| Note On | Channel, Note (0–127), Velocity (0–127) | Triggers a note when a key is pressed |
| Note Off | Channel, Note, Velocity | Releases a note when a key is lifted |
| Control Change (CC) | Channel, CC Number (0–127), Value (0–127) | Moves a knob or fader — filter cutoff, volume, pan |
| Pitch Bend | Channel, 14-bit value (−8192 to +8191) | Pitch wheel or expression pedal movement |
| Program Change | Channel, Program Number (0–127) | Switches patches on a hardware synth or plugin |
| MIDI Clock | 24 pulses per quarter note | Keeps drum machines and DAWs in sync |
The 0–127 value range you see everywhere comes from 7-bit binary data — a deliberate design choice that kept hardware costs low in 1983. Middle C is note number 60. Velocity 127 is the hardest possible hit; velocity 0 is often used as an alternative Note Off command.
MIDI Channels and Routing
MIDI supports 16 channels on a single cable or connection. Each channel can address a different instrument, so one controller can play a bass on channel 1, a piano on channel 2, and a drum kit on channel 10 simultaneously. Channel 10 is the universal percussion channel in General MIDI — a convention still honoured by most hardware.
In a modern DAW, channels map to individual instrument tracks. When you route a MIDI keyboard vs pad controller into your session, the DAW filters incoming MIDI by channel and forwards it to the correct instrument plugin. Understanding this routing is the foundation of multi-instrument production templates.
MIDI signal flow: one controller sends data to a DAW, which routes each channel to a separate instrument plugin.
MIDI vs Audio — What Is the Difference?
This is the single most common point of confusion for beginners. Audio is a recording of actual sound waves — it is what you hear directly from a microphone or a rendered mixdown. MIDI is a set of performance instructions that a sound engine interprets. For a deeper comparison, see the dedicated guide on MIDI vs audio explained.
A practical implication: if you record a vocalist, you get an audio file. If you record yourself playing a MIDI keyboard, you get a MIDI file — no audio is captured until a plugin renders it. This is why MIDI tracks in a DAW show colourful blocks with note lanes, not waveforms.
MIDI in Modern Production Workflows
Every mainstream DAW — Ableton Live, FL Studio, Logic Pro, Pro Tools — is built around MIDI at its core. When you draw a melody in a piano roll or program a drum pattern, you are editing MIDI. Plugins like Kontakt, Serum, and Massive receive MIDI and output audio in real time.
To get MIDI into a DAW you need a MIDI controller — a keyboard, pad grid, or drum machine — typically connected over USB. Most modern controllers do not need a dedicated audio interface for MIDI; USB carries the protocol natively. If you are still using older 5-pin DIN hardware, an audio interface with MIDI I/O ports will bridge the gap. See the audio interface buying guide for hardware that includes MIDI DIN connectors.
Once captured, MIDI data can be edited with surgical precision: quantise note timing to a grid, humanise it with micro-offsets, adjust velocity curves, or apply pitch-to-MIDI conversion from a recorded audio take. For a practical walkthrough, the guide on how to use MIDI in your DAW covers session setup step by step.
MIDI 2.0 — What Changed
The MIDI Association ratified MIDI 2.0 in 2020, with hardware and software support rolling out through 2023–2026. The headline upgrades: velocity resolution jumps from 7-bit (128 steps) to 32-bit (over four billion values), per-note pitch bend and expression become standard, and the protocol gains bidirectional capability so devices can auto-configure themselves. For most producers working entirely inside a DAW with modern plugins, MIDI 2.0 benefits are still arriving gradually — but it is worth knowing the ecosystem is evolving. Logic Pro 11 added MIDI 2.0 support, and Ableton Live 12 includes early implementation for compatible hardware.