What is the Chyron iSQ?
The Chyron iSQ is a graphics playout and control system for newsroom automation. The Cuez Automator can control the iSQ Viewer directly — loading and closing running orders, navigating home, cueing stories and items, taking and stopping items and columns, pausing/releasing playback, and running macros. Item- and column-level functions target the currently open MOS rundown, with an optional Running order id to target a specific running order instead.
Find more information about Chyron iSQ on their website.
Adding a Chyron iSQ '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 'Chyron iSQ' from the 'Device type' dropdown list, then give it a name.
Basic device configuration
Enter the Host name of the machine running the iSQ Viewer (localhost if the Automator and iSQ Viewer are on the same computer). The Port defaults to 10820, matching the iSQ Viewer's control port. The Application ID defaults to 1 and identifies which iSQ Viewer instance to control if more than one is running.
Once the settings have been entered correctly, the device should show as 'Online' (green) instead of 'Offline' (red).
Configuring actions
The next step is then to configure each Item and Block configuration with the (set of) functions you want to perform on the Chyron iSQ when triggering the Item or Block; more general information on that is available in this article.
Available functions
Load running order — Loads the specified running order into the iSQ Viewer. Configured with Running order id (optional — defaults to the currently open MOS rundown).
Close running order — Closes the specified running order in the iSQ Viewer. Configured with Running order id (optional).
Close all running orders — Closes every running order currently open in the iSQ Viewer.
Home — Returns the iSQ Viewer to its home/idle state. Configured with Running order id (optional).
Story cue — Cues a specific story from the rundown, preparing it in the Viewer without taking it to air. Configured with Item and Running order id (optional).
Cue item — Cues a specific item within a story. Configured with Item and Running order id (optional).
Take — Steps through the playlist sequentially: cues the next item in sequence and, on subsequent presses, advances it. Configured with Item and Running order id (optional).
Take to air — Bypasses the cue/preview step and plays the selected item directly to air in a single action. Configured with Item and Running order id (optional).
Stop — Stops a currently playing item. Configured with Item and Running order id (optional).
Pause release — Pauses a playing item, or releases it to resume if already paused. Configured with Item and Running order id (optional).
Column take — Takes a specific column's content. Configured with Column and Running order id (optional).
Column stop — Stops a specific column's playback. Configured with Column and Running order id (optional).
Column stop all — Stops all columns' playback. Configured with Column and Running order id (optional).
Column pause release — Pauses or releases a specific column's playback. Configured with Column and Running order id (optional).
Column pause release all — Pauses or releases all columns' playback. Configured with Column and Running order id (optional).
Execute macro — Runs a saved macro slot on the iSQ Viewer. Configured with Slot.
💡 Available in Stable from v1.36.0 (1 Sep 2026) onwards.
Troubleshooting
If the Chyron iSQ device shows 'Offline' in the Automator:
Confirm the machine running the iSQ Viewer is powered on and reachable on the same network as the machine running the Cuez Automator.
Double-check the Host name and Port match what's configured on the iSQ side — the default port is
10820, but this can be changed on either end.Confirm the Application ID matches the iSQ Viewer instance you intend to control, especially if more than one instance is running on the same machine.
If a firewall or network security tool is active on either machine, make sure port
10820isn't being blocked.


