Button to activate next scene

Archive of the non-categorized posts related to the QLC+ technical support.
Please do not create new threads here, instead, use the categories above !
Post Reply
Maarten.Provo
Posts: 14
Joined: Thu Aug 06, 2015 1:48 pm
Location: Tongeren, Belgium
Real Name: Maarten Provo
Contact:

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
Maarten Provo is a professional allround dj/entertainer specializing in weddings and corporate events. More info on www.maartenprovo.be .
User avatar
nedmech
Posts: 83
Joined: Sat Jun 20, 2015 12:39 am
Real Name: Nathan Durnan

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.
Maarten.Provo
Posts: 14
Joined: Thu Aug 06, 2015 1:48 pm
Location: Tongeren, Belgium
Real Name: Maarten Provo
Contact:

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.
Maarten Provo is a professional allround dj/entertainer specializing in weddings and corporate events. More info on www.maartenprovo.be .
User avatar
forresthopkinsa
Posts: 22
Joined: Tue Sep 29, 2015 3:23 am
Real Name:

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.
Production Director for Coastline Church NW

Software Engineer at AWS S3
User avatar
nedmech
Posts: 83
Joined: Sat Jun 20, 2015 12:39 am
Real Name: Nathan Durnan

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.
Attachments
chaser_loopback_buttons.qxw
(6 KiB) Downloaded 82 times
Post Reply