Piezo hits right after switch hits not registering

[ignotus]

Hi,

I'm very close to getting my kit nicely dialled in with the new MD board but there's a thing that's bugging me and that also used to happen with my old MD: you have a piezo/switch pad, where bow is piezo and the switch is either edge or bell: if you hit the switch zone first and rapidly after that the bow (piezo), the bow hit isn't picked up. There's a space of time (roughly around 1/4 to 1/2 a second) right after the switch is hit during which piezo hits aren't picked up.

I'm wondering if there are any settings that might be causing this, or if it happens to anyone else. It means I can't do quick edge/bow patterns on the hi hat or bow/bell patterns on the ride without them missing hits.

[dmitri]

I'll check that.

[dmitri]

I just tested it with Yamaha PCY135. I tried hitting with as little space between hits as possible. These are settings and MIDI Log:

pcy135.png

Please note, that if a bow hit after an edge/bell hit is of similar or lower velocity and with little space between hits then MegaDrum will try to suppress it to prevent double triggering.

[ignotus]

Ok, so it looks like it's something about my setup. Is there any setting I should be looking at that might reduce the problem? I have crosstalk set to 0, retrigger to 2 or 3 and dynlevel and dyntime to 0 on those pads... maybe minscan or something?

[dmitri]

To be honest, I didn't do anything special. Most of settings are at defaults as you can see. I only reduced DynLevel/DynTime to 0 and Retrigger to 2 as I normally do (these settings probably should be default but for historic reasons I have not done this). I also lowered XTalk Level just to make sure, as expected, it doesn't affect triggering suppression between zones of the same pad/cymbal.
Also, but I guess you are very well aware of this, HighLevel on both bow and edge zones must be set correctly, otherwise false triggering suppression will work incorrectly.

[ignotus]

Thanks Dmitri, you might be on to something... I'll check it properly tomorrow but there's a chance that the highlevels may not be at optimal values. I have a bad habit of not using the HighLvlAuto function to get an approximate highlevel value first and often leave it at 'No' and just raise it manually until I reckon it's ok - so that might be it right there.

[ignotus]

Yep, turns out high levels were the culprit; working fine now... duh!