The latest on the Alesis NITRO ULTIMATE

[Strike Multipad] Bug with pad feeling settings?

Started by Tré Cool 412, May 23, 2026, 08:33:30 PM

Previous topic - Next topic

Tré Cool 412

Hi everyone!

As announced in my introduction earlier tonight I'd like to share I problem I ran into two weeks ago, setting up the SMP with 2box TrigIt triggers on an acoustic snare drum, bass drum and a floor tom.

Having the bass drum on TrigIn 1 and the snare on 2/3 I achieve a decent result with my dialled in main and kit settings regarding those triggers. No double triggering, no lost hits, no xtalk / good head-rim separation, acceptable dynamic range, about 70 samples latency (transient mic signal vs transient DI signal, snare to oh mics transients differ about 130 samples).

Adding another trigger on TrigIn 4/5 messes up everything, no matter if mounted on a low or high tom, close or far away from BD and SD. Even splitting up the input with a dedicated edrum y-splitter and using two triggers "mono" for the heads only with the respective trigger setting in the SMP didn't cut it. I spent a whole sunday afternoon trying to dial in good enough settings without any success. 

And I noticed something strange: whenever I set the threshold for trigger 4 or 5 [Pad->Feeling], the threshold for the other trigger was altered as well. This was not the case for trigger 2 and 3. Their threshold values can be set independently. Also the sensitivity of trigger 4 and 5 can be set independently at the same time (at least the GUI makes me believe that but the difference in the dynamics of the sound triggered is audible as well). This also wasn't affected by the trigger type setting (2 triggers vs. dual-zone).

I also noticed, that the respective "head threshold" (triggers 2 and 4) seems to affect the effective threshold of the "rim" as well (no matter the trigger type setting). Increasing the threshold of trigger 2 increased the necessary velocity to produce the rim sound noticeably (but not as if it was the exact same threshold like on 4/5).

I'm at my wits end and absolutely exhausted. Is this a known bug with the SMP FW 1.3 or the SMP in general? If so, I don't consider reaching out to the support a viable solution because Chaser (imho correctly) stated on a different issue here in 2024 already:

QuoteAlesis has never addressed/posted an Official Fix/response and probably never will as the v1.3 Update was released June 2020 (4 years ago) and is more the likely the Final Version.
I'd really appreciate any insights of fellow SMP users, especially those using triggers as well. I've seen this YouTube video where an SMP is hooked up with 5 DD triggers on an acoustic drum set, working like a charm. So I refuse to believe it can't be done, yet. Else the SMP will have to yield to an SPD SX Pro  :-\

Many thanks and kind regards,

Sebastian