Output Types Overview
WATCHOUT sends data to external systems two ways: the Output cue and Art-Net on a Media cue. This page maps each to its use, then links to the detailed pages.
Two mechanisms
The Output cue sends one text payload over TCP, UDP, or HTTP. Add it with Add Output Cue. A single Protocol dropdown selects the transport.
Art-Net is not a separate cue type. It is an option on a Media cue. Drag an Art-Net Fixture asset onto a timeline. The cue gains a Fixture property section that outputs DMX over Art-Net.
Output cue
The Output cue has one Protocol field with three values: TCP, UDP, and HTTP.
| Protocol | Transport | Use |
|---|---|---|
| TCP | Reliable, ordered delivery | Show control systems, PLCs, custom applications |
| UDP | Lowest latency, no delivery guarantee | Low-latency, non-critical triggers |
| HTTP | Request to a web service | REST APIs, middleware, logging endpoints |
With HTTP selected, the cue shows a Path field, an HTTP Method field (POST, PUT), and a Content Type field (JSON, XML, Plain Text).
The Keep Connection Alive setting appears only for TCP.
For full configuration details, property tables, and troubleshooting, see Output Cues.
Art-Net on a Media cue
Art-Net Media cues transmit DMX over Art-Net at a fixed 44 frames per second. The fixture's channel layout comes from the Art-Net Fixture asset the cue references.
An Art-Net Fixture asset comes from a built-in preset (1ch Generic or 10 ch Generic) or an imported file.
GDTF (General Device Type Format) files import as Art-Net Fixture assets. GDTF defines a manufacturer's channel layout, modes, and capabilities.
A GDTF channel can carry value-dependent capabilities. The name shown for a channel changes with its current value — for example a shutter channel reads open or closed at different levels.
An Art-Net Recording (a .ndjson file captured with the Art-Net Recorder) attaches to an Art-Net cue as a recording source. Recorded values multiply with tween values, so tween keyframes act as a primary intensity control.
Art-Net cues are not supported inside compositions. Place them on a regular timeline.
For fixture definitions, universe addressing, channel relations, recording workflows, and troubleshooting, see Art-Net Fixture Cues.
Choosing the right output
| Scenario | Use |
|---|---|
| Trigger an automation controller with a simple command | Output cue, TCP or UDP |
| Send a command to a REST API or web service | Output cue, HTTP |
| Notify a logging or monitoring server | Output cue, HTTP POST |
| Fire a low-latency, non-critical trigger | Output cue, UDP |
| Control a DMX fixture directly from the timeline | Art-Net Media cue, preset or GDTF fixture |
| Replay a lighting sequence captured from an external console | Art-Net Media cue with a recording |
Related
- Output Cues — TCP, UDP, and HTTP messages
- Art-Net Fixture Cues — DMX control on a media cue