-
-
Notifications
You must be signed in to change notification settings - Fork 360
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
OSC: collection and chase feedback error #1413
Comments
Thanks for the comprehensive report. I was able to reproduce this problem. QLC+ has 3 states for a button: On, Monitoring and Off. https://www.qlcplus.org/docs/html_en_EN/vcbutton.html Since the buttons are put into "Monitoring" mode, the behaviour is expected. This is unless there is a "highlight" option in OSC which I can't find documentation on. |
Hello, first of all thank you for the feedback. In the last period I have studied various documentations on the use of OSC and I can confirm you that there is no "highlight" value (state) in OSC. For "button" type commands (and similar), only the "on" and "off" values are provided. It would be very useful if in the OSC plugin configuration of QLC+ there was the possibility, perhaps through a flag, to choose whether to send an "on" feedback status even when the VC buttons of QLC+ are put into "monitoring" mode. |
Recently I found a similar use case to you when using a MIDI controller. I think this is an opportunity to improve the feedback functionality globally. When a function is active, there is no visible indicator on RGB pad if it's only in the "Monitoring" state. This can make it confusing when looking at a midi controller to determine the currently running functions. There are many ways to implement the ability to provide feedback to controllers for widgets in the "Monitoring" state. Here are some suggestions:
Solution Suggestion 2
If you have any thoughts or like these suggestions, I'm happy to make a feature request in the forum. Cheers. |
Good morning, I think the "Solution Suggestion 2" proposed by @yestalgia is better. |
Describe the bug
When QLC+ is configured to communicate through OSC Plugin, we are encountered a problem with the feedback of the scenes commanded by a "collection" type function and with the feedback of the scenes commanded by a "chaser".
Put simply, we have these two cases:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The expected behavior is that when a collection or chaser function is activated, the feedback of the child functions will be sent (so not only when in "virtual console" the edge of the buttons is green, but also when it is orange).
Screenshots
In this image we see:
(DEBUG, OSC) In: { address: '/rgbw/r', args: 1 } From: 127.0.0.1:62002 | ("/rgbw/r" is the OSC ID of the "R" button of "Generic RGBW")
(DEBUG, OSC) In: { address: '/rgbw/r', args: 0 } From: 127.0.0.1:62002 | ("/rgbw/r" is the OSC ID of the "R" button of "Generic RGBW")
(DEBUG, OSC) In: { address: '/rgbw1/r', args: 0 } From: 127.0.0.1:62002 | ("/rgbw1/r" is the OSC ID of the "R" button of "Generic RGBW 1")
(DEBUG, OSC) In: { address: '/rgbw2/r', args: 0 } From: 127.0.0.1:62002 | ("/rgbw2/r" is the OSC ID of the "R" button of "Generic RGBW 2")
The same error happens even if the buttons are activated by the OSC software.
Desktop:
Additional context
This zip contains the files used for the test:
test.zip
The text was updated successfully, but these errors were encountered: