# Alesis Nitro Max - Strange Conflict Between Tom 3 and Ride
**URL:** https://forum.bfddrums.com/t/alesis-nitro-max-strange-conflict-between-tom-3-and-ride/8596
**Category:** General Discussion
**Created:** [February 27, 2025, 5:25am UTC](https://forum.bfddrums.com/t/alesis-nitro-max-strange-conflict-between-tom-3-and-ride/8596 "2025-02-27T05:25:50Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@ccie5754](https://forum.bfddrums.com/u/ccie5754)
#### Post date: [February 27, 2025, 5:25am UTC](https://forum.bfddrums.com/t/alesis-nitro-max-strange-conflict-between-tom-3-and-ride/8596/1 "2025-02-27T05:25:50Z")
Ok strange situation:
- Ride cymbal works fine.
- Tom 3 pad works fine.
- If I play ride followed by Tom 3 in close succession, everything is fine.
- If instead I play Tom 3 and Ride right after (close together hit), ride does not trigger (no sound on Alesis headphone jack)
- Simultaneous is 50/50
Doesn’t matter if I hit the ride harder, it’s dead. If I wait about one second between hitting tom 3 and ride, they work just fine. This is the only combination that gives me this weird result. Any ideas?
---
### Author:  [@Thecubasekid](https://forum.bfddrums.com/u/Thecubasekid)
#### Post date: [March 7, 2025, 3:08pm UTC](https://forum.bfddrums.com/t/alesis-nitro-max-strange-conflict-between-tom-3-and-ride/8596/2 "2025-03-07T15:08:12Z")
dont know the Nitro Max Module, but on my Alesis DM10 module i had some simialr issues, and it was related to cross talk send and cross talk recieve settings being too high (i went overboard initially trying clear cross talk, i got rid of xtalk but had some missed triggers in some scenarios) lots of tweeking on sensitivy / threashold / xtalk send and recieve eventually got everything working good with 99%+ cross talk gone while having much less aggressive settings.
---
### Author:  [@ccie5754](https://forum.bfddrums.com/u/ccie5754)
#### Post date: [March 11, 2025, 9:33pm UTC](https://forum.bfddrums.com/t/alesis-nitro-max-strange-conflict-between-tom-3-and-ride/8596/3 "2025-03-11T21:33:23Z")
THANK YOU!!!
That’s exactly what my problem was!! All good now 🙂