Workflows
Monitoring
FPS, GPU memory, dropped frames, projector telemetry, and log stream — all live.
The monitoring dashboard streams the rig’s vitals in real time. You see what’s healthy and what isn’t before the room sees it.
Opening the dashboard
Open the Monitoring panel from the main UI. It splits into four sections by default:
- TouchDesigner host stats (FPS, GPU memory, dropped frames)
- Per-projector status (signal, lamp hours, temperature)
- Network health (WebSocket latency sparkline, WebRTC stream stats)
- Log stream with severity filtering
TouchDesigner stats
Frame rate, GPU memory usage, and dropped-frame count update at 1 Hz with a rolling sparkline showing the last 60 seconds. The sparkline makes problems visible before they hit a threshold — a slow climb in GPU memory tells you about a leak hours before it actually OOMs.
- FPS — sustained framerate. Target is your show’s configured frame rate (60 by default). Drops below target are highlighted.
- GPU memory — used and available VRAM. Persistent climbing here without releases between scene changes is a red flag.
- Dropped frames — frames that missed their deadline. Should be zero or near-zero on a healthy system.
Per-projector status
For each projector with PJLink:
- Signal status — is the projector receiving the signal you’re sending it?
- Lamp hours — current bulb age
- Temperature — projector internals temperature, with thresholds for warning and critical
- Power state — on, off, cooling, warming
- Errors — any reported by the projector’s onboard diagnostics
Projectors without PJLink still render in the list but show only the routing/status that TouchDesigner can infer locally.
Network health
The WebSocket latency sparkline shows the round-trip time for control messages. Should sit under 5ms on a healthy LAN; anything above 20ms is unusual.
WebRTC stream stats show:
- Active connections (one per browser)
- Bitrate per stream
- Packet loss percentage
- Resolution / framerate negotiated
A growing packet-loss rate is a network problem to investigate — usually wifi or VLAN traffic.
Log stream
The log stream shows messages from both the TouchDesigner side and connected browsers. Severity filtering (debug / info / warning / error) lets you tune signal-to-noise.
Logs are persistent across sessions on the TouchDesigner side; they survive a browser refresh. They don’t survive a TouchDesigner restart unless you’ve configured file-based logging.
During a live show
Keep the monitoring panel visible on a secondary screen during the show. The sparklines and projector status are the early-warning system — if something is going wrong, the dashboard shows it before the visual artifact appears in the room.
If you have a stage manager or technical director on a separate display, the monitoring view alone (without the rest of the editing UI) is a sensible thing to give them — they can flag issues without needing to operate the show themselves.
What monitoring doesn’t do
Monitoring does not alert externally. There’s no email or SMS integration. If the rig fails in the middle of the night during an unattended install, you’ll find out when you check the dashboard or when someone walks past the venue.
For long-running installs where unattended alerting matters, route the same data into your venue’s standard monitoring tool — the TouchDesigner side can export to systems that handle alerting.
Related
- Concepts: Architecture — where the monitoring data comes from
- Projectors — the entity the monitoring data is attached to