My drum pad plays the wrong instrument in software
Plug your kit in
Don’t guess, measure. The kit check is open to everyone and needs no account.
Check my kitYou hit a tom and hear a cymbal, or two pads control the same plugin voice. The problem is easy to hear, but the cause may be the note the module sends, a collision between zones or the software map.
The eDrumWork diagnostic starts with raw MIDI so D12 can be identified without relying on the selected sound.
Compare three maps
Three links are involved: stroke to module note, note to eDrumWork zone, and note to plugin instrument. A mistake at any of these levels sounds much the same, and changing all three at once destroys the evidence.
Turn off automatic playback and hit each zone on its own. Write down the number, not the sound. Two different zones that consistently send the same number are D12.
If every pad has its own number, check the virtual instrument's map. The module may be right while the software expects a different convention.
If zones on the same pad swap between head and rim depending on the stroke, test D08. If a stray note comes with the correct one, test D07.
Changing the assignment at the source can help several applications tell the elements apart, but older projects and maps then need updating. Export or note down the current map first. Roland, Yamaha, Alesis, Pearl, Millenium and 2box modules may limit which notes can be edited or apply rules per articulation.
The pad learned first has no more claim to the note than the second. eDrumWork shows the collision instead of silently overwriting a zone.