-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 mapping for Behringer controllers DDM4000 & BCR2000 #12969
Fix mapping for Behringer controllers DDM4000 & BCR2000 #12969
Conversation
A case which is not covered by #12437 yet |
Root cause is QTBUG-95677, see #11473 (comment) for details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm otherwise
README.md
Outdated
bug list][easybugs] and get started! | ||
bug list][easybugs] and get started! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls remove this change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done. It was required for the CI build.
This reverts commit ea07859.
LGTM! Thank you! |
This PR fixes a bug introduced by commit 306bbe4 (PR #12401) that covers the switch to QJSEngine for v2.4.
When an affected controller (Behringer DDM4000 or BCR2000) is configured, the following message is shown on application start of v2.4.0:
With the suggested patch applied, no error is shown and the controllers work as expected.
Probably related: #11473
/cc @Swiftb0y @JoergAtGithub