Up to 20% off all individual MIDI packs for drums, EZkeys and EZbass!*

Up to 20% off all individual MIDI packs for drums, EZkeys and EZbass!*

Up to 20% off all individual MIDI packs for drums, EZkeys and EZbass!*

Replies created

 

Viewing 1 replies (of 1 total)
  • Hackcraze
    Participant

    Hi,

    I just downloaded the demo version of EZdrummer to see if it works in conjunction with my new Millenium MPS-850 edrum set. Overall, I am pretty impressed how well your software complements the drum set, but I have one big problem with the hi-hat control.

    In my case EZDrummer does not recognize the opening of the hi-hat. If I close it by foot EZDrummer makes the corresponding sound but from then on the hi-hat stays closed forever. Of course, I extensively tried out different settings, especially “MIDI Mapping” and “Pedal Correction”, unfortunately without success (none of the MIDI mappings or pedal control curves helped). I had a look at the MIDI data the drum module sends to the computer with MIDI-OX (see below). I found that a Note On and Note Off is only sent when the hi-hat is closed, not when it is opened. However, the CC4-data (“foot controller”) is sent correctly. When using the internal sound engine of the MPS 850 module the hi-hat works as it should (opening and closing), thus the hi-hit controller obviously works as intended.

    I could imagine that the MPS 850 drum module just has a strange or unusual way to put out the hi-hat controller data. As far as I can see there is no way to cahnge this on the side of my drum module. Is there any way of making EZDrummer interpret the MIDI data from my drum set correctly? It could of course also be that I am just make a stupid mistake …

    It would be sad if EZDrummer is not useable with the MPS850 kit because apart from this hi-hat issue it works very well and I like it very much.

    Thanks a lot for any help!


    // HI HAT CLOSE
    TIME IN PORT STATUS DAT1 DAT2 CH NOTE EVENT
    ------------------------------------------------------------------
    436485 3 -- 185 4 26 10 --- CC: Foot Controller
    436624 3 -- 185 4 44 10 --- CC: Foot Controller
    436655 3 -- 185 4 63 10 --- CC: Foot Controller
    436711 3 -- 185 4 77 10 --- CC: Foot Controller
    436713 3 -- 153 44 28 10 G# 2 Note On
    436715 3 -- 153 44 0 10 G# 2 Note Off
    436717 3 -- 169 42 127 10 F# 2 Key Aftertouch
    436719 3 -- 169 42 0 10 F# 2 Key Aftertouch
    436721 3 -- 169 22 127 10 Bb 0 Key Aftertouch
    436723 3 -- 169 22 0 10 Bb 0 Key Aftertouch
    436725 3 -- 169 127 127 10 G 9 Key Aftertouch
    436727 3 -- 169 127 0 10 G 9 Key Aftertouch
    436771 3 -- 185 4 93 10 --- CC: Foot Controller
    436880 3 -- 185 4 114 10 --- CC: Foot Controller
    436909 3 -- 185 4 127 10 --- CC: Foot Controller


    // HIT HAT OPEN
    TIME IN PORT STATUS DAT1 DAT2 CH NOTE EVENT
    ------------------------------------------------------------------
    438689 3 -- 185 4 114 10 --- CC: Foot Controller
    438701 3 -- 185 4 102 10 --- CC: Foot Controller
    438721 3 -- 185 4 84 10 --- CC: Foot Controller
    438755 3 -- 185 4 71 10 --- CC: Foot Controller
    438843 3 -- 185 4 53 10 --- CC: Foot Controller
    438883 3 -- 185 4 35 10 --- CC: Foot Controller
    438915 3 -- 185 4 21 10 --- CC: Foot Controller
    438947 3 -- 185 4 0 10 --- CC: Foot Controller

    It sounds like a midi mapping issue. You either change the output from the drum module using its midi mapping and select the cc that you need, or you can map in your host AU drum kit.

    HackCraze

Viewing 1 replies (of 1 total)

No products in the cart.

×