MIDI Note D9 122

[gastric]

I've built a Synthex V2.8 kit, it's assembled, appears to be functioning properly, has firmware 20090326.

One oddity that I am experiencing is where MD will incorrectly output the wrong MIDI Note. Instead of outputting the correct MIDI Note per the Note assignment in MD, it outputs MIDI Note D9 /122. Nowhere in any of the MD parameters for any of the triggers is this note configured so it's not a crosstalk issue. However, according to MCT and MIDI-OX it is truly outputting MIDI Note D9 / 122.

Based on my testing this ONLY occurs in the following scenario:

* Dual-trigger drum or cymbal
* Dual-head = Yes
* Play on the head trigger ONLY and it will often trigger MIDI Note D9 / 122 instead of the assigned note
* Play on the rim trigger and it never happens
* Set Dual-head = No and it never happens
* Set MIDI Note on rim trigger = Disabled and it never happens (even when Dual-Head = Yes)

So my conclusion is it's related to crosstalk. Whenever it's rejecting a trigger due to whatever computation and it cannot successfully determine if it's a head or rim strike then it outputs MIDI Note D9 / 122 specifically. Which is apparently handy for troubleshooting.

But I'd like confirmation this is what is supposed to be happening.

The keywords for this issue are too small to effectively search on, hence this new post.

[dmitri]

In the documentation section for pad settings, http://www.megadrum.info/content/pads-settings, read about BNote and BThreshold.

[gastric]

Always amazing. I've been staring at MCT for hours and literally never looked at 3rd zone. And of course there's MIDI Note 122. Bingo!

My suggestion would be to disable the 3rd zone in firmware by default as I'm sure it is a very rarely used feature. And even then, it probably only will be used on the snare.

OK, so I've set my 2-zone (bow/bell piezos) ride as seen in the attached screenshot (ignore the final trigger of Note 37 for my snare, which is where I set my headphones). When playing the bell I get what appears visually and audibly as perfect bell triggering. However, when playing the bow I often get a MIDI Note -1 / 0 triggered.

I'm guessing this is still related to the 3rd Zone. And Disabled is actually triggering MIDI Note 0 when it should be removing 3rd Zone from all consideration.

[gastric]

Dmitri, unrelated, but since I've got your attention here, can you review my post in the "gain parameter" threadand correct any mistakes I have in understanding how Gain should truly be functioning.

[dmitri]

Always amazing. I've been staring at MCT for hours and literally never looked at 3rd zone. And of course there's MIDI Note 122. Bingo!

My suggestion would be to disable the 3rd zone in firmware by default as I'm sure it is a very rarely used feature. And even then, it probably only will be used on the snare.

OK, so I've set my 2-zone (bow/bell piezos) ride as seen in the attached screenshot (ignore the final trigger of Note 37 for my snare, which is where I set my headphones). When playing the bell I get what appears visually and audibly as perfect bell triggering. However, when playing the bow I often get a MIDI Note -1 / 0 triggered.

I'm guessing this is still related to the 3rd Zone. And Disabled is actually triggering MIDI Note 0 when it should be removing 3rd Zone from all consideration.

Set BThreshold to 0 as suggested in the documentation. MCT should set BThreshold to zero when disabling the 3rd zone but apparently it doesn't.

[gastric]

That's a reasonably idea. However, BNote = 0 in MD. So apparently MCT is correctly updating that parameter properly, it simply displays "disabled" instead of "0". Other thoughts?

[dmitri]

That's a reasonably idea. However, BNote = 0 in MD. So apparently MCT is correctly updating that parameter properly, it simply displays "disabled" instead of "0". Other thoughts?

BThreshold and BNote are two different things.

[gastric]

Thank you for clarifying. It appears if I set BThreshold to 0 that corrects the problem. I agree, if you set BNote = Disabled in MCT it should set BThreshold = 0 if that's what it takes to truly and completely disable it entirely.

Again, I'd suggest disabling the entire 3rd zone by default in the firmware. Users can then turn it on if they want, rather than everyone having to specifically disable it on all inputs.