Here is what I am trying to do in a chaser
Scene 1 - set all 6 lights to an assigned color
Scene 2 - Set only 2 of the 6 lights to different colors without having to program the other lights
Scene 3 - repeat scene 1 - back to previous setting
The idea is that I want to make relative changes to a lighting scene without repeat programming with the current settings of the fixtures that are not changing.
When I tired this the other 4 lights turned off as they where not part of scene 2
Any advice would be appreciated as I am still learning the program
how to add lighting changes to a sub-set of lights
- GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
Did you try this in 'live' mode?
While you are editing cue's the current value of the cue are outputted. Once you go live -only- the current cue channels with values are sent.
But if say cue 1 has only white (R G B : 255) and cue 2 has f.i. (R 120, G 120, B 255) you will not see any changes (!!)
Why you ask? Well because of HTP (the highest value wins the contest between cue 1 and 2)
You could go in LTP mode - but be aware that this demands an other working approach.
While you are editing cue's the current value of the cue are outputted. Once you go live -only- the current cue channels with values are sent.
But if say cue 1 has only white (R G B : 255) and cue 2 has f.i. (R 120, G 120, B 255) you will not see any changes (!!)
Why you ask? Well because of HTP (the highest value wins the contest between cue 1 and 2)
You could go in LTP mode - but be aware that this demands an other working approach.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
-
- Posts: 204
- Joined: Tue Mar 22, 2016 9:07 am
- Real Name:
@CLS, no way, unless you change your channels to LTP, as proposed.
Or, you take the hard way. Therfore you have to place a override slider in level mode for
each channel of each fixture you want to override and controls the slider throught loopback
channels which can actualy be placed in chasers...
For 6 fixtures with 3 channels each, you will end up with 18 sliders...
Or, you take the hard way. Therfore you have to place a override slider in level mode for
each channel of each fixture you want to override and controls the slider throught loopback
channels which can actualy be placed in chasers...
For 6 fixtures with 3 channels each, you will end up with 18 sliders...
-
- Posts: 4
- Joined: Sat Mar 16, 2019 1:33 am
- Real Name: Ken Cardita
Guys thanks for the pointers ...
I really can't use Live mode - I did not explain my use case - so here we go ..
I am playing guitar in my band and when I change sounds during songs I can send put MIDI CC/PC commands.
Each MIDI PC is set up in Qlc+ to trigger a set scene or a chaser that are all contained in a solo panel... this is how I will control the light show- I also have a dedicated button on my midi controller to toggle blackout
So for example I am switching scenes for red and blue between the songs verses and choruses
When its time for a guitar solo I want to have 1 or 2 lights change to a soloist spot light (white or yellow) - it is this relative change I want to make using only one Midi PC trigger regardless of what the current scene is .
I want to do this for 30 songs and not burn up 30 Midi PCs one for each song-- I just want to have a single "additive" scene for each soloist to reuse for our entire show
is there a clever way to do this ? maybe using a script to read current values and grammatically program the scene on the fly ?
(note: I have not looked into QLC scripts - but I have many years of software programming experience from yesteryear.
OR am I having to hard code all of my scenes for every light all the time ?
thanks again
I really can't use Live mode - I did not explain my use case - so here we go ..
I am playing guitar in my band and when I change sounds during songs I can send put MIDI CC/PC commands.
Each MIDI PC is set up in Qlc+ to trigger a set scene or a chaser that are all contained in a solo panel... this is how I will control the light show- I also have a dedicated button on my midi controller to toggle blackout
So for example I am switching scenes for red and blue between the songs verses and choruses
When its time for a guitar solo I want to have 1 or 2 lights change to a soloist spot light (white or yellow) - it is this relative change I want to make using only one Midi PC trigger regardless of what the current scene is .
I want to do this for 30 songs and not burn up 30 Midi PCs one for each song-- I just want to have a single "additive" scene for each soloist to reuse for our entire show
is there a clever way to do this ? maybe using a script to read current values and grammatically program the scene on the fly ?
(note: I have not looked into QLC scripts - but I have many years of software programming experience from yesteryear.
OR am I having to hard code all of my scenes for every light all the time ?
thanks again
- edogawa
- Posts: 630
- Joined: Thu May 07, 2015 10:34 am
- Real Name: Edgar Aichinger
If the lights really have to go brighter all the time it's rather easy (If I understood correctly)...
Build your cuelist with the plain song scenes, no extras, but create some more scenes with just the brighter channels for the soloist. Then add a VC button for each of these "solo" scenes. Add in/out fade times as you like and map some dedicated pads from your controller to these VC widgets...
Build your cuelist with the plain song scenes, no extras, but create some more scenes with just the brighter channels for the soloist. Then add a VC button for each of these "solo" scenes. Add in/out fade times as you like and map some dedicated pads from your controller to these VC widgets...
-
- Posts: 4
- Joined: Sat Mar 16, 2019 1:33 am
- Real Name: Ken Cardita
@edogawa -- That did the trick !
A very simple solution to do exactly what I described. I created scenes for solos spots (color + intensity) for each performer and just added VC buttons (trigggered via MIDI) outside of my SOLO panels that contain all of my cue list, chasers ( verse , chorus of each song) and it worked just as I needed . The only thing I had to add was for improvised solos where I don't know when it will end I have to toggle off the SOLO scene when leaving my solo sound back to the verse ...
Thanks for your hep - much appreciated !
A very simple solution to do exactly what I described. I created scenes for solos spots (color + intensity) for each performer and just added VC buttons (trigggered via MIDI) outside of my SOLO panels that contain all of my cue list, chasers ( verse , chorus of each song) and it worked just as I needed . The only thing I had to add was for improvised solos where I don't know when it will end I have to toggle off the SOLO scene when leaving my solo sound back to the verse ...
Thanks for your hep - much appreciated !
-
- Posts: 4
- Joined: Sat Mar 16, 2019 1:33 am
- Real Name: Ken Cardita
@yokosuna - I have attached my file for you to check out
- Attachments
-
- spotlight demo.qxw
- demo of relative spotlight
- (10.86 KiB) Downloaded 31 times
-
- Posts: 204
- Joined: Tue Mar 22, 2016 9:07 am
- Real Name:
Ok - I think I see what you wanted to achive and your were succesfull.
As long as you did´nt want other "color" than white as your hightlight.
Because "white" set all RGB values to their "highest" value and this works as expected for HTP channels.
Easy enought, try to set "red" as your spotlight while the others remain green: you will end
up with yellow as your spotlight. That's the stupid thing about HTP. And sadly it ´does change your
spotlite to a random color, if you are running one of your chasers: "Grid wave" or "Rainbow linear".
And that´s why GGGss an me were talking about LTP in the first place. But this even doesn´t solve
your problem if you are running chasers or rgb fx at all.
As long as you did´nt want other "color" than white as your hightlight.
Because "white" set all RGB values to their "highest" value and this works as expected for HTP channels.
Easy enought, try to set "red" as your spotlight while the others remain green: you will end
up with yellow as your spotlight. That's the stupid thing about HTP. And sadly it ´does change your
spotlite to a random color, if you are running one of your chasers: "Grid wave" or "Rainbow linear".
And that´s why GGGss an me were talking about LTP in the first place. But this even doesn´t solve
your problem if you are running chasers or rgb fx at all.
-
- Posts: 204
- Joined: Tue Mar 22, 2016 9:07 am
- Real Name:
I thought about a solution and came up with the project as in the attachement.
Explanation:
- One has to use a "shadow" fixture corresponding to the "physical" fixture you want to override.
- This "shadow" has to be in the loopback universe.
- Setup a slider with "override" for every channel you want to override in the "real" fixture and use the "real"
channels at the "level mode"
- Use the corresponding channels of the "shadow" device as the input for the overriding slider
- Then you can create a scene where you set the "shadow" values to the desired values.
Now, here it becomes tricky:
- Use a sepearte "dimmer" in the loopback universe to reset the "overrider" slider.
- But this channel must use a channel modifier to act as an inverter
- Use this "reset scene" at each "override slider" to reset the override functionality.
- Create a scene to set this "reset" dimmer to zero (!) which - in turn - sets it to 255 (!) in reality.
- Create a collection where you place the "reset" scene and the "any color you like" scene.
- Add a button in the VC to activate this "collection"
Puh ! There you go... HTH
Explanation:
- One has to use a "shadow" fixture corresponding to the "physical" fixture you want to override.
- This "shadow" has to be in the loopback universe.
- Setup a slider with "override" for every channel you want to override in the "real" fixture and use the "real"
channels at the "level mode"
- Use the corresponding channels of the "shadow" device as the input for the overriding slider
- Then you can create a scene where you set the "shadow" values to the desired values.
Now, here it becomes tricky:
- Use a sepearte "dimmer" in the loopback universe to reset the "overrider" slider.
- But this channel must use a channel modifier to act as an inverter
- Use this "reset scene" at each "override slider" to reset the override functionality.
- Create a scene to set this "reset" dimmer to zero (!) which - in turn - sets it to 255 (!) in reality.
- Create a collection where you place the "reset" scene and the "any color you like" scene.
- Add a button in the VC to activate this "collection"
Puh ! There you go... HTH
- Attachments
-
- spotlight demo.qxw
- (14.68 KiB) Downloaded 40 times