Record Streaming Cues

CueServer is a highly-dynamic tool. From dazzling audiences with award-winning parade performances to running point on high-end architectural lighting, CueServer has performed in just about every situation possible, easing the woes of countless lighting designers.

Through it all, one of the CueServer's features, the ability to seamlessly record and playback lighting data, has long remained among its most powerful.

Whether you're commanding a full 32 universes with your favorite lighting console or crafting a precision-tuned show with computer-driven software, CueServer can capture it -- in all its glory. 

This well-known feature is called a Streaming Cue, which is a type of cue that stores DMX channels and their changes over a period of time. From why you might need Streaming Cues to how you record them, this article will take you through the process, start to finish.


For more information on types of cues, take a look at Cue Types in the manual. For more on Cues in general, check out this section on Cues.

The Scenario

You've put together the lighting for a repeating show. This show is, for the most part, always the same. You have several of these shows that rotate throughout the week. Using the CueServer system to record and maintain cues for each rotating show will greatly reduce time and cost by allowing the show to be created once and recorded for future playback.

The Breakdown

There are two routes one can take when recording cues and two optional methods to improve precision and simplify the process.

One route is to use the CueServer Studio GUI to manually record an incoming stream to a cue. This is the most straightforward method and involves simply creating a new cue and recording the stream from within the window directly.

Alternatively, a second route is to use CueScript commands to record incoming lighting data as a streaming cue. This method can be used through either the GUI (in the command box) or via a number of network or serial communication interfaces.

The latter option can also be attached to buttons, macros, rules, triggers, etc.


Below we'll go through each of the two options and the features you can use to enhance the process.

The Walkthrough

Option 1: Using the GUI


  • To begin, open CueServer Studio and navigate to the Cue List within the Editor Window. 



  • Add a new cue to the cue list using the plus button ( alt ) at the lower-left corner of the cue list.


  • Give the Cue a Number and Name and click Save in the bottom right.
    • Note: Fade does not apply to streaming Cues



  • Click on the Capture button ( alt ) to open the capture dialog.


  • Inside the capture dialog, click on the Stream button to display the stream-recording controls.



Manual Recording

  • For manually recording a stream, leave both Record Length and Trigger Channel blank
    • Clicking Record will start the recording process and the timer will display elapsed time
    • Once recording, the Record button will be replaced with a Stop button to end the recording


Record Length

  • If using Record Length, the recording will be automatically stopped once the entered time has passed (accurate to 1/100 of a second).


Trigger Channel

  • If using Trigger Channel, once the Record button is pressed, CueServer will wait for the targeted channel's value to raise above 0 to begin recording.

  • Once the targeted channel's value returns to zero, the recording will end (unless previously ended via a Record Length).

Option 2: Using CueScript


  • To get started, identify the Cue number you wish to record to and whether it already exists or needs to be created.


  • Since we are not using the GUI, the only step needed is to issue a CueScript command via your preferred interface (in this example, I'll demonstrate using the command CueServer Studio command shortcut -- CMD/CTRL + SHIFT + C)



Note: In the following examples, the Cue we will be recording to is Cue 7.

Manual Recording

  • If not using either of the optional features listed above, the only variable here is whether the Cue exists or not.

Cue Doesn't Exist

  • When creating a new Cue, use the Record Stream command.
  • The syntax for the record command is:
    • Record [options] Stream <cue number>
  • Since we're not using options, all we need here is 

  • Followed by the Stop Record command to end the recording 

Cue Does Exist

  • When updating an existing Cue, use the Update Stream command.
  • The syntax for the update command is:
    • Update [options] Stream <cue number>
  • Follow the same steps as above, replacing the Record in Record Cue with Update


Record Length

  • If using Record Length, the recording will be automatically stopped once the entered time has passed (accurate to 1/100 of a second) following the issuance of the Record or Update command.
  • To use the Record Length command, use the following command syntax (depending on whether cue already exists)
    • Record Time [Rec Length] Stream [Cue #] (cue doesn't exist)
    • Update Time [Rec Length] Stream [Cue #] (cue exists)
  • For Example, to create Cue 1 and record a 15-second stream into it:
    • Record time 15 stream 1


Trigger Channel

  • To use the Trigger Channel command, use the following command syntax (depending on whether the cue already exists)
    • Record Channel [Trigger CH#] Stream [Cue #] (cue doesn't exist)
    • Update Channel [Trigger CH#] Stream [Cue #] (cue exists)
  • If using Trigger Channel, once the Record command is issued, CueServer will wait for the targeted channel's value to rise above 0 to begin recording.
  • Once the targeted channel's value returns to zero, the recording will end (unless previously ended via a Record Length property or a Record Stop command).


Have a Tip or Trick you would like to see? Let us know!

We hope you enjoyed this Tip & Trick, and as always, if you ever have any suggestions or ideas that you would like to see
featured, shoot us an email at and let us know!