Page 1 of 1
Button to activate next scene
Posted: Sun Sep 27, 2015 8:50 am
by Maarten.Provo
Hello
I have a moving head for which I have programmed a scene for every Gobo. I would like to have a button to switch Gobo/Scene. I thought, I've I put all the scenes in a chase and then link a button to that chase ... But the button just has start/stop function.
How do I accomplish this?
Regards
Re: Button to activate next scene
Posted: Sun Sep 27, 2015 2:55 pm
by nedmech
You should be able to do this by using a Cue List control for the Chaser instead of just a Button. With the Cue List control, you can assign Previous and Next buttons as well as the Start/Stop button. If you assign just the Next button, by default it will start playing the Chaser, then start stepping thru the scenes. Just make sure you set the Chaser to have an Infinite hold time or it will start stepping thru the scenes on its own.
Re: Button to activate next scene
Posted: Tue Sep 29, 2015 1:14 pm
by Maarten.Provo
I think I have that one now ... With the list of different steps in the chase the fader, play, prev and next button ... But I was looking for someway to get just a Next button in my virtual console, no the entire thing since it's to big.
Re: Button to activate next scene
Posted: Tue Sep 29, 2015 2:34 pm
by forresthopkinsa
Well, put the Cue List inside a frame, and collapse the frame (or maybe you could enable Headers on your cue list itself, and collapse that).
Either way, I'm 75% sure that the assigned hotkeys will still be functional even if their target is not visible.
Re: Button to activate next scene
Posted: Tue Sep 29, 2015 2:46 pm
by nedmech
forresthopkinsa wrote:Well, put the Cue List inside a frame, and collapse the frame (or maybe you could enable Headers on your cue list itself, and collapse that).
Either way, I'm 75% sure that the assigned hotkeys will still be functional even if their target is not visible.
You beat me to it. That's half of what I was going to suggest. Putting it in a collapsed frame saves you the screen space. If you still want another button to interact with via mouse clicks, you can set up loopbacks to use as Prev/Next triggers, then just set up buttons for those loopbacks. I've attached a workspace as an example.