-
-
Notifications
You must be signed in to change notification settings - Fork 40.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix handling multiples of the same MIDI note (fixes bug brought up in issue #10199) #11639
Conversation
An issue I've noticed while playing some with this change applied is that if I change octaves on the keyboard while a note is held, the note is sustained as the note off message being sent when hte key is released is an octave off from the note on message that was sent when the key was pressed. I would optimally try to map the registered presses to physical keys rather than keycodes, but since that would be layout dependent I'm assuming it can't be done in core so I'll have to think of a different solution. I assume this also applies to transpositions. |
Extend MIDI note status to fix note releases
Failing build is addressed in PR #11652 |
Thank you for your contribution! |
Hi @jakobkg. If I tried the previous version (c66df16) by the following command, the problems can be solved. Could you check it at your enviromnent? |
Description
This change makes it so that MIDI note on messages are sent every time a MIDI key is pressed, but the MIDI note off message is only sent once all instances of the same MIDI note have been released. This issue would make it so that if you have a keymap with several MIDI chords, where the chords had overlapping notes, the common notes would be turned off once one chord was released even if another chord containing the same note is still being held. This PR fixes that.
Types of Changes
Issues Fixed or Closed by This PR
Checklist