How to recognize crosstalk between electronic drum pads

Crosstalk occurs when a real stroke on one element also produces a MIDI event from another element that was not played. MIDI cannot identify the physical path of the vibration, but it can establish a repeatable source-to-victim relationship.

The eDrumWork diagnostic tests each mapped zone separately and links extra notes to the strokes just before them.

What reliable evidence looks like

A snare may trigger a tom, a kick may trigger a cymbal, or two crashes mounted on the same rack may react together. The unwanted note is often weaker, but low velocity alone is not proof.

What counts is repetition: the same victim follows several strokes from the same source, within a consistent time window.

Map the kit first

A MIDI number does not mean “tom 2” or “right crash” by itself. eDrumWork first learns the main note of each zone. Until that map is complete, an unknown event stays unassigned instead of being given an invented owner.

Hit one pad repeatedly at normal force, then harder, and test every suspicious pair in both directions. You get a map by direction: A triggers B, B triggers A, or both.

Correct without silencing real playing

Stronger crosstalk rejection can remove the false notes, at a cost: the module may suppress a genuine note when both pads are hit together.

So every retest needs a second phase with both pads hit at once. If the stray note disappears but one element goes missing from the pair, the fix has created D09.

Values do not carry over between models, even within one brand. eDrumWork reports the source, the victim, how often it happens and the MIDI events behind it, then relies on the module you declared for model-specific advice.

Map and test my kit for crosstalk