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
After upgrading QLC the blackout button doesn't work anymore
To Reproduce
Create a new show
Patch some dimmers
Create a virtual desk with some fader set to control the dimmers's levels
Go live
Toggle blackout doesn't work
Expected behavior
I expect the blackout button to set all dimmers to 0, as in previous versions
Please note that the grandmaster fader works so it isnt a patch issue
Screenshots
Desktop (please complete the following information):
OS: Windows 10 Pro
QLC+ Version 4.13.0
Simple one universe setup with an Enttec dongle
Additional context
The text was updated successfully, but these errors were encountered:
Hey, there has been a change to QLC+ dimming which actually came about in 4.12.7
This was done so only HTP (highest takes priority) channels were set to 0. Which means when you hit blackout the movement channels don't go to zero.
From Massimo on the forum: "Blackout was once resetting ALL channels (HTP+LTP)
As requested, I adapted it like all the consoles in the world do: reset only HTP channels
Stop all functions instead, stops ALL the running functions, leaving LTP channels where they were (so they're not reset too)"
I'm pretty sure that blackout still works for the generic dimmers but I don't have it in front of me.
Can someone else confirm?
mcallegari
changed the title
Blackout not working anymore on QLC 4.13.0
Blackout not working anymore on QLC+ 4.13.0
Mar 21, 2024
Describe the bug
After upgrading QLC the blackout button doesn't work anymore
To Reproduce
Expected behavior
I expect the blackout button to set all dimmers to 0, as in previous versions
Please note that the grandmaster fader works so it isnt a patch issue
Screenshots
Desktop (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: