Moving head and dimming

Ask a generic question about the usage of QLC+, not related to a particular operating system
Post Reply
Franzi
Posts: 32
Joined: Sun Nov 03, 2019 3:35 pm
Real Name: Franziskus Loibl

Dear friends,

I need some help. I don´t know how to make a solution to this with 10 moving heads:
- set all 10 moving heads to a start position
- turn light on for the first fixture
- move the first on to a new position with a efx, line2
- while the first made 10% of its way
- turn light on for the second fixture
- move the second on to a new position with a efx, line2
...
- when moving head 1 reaches its end position, turn fixtures light off
- return moving head 1 to its start position
- when moving head 2 reaches its position, turn fixtures light off
- return moving head 2 to its start position
....
- loop

_AND_ controll the speed of the efx through a speed dial widget.

Thank you.
User avatar
GGGss
Posts: 3052
Joined: Mon Sep 12, 2016 7:15 pm
Location: Belgium
Real Name: Fredje Gallon

It all comes down to timing.

Stating: "when it comes at it's end position it should..." is unknown because it depends on the internal speed of the fixture.
DMX is not working in both ways - so QLC+ does not know where the head is at.
And since you are using EFX Line2 - this is a straight change of position 1 to 2 <- this you can substitute with 2 cues.

So looking at what you want you can simply use a chaser with all your cues inside. The common hold time then can be changed by the Speed Dial widget.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
Franzi
Posts: 32
Joined: Sun Nov 03, 2019 3:35 pm
Real Name: Franziskus Loibl

Greetings!

> because it depends on the internal speed of the fixture.
Yes, and therefore I experimented with dummy steps with a duration approximating the speed of the moving heads.
This does not work since, using them in the same cue, it "holds" the same amount of time that the original efx runs...and
using diffent hold time, the chaser cannot be set to a speed dial anymore. So no solution, i think.
I was thinking to use a loopback to advance to the next step an using infinit hold time, but I think could work only in
sharp situations.

> And since you are using EFX Line2 - this is a straight change of position 1 to 2
I have to admit that "Line2" is my first try. I think The problems becomes more compex with complexer movements.
And I´m not aware of controlling the time between transition other than using a efx. Otherwise, the moving head will
go as far as he can :-(

> this you can substitute with 2 cues.
Don´t understand your proposal. My approach was: use a collection to turn on lights and start the efx. Then
I placed this one time movement in a endless chaser. This, because I want to combine more movements into one chaser.
The the chaser restarts (or starts a new efx) - and thus the moving heads are on wrong position, namely in between the
return to their start positions.

I also tried including dummy loopback dimmers that fall back to zero when EFX ends and
used them to trigger the real dimmers of the fixtures throught scences on the virtual console as "flash" buttons.
That works for the case that I want to turn off every fixture immediately.
But it fails using more complex functions, for example, some kind of "waving" through the heads.

> So looking at what you want you can simply use a chaser with all your cues inside. The common hold time then can be changed by the Speed Dial widget.
I really dont´t know what you mean by "use a chaser with all your cues inside".
And "The common hold time then can be changed by the Speed Dial widget." does this mean the hold time of the chaser and/or the efx itself ?

I know it's a lot to ask, but sometimes a picture says more than a thousand words.
Sp perhaps you can post a screenshot ?

Thank you very much.
Franzi
Posts: 32
Joined: Sun Nov 03, 2019 3:35 pm
Real Name: Franziskus Loibl

Well, I think I got it (at least, portions of it).
I´m now using loopback dimmer as the last step in a chaser to force a "next"
to a cue in the virtual console.
For me it is a little bit akward to use a "visual" element to perform "programming" task but
better a bad solution than none at all.

Thank you.
Post Reply