How to run an EFX in a chaser exactly 4 times

[yokosuna]

Hi out there,

How to run an EFX in a chaser exactly 4 times...have no clue.

Thx.

[mcallegari]

With a Script.
startfunction - wait - stopfunction - startfunction - wait - stopfunction - etc..

[yokosuna]

thx for the answer.
I tried this already.
I came to the insight, this isn´t going to work since I don´t know how long the animation
will take to finish since the animation's hold time is linked to a speed dial widget
I asked a similar question two years ago.
Now I hoped that some progress in QLC+ made this possible.

[GGGss]

And what about when you create an 4 step chaser (master) and have this one fireing your other chaser (slave) by loopbacks?
In the slave chaser you need dummy loopback steps to advance the master, so when sequence in the slave finishes it fires the next step in the master...

[yokosuna]

For me it seems that the major problem is the missing possibilty to be "notified" when the EFX finish one cycle...
I see no solution to this unless QLC+ will implement this one day.
You´re proposal also needs to "estimate" the runtime of the fired chaser and that´s not what I´m looking for.
But maybe I´m missing something here...

[GGGss]

For me it seems that the major problem is the missing possibilty to be "notified" when the EFX finish one cycle...
I see no sulution to this unless QLC+ will implement this one day.
You´re proposal also needs to "estimate" the runtime of the fired chaser and that´s not what I´m looking for.
But maybe I´m missing something here...

Since you said the EFX timing is determined by a VC speed widget, one can assume that one cycle will follow this tempo - hence timing IS known...

[yokosuna]

Thx for pointing me in the right direction,

using an additional QUEUE for the chaser, this can be achieved

[yokosuna]

Sadly, this solution is not working well in conjunction with the speed dial widget and using the tap
This is, however, not connected to the solution in the first place.
By design or by error - tapping the tap-button restarts the animation so will be pretty useless in my scenario (

[yokosuna]

Well...found out that EVERY tap will reset a chaser
So this makes it completly useless in conjunction with an external midi or artnet trigger that gives me a beat
Unless someone shows me how to avoid this...

[yokosuna]

Code: Select all

Since you said the EFX timing is determined by a VC speed widget, one can assume that one cycle will follow this tempo - hence timing IS known...

This is only true if the count of steps will be 2, 4, 8 or 16

[GGGss]

Well...found out that EVERY tap will reset a chaser
So this makes it completly useless in conjunction with an external midi or artnet trigger that gives me a beat
Unless someone shows me how to avoid this...

Getting off topic now but you have to bind your external 'tap' signal only to the tap button in the speed VC.
Why your chaser is reset by external signal ?????
If I remember well there was once a case where this behaviour was noticed. Don't know anymore how we solved this.

[yokosuna]

Getting off topic now

Yep

you have to bind your external 'tap' signal only to the tap button in the speed VC.

It is

Why your chaser is reset by external signal ?????

That is the question here.
I found, that the behaviour has nothing to do with an external signal.
It happens EVERY TIME you hit the the tap button (well, nearly every time)
It does NOT happen when I change the timing with the dial or with the + or -

See attached project: when you start the queue, the rgb matrix is filled.
(nearly) every time you press the tap, the filling process is immediately stopped and
begins from start ...watch with dmx monitor

Thx.

Fehler Tap.qxw

(5.03 KiB) Downloaded 28 times

[yokosuna]

Any news on this? From my point of view it is a bug, but that is only my opinion. Others might think it's a feature.