Skip to main content

Calrec and the Automator

Learn how to use Calrec audio consoles with the Cuez Automator.

What is Calrec?

Calrec is a leading manufacturer of professional broadcast audio mixing consoles, used by broadcasters around the world for live sports, entertainment, and news production. Their range includes the Argo series, Apollo, Artemis, Brio, Summa, and Omega, among others.


The Cuez Automator controls Calrec consoles using CSCP, the Calrec Serial Control Protocol, carried over TCP/IP. This lets you open, close, mute, and fade faders directly from your rundown, and the Automator reads the live level, mute, and PFL state back from the console, including changes made at the desk.


For more information about Calrec, visit the Calrec website.

💡 The full Calrec (CSCP) function set described in this article is available from Automator Stable v1.42.0 (22 October 2026) onwards. Earlier versions of the Calrec integration offer a much smaller set of functions.

Which consoles are supported?
Calrec documents CSCP over TCP/IP for the Argo, Apollo, Artemis, and Brio consoles. Omega consoles only offer CSCP over a serial (RS232) connection, so they cannot be used with this integration. For other models, such as Summa, check with Calrec whether CSCP over TCP/IP is available on your console.

Before you start: enable CSCP on the console

CSCP is switched off by default on Calrec consoles and has to be enabled on the console before the Automator can connect to it. How you do this depends on the console model, and on some consoles it needs a configuration change from Calrec. Contact your Calrec representative or Calrec support, and have the console's serial number ready.

  • Port - the TCP port is set on the console when the CSCP interface is created, and it differs per console and site. Note it down, as you will need it in the Automator. The Automator's default of 12345 is only a starting value.

  • CSCP version - use the newest CSCP version your console offers (CSCP21). On older versions (CSCP01 or CSCP20) the console cannot tell the Automator which type each fader is, so the fader picker only shows fader names and numbers, and the Automator writes a warning to its log.

  • Network - the machine running the Automator must be able to reach the console over the network. Audio networks are often isolated, so confirm there is a route between the two.

  • Faders - the faders you want to control must be in the console's protocol-controlled area. Calrec recommends not cloning faders in that area.

Adding a Calrec 'device' to the Automator

In the top right corner of the Automator, we see 'Devices' - this can be either in red or green depending on the status of the configured devices. Click it and select 'Add device'.

Next, select 'Calrec' from the 'Device type' dropdown list, then give it a name.

Once the Calrec device is selected and given a name, you will see all the fields needed to configure it for use with the Automator.

Basic device configuration

You can enable or disable the Calrec device and enter the following settings:

  • 'Host name' - the IP address or hostname of the Calrec console on your network.

  • 'Network port' - the TCP port of the CSCP interface on the console. The default is 12345, but the port is set per site, so it must match what is configured on your console.

  • Fader numbering - an option to start numbering at 1. It is checked by default on new devices. Existing devices keep their original numbering, so saved automations keep pointing at the same faders.

Once the settings have been entered correctly, the device should show as 'online' (green) in the top right corner.

Configuring actions

Once your Calrec device is configured, you can set up the actions you want to perform on the console when triggering an Item or Block in Cuez. More on that in this article.

Available functions

The Calrec integration includes 13 functions, covering fader level and mute control, pre-fader listen, and presets and fades. They work on channel, group, VCA, main, and aux faders, which all appear together in one picker. The picker shows each fader's name and type as read from the console, and stays current when the console is reconfigured.

Levels are entered as a percentage of fader travel (0 to 100). On a channel fader, about 74% is the 0 dB position. On a main fader, 0 dB is at about 98%.

Level and mute

Set fader level

Sets a fader to a specific percentage of its travel.

Open fader

Opens a fader to its 0 dB position.

Close fader

Closes a fader fully.

Volume up

Nudges a fader up by a number of percentage points from its current live level. The move is instant, and stops at 100.

Volume down

Nudges a fader down by a number of percentage points from its current live level. The move is instant, and stops at 0.

Mute fader

Mutes a channel, group, or VCA fader.

Unmute fader

Unmutes a channel, group, or VCA fader.

Toggle mute

Reads the fader's current mute state from the console and switches it.

Pre-fader listen

Pre-fader listen on

Switches pre-fader listen on for a channel or main fader.

Pre-fader listen off

Switches pre-fader listen off for a channel or main fader.

Presets and fades

Store fader preset

Saves a fader's current live level under a name you choose. The preset is stored by the Automator, not in the console's memory: it is kept on the computer running the Automator, per device and per fader, so Fade to preset has to use the same fader and the same name.

Fade to level

Fades a fader to a percentage level over a duration you enter in milliseconds (up to 15000, which is 15 seconds), using a linear, ease in, ease out, or ease in-out curve. A duration of 0 sets the level instantly.

Fade to preset

Fades a fader back to a stored preset level, with the same duration and curve options. If no preset with that name is stored for the fader, the function reports an error.

Good to know

  • No scene or memory recall. CSCP has no command to recall a console memory or snapshot, so the Automator cannot do this. If someone recalls a memory at the console, the Automator picks up the new fader state.

  • Mute and PFL limits. Mute and unmute work on channel, group, and VCA faders only, not on main faders or aux outputs. PFL works on channel and main faders, not on aux outputs. Pointing these actions at an unsupported fader reports an error.

  • Fades are stepped. The Automator builds fades by sending a series of small level changes. The console's own display updates at most 10 times a second, so it can look coarser than the fade the Automator sends. If the connection to the console drops during a fade, the fade stops.

  • Fader names in the picker. Channel, group and VCA faders show their number, name and type. Main faders show as "Main 1" and aux outputs as "Aux 1". A main output that is assigned to a fader can appear twice, once as a main and once as a channel fader. They use different dB curves, so the same position shows different values. That is how the console works, not a duplicate.

  • Aux send routing and routing to the main outputs are not available at this time.

Troubleshooting

If the Calrec console shows as offline in the Automator, check the following:

  • CSCP enabled - confirm CSCP has been switched on for your console. It is off by default.

  • Host name - confirm the IP address or hostname matches the console.

  • Port - confirm the port in the Automator matches the CSCP interface on the console, and that it is not blocked by a firewall. The default of 12345 is unlikely to match unless it was set up that way on the console.

  • Console model - confirm your console offers CSCP over TCP/IP. Omega consoles are serial only and cannot be used with this integration.

  • Network - confirm the Automator machine can reach the console. Audio networks are often isolated from the production network.

If the device shows online but a function does nothing, or moves the wrong fader, check the following:

  • Fader numbering - confirm the fader numbering option (start at 1) matches how your automations were set up.

  • Protocol-controlled area - confirm the fader is in the console's protocol-controlled area, and that no cloned faders sit in it. A cloned fader can undo an earlier command.

  • VCA masters - a fader under a muted VCA master reads as muted, and the console ignores requests to change it.

  • Fader types missing - if the picker only shows fader names and numbers, without a type for each fader, use the newest CSCP version your console offers.

  • Online, but the fader picker is empty - confirm CSCP is enabled on the console and that the faders are in its protocol-controlled area. The Automator writes a warning to its log when it is connected but has found no faders.

Did this answer your question?