Now if only NI found a way to send them a message. So, time for a new MIDI controller! Or an email to the Reaper guys, might be a simple thing for them to fix actually. NI know this but it's not a high priority thing currently, somewhat understandably, as they're doing things by the book - only a certain amount of MIDI controllers don't. (The grey rows are the black keys on the piano) MIDI Note. F3 through F6 are required to play the two Mozart works for the armonica. So, if you're experiencing this too, then now at least you know why. This table lists the MIDI note number, the ANSI note name, and the frequency (hz) for each note on the piano keyboard. I've also not encountered similar issues with other VST3 instruments, so I'm inclined to guess that Super 8 should ideally re-interpret that 'Note-On with a zero value' as a Note-Off.

This kind of auto-conversion might be happening in lots of DAWs, not sure, but this 'bug' seems not to get reported very often. I compared that to this list here:Ībleton Live converts that same message to having a status byte of 128, which according to that list is a regular Note-Off. The 'status byte' in the MIDI messages that my keyboard sends is 144 (in decimals).

Was that a standard at some point? Seems that a number of MIDI controllers do that, if the above reports from others are to be believed.Ībleton Live then seems to auto-convert these messages to 'regular' Note-Off messages, and Reaper leaves them as they come in. my MIDI controller sends Note-Ons with a value of zero when letting go of a note. What I found out and posted in another thread (Super 8 related), in case this happens to some of you and you're wondering why: If you use Reaper and your MIDI controller is of a certain age or model, your Note-Offs will not be recognized.

Midi note number zero