[Updated for QLab 4.1 16 JUL 17]
Sometimes we may wish to hijack the space bar so that when we use it to GO we can execute some other actions in addition to the normal GO command. This might include logging a timestamp for the go, or some custom cue list behavior. In this example, we are going to create a behavior that skips disarmed cues in a simple linear cue list.
Here it is in action:
How it works:
It’s worth noting that in anything other than the most simple workspaces there may be similar cue structures that can be programmed where the cue list may not behave quite as you expect or want it to, particularly with auto continues and auto follows and complex groups.
You can also explore a method for setting marked blocks of cues to be skipped here
Here’s a more advanced example [QLab4 Only]
This uses OSC queries in QLab to give video feedback on triggered cues and the next selected cue. Here’s a screen recording of it in action (best viewed full screen):
How it Works:
The spacebar is hijacked as in the above example by deselecting it in settings/Keymap
In a second cue list, a fire all group cue is added.
This is triggered by the space bar (or any MIDI triggers you set to use).
It first clears the existing video output.
It then sets the first text cue numbered Line1 using an OSC cue with 2 OSC queries to create the top line of text
/cue/Line1/text “Cue #/cue/selected/number # • #/cue/selected/listName # Triggered”
The messages between the hash symbols in the OSC tells QLab to get that information from the selected cue (which will be the cue about to be fired).
The cue is then fired with an OSC /go message, which then means that the selected cue will be the cue standing by to be triggered.
An OSC cue then sets the second text cue numbered Line2 using another OSC cue containing queries
/cue/Line2/text “Next Cue: #/cue/selected/number # • #/cue/selected/listName #”
Finally the 2 text cues display their text
You can download the workspace here
Chapter Author: Mic Pool
Chapter Graphic: Public Domain/NASA