www.megadrum.info

I was setting up my Megadrum. Things were going reasonably well, I had set up two toms, a hi-hat, a ride, and a crash.

(Not sure this is relevant) In the middle of my work, I upgraded to the April firmware. I was able to continue working after this.

At any rate, I went to copy the configuration from the second tom to the third tom (input 14/15) and somewhere in that process I started getting a continuous stream of notes from my megadrum for the tom3 input.

At this point, I haven't even connected the cable from the drum. If I connect the cable, then the notes continue, but the velocity goes up.

If I unplug the cable and set the gain to zero, I only get occasional notes. If the cable stays plugged in, there doesn't seem to be any way to stop the notes.

What I have tried:
- Connecting the (working) cable from tom2 to the tom3 input, notes continue.
- Connecting the cable from tom3 to the tom2 input, tom 3 plays tom2 correctly
- Copying a configuration to tom 4; tom 4 instantly started emitting notes.
- Downgrading to the March firmware
- Unplugging/Restarting Megadrum
- Changing Megadrum Autoload Conf to No and restarting

It is almost as if the gain to the A/D converters has been boosted to a crazy level and just the random noise is triggering the hits.

I am pretty stuck, any ideas?

raise the threshold.

A cable connected to an input without a pad/cymbal at the other end serves like an antenna picking up electromagnetic noise.

Which input do you use for Tom2 on your MD.

I was updating to the april firmware...and my input 6/7 (which I use for TOM1) went totally bananas. Had to raise the threshold very high on the RIM/Edge to get rid of the false notes. (39-40)

Felt very strange - I had been using the same settings for about 10 different firmware updates...and suddenly the TOM 1 goes bananas...

Best Regards

ANGR77

angr77 wrote:I was updating to the april firmware...and my input 6/7 (which I use for TOM1) went totally bananas.

From which version to which did you update that caused you to raise Threshold on the input 7?

I think I was on 20140318 and went for the test release of 20140414. The vh13 fix.

Have not tried the 20140418 yet.

Best Regards

Anders

I just checked the code difference between 20140302 and 20140417 versions and there is nothing there which could have effected any inputs sensitivity or handling. Are you sure there is a difference in sensitivity/false triggering on the input 7 between those versions? Can you load the old version and check?

Thank you for the help, raising the threshold solved the problem. There's a lot of settings, still getting my head around which ones are available.

For reference, the unit was false triggering with nothing plugged into the Megadrum. Whenever I connected a cable, there was always a drum at the other end.

And, the inputs that I saw this on were 14/15, 16/17, and then after I downgraded firmware, 6/7.

Now, I am back up on April's firmware, raised thresholds and no repeated notes.

Is input 7 false triggering with default Gain and Threshold? If not, what are the Gain and Threshold which cause false triggering on the input 7 but not on other inputs?

When I reloaded the April Firmware, the false triggering seemed to move back to Tom 3 (14/15). Unfortunately, I am still learning the system, so I don't think I am a very reliable witness. I may have done something else simultaneously.

I do know that I have the threshold up to 40 to prevent false triggering on Tom 3. I have been working on my hi-hat and I was getting false triggers on Tom 3 when I hit the hat if I had it any lower. This is a Yamaha RHH-135 on a high hat stand and a real floor tom with a piezo conversion. They should be pretty well isolated from a vibration point of view.

For Tom 3, If I turn the threshold down to 20, I get continuous notes. As I raise it, the notes become more occasional, pretty well disappearing by 26. However, I still get lots of spurious triggers from other drums. 40 seems to be the level that cuts that off.

I hope that answers the question.