Q Light Controller+

Is it posiible to use fader to controll cue list?
Example: If fader moved from 1% to 10 % - Cue 1
11%-20% - activates cue 2 and etc.

Here is a video on Martin console. It's tutorial, so for the effect skip to ± 10:15.
https://youtu.be/tx4jznXS6e4?t=10m15s

Uhmm.. interesting...
But I'm wondering how many million of cases we should handle to avoid dead ends.

For example if you control that fader with an external controller (so on a 0-255 range) and the cue list has more than 256 cues, what should happen ?

Ohh.. and maybe I'm wrong talking about cue list, maybe it would be easier to use scenes. Or we can add anything we have (like in sound widget) to selected ranges of fader.

In my case it would be enough to control list of 5 or 10 cues. (Or scenes) we always can have some smart limitations.
So 255 / 5 = 51 so first cue/or scene 1-51, second 52 - 102. end etc.
If you let add more cues, for example 20. It would be hard to chose right cue with fader, it will be so sensitive, because swithing to next cue step will be 12,5. So it 's hard to control with console which have short faders.
So maybe you can add this wish to your long To DO list?


In my mind it should look like this:
when we add fader to VC, we can chose it's mode from level, playback, sub-master. So here can be new mode, or everything added to palyback mode.
And simply five fields to assign function to that range.
1-51 = Add/remove Function 1
52-102 = Add/remove Function 2
103-153 = Add/remove Function 3
154- 204 = Add/remove Function 4
205-255 = Add/remove Function 5

Adding 5 fixed fields doesn't sound like a good idea to me.
If this is going to be added, it must be generic and flexible.

One question though.
Let's say you have 5 scenes controlled by the fader. If you connect the fader to an external controller and its starting value is 0, when you want to reach scene 4, you need to go through scene 1, 2 and 3.
This doesn't make much sense to me.

How would you cope with that ?

Yes, that's basic idea, that you need go throught 1,2,3 scenes to reach scene 4. If you need skip 1,2,3 scenes than user should use other methods than this.
Example with moving heads and strobe on fixtures:
1st scene - moving heads aligned at line moved to stage front line
2nd scene - moving heads aligned at line moved to audience position
3 scene - moving heads aligned at line moved to stage blinder position
4 scene - moving heads aligned at line moved to sky position
5 scene -moving heads aligned at line moved to stage front line + strobe

So in concert if I'm not familiar with song, i can easily control effets whitch related to audience. And if song suddenly changes to fast drums or something i can move my fader fast to use strobo effect (scene 5).

Another example would be for moving heads which are on 5 truss.
1scene - 1 truss fixtures aligned at line moved to stage front line
2 scene - 1 truss fixtures audience possition, 2 truss fixtures aligned at line moved to stage front line
3 cene - 1 truss fixtures sky possition, 2 truss fixtures audience possition, 3 truss fixtures goes to stage front line


and etc. (like in video which i mentioned). So here I can control fast and easy how many moving heads will go to the crowd, and how many will stay at the stage.

It's harder to explain than i tought. but that is usefull for positions, strobo effect, color crossfades end etc. If you have some time, you should wath all video to understand how it works, maybe it will be easier to understand

OK, I've watched the video and I got it now.

I think, in terms of code, it should not be too hard to implement on Cue Lists. I would go that way instead of more options on a generic VC Slider.

Funny that the guy in the video says that it's "a Q Blender unique feature"....not for much longer dude !

mcallegari wrote:OK, I've watched the video and I got it now.

I think, in terms of code, it should not be too hard to implement on Cue Lists. I would go that way instead of more options on a generic VC Slider.

Funny that the guy in the video says that it's "a Q Blender unique feature"....not for much longer dude !

That's a great news, thank you

In the video the blending from one queue point to the next is very nice.

OddSocks wrote:In the video the blending from one queue point to the next is very nice.

What do you mean ?
Oh and Tim, please help me to find a proper word for this functionality. How about if I call this "Slider in sweep mode" ?

step fader

darth fader

No ?
Darth Fader would be the best though

mcallegari wrote:

OddSocks wrote:In the video the blending from one queue point to the next is very nice.

What do you mean ?
Oh and Tim, please help me to find a proper word for this functionality. How about if I call this "Slider in sweep mode" ?

I think I mean the cross fade from one stage to the next.

"Darth fader" +1


Maybe "Step fader" ?

maybe a direct crossfader w/ a scene on each end (cuelist needed?)
subdivide the differences to faderway - other timings ignoring, especially IMO the "taken into consideration" FadeIn-Hold-FadeOut, suppress.
I remember that fine to Rotate Gobos on left stage cw / right stage ccw on various speeds - but I can't predict accordion effects to pan&tilt

btw - ma scanco: activate one selective memory (=button) -> switch into crossfade mode -> hit another button and fade in between. that was knowledge builded in .... 1992

addendum:
I don't want to brag too much with that ma's - nowadays 16.000 bucks "also for school and educational usage" is quite hefty...
but no thinkings of "black=red & plus=minus" needed, and if you cannot domesticate him right, you're the faulty - sure!
Biggest of that direction I've had (16 heads, mh660 & ypoc-washers) was ......here:
http://diginights.com/partypics/2010-06 ... pic/990034

The accordion effect: theoretical AFAICT, I need here 8 steps (scenes) "glued" together to one sequence, to move all up:

1st "head-row" alow..top (hold values), then 2nd head alow..top, a.s.o.

At manual I do 5 zig-zag pull-pushes w/ a knob in fingers (IMO not quite fine on touchscreens...)
but also possible, to set a fadetime - by another fader - over that all and hit "Go"

I've actually no plan how to transfer such better into code,
so back to our cuelist again - the "play" is your practice part, but I'd enjoy a "Darth Fadering" qxw, too...

Hi all,

How about this -
viewtopic.php?f=12&t=8805#p38329

Regards

Alex

Tested on Win7 64-Bit, QLC+ 4.10.0_TEST-20150925

I've got 10 steps in my Chaser, and it works great for scanning between all the steps with the fader. Except that once I reach about 250 on the slider, it rolls back around from step 10 to step 1 in the chaser.

One other comment - would it be possible to add an invert option for the slider? It's a little non-intuitive having the slider and the chaser steps moving in opposite directions.

nedmech wrote:Tested on Win7 64-Bit, QLC+ 4.10.0_TEST-20150925

Thanks Nathan !

nedmech wrote:I've got 10 steps in my Chaser, and it works great for scanning between all the steps with the fader. Except that once I reach about 250 on the slider, it rolls back around from step 10 to step 1 in the chaser.

Might be an approximation glitch. I'm gonna look into that asap.

nedmech wrote:One other comment - would it be possible to add an invert option for the slider? It's a little non-intuitive having the slider and the chaser steps moving in opposite directions.

I noticed that too. Actually Chasers can be run in reverse order, but I would say the "steps" fader should be inverted by default.

nedmech wrote:I've got 10 steps in my Chaser, and it works great for scanning between all the steps with the fader. Except that once I reach about 250 on the slider, it rolls back around from step 10 to step 1 in the chaser.
One other comment - would it be possible to add an invert option for the slider? It's a little non-intuitive having the slider and the chaser steps moving in opposite directions.

Should be all fixed now. The step fader is now inverted by default.
At the moment I don't have time to build a Windows version, so if you want to check the change, please build from sources yourself.

Pull and rebuilt on Linux Mint KDE 17.2. Everything looks and runs great for this feature now. Thanks, Massimo!

Tank you for this feature, it is so freaking awesome