The protocol isn't sound — it's instructions. Understanding that distinction changes everything about how you work with music technology.

01MIDI Is Sheet Music for Machines

MIDI — Musical Instrument Digital Interface — is not audio. Play a MIDI file and you are not playing a recording; you are triggering a set of instructions that tell a compatible device what note to play, how hard, for how long, at what tempo, and on which instrument. The sound you actually hear comes entirely from whatever is generating it at the other end — a hardware synthesizer, a DAW's software instrument, a smartphone app, or the cheap tone-generator baked into a budget sound card. The same MIDI data can sound breathtaking through a Yamaha grand-piano sample library and flat through a low-end chip. The protocol is not the performance. The device is.

That single distinction trips up a surprising number of first-time buyers, who assume that getting MIDI working means they are getting a recording. It doesn't. MIDI messages are performance data: numbers describing pitch (0–127), velocity (how hard a key was struck), duration, and channel assignment. Nothing about them encodes timbre, room acoustics, or dynamic warmth. Those qualities live in the synthesizer or sample library on the receiving end.

Structurally, MIDI rests on three pillars: the message specification that defines what those numbers mean, the file format used to store sequences, and the physical or wireless transport that carries the data between devices. Understanding all three saves a lot of head-scratching when something in your rig stops talking.

The message specification is what devices actually exchange in real time — note-on and note-off events, Control Change messages for parameters like volume and modulation, and System Exclusive messages that carry device-specific data no general-purpose command can handle. Every MIDI-compatible device, from a Roland keyboard to a plugin instrument inside Steinberg Cubase, speaks this same underlying language.

The Standard MIDI File (SMF) format bottles those messages into a portable container you can hand off to any compatible sequencer or DAW. Open an SMF in Avid Pro Tools or Image-Line FL Studio and the performance data is right there, editable down to the individual note.

The transport is whatever physically moves the data. Classic 5-pin DIN connectors — the round, five-pronged ports you still see on plenty of keyboards and synthesizers — defined MIDI hardware for decades. USB-MIDI has largely replaced DIN for studio setups; a MIDI interface sits between your keyboard and your computer, handling the translation. Bluetooth MIDI covers wireless performance scenarios. FireWire carried MIDI in some earlier interfaces, though that transport has all but disappeared from new gear.

One number worth knowing: a single MIDI connection carries 16 independent channels simultaneously. Each channel can drive a different instrument, which is why a single cable once controlled an entire rack of synthesizers without confusion.

Screenshot of a MIDI piano-roll editor showing individual note blocks
Piano-roll MIDI editor showing individual note blocks — performance data, not recorded audio

02Why Editability Is Its Real Superpower

Because MIDI stores instructions rather than recorded sound, nothing is locked in after you hit stop. A wrong note is a number — change it. A sluggish passage needs tightening — quantize it. The tempo drags in the bridge — remap it globally without touching a single note. The string patch sounds thin — swap it for a different sound in seconds. None of this requires re-recording anything, which is why composers, arrangers, and producers have been reaching for MIDI-based sequencers since the early 1980s when the protocol was first standardized.

The tempo drags in the bridge — remap it globally without touching a single note.

That same flexibility explains why General MIDI (GM) exists. GM is a standardized layer on top of the basic protocol that maps instrument sounds to consistent program numbers: patch 1 is always an acoustic grand piano, patch 25 is always a nylon-string guitar, regardless of manufacturer. It was designed so that a sequence created on a Roland module would trigger recognizable instruments on a Yamaha or any other GM-compliant device. The results were not always beautiful — GM playback quality varied wildly by hardware — but the portability was real.

Think of MIDI the way you would think of a recipe: the instructions are precise and repeatable, but the quality of the dish depends on the cook and the kitchen. A recipe does not taste like anything. MIDI does not sound like anything — until a device performs it. Choose that device carefully, and the same sequence you sketched on a laptop controller can evolve into a fully produced track without changing a single note.

The chronology

  1. 1983MIDI protocol first standardized; adoption spreads across keyboard and synthesizer manufacturers
  2. 1980s onward5-pin DIN connectors dominate hardware MIDI connections
  3. 1990s onwardGeneral MIDI spec establishes consistent patch numbering across devices
  4. 2000s onwardUSB-MIDI becomes standard transport for studio interfaces