With every new firmware update, the Alesis Strike kit grows smarter and more capable of automatically adapting to each player, including the elusive hi-hat. Hi-hat auto-calibration and new precision settings for fine-tuning response mean a better feeling hi-hat and a more satisfying kit overall. This article covers every step of hi-hat configuration, including physical setup, adjusting settings (if necessary), and what do if the hi-hat is not responding as expected.
Before continuing with this guide, we recommend installing the latest v1.4 firmware update for your Strike module. Visit the Strike product page to download and our installation and setup guide for a complete overview.
While there is no one perfect preset to encompass all drummers, playing styles, hi-hat stands, etc., this guide will explain what you need to know to best adapt the response to you.
While following this guide, remember that every percussion instrument, acoustic or electronic, will require a unique touch. Electronic drum kits rely on distinct and deliberate performances in order to correctly read the player and react with the appropriate sound, velocity, volume, etc. This makes for a satisfyingly consistent and reliable sound when done correctly, but can be more unforgiving to mistakes than their acoustic counterparts. No amount of setting adjustments can account for simply not striking a pad consistently, completely or with enough force.
The intent of this article is to get you as close to a "perfect" hi-hat response as possible, so you can play the Alesis Strike kit with confidence.
The first step to being successful with the Strike hi-hat is the physical arrangement of the hi-hat pads and stand. The Strike hi-hats will work with virtually any hi-hat stand and can easily adapt to your playing style, but their response and feel will depend on if the pieces were put together correctly. Changing settings to account for placing the spring upside down, may only make the response worse.
So, before touching any settings, it's important to ensure the hi-hat is arranged correctly on your hi-hat stand.
During your setup, be cognizant of the placement of the ALESIS logo on this pad. The logo should be farthest away from you, so you can read ALESIS correctly. If you need to turn this around to get a better response, see our troubleshooting section below for instructions.
The automatic calibration will complete the hi-hat optimization process for most users. But, there are a few adjustable parameters, that when used correctly, can help you further define the hi-hat perfomance.
Keep in mind, these settings should only be used to correct specific behaviors and changing settings without a full understanding may only make the response worse. Make adjustments only in small increments and as recommended below to avoid going down the rabbit hole. The settings do require a balance for the best response, but if you find that adjusting one setting means that you need to re-adjust another, you may be adjusting the wrong parameter.
It's popular to reach for the Sensitivity setting when you're experiencing missed or dropped hits, but remember that the sensitivity setting here is intended only for adjusting the chick/stomp setting and will not make the pads more susceptible to responding to hits.
While making your adjustments, keep in mind that most settings will not need to be changed dramatically. If you feel like you've made too many changes and would like to start over, you can reset to all factory settings by holding down STOP and ENTER while powering on the module, or refer to the chart below for all default hi-hat settings for firmware v1.4:
Hi-Hat Bow | Hi-Hat Edge | Pedal | |||
---|---|---|---|---|---|
Sensitivity | 70 | Sensitivity | 35 | Foot Sens | 42 |
XTalck RCV | 03 | XTalk RCV | 00 | Splash | 80 |
ReTrigger | 40 | ReTrigger | 40 | Offset | 55 |
Threshold | 05 | Threshold | 05 | Velocity Curve | Linear |
Curve | LOG1 | Curve | LOG1 | Pedal Curve | LOG1 |
Input Type | PIEZO | Input Type | SWITCH | ||
XTalk Send | 00 | XTalk Send | 00 |
This section compiles common hi-hat behavior and what to do if you experience these particular symptoms. Remember that any setting adjustments should be made in small increments and only for the reasons prescribed. If you find yourself, reaching for more than one setting at a time, or pushing some of the values to their extremes, you may want to reset to the default settings above and start over.
Your hi-hat settings are specific to your hardware (i.e. hi-hat stand) and the physical arrangement of that hardware. If you were to change the distance between the top and bottom pads, switch hi-hat stands, or even the surface the hi-hat is placed on, you may need to make some new adjustments.
Just like a real drum kit, the surface/stage you are playing on will absorb vibrations better or worse than others, which means more or less vibration to be absorbed and used by the hi-hat trigger. For example, if the hi-hat has been optimized to respond best on a hard, concrete floor, you may find that moving to a soft carpet dulls the response. This will affect all triggers, but the intricate nature of the hi-hat makes this a bit more sensitive than the rest of the kit. In this situation, increasing sensitivity or decreasing threshold for the trigger in question (bow, edge, or pedal) will make the hi-hat more responsive when a portion of each strike is being absorbed into the floor.
If it seems like the spectrum of movement between closed and open sounds is slightly off (pressing harder than expected to trigger closed, or mid sounds triggering when the hi-hat is wide open), try a different Curve setting. Choose Log 1-4 to favor more closed and mid sounds, and EXP 1-4 to favor more open sounds.
Try a different Pedal Curve setting. Choosing a logarithmic curve (LOG 1-4) will make it easier to generate a closed or semi-open sound.
The Offset parameter will ultimately decide where the Strike module considers your hi-hat to be closed. If set too high, you may find that chick or closed sounds start triggering too much, even when the hi-hat isn't fully closed. Start playing the hi-hat, preferably with a range of open and closed sounds, and slowly turn the Offset parameter down until the closed and chick sounds start triggering at a point that feels natural. Once this is correct, the other hi-hat parameters listed in the section above can be used to further define the volume and velocity of the response.
If the chick and closed sounds are not triggering enough, do the opposite: Start playing the hi-hat and slowly turn the Offset parameter up until the chick and closed sounds trigger at a natural point in the hi-hat range.
Reach for the splash setting. More footwork may make the splash trigger more accidentally, so decreasing the Splash setting will decrease the range in which the splash will occur. Increasing the value will open the splash range and make it easier to hit.
If you find that you're getting a better response by striking using the back-side of the top-cymbal (the side with the Alesis logo), this could mean a problem with the pad. Contact your nearest support team to help take a closer look.
If the top cymbal is not responding, start by making sure that the top cymbal is plugged in correctly by following the steps in the hardware setup section above. The cable labeled "Hi-Hat" should be connected to the top cymbal and the Hi-Hat input on the module.
If that doesn't do it, disconnect the cable from your crash cymbal and connect it to the top hi-hat cymbal. If you are able to trigger the Crash edge and bow sounds than the cymbal is working correctly and the problem is somewhere in the hi-hat settings or physical setup. If it does not respond, this could mean a problem with the pad. Contact your nearest support team to help take a closer look.
For any further questions or technical support, please visit the link below to connect with any of the following support options: online community support, phone support, email support.
Alesis is a registered trademark of inMusicBrands, LLC. © All Rights Reserved.
All other products or company names are trademarks or registered trademarks of their respected owners.
Privacy Policy | Terms of Use