www.megadrum.info

Hi,
even if I set the pads' threshold to 127, MD still transmits notes with low velocities. Is it normal to get output notes well below the threshold set?

Threshold is just to configure sensitivity of an input and relates to a voltage on an input and not to MIDI velocity (at least not directly). If you want an input to produce velocities in certain range (e.g. 64 to 127) you can do it with Custom Curves and/or LvlShift. Note that in this case light hits will still produce Note On/Off messages but with higher minimal velocity.
If you just want to cut off Note On messages below certain velocity level than it can be done with a MIDI filter on a PC. Or I can add this feature in firmware if more people find it useful.

dmitri wrote: Or I can add this feature in firmware if more people find it useful.

This would be great. I can filter the data on the receiving devices, but it generates unnecessary extra MIDI traffic, contrary to suppressing those notes below the threshold on MD.

The Threshold parameter works like this on all other trigger-to-MIDI converters I know.

The need for this varies from pad-to-pad or even from application-to-application on the same pad: e.g. I have some pads which are used for sequencer transport control only. These ones should be nearly dumb and should only react to strong strokes, no note should sneak out when hitting a nearby acoustic cymbal or tom and stop playback accidentally. Some pads trigger sounds where a little leakage is ok (for the sake of added sensitivity when playing), like a snare sample, while the same pad might trigger a loop in another tune, where leakage is not allowed at all.

I know you like to identify MD as a DIY project, but its feature set stretches far beyond the needs of hobbyists, so please consider this addition if it's not too hard to implement.

Thanks,

Endre

What if I implement it like this:

There is a 'Special' function in Pads Settings. On rim/edge inputs it activates Program Change support. On head/bow inputs this function does nothing at the moment. I can use it to enable a 'Cut Off' function. When enabled on a head/bow input it will use ANote as a 'cut off' velocity level of the input. If the triggered signal has a velocity level below ANote number then no MIDI Note On/Off will be sent. Of course the note alternation will not work on a head/bow input where this function will be enabled but I guess it will not be needed on a special purpose input.

What do you think?

This would be fine for the head/bow inputs, but it wouldn't solve the problem for the rim/edge inputs. I understand that you must be very economic about the remaining space available for adding new features, but would it be possible to add a new setting that would determine what the "Special" setting does for the pads: enabling PC or Threshold setting. I don't mean a per Pad setting, but a global one, that shouldn't take too much space, I guess.

dmitri wrote:If you want an input to produce velocities in certain range (e.g. 64 to 127) you can do it with Custom Curves and/or LvlShift. Note that in this case light hits will still produce Note On/Off messages but with higher minimal velocity.

Why not just add the option to enable "choke P1 to p2" data in the "Pads Extra Settings"?

This way, when enabled, P1 to P2 sends no data and P2 to P9 reallocate the sampled data to the new MIDI curve.

See where I'm going with this?

- Bean

Bean wrote:
Why not just add the option to enable "choke P1 to p2" data in the "Pads Extra Settings"?

This way, when enabled, P1 to P2 sends no data and P2 to P9 reallocate the sampled data to the new MIDI curve.

See where I'm going with this?

- Bean

Let's wait for Dmitri's feedback on this, but if I understand it correctly, this could work, although it would be harder to relate the settings to the actual MIDI velocity threshold.

Check the latest firmware version:

Changes in version 20120303:

1. Replaced the 'Special' pad setting with a 'Function' setting. It can be set to 'Normal', 'PrgChg' or CutOff. Default is 'Normal'. When set to 'PrgChg' it behaves as when 'Special' was set to 'Yes' in previous versions. When set to 'CutOff' the 'ANote' setting changes it meaning to 'cut off' level - hits with velocities below level set in 'ANote' will not trigger Note On/Off messages.

dmitri wrote:Check the latest firmware version:

Changes in version 20120303:

1. Replaced the 'Special' pad setting with a 'Function' setting. It can be set to 'Normal', 'PrgChg' or CutOff. Default is 'Normal'. When set to 'PrgChg' it behaves as when 'Special' was set to 'Yes' in previous versions. When set to 'CutOff' the 'ANote' setting changes it meaning to 'cut off' level - hits with velocities below level set in 'ANote' will not trigger Note On/Off messages.

Unmatched support quality is one of the main reasons why I love MD!!!!!!!!!!!! Thanks!

Does the new setting apply equally to head/bow&rim/edge inputs?

el-dr wrote:Unmatched support quality is one of the main reasons why I love MD!!!!!!!!!!!! Thanks!

Works like a charm on my 16" & 20" mesh floor tom's!

I have been struggling with mechanical after-bounce on my largest toms, this new feature covers up the flaw in my pads rather nicely.

- Bean