www.megadrum.info

Since I updated my firmware to 20100618 I'm experiencing some "issues" on my pads. When I strike a pad hard it triggers both head and rim even though I don't have a trigger for the rim. I have the same setting on my pads as I've had before so nothing has changed except for my experimentation with my hihat pedal.

I can get rid of the simultaneous triggering of both head and rim at high velocities by setting "Dual Head: Yes". I'm curious to why it suddenly started to behave this way when it hasn't behaved like that before?

What version do you compare it to?
Is it high velocity false triggering on a rim?
Is it happening if you shorten a rim?

I'm comparing it to the previous 20100613 firmware.
I don't have a rim trigger. It's when I hit the head-trigger hard which generates a high velocity output (close to 127) that both head and rim notes triggers.
What do you mean by "shorten rim"?

rockdude wrote:I'm comparing it to the previous 20100613 firmware.

Nothing has changed at all between 20100613 and 20100618 versions except checking for correct bit for enabled/disabled "soft chick". It is a one byte change in the code.

I don't have a rim trigger. It's when I hit the head trigger hard which generates a high velocity output (close to 127) that both head and rim notes triggers.

And what is the velocity of this false rim note?

What do you mean by "shorten rim"?

I mean connect the rim input to the ground.

dmitri wrote:

rockdude wrote:I'm comparing it to the previous 20100613 firmware.

Nothing has changed at all between 20100613 and 20100618 versions except checking for correct bit for enabled/disabled "soft chick". It is a one byte change in the code.

I don't have a rim trigger. It's when I hit the head trigger hard which generates a high velocity output (close to 127) that both head and rim notes triggers.

And what is the velocity of this false rim note?

What do you mean by "shorten rim"?

I mean connect the rim input to the ground.

Hmm then it must be something that's changed on my end. I've only changed my settings for the pedal since the last firmware update, so I have no clue of what I might have done to cause this .....

I'm not at my drumset right now so I can't give you an exact velocity number for the rim triggering, but the sound triggered was as loud as the head-trigger so it must have been close to 127 too. I'll get back to you on this one and bring more information when I'm at my drumset tomorrow.

I managed to find another solution to get rid of the unwanted rim triggering. In the the settings for rim I changed "High level auto" to "NO" and set a higher value in "High level". So either I have to set "Dual Head=Yes" to get rid of the unwanted triggering...or if "Dual Head" is set to "No" I have to set "High level auto=NO" and up the value for "High Level" for my Rim channel.

HiLvlAuto should not really be left as Yes. It is a convenience options for quick start. After seeing what HighLevel you get with HiLvlAuto set to Yes you should really set it to No and fine tune HighLevel.

dmitri wrote:HiLvlAuto should not really be left as Yes. It is a convenience options for quick start. After seeing what HighLevel you get with HiLvlAuto set to Yes you should really set it to No and fine tune HighLevel.

Yes, I understand what you mean. I just didn't think it was necessary to bother changing anything for the rim channels since I don't have anything connected to them. I'm all single zone at the moment.

rockdude wrote:

dmitri wrote:HiLvlAuto should not really be left as Yes. It is a convenience options for quick start. After seeing what HighLevel you get with HiLvlAuto set to Yes you should really set it to No and fine tune HighLevel.

Yes, I understand what you mean. I just didn't think it was necessary to bother changing anything for the rim channels since I don't have anything connected to them. I'm all single zone at the moment.

In this case, even a smallest electrical crosstalk to any unconnected channels with HighLevel set to default (64) can trigger a high velocity signal.
It is better to disable unconnected inputs by setting Note number to 0. This way MegaDrum will skip these inputs and will have more CPU cycles for connected inputs.

dmitri wrote:In this case, even a smallest electrical crosstalk to any unconnected channels with HighLevel set to default (64) can trigger a high velocity signal.
It is better to disable unconnected inputs by setting Note number to 0. This way MegaDrum will skip these inputs and will have more CPU cycles for connected inputs.

Ok, I see. Thanks for clarifying.