Strike Pro problems: Hi-hat barking, volume sliders, Strike Content Update 1.2

Anyone else have problems with the hi-hat (specifically no longer being able to "bark") AFTER updating to 1.2? It seemed that no matter if I adjusted the module settings or the height of the top hi-hat made any difference. I actually reinstalled the 1.1 OS and trigger settings and it fixed the problem. By the way, I couldn't get the "splash" to work on the hi-hat either after the update no matter what the setting was on. Perhaps this is relevant? (All I can say is yes, I know how to make the hi-hat "splash").

P.S.
I also wasn't able to install the "Strike Content Update 1.2.bin" after successfully installing the Strike Editor, either. I submitted a "ticket/question" but haven't heard from anyone in about three days.

Thanks for your time.

P.P.S.
You know what, while I'm here:
Perhaps this is only software related, but when I set the sliders below about the halfway point, the sounds get very whispy and hollow/distant. I don't quite know how to explain it. One would think they would simply get quieter, but instead they get "fake" and hollow. Does this make any sense?
UPDATE: To better describe the problem, I actually hear a slight delay, too. Meaning the lower I drag the sliders down, the more of a distant, hollow, and delayed sound I hear. The longest the delay lasts is about a third of a second or so. Maybe this will help in the diagnosis.

P.P.P.S.
On this webpage on the right side it asks me to "add at least one product or service" before I submit this post. The list isn't even in alphabetical order. Not very user-friendly.
1 person has
this problem
+1
Reply
  • Hello,

    Thanks for posting. 

    I'm not sure what you're referring to when you say "bark", but if your hi-hat is not triggering properly, this would indicate the firmware update was not done properly. Follow these instructions below:

    Sound Content Update Instructions (Windows and Mac OS X)
    1. Download the Strike Editor software for your operating system as described in the Downloads section above. 
    2. Follow the software installation instructions in the included user guide (you will use the Strike Editor to update the internal (preset) content of your Strike module).
    3. Make sure the USB port on your Strike module is connected to your computer. Connect it directly to your computer and not through any USB hub or other peripheral devices to ensure a fast, reliable connection.
    4. In the Strike Editor, select File Alesis Factory Content Update.
    5. Locate and select the update file that was included in your firmware update download package: Strike V1.2 Content Update.bin.
    6. Updating Alesis Factory Content will appear in the status bar at the bottom of the Strike Editor window. When the update is finished, the Strike Editor will show Alesis Factory Content successfully updated.
    7. Click OK.
    You know what, while I'm here: 
    Perhaps this is only software related, but when I set the sliders below about the halfway point, the sounds get very whispy and hollow/distant. I don't quite know how to explain it. One would think they would simply get quieter, but instead they get "fake" and hollow. Does this make any sense? 
    UPDATE: To better describe the problem, I actually hear a slight delay, too. Meaning the lower I drag the sliders down, the more of a distant, hollow, and delayed sound I hear. The longest the delay lasts is about a third of a second or so. Maybe this will help in the diagnosis. 
    This should be addressed by correctly performing the update above. If it doesn't, please let me know, and we'll dig deeper into this.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I appreciate your assistance. May luck be on my side and may we both have patience in this endeavor, heh.

    By "hi-hat barking" (not sure if you're a drummer, but a quick Google will home in on what it is just in case the following description does it no justice) I mean when I have my foot pressing down on the hi-hat pedal and strike the hi-hat with a stick while simultaneously lifting my foot off of the pedal; basically starting the sound with a closed hi-hat while opening it midway through.

    Although you said I should update to 1.2 (alluded to this, at least), you only copy-and-pasted the instruction for the 1.2 Sound Content update. I'm assuming you mean the full, three-piece update, including the OS v1.2, the Trigger v1.2, and the Sound Content v1.2, which is following (because I'm using Windows) numbers 2, 3, 4, and 6 in this article (http://www.alesis.com/kb/article/2341).

    Successfully installed the 1.2 OS and Trigger updates. Per the instruction in both the .pdf and online article, I restarted the module ONLY AFTER installing both the OS and the Trigger updates. This leaves me with a module that is powered on like normal (still left the updated open in Windows because I'm following the instructions to a "t", leaving no room for error on my part), and the OS and Trigger versions (In the sub-menu of the "UTILITY" button) reads 1.2, meaning two of the three updates were properly installed, just like before, and as they should be.

    "After Update Complete / Please restart now appears on the screen, restart the module. You’re done with the firmware update! Remember to update the sound content too. Click here to go to the sound content update instructions."
    (If the text doesn't match what you're looking at this may be because Alesis has two different versions of the update instructions, one in the .pdf packed with the update itself and another in the aforementioned article)

    Now onto the Sound Content update, just like before:
    1. I uninstalled the Strike Editor software and reinstalled it fresh, just in case.
    2. Open the Strike Editor and immediately get the error message "The Strike Hardware could not be found" (remember, per the previous instructions, I currently have the module turned on after the restart and am sitting at the kit selection overview screen). I hit "Ok" under the message and the window closes and the software doesn't start.
    3. THIS is the specific problem I alluded to in the first post and have now more explicitly laid it out for you here (hopefully this is the issue that, once resolved, will fix the other problems I mentioned, best case scenario).

    At this point, I'll do everything you say, step-by-step.

    P.S.
    Also tested the hi-hat barking again. Still not working on various pedal settings. Also, the issue with the distant/echo-like/delayed sounds after adjusting the manual volume sliders below the halfway point is still happening. Again, the slider issue has happened since I got the drumset, so is not isolated to the 1.2 update.

    Thanks again. Just let me know if anything was unclear and I'll get back to you.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I wanted to try my hand at this again, and tried one thing differently: I plugged the USB cable into the back of my computer rather than in the front. When I read "don't plug it into a USB hub" I did not interpret that as "do not plug it into the front of your computer". I reinstalled the first two 1.2 OS and Trigger updates successfully (no difference here as before), but when I started the Strike Editor software it no longer crashed, which was new. I followed the instructions as before, loading the .bin and processing the update (I noticed on the Strike module it was "streaming" at the bottom of the screen), but was greeted with an error in Strike Editor software after about one minute:
    "The application encountered problems during startup and will now close."
    After clicking "Ok" it sat there for a few seconds and crashed with a Windows error.

    Just to see if this changed anything, I began to play. Same exact problems.

    P.S.
    I was reading some other people's issues and came across a reply of yours that has me slightly worried:

    "If you are experiencing any of the symptoms like the ones listed below, do NOT attempt to update the firmware in order to remedy this...
    - Latency/delay in playback or any audio playback related issues"

    As I mentioned in an edited/updated post above, when I move the volume sliders below about halfway, I begin to hear a roughly third of a second delay in the sounds. Although the volume does seem to go down, it suffers from a "hallway" kind of effect and only triggers the sound after about a third of a second. Again, this has occurred since I owned it, although I kind of didn't think much of it. Now that I'm getting all these issues sorted, I just wanted to make sure that was mentioned as well. If there's a catastrophic issue with the module itself, I'd like to get that dealt with well before the year warranty has passed.

    Thanks again.

    I'll just revert back to 1.2 until you're ready so at least I can bark the damned hi-hat, heh.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • This reply was removed on 2017-09-01.
    see the change log
  • Can you please provide a screenshot of the error message you're experiencing?

    If you notice that your pads sound like they're  being delayed, there's a good chance your triggers have not been adjusted properly. This guide will walk you through optimizing the response of your triggers on your Strike Pro Kit, giving you the best performance:

    Let me know how this goes.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Hello Corey,

    Funny enough, I tried it again to get a picture of the error (with all parameters exactly the same) and the update went through without issue (guess it arbitrarily takes two tries?).

    Although this didn't fix the echo/delay issue I described with the volume sliders, what did fix this issue (after a lot of poking around) was lowering the "Reverb Send" (in "Voice">"FX/Midi") to 0. What seemed to be happening was that this setting leaves a faint trace of the sound immediately behind the triggered sound to give it a bit more depth (which I don't seem to care much for anyways). When I'd lower the volume on the sliders, it would lower the volume on the triggered sound itself, but not this reverb. This led to the dominant sound being the reverb after lowering the volume on the slider to a point below halfway and causing that roughly third of a second delay. Maybe programmers can tweak the sliders so that the main triggered sound and the reverb decrease in volume together such that this doesn't happen (for those people who actually want the reverb along with lower volumes on the slider).

    I tried to explain what hi-hat barking is to Bill, so I'm going into this assuming you know what I mean by this, just let me know if you still don't, but here's one last attempt: While you have your foot on the pedal, you strike the hi-hat at the same time as lifting your foot off the pedal and closing it almost immediately. Here's a video that explains it perfectly well and gives plenty of examples: https://www.youtube.com/watch?v=mHRF_...

    However, it seems this successful "Content" update failed to help the hi-hat barking issue. I tried raising the top hi-hat a bit off of the bottom hi-hat and I tried letting it rest on the bottom hi-hat (with the spring properly seated in both cases). I tried various combinations of "open" and "closed" settings to no avail. I even tried mucking with the new "splash" setting, but got nowhere.

    The interesting thing is is that with the previous 1.0 and 1.1 OS/Triggers, the hi-hat barking worked fine and emulated an acoustic kit almost perfectly. The only way I can bark now is if I wait unnaturally long after I open the hi-hat before I strike it with the stick (basically the same as striking it when my foot is off the pedal completely), which isn't acceptable, and even then it isn't consistent. You should be able to strike the hi-hat AS it's opening to bark it. There had to have been some change to the triggers (at least in the hi-hat, maybe the "splash"?) in the 1.2 update that changed how barking works. I don't know if the programmers would know what they did, but something changed and made it worse.

    Thanks for offering your assistance as well.

    Peace and farewell.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Well, I can kind of get a decent bark response if I tighten the top hi-hat just slightly above the lower one, although it's just not as responsive as in the previous versions for some reason. I have the settings for Open, Closed, and Splash at 99, 78, and 70, respectively. Something about the 1.2 update made this a bit more tedious to set up to perfection (with my hi-hat stand at least: Iron Cobra 200). I don't know.

    So I guess all my problems are fixed (I'll assume the barking is just going to be more tedious to set up properly, I'll need to fool around with the settings even more to fine tune the blasted thing).

    Peace and farewell, and thanks for your time. Looking forward to what the next update might have to offer (assuming there is one, of course).
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Update:
    Couldn't stand it. Had to revert back to the v1.1 because the barking works so much better with it for some reason. Hopefully the open-closed hi-hat dynamics will be tweaked a bit differently in an upcoming update (maybe it had something to do with adding the "splash" setting).

    Maybe it's just me. Oh well.

    Peace and farewell.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I had the same problem. I had to revert back to v1.1 because of this also.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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