MIDI Mapping 101: Customizing Your E-Drum Kit

Out of the box, most electronic drum kits map their pads to a standard set of MIDI notes: kick drum on C1, snare on D1, hi-hat on F#1, and so on. This General MIDI (GM) mapping works for basic playback, but it is rarely optimal for serious practice, recording, or software integration. Customizing your MIDI map is one of the highest-impact tweaks you can make to your e-kit setup.

This guide covers MIDI note reassignment, velocity curve adjustment, and cross-platform configuration so your kit behaves consistently whether you are practicing with DrumDash, recording in a DAW, or performing live.

Why Default Mappings Fall Short

The General MIDI drum map was designed in the 1980s for simple drum machines with twelve or fewer sounds. Modern e-kits have twenty or more pads, including multiple zones per pad (head, rim, edge, bell). The GM map has no standard assignment for a ride cymbal bell, a cross-stick zone, or a fourth tom.

Furthermore, different manufacturers use different default mappings. Roland's TD series, Yamaha's DTX series, and Alesis kits all send different MIDI notes for the same physical pad. When you switch between software, you often find that your snare triggers a wood block or your crash triggers a cowbell.

Understanding MIDI Note Numbers

MIDI notes are numbered 0-127, where each number corresponds to a specific pitch. In drum mapping, these "pitches" are arbitrary labels—they do not represent actual musical pitches but rather trigger slots in a sampler or software instrument.

The most common drum mapping conventions are:

• General MIDI (GM): Kick = 36 (C1), Snare = 38 (D1), Closed Hi-Hat = 42 (F#1), Open Hi-Hat = 46 (A#1), Crash = 49 (C#2), Ride = 51 (D#2)
• Roland TD: Similar to GM but with extended assignments for rim shots, bells, and additional toms.
• Yamaha DTX: Uses a proprietary mapping that often conflicts with GM software.
• VST-specific: Some drum samplers (e.g., Superior Drummer, Addictive Drums) use their own optimized maps that group related sounds contiguously.

When configuring your kit, the goal is to align your drum module's output with the input expectations of your target software.

How to Remap Pads on Popular Modules

Roland TD-17 / TD-27 / TD-50

1. Press KIT to enter kit editing mode.
2. Select the pad you want to remap.
3. Navigate to MIDI > Note Number.
4. Use the dial to select the desired MIDI note.
5. Repeat for each pad and zone.
6. Save the kit to a user slot so you do not overwrite the factory preset.

Roland modules also support MIDI note layering, where a single pad can trigger multiple notes at different velocities. This is useful for creating dynamic sample switching without leaving the module.

Yamaha DTX-PRO / DTX-PROX

1. Enter Trigger Settings from the main menu.
2. Select the trigger (pad) to edit.
3. Find MIDI Note and change it to the desired value.
4. Yamaha modules allow per-zone mapping, so you can set the head, rim, and edge to different notes independently.

Alesis Strike / Command / Nitro

1. Press Menu and navigate to Utility > MIDI.
2. Select the pad to remap.
3. Change the Note value.
4. Alesis modules typically have fewer zone options than Roland or Yamaha, but the basic mapping process is straightforward.

Velocity Curves: Making the Kit Feel Right

A velocity curve defines how the physical force of your stroke translates to MIDI velocity (0-127). The default curve on most modules is linear: hit twice as hard, get twice the velocity. In practice, linear curves rarely feel natural because human touch is not linear.

Most modules offer several curve presets:

• Linear: Direct 1:1 mapping. Best for recording where you want to capture your exact dynamics.
• Exponential: Soft hits produce lower velocities; hard hits are exaggerated. Good for players with a light touch who want more dynamic range.
• Logarithmic: The opposite: soft hits are louder than they should be, compressing the dynamic range. Useful for practice when you want consistent volume.
• Fixed: Every hit sends the same velocity, regardless of force. Rarely useful for musical playing but handy for testing MIDI connections.

We recommend starting with an exponential curve for practice and a linear curve for recording. Adjust per pad if your module allows it: snare and toms often benefit from different curves than cymbals.

Configuring for DrumDash

DrumDash listens for standard GM drum notes on the default MIDI channel (channel 10). If your kit is already mapped to GM, no changes are needed. If you are using a Yamaha or custom map, you have two options:

1. Remap the module: Change the module's output notes to match GM. This is the cleanest solution and ensures compatibility with all software.
2. Use a MIDI translator: Software like MIDI-OX (Windows) or MidiPipe (macOS) can intercept the MIDI stream and remap notes on the fly. This is useful if you cannot change the module's internal mapping.

For the WebGL version of DrumDash, ensure your browser supports the Web MIDI API (Chrome and Edge do; Safari support is limited). You may need to grant MIDI access when prompted.

Recommended Electronic Drum Kits for MIDI Mapping

The following are affiliate links. We earn a commission from qualifying purchases at no extra cost to you.

If you are looking for an electronic kit with deep MIDI customization, these models offer the best balance of features, build quality, and software compatibility:

• Roland TD-07KV V-Drums — Roland's SuperNATURAL engine with Bluetooth MIDI and full pad-zone mapping.
• Roland TD-02KV V-Drums — entry-level Roland with mesh-head snare and noise-reducing design.
• Yamaha DTX452K Electronic Kit — 400+ sounds, USB audio/MIDI, and 3-zone snare pad.
• Alesis Nitro Max Mesh Kit — 8-piece kit with Bluetooth MIDI and 440+ sounds.
• Roland UM-ONE mk2 USB MIDI Interface — compact plug-and-play interface for connecting any e-kit to your computer.

Cross-Platform Consistency

If you use multiple computers or switch between the Android app and the web version, maintaining a consistent MIDI map saves hours of frustration. We recommend:

• Document your map: Create a simple spreadsheet with pad names, physical locations, and assigned MIDI notes. Update it whenever you make changes.
• Save module backups: Most modern modules allow you to export kit settings to USB. Back up your custom map before firmware updates.
• Use a hardware MIDI mapper: Devices like the MIDI Solutions Event Processor can remap notes in hardware, ensuring your kit sends the same notes regardless of which software is receiving them.

Conclusion

MIDI mapping is not a one-time setup; it is an ongoing process of refinement as your playing style evolves and your software ecosystem changes. The time you invest in customizing your map pays dividends in responsiveness, consistency, and musical expression.

Whether you are a beginner trying to make your first e-kit feel natural or an advanced player optimizing for low-latency software integration, understanding MIDI mapping puts you in control of your instrument rather than at the mercy of factory defaults.