MIDI transmits instructions, not audio — here's how to keep those instructions moving cleanly from one rig to the next.
01What MIDI Actually Sends
Nearly every digital piano, synthesizer, and keyboard ships with MIDI built in, and for good reason. Press a key and your instrument generates a precise digital signal — a MIDI message — that triggers a note on any connected device. That handshake is what lets a single performance drive dozens of sounds at once, blending strings, piano, and synthesized textures into one result. The receiving device decides how those instructions sound; MIDI itself carries no audio whatsoever.
That distinction matters the moment you move a project between studios or rigs. The same MIDI data can sound completely different through a different sound module, software instrument, or General MIDI device — because the playback engine, not the file, determines the timbre.
02Standards Worth Knowing
Consistent playback depends on following established sound specifications. Three Downloadable Sounds (DLS) tiers cover most situations:
- DLS Level 1 sets the minimum feature set a device needs to play DLS samples reliably.
- DLS Level 2 aligns with modern multimedia computing and expands synthesis capabilities.
- Mobile DLS targets mobile applications and pairs with a wavetable instrument for broad compatibility; for a full mobile performance, combine it with Mobile XMF file technology.
General MIDI gear must meet a baseline spec regardless of tier: a complete percussion set, defined note-number mappings, clean audio output, and correct response to MIDI Control Change messages. The General MIDI 1 specification requires a minimum of 24 polyphonic voices. Meet those requirements and your sequences will translate predictably across hardware.
03Keeping Your Projects Portable
MIDI systems are personal — you choose the instruments and sounds; manufacturers supply the raw material. Because a sequence built on one rig may not map cleanly to another, plan to redirect channels and repatch messages whenever you move a project to different hardware. That's not a flaw; it's the protocol working as designed.
Standard MIDI Files (SMFs) make portability straightforward. Import an SMF into any sequencer and your sequence data survives intact, even if the destination program lacks every editing feature you're used to. Use them as your default exchange format.
One principle cuts through every compatibility question: MIDI does not tolerate ambiguity. Every signal must map to a specific, deliberate instruction. Label your channels, document your patch assignments, and test playback on the destination device before a session or show. A few minutes of planning eliminates the most common MIDI headaches — wrong patches, silent channels, runaway notes — before they derail your workflow.