Different sequences in chasers, but only one should run ???

[Alhifi]

Hi QLC+-professionals,

actually I am a little bit confused using different chasers with scenes for one unit.

As an example, I have diffenrent chasers for a moving head:
The first moves the head up and down.
The second turns the head from left to right and back.
The third does something else (it's only an example).

On the virtual console (I hope you know what I mean, I use the german GUI) I create a new "solo frame" because I understand the functionality that within a solo frame only one thing can run at the same time, am I right?
In the solo frame I created 3 cue-lists from the chasers above, every one uses the ArtNet (and VirtualDJ for Beat-Input) to go to the next cue point, I think it works.

My problem is, that of course all 3 chasers starts running while the beats are coming through the ArtNet. How can I only use one of then and then, after clicking a button or whatelse, the chanser changes to another one, it starts with No. 1, I push, then is No. 3 running, I push another one to go back to No. 1 and then a third button to change to No. 2.

Am I on the right way as described above or am i completely wrong?

Bye
Roger

[Alhifi]

Hi again,

can no one help or was the question misunderstood?

So I try again:



I have 3 different chasers with scenes of a "LED-spider", they define the 3 bars. Every chaser is pushed to the next step by the same ArtNet channel ("every beat"). When I start QLC (change the mode to operation) and the signal cames through ArtNet, every of the three chasers react and goes to the next step. What must I change that only one chaser will run and I can change between them during operation.

Bye
Roger

[yokosuna]

Actualy, a disabled frame prevents a cue from receiving triggers.
Thus said, put each cue in a seperate frame and assign each frames´
activation button to a shortcut or external trigger.
Unfortunately, the activation button always acts as a toggle.
So you cannot enable one frame by simultaneously disable the other one.
(at least, I´m not aware of any solution)
Maybe some day we will be able to activate/deactivate a frame by an absolut
value instead of toggeling it on/off for every change of a channel ....

[GGGss]

Dont use multiple chasers inside a solo frame (using the same cues) this will cause havoc.
While you want to be in control of which chaser is running all put them inside their own frame. Now, through a loopback channel you can bind buttons inside a solo frame to dis-/enable the frame with the chaser inside.

Your step problem -> check your (Artnet) input profile for 'add additional click' (or something called like that) It could be that the flank of a changing Artnet signal triggers twice.

Now the chasers should advance to your Artnet input, and with the solo buttons you can choose which chaser is in control...

[yokosuna]

Unfortunately, the activation button always acts as a toggle.
So you cannot enable one frame by simultaneously disable the other one.
(at least, I´m not aware of any solution)

GGGss, this problem persist ... or do you have a solution ?
The only way to come around this, is to bind the frame´s activation to a fixed value:
say: "0" == frame is disabled, "171" == frame is enabled.
But that seems not to be supported by QLC at the moment

[GGGss]

3 frames asks for 3 loopback channels ...
This should work...
you have a cue with the 3 loopback channels inside - say 'enable 1'. Activating that cue will enable 1 and disables 2 and 3... and so on.
How you trigger the cue's (by VC buttons in a solo?) is out of scope now.

[yokosuna]

GGGss,

nop, this does not solve the problem.
Since the "activation button" reacts to "value change", the behaviour is based on the
current state of the activation.
This means, if the frame is activated and the value of the attached loopback channel
goes to - say - 255, the frame is - unintentionaly - disabled.
Same happens vice versa.
This is due the fact, that the "activation button" isn´t related to a specific value but to a
value change, no matter in which direction.
Maybe I´m missing something here...

PS: found an issue at this occasion: when the trigger channel for the "activation button" goes - say- from "zero" to "one",
the state changes. Whereas if the value goes from "one" to "zero" - nothing happens.
This is not he case when the value goes from "one" to "two" an back to "one"....
Version is 4.2.12

[yokosuna]

OMG.

Now that I´ve found that issue with "zero" and "one" it works like a charm !
One have to ensure that the initial value of the loopback channels will be "one"
and not reset them to "zero" on any circumstances !

I´ve attached a sample project:

Radiobuttons.qxw

(7.34 KiB) Downloaded 34 times

PS: One can set a channel modifierer too for "zero" becoming "one"

[Alhifi]

Ok, actually I did not really unterstand what you are talking about, BUT the word "frame" has put me into the rigt direction, actually I'm still do the first tests and it will be "learning by doing", but now I have understand what the meaning of a frame is.

Actually after a first fast configuration I can choose between the 3 chasers, only one will run and I can activate or change them from my APC Mini, also the buttons there are as an example green and green flashing while active ... what a good day!

Thank you very much, I will try the other hints here later on too!

Bye
Roger

[SPS]

Thanks for the explanations.
Two questions regarding the Radiobutton example:
1) What is the purpose of the loopback input in universe 1?
2) When do you use the script?

Thanks for your reply
Paul

[Deece]

I like the solution using 1-255, not 0-255, for channel values.
I've been wodering how to do 'true' radio buttons for while. Thanks for the idea.

I've slightly modified your workspace so the script (not reset scene) is autorun on workspace load.
This ensures Frame Enables are set OFF ,ie disabled, at the start.
Using a scene means the scene is running all the time. Hit STOP all functions, stops the Scene and stops the radio buttons working as intended.

I've added Channel modifers as well.
The .qxmt file needs to be added to your Modifiertemplates.
Then check that Fixtures have channel modifier set to 'Linear 1-255'

Good fix. Ty.