Author Topic: STRIKE Module Firmware /Editor Updates  (Read 5384 times)

Offline Chaser

STRIKE Module Firmware /Editor Updates
« on: November 20, 2017, 04:04:01 PM »
STRIKE Module Firmware 1.3
STRIKE Editor 1.1.1
New samples,instruments and kits (Power Station New England)
Automatic HiHat calibration,expanded effects section ,compressor and eq..midi program change
http://alesis.com/products/view/strike-pro-kit

Changelog:
Power Station New England Kit Expansion: Added two new preset kits.
Improved Playability: Extensive improvement of trigger response and realism.
Automatic Hi-Hat Calibration: Firmware now automatically adjusts to the hi-hat pedal and hardware performance. If you adjusted the position of your top hi-hat cymbal or your hi-hat pedal hardware, enter Trigger Mode (press Edit > Triggers), set Trig to HiHat Bow or HiHat Edge, and then press F1/F2/Pedal. In the screen that appears, press F1/F2/HiHat Reset to initialize the calibration.

We also added three new parameters to Trigger Mode, though you should not have to adjust them for most hi-hat hardware:

Chick: Raises or lowers the point at which your pedal will trigger the "chick/stomp" sound.
If you play with the top cymbal really high above the bottom one, or if you hi-hat pedal has high-tension springs, increasing this setting may help you get a more consistent chick/stomp sound.
Tightness: You should not have to adjust this much, but if you tend to play with very little distance between the hi-hat cymbals when opening and closing them, lowering this setting may help capture the finer details of your playing. If this setting is too low, you may trigger unintentional "chick/stomp" sounds while striking the top cymbal.
Sensitivity: Lowering this setting can help increase the dynamic range of the "chick/stomp" sound (though setting it too low can cause inconsistent chick volumes).
Splash: This setting determines how easy or hard it is to create a hi-hat "splash" sound. Higher values make it more difficult to "splash", though you may prefer that depending on your "footwork".
Curve: If you prefer to hear more closed or semi-open sounds, choose one of the logarithmic curves (Log 1-4). If you prefer a more open sound, choose an exponential curve (Exp. 1-4). Select Linear for an even balance between these.
Compressor,  EQ, and FX2 processor: Kit FX Mode now includes a built-in compressor and equalizer, great for adding those final touches to your sound. We also added an FX2 processor (the previous FX tab is now FX1).
Updated Effect Routing: Onboard effects are now pre-fader so adjusting your Strike module's sliders will adjust any associated effects too, such as reverb or delay tails.
Program Change Receive: Send MIDI program change messages to your Strike module's MIDI input or USB port.
The numbers of program change messages correspond to the kits listed in the current folder. Alternatively, send MIDI CC #118 to increment by one kit or MIDI CC #119 to decrement by one kit.
Minor bug fixes.

https://m.youtube.com/watch?feature=youtu.be&v=zRzAguSO7zc
« Last Edit: November 24, 2017, 10:02:47 PM by Chaser »

Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #1 on: November 20, 2017, 07:39:46 PM »
I'm excited about this update. It sounds good from the Alesis video I saw.  ;D

I am having a small issue with the update however. It's a two part update and the first part updates just fine. The second update (and yes, I'm doing it exactly as Alesis states) is failing at 36%.  :(

I was doing the update on a Mac. I will try my PC later tonight. PC is up stairs and not next to my kit like my Mac. Will report back soon.
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline Chaser

Re: STRIKE Module Firmware /Editor Updates
« Reply #2 on: November 20, 2017, 09:28:11 PM »
I'm excited about this update. It sounds good from the Alesis video I saw.  ;D

I am having a small issue with the update however. It's a two part update and the first part updates just fine. The second update (and yes, I'm doing it exactly as Alesis states) is failing at 36%.  :(

I was doing the update on a Mac. I will try my PC later tonight. PC is up stairs and not next to my kit like my Mac. Will report back soon.

The 2nd part of the update (trigger)stalled on me also..(Touch Screen Rig)..I thought I may have incidentally touched something.
I restarted...showed new firmware V1.30..so I just restarted again in update mode and just did the trigger update.The module went through the erasure/update no problem.
Both the Trigger OS and DSP OS display V1.30.
So I am wondering if it's absolutely necessary to do both at once
The 2 new kits aren't numbered like the rest..turn the dial to the left to access them.
Power Station Natural is now the default startup kit

EDIT:
Apparently Alesis is aware of this as now there is a FAQ page and solution is simply "restart" updater
So it's not necessary to do both in one update instance
Also solutions for error messages/update failure/midi device issues for Mac users.
http://www.alesis.com/kb/article/2377
« Last Edit: November 20, 2017, 11:50:05 PM by Chaser »

Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #3 on: November 21, 2017, 08:11:37 AM »
EDIT:
Apparently Alesis is aware of this as now there is a FAQ page and solution is simply "restart" updater
So it's not necessary to do both in one update instance
Also solutions for error messages/update failure/midi device issues for Mac users.
http://www.alesis.com/kb/article/2377

I was already trying that and it still doesn't work. As a matter of fact the original Alesis video that described how to install the update stated to do just that (restart the updater). So when I stated that I followed Alesis instructions that is what I was referring to. The second part just will not load. No matter if I restart the updater, or if I restart my module and then restart the updater, it just doesn't work. Nothing else is running on my computer, I'm plugged strait into the USB (no hubs). I've trying everything on my Mac to get it to work and it does not.

I will try their newer fix which through the Audio Midi set-up.
« Last Edit: November 21, 2017, 08:14:34 AM by Hellfire »
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #4 on: November 21, 2017, 08:22:47 AM »
EDIT:

Also solutions for error messages/update failure/midi device issues for Mac users.
http://www.alesis.com/kb/article/2377

^^^This worked^^^

meaning reseting the Audio midi device in the utilities. It's a little more cumbersome than most Mac procedures, but it gets the job done.

Thanks Chaser!
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #5 on: November 21, 2017, 11:40:15 AM »
New Problem,

The new Editor doesn't seem to play nice with my Mac. It sees the Strike as two external drives and can't read it correctly. So, right now I'm unable to install the new sounds/kits. More testing.  ::)
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline Chaser

Re: STRIKE Module Firmware /Editor Updates
« Reply #6 on: November 21, 2017, 02:13:56 PM »
New Problem,

The new Editor doesn't seem to play nice with my Mac. It sees the Strike as two external drives and can't read it correctly. So, right now I'm unable to install the new sounds/kits. More testing.  ::)

Sorry to hear so much trouble with Mac OS

Under Windows I have always shown as 2 "removable disks"..1 locked (module)
I haven't had any scanning trouble even when I upgraded card to U3 64GB.and formatted in the module..the module recognized and labeled it HD-60

Maybe try removing the external card..open the editor and update content?
« Last Edit: December 14, 2017, 01:38:51 PM by Chaser »

Offline Blargomite

Re: STRIKE Module Firmware /Editor Updates
« Reply #7 on: November 24, 2017, 09:49:09 PM »
Anyone else have a problem where none of the kit FX work on the two new Power station kits? Maybe this was intentional, but reverb, compression, and EQ all do nothing to the new kits.

Offline Chaser

Re: STRIKE Module Firmware /Editor Updates
« Reply #8 on: November 24, 2017, 10:24:30 PM »
Anyone else have a problem where none of the kit FX work on the two new Power station kits? Maybe this was intentional, but reverb, compression, and EQ all do nothing to the new kits.

You also have to go into [Voice] > [FX/MIDI] ...you can turn eq/compression on/off.. and adjust the sends per Trigger... Reverb, FX1 and FX2.
By default they are 0 ( Zero)

EDIT:
There is some confusion though as far as information on the update..the V1.3 update announcement posted by an employee in the Alesis Community
Updated Effect Routing: Onboard effects are not pre-fader so adjusting your Strike module's sliders will adjust any associated effects too, such as reverb or delay tails.
http://community.alesis.com/alesis/topics/strike-pro-kit-firmware-version-1-3-out-now

the V1.3 update pdf and the FAQ link . ..
Updated Effect Routing: Onboard effects are now pre-fader so adjusting your Strike module’s sliders will adjust any associated effects too, such as reverb or delay tails.
http://www.alesis.com/kb/article/2377

The post in the Alesis Community forum is locked ..so I couldn't comment/reply

« Last Edit: November 25, 2017, 01:55:00 AM by Chaser »

Offline Chaser

Re: STRIKE Module Firmware /Editor Updates
« Reply #9 on: January 09, 2018, 03:52:42 PM »
STRIKE Editor 1.1.2
Minor Bug Fixes
http://www.alesis.com/products/view/strike-pro-kit

Offline Chaser

Re: STRIKE Module Firmware /Editor Updates
« Reply #10 on: July 11, 2018, 09:51:37 AM »
NEW! Strike Performance Drum Module - Firmware and Content Update v1.4
http://alesis.com/products/view2/strike-pro-kit



NOTE:
In Februrary John Emrich accepted a position with Alesis as Sound Designer and Product Development Specialist.
If you are not familiar with John for the past 20 years he has been involved with Sound Design and Product Development for eDrums and VSTi work for the following companies: Alesis, FXPansion, KAT, Simmons, Yamaha, Zildjian, Sabian, Native Instruments, Platinum Samples, WaveMachine Labs and most recently NFUZD Audio.(created the sample library that is included in the NSPIRE I/O and R&D lead for the completion of the module.)

Here he is demonstrating the New v1.4 update.Note the nearly instantaneous loading of the kits.
Introducing Alesis Strike Series Firmware v1.4
« Last Edit: July 11, 2018, 01:53:46 PM by Chaser »

Offline korakios

Re: STRIKE Module Firmware /Editor Updates
« Reply #11 on: July 11, 2018, 02:05:45 PM »
They seem to implement disk streaming ;)
Now more ram available so new features may come :)


Edit: Reading next posts there are still long loading times between different kits ,(although lot faster) so they might still load stuff in memory .
« Last Edit: July 12, 2018, 10:10:10 AM by korakios »

Offline ironman187

Re: STRIKE Module Firmware /Editor Updates
« Reply #12 on: July 11, 2018, 09:14:13 PM »
I'm loving the new graphics, but I feel Alesis took a step back with them. Now instead of showing you which zone is being triggered on each pad, it only shows what pad is being triggered. I am at work so haven't been able to go into the trigger settings, but I hope they now have an intensity graph for each trigger page to compensate. If not, it seems like a major blunder on their part.

Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #13 on: July 11, 2018, 09:40:40 PM »
I'm loving the new graphics, but I feel Alesis took a step back with them. Now instead of showing you which zone is being triggered on each pad, it only shows what pad is being triggered. I am at work so haven't been able to go into the trigger settings, but I hope they now have an intensity graph for each trigger page to compensate. If not, it seems like a major blunder on their part.

I too have my module updated. I do like the new graphics but like ironman187, I liked seeing the zone I was hitting. Haven't dug too deep into anything yet, but I can say:

 ;D ;D ;D ;D ;D"LOAD TIME IS NO LONGER AND ISSUE". ;D ;D ;D ;D ;D

The longest kit load I've found is about 2 seconds tops. Vast majority of the kit's being less than a second.

The new kits sound really good. I'm not quite sure why they made the new kits different just because of Xstick. They could have just used velocity switching on the rim of the snare to get the two different sounds (cross stick and snare shot). Well, I'm sure I can do this myself.

I would like to see an update to include starting up on the last kit I was playing. We long time Alesis players have been asking for this since 2009 (starting with the DM10). I would have thought by now this would have been standard in the flagship module.

All in all, this is what the Strike should have been when originally shipped. Congrats Alesis! Strike is now a viable option over Roland (at least module wise).

Sorry ironman187, I still don't see an intensity graph for the triggers. I agree this needs to be added. It would be a great tool when tweaking the triggers.

BTW Chaser, I made this topic a sticky. ;)
« Last Edit: July 11, 2018, 09:42:20 PM by Hellfire »
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline ironman187

Re: STRIKE Module Firmware /Editor Updates
« Reply #14 on: July 11, 2018, 09:53:49 PM »
Sorry ironman187, I still don't see an intensity graph for the triggers. I agree this needs to be added. It would be a great tool when tweaking the triggers.

Oh wow.  :'(

I'd like to see that added to the next update ( assuming there is one.) I'd also like to have the ability to load trigger setting profiles from the SD card. This would mean that my 10 year old daughter could pop in an SD card and play right away, then I could do the same. This would also be a great feature for churches with a Strike kit. The last thing would be the ability to move the drums on the display around, and even change their type, although that my be difficult to implement, and other than visuals, serves no functional purpose.

I've also been reading that the kit sizes are smaller, but nobody knows why.
« Last Edit: July 11, 2018, 10:04:25 PM by ironman187 »

Offline Chaser

Re: STRIKE Module Firmware /Editor Updates
« Reply #15 on: July 12, 2018, 12:47:53 AM »
I've also been reading that the kit sizes are smaller, but nobody knows why.
I thought at first they may be multiple velocity/layered waves,but now I think there is some compression going on.
There are reports of user kits with user samples being reduced in size also.Including custom kits I have constructed.

I'm loving the new graphics, but I feel Alesis took a step back with them. Now instead of showing you which zone is being triggered on each pad, it only shows what pad is being triggered. I am at work so haven't been able to go into the trigger settings, but I hope they now have an intensity graph for each trigger page to compensate. If not, it seems like a major blunder on their part.

I too have my module updated. I do like the new graphics but like ironman187, I liked seeing the zone I was hitting. Haven't dug too deep into anything yet, but I can say:

Sorry ironman187, I still don't see an intensity graph for the triggers. I agree this needs to be added. It would be a great tool when tweaking the triggers.

I also prefer the ability to see the zones when struck so I can tell if a trigger I am building/testing is working.
This may have been the trade off.I don't know how much ram was being used (if any)to monitor separate zones.
The only way to check a zone or a trigger in v1.40 is to turn on/off the voice for trouble shooting.

I am currently running the V1.30 with the 1.40 content.I am using the modules for R&D and I don't need the quick load,or the unlimited recording to SD
I mainly use the module to build a database and I need to see the zones as I test various triggers.

OS v1.30 with v1.40 Content

..all kits work..kit load times vary from instantly (after a certain kit is loaded so they are variances of the same kit.) to 25 secs and everything in between
However,as I mentioned above there is some sort of compression going on.. in v1.30 they are uncompressed and much larger...compare to v1.40

#001 Birch Rock(186mb)...20 secs
#002 Birch Rock Xst (182mb) thru #004Birch Slap(186mb)..instantly
#005 Pop Maple (180mb)...20 secs
#006 Pop Maple Xst(177mb) thru #008 Natural Maple Xst(177mb)..instantly
and so on.

I have compiled a list of times and which kits load instantly,if anyone is interested in a particular kit(s) and prefers seeing the zones.(before downgrading the OS.)

Overall I like the sounds.Mr Emrich did a great job for the short time he's been with Alesis.I think a lot of people will be happy.

BTW Chaser, I made this topic a sticky. ;)

I would like to see an update to include starting up on the last kit I was playing. We long time Alesis players have been asking for this since 2009 (starting with the DM10). I would have thought by now this would have been standard in the flagship module.

All in all, this is what the Strike should have been when originally shipped. Congrats Alesis! Strike is now a viable option over Roland (at least module wise).
Sorry ironman187, I still don't see an intensity graph for the triggers. I agree this needs to be added. It would be a great tool when tweaking the triggers.


Mr Emrich is "Hiding in Plain Site"...maybe he'll chime in..


« Last Edit: July 12, 2018, 01:46:31 AM by Chaser »

Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #16 on: July 12, 2018, 08:25:55 AM »
Mr Emrich is "Hiding in Plain Site"...maybe he'll chime in..

Yes he is. It's good to see John Emrich is working with Alesis.
As a matter of fact he has been (to use your phrase) "Hiding in Plain Site" here on alesisDrummer.com since 2009.
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline rhysT

Re: STRIKE Module Firmware /Editor Updates
« Reply #17 on: July 13, 2018, 08:26:53 AM »

I too have my module updated. I do like the new graphics but like ironman187, I liked seeing the zone I was hitting. Haven't dug too deep into anything yet, but I can say:

 ;D ;D ;D"LOAD TIME IS NO LONGER AN ISSUE". ;D ;D ;D

The longest kit load I've found is about 2 seconds tops. Vast majority of the kit's being less than a second.

The new kits sound really good. I'm not quite sure why they made the new kits different just because of Xstick. They could have just used velocity switching on the rim of the snare to get the two different sounds (cross stick and snare shot). Well, I'm sure I can do this myself.

I would like to see an update to include starting up on the last kit I was playing. We long time Alesis players have been asking for this since 2009 (starting with the DM10). I would have thought by now this would have been standard in the flagship module.

All in all, this is what the Strike should have been when originally shipped. Congrats Alesis! Strike is now a viable option over Roland (at least module wise).

Yeah the Strike module is gaining more of the DM10's useful features and I'll prob'ly get one if there's minimal kit loading delays with User kits including custom multi-velocity layered sounds. At least John Emrich has experience with adapting BFD Eco instrument samples for the NSPIRE module: https://www.fxpansion.com/products/bfdeco-nfuzd/

Mr Emrich is "Hiding in Plain Site"...maybe he'll chime in..

Yes he is. It's good to see John Emrich is working with Alesis.
As a matter of fact he has been (to use your phrase) "Hiding in Plain Site" here on alesisDrummer.com since 2009.

FYI, here's a profile of John Emrich with some background info and his interest in the Zendrum (p-28):
https://issuu.com/digitaldrummer/docs/digitaldrummer_august_2013_lr_v2
http://www.zendrum.com/index.php?route=product/category&path=61
« Last Edit: July 15, 2018, 07:48:01 AM by rhysT »

Offline Purpledc

Re: STRIKE Module Firmware /Editor Updates
« Reply #18 on: July 15, 2018, 08:09:28 AM »
I LOVE the update.  But its not perfect.  Issues I have found that I cant correct.

1. New hi hat settings hate any hi hat other than the strike hi hat. I have a VH10 and it takes very specific settings to work properly and even then its better than stock but not as good as it could be if they had an option for a non factory hi hat.  I can get semi open sounds and arguably more than i did with previous revisions. But I cant change my pedal curves or else the module wont recognize that the hat is fully open.  If anyone has any tips on that Im all ears.

2. Load times are better. But they load in the background in a different way..  You can tell this by selecting any kit and play fast on the snare.  You will note that it takes quite a few seconds for the round robins to kick in and give you the velocities and dynamics we love about the module.   I think what they did was hide the loading bar so that it wasnt on your mind and they are letting your perception of sound dictate what is acceptable. But it also seems that it loads a single velocity in each velocity layer firs so that if you start just playing a groove you cant even notice the other velocities are missing.  But if start with a fast snare roll its very apparent. Before it would load one instrument at a time and sometimes you would have a dead pad till it kicks in.  Its clever but not instant like some describe.


3. The kit sizes shrank tremendously.   EDITED:  So my previous statement was that you could add layers but at the sacrifice of velocities within the velocity layers of the instruments.  I think I was 100% wrong.    You see with previous firmware revisions I would be able to see that bar telling me the kit was loading. So any loss in velocity depth i attributed to it needing more time to load. 

But now, the load times are hidden.  They are reduced for sure but they are in the background as i mention in point 2.   And what is really throwing me off is the kit needing to reload after you choose a new instrument as a layer.  This would happen to me on the previous versions when layering and especially in strike editor.  I would make a change or two and it would refresh.   


It seems to still do this but in the background.  So everytime I would select a layer and try playing the kit it sounded machine gunny because it was reloading in the background and i didnt know it and attributed to a loss of velocity.  So I saved the kit frustrated a couple days ago and come back from a mini vacay and it seems to be fine.  Because Im not editing its not refreshing.   I just would like an official word from alesis to confirm just what we can and cant do.

This





« Last Edit: July 15, 2018, 09:14:28 AM by Purpledc »

Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #19 on: July 15, 2018, 12:15:27 PM »
I LOVE the update.  But its not perfect.  Issues I have found that I cant correct.

1. New hi hat settings hate any hi hat other than the strike hi hat. I have a VH10 and it takes very specific settings to work properly and even then its better than stock but not as good as it could be if they had an option for a non factory hi hat.  I can get semi open sounds and arguably more than i did with previous revisions. But I cant change my pedal curves or else the module wont recognize that the hat is fully open.  If anyone has any tips on that Im all ears.

I still don't have very good hi-hat control. I find the Strike hats themselves not very sensitive. I get much better tracking from my Roland VH-12 pad. I'm playing with the setting now, so I'll see if I can squeeze anymore proformace out of the stock hats.

2. Load times are better. But they load in the background in a different way..  You can tell this by selecting any kit and play fast on the snare.  You will note that it takes quite a few seconds for the round robins to kick in and give you the velocities and dynamics we love about the module.   I think what they did was hide the loading bar so that it wasnt on your mind and they are letting your perception of sound dictate what is acceptable. But it also seems that it loads a single velocity in each velocity layer firs so that if you start just playing a groove you cant even notice the other velocities are missing.  But if start with a fast snare roll its very apparent. Before it would load one instrument at a time and sometimes you would have a dead pad till it kicks in.  Its clever but not instant like some describe.

Damn, you're right! I didn't notice this before because I was just playing a simple rock beat every time I changed a kit. Good ear! The rolls tend to sound much better after about 4-5 seconds.
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline Purpledc

Re: STRIKE Module Firmware /Editor Updates
« Reply #20 on: July 15, 2018, 06:21:51 PM »
I LOVE the update.  But its not perfect.  Issues I have found that I cant correct.

1. New hi hat settings hate any hi hat other than the strike hi hat. I have a VH10 and it takes very specific settings to work properly and even then its better than stock but not as good as it could be if they had an option for a non factory hi hat.  I can get semi open sounds and arguably more than i did with previous revisions. But I cant change my pedal curves or else the module wont recognize that the hat is fully open.  If anyone has any tips on that Im all ears.

I still don't have very good hi-hat control. I find the Strike hats themselves not very sensitive. I get much better tracking from my Roland VH-12 pad. I'm playing with the setting now, so I'll see if I can squeeze anymore proformace out of the stock hats.

2. Load times are better. But they load in the background in a different way..  You can tell this by selecting any kit and play fast on the snare.  You will note that it takes quite a few seconds for the round robins to kick in and give you the velocities and dynamics we love about the module.   I think what they did was hide the loading bar so that it wasnt on your mind and they are letting your perception of sound dictate what is acceptable. But it also seems that it loads a single velocity in each velocity layer firs so that if you start just playing a groove you cant even notice the other velocities are missing.  But if start with a fast snare roll its very apparent. Before it would load one instrument at a time and sometimes you would have a dead pad till it kicks in.  Its clever but not instant like some describe.

Damn, you're right! I didn't notice this before because I was just playing a simple rock beat every time I changed a kit. Good ear! The rolls tend to sound much better after about 4-5 seconds.
Yeah, I dont know whats up with the hi hats.  I get better performance my VH10 top cymbal but with a Goedrum controller.   I took both apart to see if I could spot any difference between the two and the go edrum is significantly different.  My roland controller has a nylon wheel that rolls on a silicone pressure plate.  And any other curve but linear on the hi hat and its no good. But it makes it much harder to grab in between sounds.  The go Edrum has a fader switch.  A long fader like we use on the module.   

So, not knowing much about the controllers It has me thinking and hopefully someone can say Im either on to something or an idiot.  But I remember things in guitars like audio taper pots and linear taper pots.   And since a fader is a pot and the roland seems to use a modified version of that is there any chance that the Roland controller will ONLY work properly if you set the pedal to Linear to match the type of physical unit that is in the controller linear?  Like If I could modify it to have a logametric taper would it change anything? 


 



Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #21 on: July 15, 2018, 08:03:20 PM »
Yeah, I dont know whats up with the hi hats.  I get better performance my VH10 top cymbal but with a Goedrum controller.

I use a very similar set-up too and I too get better performance from my Vh12 top hat with Goedrum controller.

I took both apart to see if I could spot any difference between the two and the go edrum is significantly different.  My roland controller has a nylon wheel that rolls on a silicone pressure plate.  And any other curve but linear on the hi hat and its no good. But it makes it much harder to grab in between sounds.  The go Edrum has a fader switch.  A long fader like we use on the module.   

I don't know how long you have been into electronic drums, but the way the Godrum controller is made is a tried and true method for hi-hat control going back at least 15 years. As a matter of fact many of us into DIY edrums have been making our own controllers in a very similar manner for the last decade or so.

The reason Roland (and Alesis) use a "soft pot" or FSR is because technically those device should last longer than the slide pot used in the Goedrum controller.

So, not knowing much about the controllers It has me thinking and hopefully someone can say Im either on to something or an idiot.  But I remember things in guitars like audio taper pots and linear taper pots.   And since a fader is a pot and the roland seems to use a modified version of that is there any chance that the Roland controller will ONLY work properly if you set the pedal to Linear to match the type of physical unit that is in the controller linear?  Like If I could modify it to have a logametric taper would it change anything? 

Your correct about there being different tapers to pots, and yes the taper can make a difference in edrums. The other part of a pot that makes a difference is the ohm rating. I know when I tried to use my Roland VH-12 controller I could not get a splash or get it to open all the way (of course this was with the original OS in the Strike and I haven't tried it since). I believe that's because the pot in the VH-12 is a different ohm rating than the one in the Strike (however I have not confirmed this yet). I really need to check it with my meter.
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline Purpledc

Re: STRIKE Module Firmware /Editor Updates
« Reply #22 on: July 15, 2018, 09:33:20 PM »
Yeah, I dont know whats up with the hi hats.  I get better performance my VH10 top cymbal but with a Goedrum controller.

I use a very similar set-up too and I too get better performance from my Vh12 top hat with Goedrum controller.

I took both apart to see if I could spot any difference between the two and the go edrum is significantly different.  My roland controller has a nylon wheel that rolls on a silicone pressure plate.  And any other curve but linear on the hi hat and its no good. But it makes it much harder to grab in between sounds.  The go Edrum has a fader switch.  A long fader like we use on the module.   

I don't know how long you have been into electronic drums, but the way the Godrum controller is made is a tried and true method for hi-hat control going back at least 15 years. As a matter of fact many of us into DIY edrums have been making our own controllers in a very similar manner for the last decade or so.

The reason Roland (and Alesis) use a "soft pot" or FSR is because technically those device should last longer than the slide pot used in the Goedrum controller.

So, not knowing much about the controllers It has me thinking and hopefully someone can say Im either on to something or an idiot.  But I remember things in guitars like audio taper pots and linear taper pots.   And since a fader is a pot and the roland seems to use a modified version of that is there any chance that the Roland controller will ONLY work properly if you set the pedal to Linear to match the type of physical unit that is in the controller linear?  Like If I could modify it to have a logametric taper would it change anything? 

Your correct about there being different tapers to pots, and yes the taper can make a difference in edrums. The other part of a pot that makes a difference is the ohm rating. I know when I tried to use my Roland VH-12 controller I could not get a splash or get it to open all the way (of course this was with the original OS in the Strike and I haven't tried it since). I believe that's because the pot in the VH-12 is a different ohm rating than the one in the Strike (however I have not confirmed this yet). I really need to check it with my meter.


I have only been playing edrums since nov.  I have only dabbled in drums previously.  I was a 25 year guitarist who was always a closet drummer at heart.  I practiced on pillows and random crap but never bought a kit. So I understood the mechanics before I actually touched a drum set.  But as a guitarist I did a lot of modding  in that hobby.  And I am finding much of the equipment is actually the same just repurposed.  Its kinda like learning a new language that is really similar to old one you all ready know. You just need the things to connect the dots. 


Its actually a curse, because my understanding of the topic is greater than my knowledge of the technical terms associated with it.  People discredit me as not knowing much when they hear I haven't been playing long especially when I don't know a key term.  I only know its definition.  Ive always been that way.  I can show you how to get somewhere, but Im horrible at telling you.  Leads me to be very verbose.


Its interesting that you say the ohms might be different.  Its promising yet also troubling.  Because I saw a circuit board, a tape type wiring harness and that plate. I didnt see any easily swappable part.  But If its possible I would love to figure that out.  Because those variety of semi open tones are there I just need to figure a way to access them.  I too was not happy with the performance of the top cymbal.  I was expending too much energy for the type of music I was trying to play on the edge.  But I didnt really get great semi open sounds with that either.  Well thanks a bunch.  At least now I know which direction i need to head in. 

Offline Hellfire

Re: STRIKE Module Firmware /Editor Updates
« Reply #23 on: July 16, 2018, 11:12:27 AM »
I have only been playing edrums since nov.  I have only dabbled in drums previously.  I was a 25 year guitarist who was always a closet drummer at heart.  I practiced on pillows and random crap but never bought a kit. So I understood the mechanics before I actually touched a drum set.  But as a guitarist I did a lot of modding  in that hobby.  And I am finding much of the equipment is actually the same just repurposed.  Its kinda like learning a new language that is really similar to old one you all ready know. You just need the things to connect the dots. 


Its actually a curse, because my understanding of the topic is greater than my knowledge of the technical terms associated with it.  People discredit me as not knowing much when they hear I haven't been playing long especially when I don't know a key term.  I only know its definition.  Ive always been that way.  I can show you how to get somewhere, but Im horrible at telling you.  Leads me to be very verbose.

I hope you didn't get the impression I was trying to discredit you. That wasn't my intent. You seem very knowledgable about edrums and I was a little surprised by your surprise of the difference in the GoEdrum controller (meaning you seem like you know a lot about this stuff already). Edrums need more people like you who are willing to dig in and point out what's going on with this stuff. Please don't stop.

Its interesting that you say the ohms might be different.  Its promising yet also troubling.  Because I saw a circuit board, a tape type wiring harness and that plate. I didnt see any easily swappable part.  But If its possible I would love to figure that out.  Because those variety of semi open tones are there I just need to figure a way to access them.  I too was not happy with the performance of the top cymbal.  I was expending too much energy for the type of music I was trying to play on the edge.  But I didnt really get great semi open sounds with that either.  Well thanks a bunch.  At least now I know which direction i need to head in.

I'm just glad we have the option of the GoEdrum controller out there. It still may not be perfect, but some of issues with hi-hat control might be the programing within the Strike module itself. Alesis hasn't had much experience with variable hi-hat operation.

You may have better success modifying the GoEdrum controller. Those slide pot are quite common and I sure there are other ohm value slides that would fit inside the GoEdrum itself.  Or you could just make your own. Attaching a slide pot to the hi-hat pedal of a standard stand isn't that difficult if you are handy. Just match the wiring of the GoEdrum controller.
For more edrum info, be sure to visit my web site at:
          www.HellfireDrums.com                    
My current set-up:  Alesis DM10 and Trigger I/O with modified & DIY pads

Offline Beany

Re: STRIKE Module Firmware /Editor Updates
« Reply #24 on: July 16, 2018, 01:14:49 PM »
Alesis PLEASE bring back the ability to see which zone triggers!!! This is a real backwards step. Ive had several trigger issues and seeing if rim or pad was triggered helped tremendously. Also the graphic is too small. The old graphic showed the zones numbered and big and bright. This was perfect when adjusting levels especially live. now there is no indication as to which fader to tweek quickly. A real blunder in my opinion. I may need to go back to 1.3 but with the new kits. That would be a shame because there is a bug in the recording software in 1.3 and it does cause me a problem. 1.4 solves that.  This Kit is so good....why oh why invite more bad press by implementing an ill-thoughout interface update.  Noone wants less visibility of vital information especially on stage! Please!!!!! give the option for old kit image.