Page 1 of 1
Blackout does not work as usually should do
Posted: Wed Dec 21, 2022 12:30 pm
by HAF
Hello Massimo,
this is the same request like:
https://github.com/mcallegari/qlcplus/issues/1381
but moved to Forum, like wanted.
The Problem:
Blackout should be the same as "Masterfader at Zero".
Actually it is a "All Channels to Zero", maybe needed for development, but thats really Bad for Movingheads, Effects, and so on.
Thanks for your great Work.
Hardy
Re: Blackout does not work as usually shoud do
Posted: Thu Dec 22, 2022 11:03 am
by GGGss
... but what if you want to hard reset all channels?
Re: Blackout does not work as usually shoud do
Posted: Tue Dec 27, 2022 6:57 pm
by mcallegari
This should be fixed now upstream
Re: Blackout does not work as usually shoud do
Posted: Tue Jan 03, 2023 1:08 pm
by HAF
GGGss wrote: ↑Thu Dec 22, 2022 11:03 am
... but what if you want to hard reset all channels?
Then name it not "Blackout".
Perhaps "Hard Reset" or "All Zero"?
Re: Blackout does not work as usually shoud do
Posted: Wed Jan 04, 2023 2:50 am
by Yestalgia
mcallegari wrote: ↑Tue Dec 27, 2022 6:57 pm
This should be fixed now upstream
This is a big improvement, thank you.
Re: Blackout does not work as usually shoud do
Posted: Tue Jan 10, 2023 1:59 pm
by markzvo
But what about users that use the Blackout for years as All to Zero?
If this changes, this cause harm to users that have been using the function as it has been for many years.
Re: Blackout does not work as usually shoud do
Posted: Wed Jan 11, 2023 8:45 am
by GGGss
Please distinguish between Blackout (all intensities to zero) which serves HTP channels(?) and Stop All Functions (which is a function reset) which serves the LTP channels.
Re: Blackout does not work as usually shoud do
Posted: Wed Jan 11, 2023 12:57 pm
by mcallegari
Fredje, I think you're making a bit of confusion here.
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)
In conclusion, to reset ALL channels you now need to create a Scene with all your fixtures, with all channels enabled at zero and place a button in the VC.
Re: Blackout does not work as usually should do
Posted: Mon Nov 25, 2024 4:21 am
by paleolas
Hello all,
I have well understood what you said Massimo, but i am a bit confused on how to really use all the "off" features linked with running functions :
may i resume with my words :
- blackout is for HTP channels
- manually made "Scene with all your fixtures, with all channels enabled at zero" is for LTP channels
So : to reset ALL, we need to press the blackout AND the "Scene with all your fixtures, with all channels enabled at zero".
So maybe making a script with both actions... it works if we are setting an really big time to wait after that.
Look at my simple example which explain clearly my confusion regarding how to manage a simple black scene...
In my example, i added an extra knob, value set at 10 (which is not evident to see sometimes). And if this knob is not clearly visible (like in frame page N) we can't make a clean black scene. after searching for active function none are active but a channel is still lighting... we can search for long time before finding to good knob. and this can happen easily. to do so, just let a function fadeout and before the end, click the stop button => you have now a "visually broken project" if you save it now.
Is there a possibility to reset all the knobs at once (at least before saving project) ?
I think during blackout, the simple desk shall be greyed out (to explain user that the simple desk is not anymore showing whats going on DMX and removing the blackout will go back to the position seen in simple desk). if nobody does code it, i will.
ps : I'm using 4.13.1
Re: Blackout does not work as usually should do
Posted: Mon Nov 25, 2024 1:58 pm
by MichelSliepenbeek
if nobody does code it, i will.
Before you do so i suggest you first have a look at what you can do with:
Solo Frames (
https://docs.qlcplus.org/v4/virtual-console/solo-frame).
If you want functions to stop, just put them in a solo frame and add an extra button to it.
Depending on what the other buttons do, this button should "represent a neutral value" (In a Color Selector use Black, in a GOBO Selector use Open, in a Position Selector use Center, ........).
Of course you can also (create and) use a
Dummy Scene (that does not do anything), just to stop the other functions.
A possible next step would be to create a Collection (
https://docs.qlcplus.org/v4/function-ma ... ion-editor) with all the "Stop functions" you use in your Solo Frames.
Sliders in Submaster Mode (
https://docs.qlcplus.org/v4/virtual-con ... master-tab).
In your example you did set your Knobs in Level Mode, meaning they will override any other values you send to that specific channel.
Just create a scene that's sets the value of a chanel to 255, create a button to launch it and put this Button together with a Slider in SubMaster Mode in a Standard Frame.
Now your Slider will only Override when the Function is active.