Alesis Strike Pro Weird Triggering + Module Options Won't Save

I have a new Strike Pro kit for about a week now. Since I first started using it, it triggers weird sometimes. For example:
When I hit certain areas on my 2nd tom rim, the kit triggers the ride, the 1st tom and sometimes the snare rim as well.
When I hit certain areas on my 3rd tom rim, the kit triggers the ride, and sometimes, the kit doesn't trigger the rim but the tom itself.
When I press the hi-hat pedal (when I close the hi-hat), the kit triggers a closed - hi-hat sound and when I release the hi-hat pedal (when I open the hi-hat), the kit triggers an opened - hi-hat sound, even thought I didn't hit anything, both when I closed the hi-hat or opened it.
For last, sometimes the kit triggers the snare, the snare rim and any tom without me doing anything.

Another problem I'm having is that any setting I change in the module for example the sensitivity settings, won't load up next time I turn on the module - the settings will change back to the default state. It's really annoying to change the settings again and again every time I turn on the module.
Please help with both problems!
Thank you!
1 person has
this problem
+1
Reply
  • Hello,

    Thanks for posting. Sorry you're having issues with your Strike Pro module. 

    First, can you confirm which version of the firmware you're using with your module? The firmware version will be displayed when the module is powered on. We recommend that all users be running the latest firmware version (1.4), which you can download from the product page.

    I have a new Strike Pro kit for about a week now. Since I first started using it, it triggers weird sometimes. For example: 
    When I hit certain areas on my 2nd tom rim, the kit triggers the ride, the 1st tom and sometimes the snare rim as well. 
    When I hit certain areas on my 3rd tom rim, the kit triggers the ride, and sometimes, the kit doesn't trigger the rim but the tom itself. 
    When I press the hi-hat pedal (when I close the hi-hat), the kit triggers a closed - hi-hat sound and when I release the hi-hat pedal (when I open the hi-hat), the kit triggers an opened - hi-hat sound, even thought I didn't hit anything, both when I closed the hi-hat or opened it. 
    For last, sometimes the kit triggers the snare, the snare rim and any tom without me doing anything.
    Concerning the above, it sounds like you're experiencing crosstalk, which is impossible to prevent due to the physical tendency for vibrations to travel. It’s not common, and your Strike module has already been optimized to eliminate this when using your Strike Kit or Strike Pro Kit. However, like a real acoustic drum kit, your kit can be positioned and played in many different ways depending on your preferences, some of which may cause crosstalk. If that happens, follow these tips to troubleshoot crosstalk:
    1. Make sure your drum and cymbal pads are not touching each other or their clamps.
       
    2. Set up your kit on a soft, carpeted surface. Hard floors will generally cause more vibration through the drum rack.
       
    3. Adjust the tightness of the cymbals wingnut. Wingnuts that are too loose can let the cymbal “bounce” which can cause unwanted vibrations through the boom arm and rack. Wingnuts that are too tight don’t allow enough “bounce,” so the force from a strike will transfer directly to/from the rack.
       
    4. If a specific drum or cymbal pad seems to cause others to sound, increase the XTalk Send setting for that specific trigger. XTalk Send is best turned up on the trigger that’s causing the crosstalk on other triggers.
       
    5. If a specific drum or cymbal pad seems susceptible to unexpected triggering from crosstalk, adjust the XTalk Receive setting for that specific trigger.

    I would also suggest reviewing our Optimizing Trigger Response article here for additional setup tips. 
    Another problem I'm having is that any setting I change in the module for example the sensitivity settings, won't load up next time I turn on the module - the settings will change back to the default state. It's really annoying to change the settings again and again every time I turn on the module

    Regarding this, make sure that you're using a supported SD(HC) card and are saving your settings properly. You should be using a class 10 SDHC card, formatted to FAT32, and should also be between 8 and 64 GB. 

    Follow these steps below to properly save your kits:

    1) After editing the kit, press Kit to enter the Kit menu. 
    2) Press Save. 
    3) In the page that appears, enter the name of the Kit. Press F1/<< or F2/>> to move to the previous or next character, and turn the data dial to change the current character. 
    4) To save the kit, press F3/Save. To return to the previous screen without saving, press F6/Back. 

    If you try to save a kit with a name that already exists, the module will ask if you want to overwrite or replace the existing kit. To overwrite the kit, press F1/Save. To cancel, press F6/Back. If you edit a preset kit, save it, and then want to load that saved kit later, remember that it's actually a user kit. 

    I hope this helps! Let me know if you have any additional questions.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • This reply was removed on 2018-07-12.
    see the change log
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited