Author Topic: Anyone having this issue with Strike module? CC4 ghost data  (Read 1507 times)

Anyone having this issue with Strike module? CC4 ghost data
« on: December 27, 2017, 04:07:42 PM »
Video here: https://youtu.be/lAgv855goTs
and here: https://youtu.be/xYs6dCKw-lo

Basically the strike module is sending cc4 data when there was no cc4 input from the foot controller. I can unplug all hi-hat related cables from the module and this data is still being sent out. If I turn cc4 in the module the data stops. This is making it impossible to play the hi hat.   Anyone else had this issue? I'm currently waiting to hear back about RMA for the module.

Offline Chaser

Re: Anyone having this issue with Strike module? CC4 ghost data
« Reply #1 on: December 27, 2017, 10:24:30 PM »
Video here: https://youtu.be/lAgv855goTs
and here: https://youtu.be/xYs6dCKw-lo

Basically the strike module is sending cc4 data when there was no cc4 input from the foot controller. I can unplug all hi-hat related cables from the module and this data is still being sent out. If I turn cc4 in the module the data stops. This is making it impossible to play the hi hat.   Anyone else had this issue? I'm currently waiting to hear back about RMA for the module.

The Strike Module sends cc4 continuously...until the hats are completely closed..the controller/pedal determines the amount of openness...
Push down on the pedal and the metering will slow in midiox..push all the way down and it will stop and the midi being sent will no longer show cc controller at the side
You'll see the midi notes being sent highlighted in green...as you lift your foot it will start the continuous signal again

Re: Anyone having this issue with Strike module? CC4 ghost data
« Reply #2 on: December 27, 2017, 10:49:27 PM »
That's not what's going on here. When the cc4 controller works appropriately it sends no data, it only sends when there is a change in velocity. It should not be sending random gibberish data when there's no activation, and also when there are no cables plugged in to the module. When you apply pressure to activate the foot pedal, the data doesn't slow, it just shows whatever velocity value you are sending until you get to 127 which may make you think it slows but it's just sending 127 a million times a second. Check yours yourself with midiox and you will see that when no pressure is applied the cc4 stops sending info.

If you have a midi keyboard test this with a mod wheel. Do you get random gibberish data when the modwheel is stationary? No, you only get data when it moves. The strike module is for some reason sending random cc4 numbers with or without input from cc4, which it should not be doing. I should also mention that the module doesn't always do this, but when it does it can last a couple days before it resumes normal behavior. This result in the hi hat not behaving correctly because it constantly thinks it's in a state of open close open close open close.

« Last Edit: December 27, 2017, 10:52:17 PM by Blargomite »

Offline Chaser

Re: Anyone having this issue with Strike module? CC4 ghost data
« Reply #3 on: December 28, 2017, 12:41:26 AM »
That's not what's going on here. When the cc4 controller works appropriately it sends no data, it only sends when there is a change in velocity. It should not be sending random gibberish data when there's no activation, and also when there are no cables plugged in to the module. When you apply pressure to activate the foot pedal, the data doesn't slow, it just shows whatever velocity value you are sending until you get to 127 which may make you think it slows but it's just sending 127 a million times a second. Check yours yourself with midiox and you will see that when no pressure is applied the cc4 stops sending info.

If you have a midi keyboard test this with a mod wheel. Do you get random gibberish data when the modwheel is stationary? No, you only get data when it moves. The strike module is for some reason sending random cc4 numbers with or without input from cc4, which it should not be doing. I should also mention that the module doesn't always do this, but when it does it can last a couple days before it resumes normal behavior. This result in the hi hat not behaving correctly because it constantly thinks it's in a state of open close open close open close.

I ran some tests as I have 2 modules..one has v1.2 and the other v1.3...no issues with the v1.2 ..it responds as I mentioned , the more the pedal is depressed you'll hit the sweet spot and CC4 will start scrolling , if you take your foot off , it will splash..press all the way down(hats fully closed) and it will stop..the same if you let the pedal all the way up ..the CC4 will stop. .. however the module with v1.3 has erratic CC4 behavior..exactly as your video
the CC4 never stops scrolling.

I was running the module with v1.2 in midiox when I posted previously , that's where I came up with my response to how the module was reacting..I hadn't run a tests with midiox since I purchased them.
I downgraded the v1.3 module to v1.2 and the erratic CC4 went away , so with the implementation of the Auto-Hi hat calibration and other "improvements" something went wrong...
It was also reported on the Alesis site...but the user claimed the CC4 problem disappeared after a couple boots..
I tried more than a few re-boots... it didn't go away..not until I downgraded to v1.2
http://community.alesis.com/alesis/topics/cc4-input-into-sd3-craziness-strike-pro

STRIKE Firmware v1.3... midiox

PEDAL UP
https://postimg.org/image/z4gcud4y3/
PEDAL 1
https://postimg.org/image/6etgxqo3f/
PEDAL 2
https://postimg.org/image/ohmjoyrnv/
PEDAL DOWN
https://postimg.org/image/j67n49daz/

EDIT:
The  v1.3 sound content along with the 2 new kits seem to work fine with v1.2 DSP OS and v1.2 Trigger OS
« Last Edit: December 28, 2017, 02:28:11 AM by Chaser »

Re: Anyone having this issue with Strike module? CC4 ghost data
« Reply #4 on: December 28, 2017, 12:22:05 PM »
Looks like downgrading to v1.2 is the fix for the time being. Thanks for verifying that there is a problem with v1.3.