STEVE SCARR

Hi. Having trouble triggering note off event after midi note has been triggered on the grid.

The current solution was to use the quantize time amount (1/4, 1/8, 1/16, etc) to trigger the note off value as well. For instance: if the quantize value is set to 1 bar, consider the note on being triggered a couple beats before the next bar, and then being triggered to start at that next bar. Then also, a note off might be triggered before that next bar even happens, it would never get the opportunity to have a note off and therefore result in a forever sustaining note. So to resolve this, we need to store the data of the midi note length (currently in milliseconds) and it needs to somehow be added to the start time of the resulting note on value so that the note off value is maintained (the same length as what I play).

Can anyone help shed some light on why the configuration I have isn't turning the note off at the same interval as I'm initially playing it?

The current solution was to use the quantize time amount (1/4, 1/8, 1/16, etc) to trigger the note off value as well. For instance: if the quantize value is set to 1 bar, consider the note on being triggered a couple beats before the next bar, and then being triggered to start at that next bar. Then also, a note off might be triggered before that next bar even happens, it would never get the opportunity to have a note off and therefore result in a forever sustaining note. So to resolve this, we need to store the data of the midi note length (currently in milliseconds) and it needs to somehow be added to the start time of the resulting note on value so that the note off value is maintained (the same length as what I play). 

real-time-midi-quantize-problem-storing-midi-note-length-data-plugin

Didn't look at the patch yet but in your screenshot: the note length will not make it to the delay, it's only displayed via [message]…

Real-time MIDI Quantize problem with storing midi note length data (plugin)