www.megadrum.info

Hey

I am also using my drumkit with MegaDrum for controlling/playing the video-games RockBand and GuitarHero (yes, go ahead and laugh, but I just LOVE these games!)
There is a little box that translates the MIDI signals into suitable signals for the game. Before MegaDrum I had my Alesis DM5 Kit connected to that box and all was fine.

Now when I connect this box the MIDI-out of MegaDrum I have over 1(one) full second of lag/latency between the hit and the reaction in the game.
When I route the output with MIDI-OX from MegaDrum USB device to the MIDI-out of my UM1-G MIDI adapter I can use it without any noticeable lag/latency.

Where is the problem in Megadrum? How can it be the signals routed over a PC and another MIDI adapter are faster than the direct output of MegaDrum?

Poldi-1 wrote:Where is the problem in Megadrum?

The problem is not in MegaDrum. One of the tests I do each time after finishing building a module is connecting it to a drum machine over a standard MIDI. Also whenever releasing a new firmware I test over standard MIDI as well. You can test it yourself by connecting to proper MIDI device.
The problem is either in "a little box that translates the MIDI signals into suitable signals for the game" or in the game itself.

That explanation doesn't fit to the facts the little box works without latency on my Alesis DM5 module and when routing the MegaDrum MIDI signals over another MIDI device connected to the PC...

Connect it to a real MIDI device with a MIDI In port, e.g. a drum machine, another drum module, a MIDI keyboard. And I guess UM1-G also has a MIDI In port so you can test it with it.

Poldi-1,

I suspect the other MIDI adapter, (aka: the little box), does not send a continuous stream of MIDI data representing the high hat peddle position (as control message). One of the things that I love about the megaDRUM is it's continuous high-hat control messages to interact with SP20. RockBand and GuitarHero are gagging on this data provided by the megaDrum, The Alesis DM5 is also likely send less data for this function. I am stabbing in the dark on my assumption so forgive me if this data turns not to help you solve the problem.

- Bean

You have a good point there Bean, but it's not really connected to the main problem: Since a few hours I have my hall effect sensor based HiHat working (had a simple switch before) and when I have the pedal pressed in whatever state there comes the lag again (even in the routed config that was lag free before). So there seems to be a connection between the CC messages and the lag, but with my old pedal there were no constant CC messages and it still lagged on the MIDI-out of MD, so this is just an additional problem. (Or is my HiHat not setup properly yet when I have "flooding" CC messages on pedal movement?)
I hope the new PRO adapter that will arrive soon will fix that - or could I somehow block the CC messages on their routing-way?
I will test with the MIDI-In from UM1-G after the weekend dmitri

Poldi-1 wrote:I hope the new PRO adapter that will arrive soon will fix that - or could I somehow block the CC messages on their routing-way?

Change the Pedal type from F.Contr to Pot.

yay good point dmitri (had to look that up in the manual again...)
I will make another setup for that in slot 2

With the new official PRO adapter I can now use my standard set. HiHat CC messages no longer make it slower and the overall latency is great. Don't know why the old DIY box didn't work directly connected to MD but now I don't care anymore