Output Types Overview
WATCHOUT provides five output types for sending information to external systems, covering string-based network messaging, HTTP integration, and DMX lighting control. Each output type is implemented as a cue on the timeline, firing or transmitting data in sync with playback. Choose the output type that matches your target system's protocol and data requirements.
Available Output Types
| Output Type | Protocol | Description |
|---|---|---|
| String Output | TCP / UDP | Sends a string payload to any TCP or UDP endpoint. Use this for simple trigger messages, automation commands, or raw string data sent to show control systems, PLCs, or custom applications. |
| HTTP Output | HTTP (GET, POST, PUT) | Sends HTTP requests to web services and REST APIs. Supports JSON, XML, and plain text content types. Use this for middleware integration, logging endpoints, or any system that exposes an HTTP API. |
| Art-Net Channel Output | Art-Net (DMX) | Sends DMX channel values using WATCHOUT's built-in fixture presets (1ch Generic, 10ch Generic). Tween keyframes automate channel values over time at 44 FPS. Use this for direct DMX lighting control without external fixture description files. |
| Art-Net GDTF Output | Art-Net (DMX) | Sends DMX channel values using GDTF (General Device Type Format) fixture description files. GDTF files provide manufacturer-defined channel layouts, modes, and capabilities for precise fixture control. |
| Art-Net Recording Output | Art-Net (DMX) | Plays back pre-recorded Art-Net data captured with the standalone Art-Net Recorder application. Use this to replay complex lighting sequences originally programmed on an external console. |
String and HTTP Outputs
String Output and HTTP Output cues are point-in-time events that fire once when the playhead reaches their position on the timeline. They have no duration and transmit a single payload per execution.
- String Output sends raw string data over TCP (reliable, ordered delivery) or UDP (lowest latency, no delivery guarantee).
- HTTP Output sends an HTTP request with configurable method (GET, POST, PUT), content type (JSON, XML, PlainText), and URL path.
Both types support the Keep-Alive setting for connection reuse across multiple cues targeting the same endpoint.
For full configuration details, property tables, and troubleshooting, see Output Cues.
Art-Net Outputs
The three Art-Net output types all transmit DMX data over Art-Net at a fixed rate of 44 frames per second. They differ in how the fixture's channel layout is defined and how channel values are sourced.
- Art-Net Channel Output uses WATCHOUT's built-in fixture presets with configurable channel resolutions (8-bit through 32-bit). Channel values are driven by tween keyframes on the timeline.
- Art-Net GDTF Output uses imported GDTF fixture description files that define the fixture's full channel layout, modes, and capabilities as specified by the manufacturer.
- Art-Net Recording Output plays back
.ndjsonrecording files captured with the Art-Net Recorder application. Recorded values multiply with tween values, allowing tween keyframes to act as a master intensity control over the recorded data.
Art-Net fixture cues are not supported inside compositions. All Art-Net output cues must be placed on the main timeline.
For fixture definitions, universe addressing, channel relations, recording workflows, and troubleshooting, see ArtNet Fixture Cues.
Choosing the Right Output Type
| Scenario | Recommended Output Type |
|---|---|
| Trigger an automation controller with a simple command | String Output (TCP or UDP) |
| Send a command to a REST API or web service | HTTP Output |
| Control a DMX fixture directly from the timeline | Art-Net Channel Output or Art-Net GDTF Output |
| Replay a lighting sequence captured from an external console | Art-Net Recording Output |
| Notify a logging or monitoring server | HTTP Output (POST) |
| Fire a low-latency, non-critical trigger | String Output (UDP) |