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
Describe the bug Recently, the MIDI custom feedback settings when assigning inputs to elements such as buttons, completely disappeared and also seem to be broken.
Note
The MIDI controller (AKAI APC Mini MK2) is working correctly as expected, for both Inputs and feedbacks
The real issue is just that the user is no longer able to change the feedback parameters (such as pad color, on/off/blink status and so on...)
This is what I see when I try to edit the settings of a button that already had custom feedback parameters assigned in an onlder version of the project I used.
And this is what I see if I try to change the pad color:
Caution
All MIDI plugin parameters are correctly set. The controller is recognized and works fine. This also happens to newly-created projects
To Reproduce
Steps to reproduce the behavior:
attach a MIDI controller
create a button, link to scene and try to change its feedback settings
Desktop (please complete the following information):
OS: Windows 11 25H2 build 26200.8246
QLC+ Version 4.14.4
AKAI APC MINI MK2
Additional context
Important
I said "recently" because while digging inside the forum some user reported having MIDI issues on latest Windows builds, so I expect this to be a problem strangely related to an OS update. I absolutely need to mention that everything has always worked fine (same setup) till like two months ago. This also happens on other PCs I have with 4.13.3 that never had an issue, but were recently updated to Windows 25H2. Another PC I own that has no Internet connection, as it is installed inside a venue and runs lights offline (and did not receive updates) does NOT have this issue.
After finding out this issue, I've also started seeing unpredictable MIDI disconnections happening randomly, that force the user to restart the plugin to make the controller work. Trying disabling power saving options and USB selectivity did not work. The cable is not failing. I don't know if it is on my end or it may be related to this issue, I'm just trying to give as much details as I can.
My hopes with this report are at least in a workaround, as the issue may really not be linked directly to the QLC codebase. Using MIDI devices has been painful lately.
Describe the bug
Recently, the MIDI custom feedback settings when assigning inputs to elements such as buttons, completely disappeared and also seem to be broken.
Note
The MIDI controller (AKAI APC Mini MK2) is working correctly as expected, for both Inputs and feedbacks
The real issue is just that the user is no longer able to change the feedback parameters (such as pad color, on/off/blink status and so on...)
This is what I see when I try to edit the settings of a button that already had custom feedback parameters assigned in an onlder version of the project I used.
And this is what I see if I try to change the pad color:
Caution
All MIDI plugin parameters are correctly set. The controller is recognized and works fine. This also happens to newly-created projects
To Reproduce
Steps to reproduce the behavior:
Desktop (please complete the following information):
Additional context
Important
I said "recently" because while digging inside the forum some user reported having MIDI issues on latest Windows builds, so I expect this to be a problem strangely related to an OS update. I absolutely need to mention that everything has always worked fine (same setup) till like two months ago. This also happens on other PCs I have with 4.13.3 that never had an issue, but were recently updated to Windows 25H2. Another PC I own that has no Internet connection, as it is installed inside a venue and runs lights offline (and did not receive updates) does NOT have this issue.
After finding out this issue, I've also started seeing unpredictable MIDI disconnections happening randomly, that force the user to restart the plugin to make the controller work. Trying disabling power saving options and USB selectivity did not work. The cable is not failing. I don't know if it is on my end or it may be related to this issue, I'm just trying to give as much details as I can.
My hopes with this report are at least in a workaround, as the issue may really not be linked directly to the QLC codebase. Using MIDI devices has been painful lately.