Really depends - I have something similar (a ReaJS script that does the same) continually active in my “Second Keyboard” Rack, because this keyboard does send multiple note-ons for some notes on fast glissandi, resulting in stuck notes on a number of plugins (the ones that actually create a new voice for every note on). There’s a couple of these plugins - most notably in my setup the Korg Triton plugins - and I wouldn’t strictly call them “misbehaving”.
With a normal keyboard, multiple note-ons are mostly glitches and in most cases they serve no purpose, so it makes sense to filter them out at the source.
Only in the case of a triple-sensor keybed and a plugin that will work with that does it make sense to keep them - I would use a keyboard abstraction rack with two states (“filter active” and “filter inactive”) to switch that behavior on a song-by-song basis
It sounds like this would be a perfect solution for fixing the stuck notes that i experience with a certain controller keyboard + MIDI interface combination. If i’m understanding this correctly, any stuck note (i.e. Note Off not received) would be cleared the next time the same note was played. Magic !
Sure, but there are easier ways than that to clear stuck notes, without having to identify which note actually is stuck: Use a binding from a button on your controller (or simply use the lowest note on the keybed if you don’t have a spare button) and bind it to Engine - All Sounds Off. This will pretty reliably end all stuck notes.
I have a big fat friendly red button on my upper keyboard that says “Panic” and does exactly that. Only if my upper keyboard crashes and leaves a stuck note that way, that panic button doesn’t work. That’s why I have a reserve panic button on my Streamdeck…
If you want to be even more brutal about it, bind to Engine - Restart Engine. This takes more time (it turns the audio engine off and on again), but is even more thorough in eliminating anything stuck…
I would think the big advantage of using the de-duplicator filter is that the stuck note would be automatically cleared when the same note was played again, possibly even before you noticed
that a note was stuck.
This is great. Many MIDI controllers’ pads tend to double trigger, which can be a problem. To this date the only thing available has been a python script that isn’t maintained and iirc doesn’t run on available versions of Python.
This is only a partial solution to that problem though, since the doubled noteon may come after the associated noteoff for the original trigger.
I’m using @cdv_gabriel’s All Note Off script and now introduced the De-Duplicator into the equation. Good luck to any stuck note getting through that lot.