What MIDI Mapping Is and What You Can Actually Change on a DJ Controller.

A mapping does not “improve” your controller: it decides what each button does. It is a translation layer between two worlds unfamiliar with each other: hardware sending messages and software with a list of functions it accepts. If a function is absent from that list, no mapping can invent it.

This guide opens the topic. The goal is to predict what you can and cannot change on your equipment, rather than memorise numbers, so you stop losing afternoons trying impossible things.

What MIDI is and what “mapping” really means

MIDI (Musical Instrument Digital Interface) does not carry sound. It carries instructions: “this key was pressed”, “this knob moved to this value”. Audio follows a separate path through your controller’s converter.

The significant, reassuring consequence: a mapping cannot damage your equipment’s sound, because it never touches audio. It only decides which software function is triggered when you move something.

Mapping therefore means constructing a two-column equivalence table:

• What the hardware sends when you move a control.
• The software function you want to respond to that message.

Almost all misunderstandings confuse those columns. The manufacturer determines the first, software determines the second, and you can only pair them.

The four messages you will see repeatedly

The standard’s official table defines control messages, but in a booth you will almost always encounter the same four.

Note On and Note Off

These are on/off messages. A pad or button sends “note X on” when pressed and “note X off” when released. When software lets you assign something to a button, you are almost always assigning a note.

Control Change (CC)

This is a continuous message. A knob or fader sends “control number Y with value Z”. The standard’s table lists defined control numbers, with values from 0 to 127. Use it for volume, filter, gain or any parameter with a position.

Pitch Bend

This is the pitch wheel. It has its own message because it needs far more resolution than ordinary CC: 128 steps are insufficient for fine tempo adjustment.

Program Change

Changes a program or preset. It is rarely mapped in a booth, but appears on equipment switching sound banks.

The three MIDI limits explaining almost every problem

The MIDI channel

Each message travels on one of 16 channels. If your controller sends on channel 3 and software listens on 1, nothing happens and the control appears broken. This is configuration rather than hardware failure.

7 bits: 128 steps

A CC value has 128 possible positions. This is ample for volume or a filter, but insufficient for precise tempo tuning, so manufacturers use Pitch Bend or combine two messages. When a control “jumps” or lacks the detail you want, this limit is often responsible.

Software only listens to what it exposes

This is the guide’s key point. Software publishes a list of assignable functions. Anything absent cannot be mapped, however perfect the hardware message. The list changes across programs and versions, so the same controller can offer much more in one program than another.

MIDI Learn: what it does and does not do

MIDI Learn is the shortcut. Enable learning mode, select the software function and move the physical control: software hears the incoming message and assigns it.

It helps you:

• Quickly pair a control you already know works.
• Recover a lost mapping.
• Assign a single control without knowing its control number.

It does not:

• Create a function absent from the software.
• Control two things at once with a single control, unless software has layers.
• Make an LED respond: output assignments are separate.

Why a button can send MIDI yet be impossible to remap

There are four typical reasons, only one attributable to your configuration:

1. The message arrives, but the function does not exist. Software has no such action, leaving nothing to assign.
2. The control does not speak MIDI. It uses HID or a proprietary protocol. A MIDI monitor will not show it because it is not sending MIDI.
3. Software locks it. Some programs allow free reassignment; others lock functions they consider critical.
4. The channel or port does not match. This is the only case truly fixable through configuration.

Distinguishing case 1 from case 2 avoids the most common mistake: insisting on mapping something that will never appear in the list.

What you can and cannot change on a controller

The table brings the above together: only the first two paths work with ordinary mapping. When a control resists, check which path it uses before blaming mapping.

A surprising detail: a working button does not imply a responding LED. These are separate assignments, one input and one output. A perfect mapping with unlit lights is common; the output part is missing rather than the mapping faulty.

Checking whether your controller is mappable

Before changing anything, perform a two-minute check:

1. See whether it appears as a MIDI device. If software lists it as MIDI, there is scope. Recognising only a specific model may mean HID or its proprietary protocol.
2. Check the input port. In software with a controller manager, each mapping has input and output ports. If set to “none”, the mapping exists but is inactive.
3. Move a control and observe. If nothing lights in the assignment screen, that control is not sending what software expects.
4. Check the assignable-functions list. This is the actual boundary of what you can achieve. Anything absent does not exist for your mapping.

What MIDI mapping is NOT

Distinguish these concepts from the start, because confusing them causes most misinformation on the topic:

• HID is not MIDI. It is another control path with greater resolution and access to elements MIDI does not cover.
• A mod or custom firmware is not mapping. Changing firmware intervenes in equipment; mapping is a software setting.
• A script or middleware is not mapping either. It is an extra layer translating messages when software cannot do so itself.
• USB is not a control protocol. It is the cable carrying MIDI, HID or something else.

Maintaining that distinction tells you which territory you are in and what to expect from each solution.

Common mistakes

• Looking for the wrong function. In software B, you try to assign something existing only in software A.
• Ignoring the MIDI channel. The control sends correctly, but on a channel nobody listens to.
• Assuming LED support is included. It is not: LEDs need output assignments.
• Confusing mapping with a mod. Mapping is reversible and does not touch equipment; a mod is different.
• Reinstalling software first. A lost mapping can almost always be restored by importing or rebuilding it.

Next step

You now know what mapping means and, especially, its boundary. The natural next step is understanding why some controls do not speak MIDI at all: the difference between MIDI and HID explains cases that currently seem inexplicable.