Production Properties - Cue Control Devices - Network

Network (Telnet/UDP) Cue Control is only available with SCS Professional Plus and higher license levels.


If you want to control SCS cues by Network messages sent by another program (on the same or a different computer) then enter the relevant detail as a Cue Control Device. The layout of the lower part of the screen depends on the Device Type of the currently-selected device. The example below shows the layout for a Network device.

Properties and Controls

Enable Cue Control from these Interfaces

SCS allows you to nominate up to four devices from which SCS can be remotely controlled, such as from a lighting board. However, it would not be common to have remote control from more than one device so you will probably only have a 'C1' entry.

Mapping to Physical Devices on this Computer

All your Device mappings are held in a Device Map. This is the same Device Map used for Audio Output Devices, so the name of that Device Map is displayed but is not editable here.

The Physical Devices chosen are for this Device Map on this computer.

Device Number (C1, C2, etc): If this number is displayed with a colored background (eg see C1 in the above screenshot) this indicates this device is the 'current' device for the 'Settings' panel displayed below the device list. To make a different device the 'current' device, click on any field in the line for the required device, or on the Device Number itself.

Device Type: This drop-down list contains the Cue Control device types supported by your license level.

Computer-Specific Fields

Physical Device: The physical device assigned to this Cue Control Device. The Physical Device is a display-only field based on the 'Settings' provided in the lower part of the screen.

Active?: This display-only checkbox will be checked if SCS has successfully initialized this device, or will be blank if the initialization failed. If you have devices that have not been initialized successfully, click Retry Activating Devices at the bottom of this tab.

Other Network In Settings.

Remote Device: The purpose of this field is to simplify configuring SCS for commonly-used devices or products. The following devices and products are currently included in this list:

Any Device or Product

SCS on another computer

Behringer X32 Digital Mixer

Behringer X32 Compact Mixer


For more information on the X32 remote devices, see Cue Control using a Behringer X32 Mixer.

Network Protocol: This field will be preset and disabled for certain remote devices. If the field is enabled then select either Telnet or UDP as required by the remote device or product.

Network Role: This field may be preset and disabled for certain remote devices. If the field is enabled then select the required Network Role or connection type as follows:

SCS is a Network Client: Select this option if SCS is to be a Network Client. A Network Client means that SCS will try to establish a Network connection with a nominated host (as described below).

SCS is a Network Server: Select this option if SCS is to be a Network Server. A Network Server means that SCS will listen on a nominated port (see below) for a connection request from a program running as a Network Client.

Dummy Network Connection: Select this option if you wish to set up Control Send cues for a Network connection but you do not have a suitable Network connection available on this computer.

Computer-Specific Fields

Server Name or IP Address and Port No.: These fields only appear if SCS is a Network Client. In the Server Name or IP Address field enter either the network name of the server, or the relevant IP address. In the Port No. field enter the port number that the server will be listening on. Port No. may be preset and disabled for certain remote devices. Server Name or IP Address is never preset or disabled.

Listen on Port No.: This field only appears if SCS is a Network Server. Enter the port number this instance of SCS to listen on. Listen on Port No. may be preset and disabled for certain remote devices.

This Computer's IPv4 Addresses: This button only appears if SCS is a Network Server. The purpose of this button is to assist in setting up the network client that will be sending commands to SCS. The number of IPv4 Addresses listed will depend on what's connected to the computer. For example, you may have an IPv4 address for a wireless network connection, and a second IPv4 address for an Ethernet cable conection. The IPv4 address you set on the client depends on how that client communicates with the SCS computer, eg by wireless connection or by Ethernet cable connection.

Network Message Assignments

This panel provides information on how the selected Network message types are mapped to SCS actions. You can choose to Show OSC Message Formats or Show ASCII Message Formats.

SCS functions currently supported are as follows (blank entries indicate functions not supported with that message format):

SCS Function

OSC Message Format

ASCII Message Format


Go Button



0 (in ASCII format) is zero

Stop All




Pause or Resume All




Go To Top




Go Back




Go To Next




Go To End




Go To Cue

/ctrl/goto ,s x


x is the cue label, eg Q90

Play Cue x

/cue/go ,s x


x is the cue label

Stop Cue x

/cue/stop ,s x


x is the cue label

Pause or Resume Cue

/cue/pauseresume ,s x


x is the cue label

Activate Hotkey x

/hkey/go ,s x


x is the hotkey, eg A

Start Note Hotkey x

/hkey/on ,s x


x is the note hotkey (operates the same as 'activate hotkey x')

Stop Note Hotkey x

/hkey/off ,s x


x is the note hotkey

Set Master Fader

/fader/setmaster ,f n.n


n.n is the required dB, eg -12 or -8.5. SCS accepts dB values in the range -75 to 0 (or -75 to +12 if +12dB is selected as the Maximum Audio Level in Run Time Settings). Values outside this range will be capped, eg if -100 is received then SCS will set the master fader level to -75dB.

Set Device Fader

/fader/setdevice ,sf x n.n


Similar to Set Master Fader but applies to a specified Audio Output Device. x is the device (eg Front), and n.n is the required dB, eg -12 or -8.5.

The OSC Message Format is not just text - OSC commands are strictly formatted with an address pattern (sometimes called an 'OSC Path') optionally followed by a tag string and then followed by values for those tags. Only use the OSC Message Format from devices or software that support OSC. Note that SCS can send OSC in Control Send Cues so you can use OSC to send commands from 'SCS on another computer'.

Note: Incoming OSC messages may optionally be preceded by /scs, eg /scs/ctrl/go. This is useful for external systems that prefer all outgoing OSC messages to start with an identifier unique to the target system.

Individual ASCII Message Format commands may be terminated with a carriage return (0DH) or 'pipe' character (|). If multiple ASCII commands are received together, each command must be terminated with a carriage return (0DH) or 'pipe' character(|).

The network commands and cue labels included in the commands are not case-sensitive. For example, if you have a cue label Q90 then the ASCII command SCSGo("q90") will successfully fire that cue.

Test Network Control

Having set your required Network Connection type and selected Network Cue Control, you can now check that SCS is receiving and recognizing these messages by clicking the Test Network Control button. This will open a Network Test window, and selected incoming network messages will be displayed in that window. Where the message is recognizable for cueing purposes, the mapping is displayed.

You can clear messages from the window by clicking the Clear button. Close the window by clicking the Close button.

Device Map Buttons

The buttons at the foot of the tab apply to all device types as explained for Audio Output Devices.

< Previous Topic (Cue Control Devices - RS232)  |  Next Topic (Cue Control Devices - DMX) >