Absolute override (or pages priority)

DJLadonin · Thu Jan 10, 2019 12:35 pm

Hello everybody.
Sometimes ago I started thread of "pages priority"
The idea was: I wanted to have "master page" which have priority (HTP and LTP) for virtual console.
Example: I have different fixtures, running with different params (color, gobo, etc) and different moving effects (relative circle, etc). I need "FULLON" scene, started with one button (on my NanoControl), which can override ALL arguments (color, gobo, beam, position) and, when released, returns all my working stuff: different fixtures, running with different params (color, gobo, etc) and different moving effects (relative circle, etc). Can it be done with Simple Desk? Or, maybe, will do middle layer (virtual console <-middle layer<-simple desk)

GGGss · Fri Jan 11, 2019 2:13 pm

Did you have a try with the feedback channels?
you could use a feedback channel to dis-enable your frames so everything inside is supposed to stop?
every sub frame is linked to the feedback channel???

Just a tought

DJLadonin · Fri Jan 11, 2019 5:07 pm

GGGss wrote: ↑Fri Jan 11, 2019 2:13 pm Did you have a try with the feedback channels?
you could use a feedback channel to dis-enable your frames so everything inside is supposed to stop?
every sub frame is linked to the feedback channel???

Just a tought

Yes, I know about loopback channels and using it for Strobe. But this is the way for static scenes, not for dynamic.
In my show positions and effects are in different subframe then colors, gobos, beam. Example: 6 Wash fixtures with changing colors (using color chase) are moving pan/tilt (using position scene and relative movement effect). I need WhiteStrobe, so I have scene (color white) with loopback (which have effect for subframe with Wash color), so in result I have WhiteStrobe Wash fixtures WITH MOVING pan/tilt (using position scene and relative movement effect).
Maybe, there are another way with loopbacks to do this. BTW, implementing this "middle layer" can solve another problem of "palletes", which is discussed in another post here.

DJLadonin · Fri Jan 11, 2019 10:29 pm

Loopback can be used for static arguments (color, gobo, beam) but no for positions (yes, LTP)
Here is test show for 6 Wash. Static arguments (like shutter in "!-W_WhiteSTR_Loopback") is OK, but when you try to turn on "!!-FULLON-loopback" during disco (pan/tilt moving effect) OOPS!

DJLadonin · Fri Jan 11, 2019 10:31 pm

OOPS!
Here is file

GGGss · Sat Jan 12, 2019 1:25 pm

I opened your project (lacking the fixture)

first thing I saw: you are using the loopback (yes the feedback was wrong sorry) capability wrong here.

Through loopback you can also en- disable functionalities in QLC+: triggering frames, cue lists, the like ...
You could have f.i. 2 EFX in place and through a loopback functionality have on or two or none selected ...
So a cue list could trigger 2 EFX by sending loopback information.
Project in annex not perfect - but an example

DJLadonin · Sat Jan 12, 2019 5:57 pm

GGGss wrote: ↑Sat Jan 12, 2019 1:25 pm I opened your project (lacking the fixture)

first thing I saw: you are using the loopback (yes the feedback was wrong sorry) capability wrong here.

Through loopback you can also en- disable functionalities in QLC+: triggering frames, cue lists, the like ...
You could have f.i. 2 EFX in place and through a loopback functionality have on or two or none selected ...
So a cue list could trigger 2 EFX by sending loopback information.
Project in annex not perfect - but an example

Here is fixture library.
I tested your example, but cannot understand, how it can help me in my problem?