Support for scene / effect priorities or at least a good workaround

[bestdani]

Hi,
I like QLC+ so far for creating timelined light shows, since this works almost perfectly I had considered to switch to it for live controlled lights, too. But I quickly realised that there is nothing like priorities for scenes and that's one main aspect because I think it's nut suitable for that usage in my case currently.

A higher priority scene would overwrite the output of a lower priority scene and set some values to 0 even when the channels are set to HTP and the lower priority scene set it to 127 for instance. Or is there a workaround to achieve this by using loopbacks for instance which I could not figure out so far?

I'm especially interested in if the current code design would allow a quick implementation of that, I'm asking this since I've some reasonable programming experience and I'm wondering if it would be worth to take the time to try to implement such a priority system.

[plugz]

Hi,

- Scene 1 and scene 2 in a solo frame ?

or

- Have a loopback channel that controls a submaster slider that controls the scene you want to diminish.

EDIT- Here's an example of a loopback on a submaster.
The Red scene is "maximum priority", so it is associated (in a collection) with the submaster control scene.
The Green scene is "low priority", so it is controlled by the submaster.
See what happens in the monitor when playing with the 2 buttons.

[janosvitok]

Solo frame nor loopback is not a solution here. I myself am looking such a solution.

What is needed is a way to temporarily override current output with high priority scene (that may contain both LTP and HTP channels) and when the scene is stopped return to previous state.
Examples:

- temporarily override ("flash") Shutter channel to strobe and then back to open
- have a color chaser running on a RGB led PAR, flash to another color, then return to the chaser

I don't think it's and easy task, but I be glad if someone shows me I'm wrong.

I've already explained somewhere how the core works. I'll try to find it. Basically, you need to look at following classes: Universe, Scene, GenericFader, FaderChannel, MasterTimer.
The main output loop starts here: https://github.com/mcallegari/qlcplus/b ... er.cpp#L98

For the relationships, you may want to generate your local copy of doxygen documentation or use the one at http://qlcplus.zvukari.sk/doxygen/index.html (not very fresh, I'll update it when I find some time).


I think the first thing to fix before actual priorities are implemented is to make LTP scenes return to previous value when they are stopped (i.e. implement LTP flashing)
With this comes another question: should one LTP function be stopped ("released") when all its channels have been overriden by another LTP function? Some consoles have configuration for this.

Finally, there are questions about the design:
- what should the priorities look like (just normal/high, or multiple prorities)?
- release thing again
- ...

[pengumaniac]

Hi all,
home again from Gaildorf Bluesfest, I had now a little bit sparetime to read the news and have a look at the improvements of 4.9.1
btw: it was quite nice on setup - adjusting the Lights on Stage, switch them by staying 'on the spot' with my Phone -
connected via ad-hoc wlan to the Laptop ... Webinterface is REALLY GREAT & saved much ways to walk at a really hot afternoon!
If only I had a merger for secure, I would have likely tried QLC+ at showcase this time...

Well, I'm a live performer with affinities to Blues and Rock and therefore I need a reliable capability to flash scenes - quick and dirty
for short breaks in chasers or the use of blinders, ACLs, lasers etc. for a moment - and as possible sometimes with Kill(Solo) effect to blackout the rest.
So, after one year again my 2c to this flash and priority theme, feel free to move it elsewhere if it doesn't fit in here.
(http://sourceforge.net/p/qlcplus/discus ... #fe18/d860)
IMO, Flash has always appearence and a disappearence, so independent of LTP or HTP, always return to the backgrounded state, as though no flash had happened in between - Otherwise its a switch...
Having somewhere else a priority setting should act the same way.

I think we're on a good way and LTP is mostly done now. I've observed an inconsistency:
if an involved channel has value 0 before flash, it persists on the flashed value on release - until this channel is involved again with another value (than 0?)
else it seems always to return now like I expect and want to have it.

HTP: Stictly forced to LTP I must not "enable all channels in current fixture" in the Scene setup - only those, I intend to overlay.
Thats just poor by the need of more attention in programming, but works fine like on Scan Operator.
Maybe the better would be a checkbox "Force LTP" in Button Properties Dialog, nearby the Option Flash function...

Submastering flash buttons would be nice, too.

Maybe Simple Desk should have higher priority than Flash for special fixes & emergency?

[bestdani]

The submaster workaround works very well so far for scenes for instance and I'm rather satisfied with it, but not completely, since I think there's no chance to overlay a rgb matrix effect for instance over a running function.

In the end I would like to have it like this:
RGB fixtures color is for instance set to #0000ff, when I start a #ffff00 rgb matrix effect for instance the resulting color of the affected rgb fixture would be fade to #ffffff and back to #0000ff for HTP merging. When the rgb matrix effect is set to a priority higher than the base scene it would fade from #0000ff to #ffff00 and back to #0000ff.

I think it would be fine to have HTP merging within one priority layer and a kind of "highest layer takes priority" merging that allows to do this.

Greetings,
Daniel

[pengumaniac]

ah, loopback submaster - nice to know...

Daniel, I think you hit the point, I intend with "Force LTP"

Suggestion - just let's have another cheap test scenario:

ltp-htp_test1.qxw

(20.25 KiB) Downloaded 96 times

2x RGB @Dmx 1&5. (Perhaps 2x Single Dimmer patched in to satisfy "RGB+Dim cans", set on Simple Desk to 255 and forget them)

1st RGB is completely forced to LTP
2nd is normal HTP

• have a look at the difference between "add" and "solo" functions
• Just feel free right now, play around, watch and compare with your instincts
• I don't want to say here & now pertly, whats currently already fine or cra- ehm. bad in my eyes and I still have to attempt any further...

--
have a nice weekend

I think I can dream
I think I can think
but I'm currently lost somewhere between MasterTimer::timerTick(), doc and queues and ..., because my c++ and qt is so worse against my php

My ENV:
I. Gentoo, LXDE Dualscreen, QT4, QLC+ 4.9.1-common "homebrewed", so I have all precompiled and little changes could be testet w/o git (didn't use it already, but I'm flexible)
II. OSL 13.2, ditto + kdevelop, QT-Designer&Creator
(III. RPi 1 Model B)

I'd be glad If someone inserts patches, time is running out ...
PN always welcome for non overts

never mind the bollocks

[pengumaniac]

David, plugz, janos what about you? Would anyone of you have some minutes left?
Massimo told he's drowning in bells & whistle-wishes and justifications why not...

My intention is again to improve Flash functionalities.

Flash Button 2nd option, PLEASE

• A "temporary" LTP - (no different behavior to HTP) just simply overlay.
• At first w/o fade. Bypass. Shortcut. Done.
• Flash Must/Should not have higher Priority than fixes made on Simple Desk,
• but everytime higher than whole's VC Outputs

Load my test-project and

1. Tap speed ~3s
   (btw: please hilight wether h....ms is active to +,- and dial !)
2. tap some Fade to 3s,too
3. Start "add rgb" or "solo rgb" Chase

With Hotkey 1...3 I'll expect a true exclusive solo on #1 to the left, no
additional fades in other channels!

Funnily, if I make it steady enough, I can make fall down the stuck sliders through knock on the right
place, missing only some animated bounce - sry, don't be personal aggrieved!!!

Reduced SM: flickers a bit, too...

All in all, that tweak switch HTP to LTP isn't sympathic to me...
spoken with Espi together ~37 years real time, live mixing practice approved experience
vs.
"ever lasting LTP" theorisms and questions like "should we have
a second function on release flash" or more complex handlings
(http://sourceforge.net/p/qlcplus/discus ... 1539/#a39b )

- HTP is always just Brightness (Dimmer itensity), Sub-Masterable
- Decision wether LTP is fadeable or has switching ranges should be perhaps
more precise in fixtures definition, dead zones => one Level less in Value selection

but maybe need nonetheless "Trig-Point" to declare, WHERE on 0...100% "fadeway" to
switch...

Just tell me if thats priority=too low, I can wait...