There are several places where CueScript commands are used within the system.
When working with CueServer Studio on a live CueServer, a command line appears at the bottom of the window. This command line allows CueScript commands to be executed at any time.
Enter a CueScript command (like
Channel 5 at 33 or
Record Cue 7) and CueServer performs the requested task. Whenever a command is entered, the CueServer replies with a value (which is shown in gray text after the command).
CueServer uses the concept of rules to define automation tasks throughout the system. Using CueServer Studio, you can define global rules that are always being monitored for triggering, or you can assign local rules to individual cues, buttons, contacts, and other objects within the system.
A rule takes the form of Whenever something happens … Then do something
One of the options in the then do something clause of a rule is to perform a CueScript. In the example above, whenever this button is pressed, execute the command
Cue 1 Go.
Some objects in the system (such as Timers and Macros) are programmed with CueScript actions.
When editing a Timer or Macro, an action field appears, allowing a CueScript command to be entered as the object’s action. Whenever the Timer or Macro is triggered, the programmed action is performed.
CueScript commands can also be sent to CueServer from an external source by one of the methods listed below: