MIDI Drum Pad Plays the Wrong Sound—or None? A One-Hit Mapping Audit

A drum sound sits behind four separate mapping layers

MIDI is control data, not the drum audio itself. The MIDI Association's MIDI 1.0 message summary shows that a Note On carries a channel, a note number, and velocity. The receiving drum instrument then decides which chain or pad listens to that note and which sound that destination plays. Treating all of this as one opaque “pad assignment” makes random remapping tempting.

Record the number first, then the note name

Do not stop at labels such as C1, C2, or C3. The MIDI Association's note-number table shows multiple octave-naming conventions for the same numeric notes. Two apps can display different octave labels while agreeing on the actual number. Put the integer in your worksheet first; keep the displayed name only as a convenience for that specific app.

Channel 10 is a convention, not a universal repair switch

MIDI 1.0 provides 16 logical channels. Apple documents channel 10 as an example for a GM-compliant sound module. In Roland's V31 documentation, an incoming message must match the desired pad's note-number and channel settings. More generally, the address produced by a sender must be one the receiver's current configuration accepts or maps; a custom rack may use another channel or listen to all channels. Measure the working target instead of forcing every setup to channel 10.

Run a one-hit-per-pad audit without fixing anything mid-test

1. Freeze the setup: duplicate the project or save a version, note the controller bank/preset and receiver patch, and disable MIDI transforms that transpose, scale, repeat, randomize, or generate extra notes.
2. Prove the receiver: click each destination's preview or audition control. If the intended snare is silent when previewed directly, repair the loaded sound, mute, or audio route first.
3. Make an empty capture: select only the intended input device and track, arm recording or open a trusted MIDI monitor, and stop other clips or sequencers. Count only Note On events with velocity 1–127 as hit starts. MIDI 1.0 also permits Note On with velocity 0 to mean note-off; some monitors relabel it as Note Off and some show the original message. Do not count either release form or aftertouch as another hit.
4. Choose a physical order: label the controller's N pads P01–PN from bottom-left to top-right, or use the order printed by the manufacturer. On a 16-pad grid, that is P01–P16. Stay on one bank, strike each pad once at a comfortable medium force, and pause between hits.
5. Copy facts, not expectations: for every hit, record whether an event appeared, numeric note, displayed name, channel, approximate velocity, receiver destination, and heard result. Do not rename or remap until the table is complete.
6. Repeat once: run the same order a second time. A mapping problem should reproduce with the same address; intermittent missing or duplicate events call for a different diagnostic branch.

Do not use the sound you hear as the note identifier. “P01 produced a kick” describes the current receiver patch; “P01 sent note 36 on channel 10” describes the captured message. Keeping those observations separate is what makes the worksheet reusable.

Turn the audit result into one next test

If the note and channel are correct but soft hits disappear, hard hits select another layer, or one strike intermittently duplicates, move to velocity and trigger diagnosis rather than continuing to edit the map. The related 20-hit calibration guide below covers that separate problem.

Choose one source of truth: controller map or receiver map

Remap the controller when the physical layout should travel

This is useful when the controller can save a named preset and you want the same P01–PN addresses across several projects or instruments. Enter the receiver's documented note numbers on the controller, save to a new preset, power-cycle or reconnect, and repeat up to four test pads. Do not overwrite a factory preset unless its manual says the change is recoverable.

Remap the receiver when the kit is project-specific

This is often simpler when the controller is fixed, shared, or difficult to edit, or when one project intentionally layers sounds. Ableton's Receive chooser and Logic's input-note assignment are two official examples of receiver-side mapping. Save the resulting rack, kit, or patch under a new name and keep the controller unchanged.

Avoid two invisible translations

Either route can work. The fragile setup is one where the controller silently transposes notes and the receiver silently remaps them again, leaving nobody sure which file owns the layout. Keep a tiny manifest beside the preset: physical pad, transmitted number/channel, receiver destination, preset name, and date verified.

What the Default Drum Note Map Profile changes—and what it does not

The MIDI Association publishes a MIDI-CI Profile for a Default Drum Note Map based on note assignments widely used and later standardized in General MIDI. That is useful interoperability work, but the profile's existence does not prove that a particular controller, interface path, or instrument supports and uses it. For existing MIDI 1.0 presets and custom racks, confirm support in both manuals and keep the measured one-hit table as the authority.

Verify the saved map in a sweep, a groove, and a reload

• Sweep gate: for N physical pads, P01 through PN and back produces the intended 2N positive-velocity Note On events with no missing or extra hit event.
• Address gate: each physical pad reports the same numeric note and channel on both passes.
• Destination gate: direct preview and the mapped controller hit reach the same intended sound.
• Persistence gate: after saving and reloading both preset and project, the first four pads—or every pad when N is smaller—still pass.

Then play one bar that makes the four core destinations easy to identify. Start at a slow, comfortable tempo. This is a sound-identity check, not a timing score.

Key: K = kick; S = snare; h = closed hi-hat; O = open hi-hat. Replace P1–P4 with the physical positions from your own worksheet. If open and closed hi-hats are mapped correctly but fail to cut each other off, inspect the receiver's choke or exclusive-group setting as a separate test.

1. Pass one—watch the monitor: confirm the expected address sequence without judging feel.
2. Pass two—close the monitor: identify all eight sounds by ear. A consistent substitution points back to the map; an intermittent miss does not.
3. Pass three—reload: save, close, reopen, and repeat. A repair that only lives in an unsaved editor window has not passed.

Common questions

Why does one app call the note C1 while another calls it C2?

Octave labels vary among software conventions. Compare the numeric MIDI note number and channel. If those match, the different text label alone does not indicate a one-octave transmission error.

Should every drum controller transmit on MIDI channel 10?

No. Channel 10 is a familiar General MIDI drum convention, not a universal requirement for custom instruments. The sender and receiver need a compatible channel configuration; record the working channel instead of assuming it.

Should I remap the hardware or the plug-in?

Remap the controller when one portable physical layout is the goal and its preset is safely editable. Remap the receiver for a project-specific or layered kit, or when the controller is fixed. Choose one documented owner for the translation.

Why does one pad trigger two sounds?

First inspect the captured hit events. One positive-velocity Note On with two sounds points toward two receiver destinations sharing an input note; two positive-velocity Note Ons point upstream toward repeat, duplicate routing, a generator, or trigger behavior. Do not count the release message.

Can velocity make the “wrong” sound play?

It can select a different velocity layer or be filtered by a velocity zone, but that is not the first explanation for a stable wrong drum at every force. Confirm note and channel first, then test light and hard hits separately.