MIDImappings

MIDImappings describe the assignment of MIDI data streams to control parameters in music software or hardware. A mapping determines which incoming MIDI messages—such as note events, continuous controller (CC) messages, program changes, pitch bend, aftertouch, or system messages—should trigger a particular action within a device or software instrument. The goal is to translate performer input into audible or parameter changes in a predictable, repeatable way.

In practice, a mapping specifies the MIDI channel, message type, data byte (for CC, the controller number; for notes, the pitch), and the value range that activates a parameter. Common elements include CC numbers (0–127) to control volume, modulation, filter, or effects; program changes to select presets; pitch bend for expressive pitch variation; and NRPN/RPN messages for extended controls. Mappings can be created manually by editing a control map or automatically via a MIDI Learn function, where moving a hardware knob or fader assigns it to a software parameter. Many DAWs and hardware controllers provide built-in presets or templates to speed setup.

Storage and interoperability: mappings can be saved as project templates, device presets, or standalone mapping files and are typically portable between projects, but compatibility depends on the host application and hardware. In some ecosystems, global mappings exist on devices, while per-project mappings apply only within a given session. Avoiding conflicting assignments and documenting the intended use help maintain consistency.

Related concepts include General MIDI, which defines instrument programs rather than controls, and MIDI implementation charts that describe a device's supported messages. Effective MIDI mapping supports expressive performance, efficient workflow, and easier reuse of controller configurations across sessions.