Two different pads send the same MIDI note number
Plug your kit in
Donât guess, measure. The kit check is open to everyone and needs no account.
Check my kitA module does not send the label âtom 2â or âright crash.â It sends a MIDI number. If two elements use the same number, an application or plugin can confuse them even when the module's internal sounds seem correct.
The eDrumWork diagnostic builds a note-to-zone map and flags numbers claimed by several elements. This is D12.
Signs of a collision
Two pads play the same plugin instrument, one zone replaces another in the learned map, or two musical voices are counted as one. The effects can look like an articulation problem or crosstalk, but D12 needs neither speed nor simultaneous hits.
The simplest protocol
Hit every element on its own, one after another, several times. Note the dominant number for each zone. When two different, stable zones keep returning the same number, the collision is in the MIDI stream.
The order in which zones are learned must not decide who owns a note. eDrumWork keeps every claim and shows the conflict instead of letting the last zone overwrite the first.
- Two different elements send one number: D12.
- Head and rim are confused during a stroke: D08.
- Numbers differ but the plugin maps them to one sound: software mapping.
- A stray extra note follows the correct one: likely D07.
Assigning a new number resolves the collision, but every map that depends on it must then be updated: eDrumWork, your DAW, virtual instruments, automations and older projects. Some modules lock certain assignments or apply special rules per articulation, so advice has to come from the manual for your exact model.