Why does my tom also trigger an electronic crash?
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 a crash sounds right after it. If MIDI contains the requested tom note followed by the note of the untouched cymbal, the observable symptom is D07 crosstalk.
The guided eDrumWork diagnostic records which pad was played (the source) and which pad responded without being touched (the victim).
Direction matters
âTom and crash are linkedâ is not precise enough. If the tom triggers the crash, the crash input is the victim. If the crash triggers the tom, it is the other way around. Lumping both directions together may send you off adjusting the healthy element.
Source-to-victim protocol
- Leave the suspect cymbal untouched.
- Strike the tom repeatedly at normal force.
- Repeat with several stronger hits.
- Check whether the same cymbal note regularly follows.
- Reverse the test: play the cymbal while the tom rests.
Repetition and a short, consistent delay are what make the link visible. A single note arriving much later should not automatically be blamed on the tom.
If the extra note belongs to another zone of the same element (head and rim, or bow and edge), test D08 instead. You need a MIDI map of the kit first.
The price of cancellation
More vibration rejection can stop the crash from responding to the tom. Push it too far, and it may suppress a tom and a crash that you really hit together, which creates D09.
After any change, repeat both the source-only series and deliberate simultaneous pairs. Use the documentation for your exact module: names, direction and scale vary across Roland, Yamaha, Alesis, Millenium, Pearl and other products.