No simultaneously output of two channelshi

[stefan91]

Hi there

I have a problem with the configurstion of a 32 channel Megadrum:

When I hit every meshhead/pad/trigger alone everything is fine.
When I hit two elements of the drumkit at the same time, one sound always comes after the other - there is no simultaneously output for more than one channel possible. It sounds like a little kid is playing the drum, because everything gets out of timing..

Does anyone know how to solve this problem?

I tried USB and MIDI Out, I tried Addictive Drums Stand Alone vs PlugIn running in Cubase and I tried other Pads.. Nothing helps. Crosstalk was set to Zero.
The problem isn't present with another Millenium Module I tried, so I think a setting inside MegaDrum should hopefully do the job..
I also recorded a short MIDI signal, for example I played Snare and Tom at the same time - every tom was shortened at the beggining and fired of just after the snare hit.

... Looking forward to your answers

Greets from Germany

[dmitri]

Please post the screenshot of a MDM MIDI Log showing the problem, i.e. two simultaneous hits on two pads with the time difference between hit bars.

[stefan91]

Please post the screenshot of a MDM MIDI Log showing the problem, i.e. two simultaneous hits on two pads with the time difference between hit bars.

Ok, I think this is a good example. I hit two pads simultaneously three times each (ignore the low rim outputs at the beginning please, just wanted to clear the window sitting at the drums).. In this case snare and tom3. I hit the head of both pads, output of "Rim" was routing-error of the pad (38 = snare, 65 = tom3)

The "delay" is round about 53 ms.

You can also see Cubase in the background - i recorded this part. The tom gets "cut" at the beginning.

[dmitri]

1. Please upgrade to the latest firmware version first and repeat the test.
2. You should disable HighLevel Auto once you found the best HighLevel value.
3. Why both Tom3H and Tom3R inputs have the same Notes? Is it a single zone pad? If it is and nothing is connected to Tom3R then it must be disabled by setting it's Note to 0.

[stefan91]

1. Please upgrade to the latest firmware version first and repeat the test.
2. You should disable HighLevel Auto once you found the best HighLevel value.
3. Why both Tom3H and Tom3R inputs have the same Notes? Is it a single zone pad? If it is and nothing is connected to Tom3R then it must be disabled by setting it's Note to 0.

Hi Dmitri,

thanks for your feedback - Point 1 really solved the problem! Thank you so much! I couldn't believe the problem is a firmware from March 2016 when it's April 2016 How is that possible? I can't believe everyone from 2007 to March 2016 had this problem - is it something like "newest MegaDrumManager can't properly communicate with older Firmware Megadrum"? A answer to this is not so important/urgent, I'm just curious

Point 2 and 3: Yeah, I know, I also read this in your documentation, just started Megadrum rapidly for the test yesterday without loading the normal settings. But nevertheless: thanks for the hint

.... Now I'm just limited to my own tolerances (see picture)

[dmitri]

thanks for your feedback - Point 1 really solved the problem! Thank you so much! I couldn't believe the problem is a firmware from March 2016 when it's April 2016 How is that possible? I can't believe everyone from 2007 to March 2016 had this problem - is it something like "newest MegaDrumManager can't properly communicate with older Firmware Megadrum"? A answer to this is not so important/urgent, I'm just curious

It was a bug I introduced in March with the introduction of a new 2.2" LCD and which I fixed quite quickly.

Point 2 and 3: Yeah, I know, I also read this in your documentation, just started Megadrum rapidly for the test yesterday without loading the normal settings. But nevertheless: thanks for the hint

.... Now I'm just limited to my own tolerances (see picture)

What do you mean by tolerances?

[stefan91]

thanks for your feedback - Point 1 really solved the problem! Thank you so much! I couldn't believe the problem is a firmware from March 2016 when it's April 2016 How is that possible? I can't believe everyone from 2007 to March 2016 had this problem - is it something like "newest MegaDrumManager can't properly communicate with older Firmware Megadrum"? A answer to this is not so important/urgent, I'm just curious

It was a bug I introduced in March with the introduction of a new 2.2" LCD and which I fixed quite quickly.

Point 2 and 3: Yeah, I know, I also read this in your documentation, just started Megadrum rapidly for the test yesterday without loading the normal settings. But nevertheless: thanks for the hint

.... Now I'm just limited to my own tolerances (see picture)

What do you mean by tolerances?

Oh, i see

By "my own tolerances" I mean, that there is still a "delay" between the two hits (some ms), but thats not megadrum's fault.. it's my own (playing accuracy)