www.megadrum.info

Hello Everyone,

My MegaDrum 32 (non-rackmount) unit has started acting very strange. It's just totally unpredictable.

- a couple hours ago there WAS hi-hat and snare sound, but now these inputs has gone mute without touching the (brand new stereo symmetric) jacks or altering anything in the software. So now we don't have hi-hat and snare sound.
- my ride cymbal is playing by itself (even with 0 gain or max. threshold). We've checked the power supply of the MacBook Pro. It's flawless. The MegaDrum does this even when the laptop's running without power supply. It's not an issue of MIDI channels or an issue of Addictive Drums… I still have proper toms, crash and kick. It's not an issue of the pads, too.
- when I plug out the jack cable of the hi-hat pedal (input 1 here), the kick drum (input 2) starts to play 16th notes at 200 BpM like the craziest hardcore drummer on Earth with double kick pedals. It's keeps playing until I totally plug off the jack cable (from input 1).

And so on...

Firmware version is: 20140629
Should I upgrade the firmware?

I'd appreciate any help as soon as possible although I'm aware it's not the best timing because of Christmas... But we can't figure what the problem is and we HAVE TO work. Even a Hungarian friend of mine, Endre "eNerd" Huszar, owner of more MegaDrum units) doesn't have any idea of what the heck is happening here.

Thanks in advance,
Mirko

Post a screenshot of the settings. If you unplug the pads the cable acts as an antenna - thats the cause of the machine gun triggering.

I'd open the module and check for continuity between the sleeves of the input jacks and a ground pin on the pcb (consult the board's manual to see which ones you could use, there are several to choose from). Whenever I've had crazy non-stop machine gun triggering on several inputs it has always been due to ground connection issues. I don't think a cable acting as an antenna should cause a non-stop stream of triggering. Also check whether the ribbon cable connector is properly seated on the pcb header.

Might not be that but it's worth a try.

Plus to the above advices I'd suggest you to start with default settings (set AutoloadConf to No, wait until it exits to Menu and power cycle the module) and see if problems are still there.