Hi,
I'm trying to recreate a theater style console where you have your channel faders at the top, and at the bottom some additional faders. You set a scene with your channel faders and can assign those values to one of the bottom faders.
Similar to the playback sliders in the simple desk section.
Can i achieve this in the virtual desk?
Regards Markus
Create Theater Style Virtual Console
-
Chris Laurie
Not as far as I know - you maybe able to simulate it with the simple desk but I never work in the simple desk so I can't say.
The question is, why would you want to do that?
Theatre operations in QLC+ is mainly done by creating all the necessary scenes and saving them under their own name.
Operation is then done in 3 ways - often combined:
A cue list, where you put the scenes in order and you move from one to the other. Fading can be programmed into the cue list on forward & backward buttons or manually faded using the crossfade functionality of the cue list widget.
Buttons - each scene sits on its own button and is called up as required - cross-fades have to be specified at the scene level.
Live fixtures - using click & go and other widgets as required, you control certain fixtures directly.
There is no need to manually prepare one scene with faders and then fade to it and then manually the next. Program once and execute faultlessly by using the scene.
The question is, why would you want to do that?
Theatre operations in QLC+ is mainly done by creating all the necessary scenes and saving them under their own name.
Operation is then done in 3 ways - often combined:
A cue list, where you put the scenes in order and you move from one to the other. Fading can be programmed into the cue list on forward & backward buttons or manually faded using the crossfade functionality of the cue list widget.
Buttons - each scene sits on its own button and is called up as required - cross-fades have to be specified at the scene level.
Live fixtures - using click & go and other widgets as required, you control certain fixtures directly.
There is no need to manually prepare one scene with faders and then fade to it and then manually the next. Program once and execute faultlessly by using the scene.
-
Markus Harthum
I actually don't need it for theatre use but for lighting movie sets.
And in traditional control units you can save the current fader positions to another fader.
For example i set all my top lights to a specific setting and then assign one fader to the toplights.
Like grouping them together.
I know it can be done using scenes, but the simple desk approach where you just hit the record button, would be better for my case.
And in traditional control units you can save the current fader positions to another fader.
For example i set all my top lights to a specific setting and then assign one fader to the toplights.
Like grouping them together.
I know it can be done using scenes, but the simple desk approach where you just hit the record button, would be better for my case.
-
Chris Laurie
What works for you, of course. You could achieve something similar using the Blind mode. This allows you to work on a scene without it being shown. This could of course be new scene. To display it, just take of the blind button. This could be erratic as you may flash scenes as you switch between blind and non-blind modes. I found it hard to know what scene is actually being output during blind mode.
Another alternative is to have two sets of identical controls, controlling all the fixtures with each set in its own frame with a sub-master. Take the sub of frame 1 down and the sub of frame 2 up. Then you can set up frame 1 again. The problem here is, there is no cross-fade of the subs - you either have a black-out between the fade out and the fade-in or you alternate between the 2 (tricky & messy). Having physical sliders (or TouchOSC) solves the simultaneous fade problem.
I handle this kind of scenario a little differently. I have a workspace that is basically one RGB click & go for every fixture with some more sliders and buttons per fixture to control other functionality. Then there is large button matrix of some prepared scenes and most of them is un-assigned.
Then, in live mode, I adjust the scene to be what the director (or myself) want. When it is right, I hit the save to button and assign it to one of the unused buttons. This also creates the underlying scene, so I can recall it instantly. This method does mean that as you are adjusting the fixtures the changes shows, but mostly I have found this works better with most of our directors.
Another alternative is to have two sets of identical controls, controlling all the fixtures with each set in its own frame with a sub-master. Take the sub of frame 1 down and the sub of frame 2 up. Then you can set up frame 1 again. The problem here is, there is no cross-fade of the subs - you either have a black-out between the fade out and the fade-in or you alternate between the 2 (tricky & messy). Having physical sliders (or TouchOSC) solves the simultaneous fade problem.
I handle this kind of scenario a little differently. I have a workspace that is basically one RGB click & go for every fixture with some more sliders and buttons per fixture to control other functionality. Then there is large button matrix of some prepared scenes and most of them is un-assigned.
Then, in live mode, I adjust the scene to be what the director (or myself) want. When it is right, I hit the save to button and assign it to one of the unused buttons. This also creates the underlying scene, so I can recall it instantly. This method does mean that as you are adjusting the fixtures the changes shows, but mostly I have found this works better with most of our directors.