Script cues allow you to execute AppleScript from within QLab. AppleScript is a very old (and frankly pretty weird) scripting language which has deep integration into macOS and into many, many programs which run on macOS. A good, though fairly technical, introduction to AppleScript can be found here at macosxautomation.com. Script cues require a license of any kind.

The Inspector for Script Cues

When a Script cue is selected, the inspector shows the Basics tab and Triggers tab, used by all cues, as well as the Script tab.

The Script Tab

In a newly created Script cue, the text field in the Script tab will show the default AppleScript defined in the Script cue template.

Text entered here will follow Apple’s standard formatting rules for AppleScript.

Click the Compile Script button to compile your script. If your script contains errors, QLab will display an error message next to this button in order to help you find and address the issue.

The Run in separate process checkbox is checked by default. When it is checked, QLab spins off the script in a Script cue to an external invisible application which handles the execution of the AppleScript. This allows complex scripts to execute in the background, without monopolizing QLab and preventing you from interacting with QLab while the script runs. Uncheck this box if your script needs to execute from within QLab. Executing the script inside QLab improves the timing precision with which the script interacts with QLab.

Broken Script Cues

Script cues can become broken for the following reasons:

AppleScript error

Correct the error in the Script tab of the inspector to clear this warning.

License required

Script cues require a license of any kind.