No products in the cart.
Hi,
I found a number of wrong triggers in the EZDrummer 2 MIDI mapping when using the Alesis Strike Pro kit:
I tried all the preset MIDI mappings, but the problems persist. Does anyone know how to solve this?
I’m running a Win 10 machine, using the standalone plugin, and also within FL Studio, for recording.
Thanks
Is the Alesis Strike Pro kit set to the default mapping? Same results using the standalone and add a plugin in a DAW?
What version of EZD2 shows on the interface?
Scott Sibley - Toontrack
Technical Advisor
I am having a very similar issue. My Alesis Strike Kit is triggering some incorrect drums.
By default, the first tom will trigger my crash, and my crash will trigger my first tom, or actually trigger the crash, depending on velocity.
When using the Alesis setting under the E-Drum settings inside of EZD2, the tom is now correct, but the crash cymbal is still doing the same thing. Using all other settings in the E-Drum menu also have the exact same issue with the crash, and other drums map incorrectly when using the other settings, but that is to be expected.
I have not changed any midi mapping inside my Strike module, everything is as it normally would be. I just want to be able to trigger midi correctly, as I solely use the Alesis Strike through EZD2 to practice along to my band’s music at home.
EZD2 Plugin, version 2.1.8 on Logic Pro X version 10.4.7, MacOS High Sierra 10.13.6.
You should try using the USER KIT in USER section with the alesis or generic midi mapping if that is not working try theses mappings:
(you only need to change the ones in bold font)
KICK 036,C1
SNARE 038,D1
SNARE R 040,E1
TOM1 048,C2
TOM1 R 082,A#4
TOM2 047,B1
TOM2 R 080,G#4
TOM3 043,G1
TOM3 R 075,D#4
TOM4 041,F1
TOM4 R 073,C#4
HH BOW 019,G-1
HH EDGE 018,F#-1
HH FOOT 021,A-1
CRASH1 BOW 052,E-2
CRASH1 EDGE 052,E-2
CRASH2 BOW 049,C#2
CRASH2 EDGE 049,C#2
CRASH3 BOW 055,G2
CRASH3 EDGE 055,G2
RIDE1 BELL 053,F2
RIDE1 BOW 051,D#2
RIDE1 EDGE 059,B2
I am having a very similar issue. My Alesis Strike Kit is triggering some incorrect drums.
By default, the first tom will trigger my crash, and my crash will trigger my first tom, or actually trigger the crash, depending on velocity.
When using the Alesis setting under the E-Drum settings inside of EZD2, the tom is now correct, but the crash cymbal is still doing the same thing. Using all other settings in the E-Drum menu also have the exact same issue with the crash, and other drums map incorrectly when using the other settings, but that is to be expected.
I have not changed any midi mapping inside my Strike module, everything is as it normally would be. I just want to be able to trigger midi correctly, as I solely use the Alesis Strike through EZD2 to practice along to my band’s music at home.
EZD2 Plugin, version 2.1.8 on Logic Pro X version 10.4.7, MacOS High Sierra 10.13.6.
EZdrummer version: 2.1.8
Operating system: macOS High Sierra (10.13)
I have the same issue with my strike kit pro. Did you ever find a solution to this?
You guys have the ability to change your midi mapping inside the pro strike’s module? I am using a Simmons SD 1200 kit and I am experiencing similar midi mapping issues with EZD. I don’t think my module allows me to change midi mapping, or at least I can’t find anywhere to do that. The people that answer the phone at Simmons are clueless on this topic and have been no help. I just started another thread which shows an alternate solution using a mac app called MidiFire.
hi has anyone found any solution to the mapping of the ez drummer to the strike module? the closest i get is having it to work but when i closed my hi hat. even tho my midi mapping is correct to the midi notes listed on ez drummer, it still triggers one of the crash together with. and i realized on the snare you can only choose rimshot or sidestick as triggers on your snare. desperately need help, very new to this and i am a guitarist so i am doing my best to understand all of these.
P.S: i have updated to the newest firmware 1.5 plus i used the new user kit.skt that was supposed to be specifically designed for ez and superior. even then its the same thing happening. HELP!
No products in the cart.