You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when using my midi keyboard (AKAI MPK49) LMMS controls do not correctly process control messages, always leaving a single message "queued" and only processing that message when a new message enters that "queue" or some other event triggers processing of midi control messages.
this results in, for example:
buttons inverting their behaviour
knobs and sliders sticking to the last value received before the intended value. this is particularly annoying when trying to zero or max a control.
additionally, certain other events will partially trigger processing:
hovering certain buttons (mute, solo) will cause them to process the message
other controls depending on that particular control will not be updated (hovering solo will update solo but not the mute buttons it normally toggles)
minor details:
i have used drumstick midi monitor to verify the proper reception of midi control messages.
notes do not display this issue. it only affects control messages.
Expected Behaviour
controls process midi control messages as they arrive.
Steps To Reproduce
use a midi keyboard
map a keyboard control to an LMMS control
try to use it, it will always display the second-last value received by LMMS
Logs
Click to expand
Screenshots / Minimum Reproducible Project
No response
Please search the issue tracker for existing bug reports before submitting your own.
I have searched all existing issues and confirmed that this is not a duplicate.
The text was updated successfully, but these errors were encountered:
System Information
OpenSUSE Tumbleweed
LMMS Version(s)
1.2.2 (flatpak), 1.3.0~git2024.09.21-1.3 (repo-oss)
Most Recent Working Version
No response
Bug Summary
when using my midi keyboard (AKAI MPK49) LMMS controls do not correctly process control messages, always leaving a single message "queued" and only processing that message when a new message enters that "queue" or some other event triggers processing of midi control messages.
this results in, for example:
additionally, certain other events will partially trigger processing:
minor details:
Expected Behaviour
controls process midi control messages as they arrive.
Steps To Reproduce
Logs
Click to expand
Screenshots / Minimum Reproducible Project
No response
Please search the issue tracker for existing bug reports before submitting your own.
The text was updated successfully, but these errors were encountered: