poprobotproductions
New Member
I saw a similar thread from a couple years ago regarding triple zone ride problems with the Nitro and there was some confusion about the number of inputs on the pad and capability of the Nitro module to even offer a bell sound. So I am starting a new thread because that one wandered and didn't quite desxcribe the same issue I am having. I know I will be able to get to the bottom of this and hopefully help others who might have a similar problem.
I recently purchased the Alesis Command X - got it second-hand for a steal! ($400)
Really wanted a more versatile ride, so I bought the Alesis triple zone 14 inch ride pad.
(Also ordered the Go e-drum hi hat controller from Taiwan which will make this a super kit when it arrives in 3 weeks!)
When I connect the ride cable from the Command's proprietary snake into the ride pad input, it triggers the typical dual zone (bow, edge) of the cymbal.
But when I connect a 2nd TRS cable to the cymbal pad's bell input and the module's "Tom3" (extra input), I get the tom sound in conjunction with the ride's bow sound.
I assume the layering is a crosstalk issue which I can adjust - but the problem is, I want to be able to change the sound of that tom to a ride bell, without altering the tom3 sound of the actual tom pad.
I often use this kit to trigger midi notes in EZ Drummer2 as well (sounds soooo much better than the Alesis patches), which would make any patch programming in the Command module a moot point. But When I strike the ride pad's bell, it doesn't show up in the Command's data window as a separate trigger than the ride, so I don't know what midi note the bell is triggering. I only know it is triggering a tom3 sound, but I don't want to alter that midi note for fear it will change the actual tom.
I'd love to be able to program the module to accept the ride's bell as a unique trigger so that I can assign a bell patch in the Alesis - but even more-so, I want to be able to grab that midi note so I can assign it to the ride bell in EZ Drummer.
Anyone out there know a solution?
I recently purchased the Alesis Command X - got it second-hand for a steal! ($400)
Really wanted a more versatile ride, so I bought the Alesis triple zone 14 inch ride pad.
(Also ordered the Go e-drum hi hat controller from Taiwan which will make this a super kit when it arrives in 3 weeks!)
When I connect the ride cable from the Command's proprietary snake into the ride pad input, it triggers the typical dual zone (bow, edge) of the cymbal.
But when I connect a 2nd TRS cable to the cymbal pad's bell input and the module's "Tom3" (extra input), I get the tom sound in conjunction with the ride's bow sound.
I assume the layering is a crosstalk issue which I can adjust - but the problem is, I want to be able to change the sound of that tom to a ride bell, without altering the tom3 sound of the actual tom pad.
I often use this kit to trigger midi notes in EZ Drummer2 as well (sounds soooo much better than the Alesis patches), which would make any patch programming in the Command module a moot point. But When I strike the ride pad's bell, it doesn't show up in the Command's data window as a separate trigger than the ride, so I don't know what midi note the bell is triggering. I only know it is triggering a tom3 sound, but I don't want to alter that midi note for fear it will change the actual tom.
I'd love to be able to program the module to accept the ride's bell as a unique trigger so that I can assign a bell patch in the Alesis - but even more-so, I want to be able to grab that midi note so I can assign it to the ride bell in EZ Drummer.
Anyone out there know a solution?