Performance system
  1. Overview
  2. Visuals

External visual system to venue projection Use the visual artist's own hardware and software over wired NDI; keep venue TouchDesigner as an option.

The visual artist renders and controls the work on their own prepared system and sends the finished image to the venue. This keeps creative and runtime dependencies on the known hardware and software.

Own visual system Wired NDI Full-load test required

Approval condition: the actual sender, network, receiver, and projection chain must sustain the agreed canvas and frame rate with acceptable latency.

Primary: own visual system over NDI

The show uses the visual artist's own hardware and software and transports only the finished image.

USE FOR THE SHOW
video / network
The visual artist's own hardware and software sends a finished NDI stream over a dedicated wired network to the venue NDI receiver and projection processor.
Composition, rendering, and live control stay on the visual artist's system; the venue receives a locked image format.

Show-ready when

  • the projection canvas is confirmed;
  • the target frame rate is sustained;
  • receiver compatibility is proven;
  • end-to-end latency is acceptable;
  • a clean fallback has been rehearsed.
The large projection is an output, not a work surface.

Provide the visual operator with a separate preview monitor and controls. The public projection should never expose the visual software interface or operating-system desktop.

Keep three layers separate

Each layer needs its own owner, specification, and test.

Composition and render

Visual software, project, media, plug-ins, controls, GPU load, output format, and license.

Image transport

NDI encode, stream discovery, network capacity, receiver compatibility, and latency.

Projection delivery

Canvas, frame rate, color, mapping, operator preview, and fallback.

Preparation and alternatives

The preferred route stays visible above. Open these sections for the venue-specific deployment and validation work.

Option: TouchDesigner on the venue machine Run a packaged TouchDesigner project locally only after compatibility is proven. TEST FIRST
A packaged TouchDesigner project runs on the venue's experimental Linux machine and reaches the projection processor through DisplayPort or HDMI.
This route removes NDI transport but moves the complete visual runtime onto the venue machine.

Record the exact Linux distribution, compatibility layer, TouchDesigner build, GPU, driver, display server, and license. Audit every plug-in, Python package, codec, font, movie, device input, custom operator, and file path.

Projection canvas contract Define the exact image the venue expects before optimizing scenes. 4 QUESTIONS
  1. What are the native pixel dimensions, aspect ratio, refresh rate, and expected frame rate?
  2. Does the venue expect one frame, a wide canvas, multiple slices, or a pre-warped image?
  3. What color space, range, pixel format, and scaling behavior should be used?
  4. Which device accepts the final signal, and what formats does it support?
NDI receiver and network Specify discovery, capacity, compatibility, monitoring, and latency. 6 QUESTIONS
  1. Which hardware and software send NDI, and which application or hardware receives it?
  2. Which NDI version, pixel formats, and resolutions are supported?
  3. Is there a dedicated wired path, and what other traffic shares it?
  4. How are discovery, IP addresses, stream naming, and firewall rules handled?
  5. What sustained sender and receiver frame rates are acceptable?
  6. What missed-frame count and end-to-end latency are acceptable?
Optional: audio-responsive visuals Use only the loop, tempo, level, or WFS data that serves the composition. MIDI / OSC
CONTROL
RC / WFS state → MIDI or OSC bridge → visual-system parameters
OPTIONAL

Define the sender, receiver, message names, update rate, ownership, and failure state. The visual output should remain valid when control data pauses or disconnects.

Visual runtime checklist Freeze the primary visual environment and identify dependencies for the venue TouchDesigner option. RUNTIME
  • Record the primary hardware, OS, GPU driver, visual software, license, and project version.
  • Package media, fonts, plug-ins, Python packages, codecs, and relative paths.
  • List every device input, custom operator, and platform-specific dependency.
  • Verify startup, save, restart, full-screen output, control input, and crash recovery.
Visual test plan Approve each route independently with the representative project. 8 STEPS
  1. Lock the canvasRecord size, aspect, frame rate, color, mapping, and physical handoff.
  2. Freeze the visual systemRecord hardware, OS, GPU, driver, software, license, project, and dependencies.
  3. Configure NDIAgree stream name, receiver, discovery, IP, firewall, switch path, and ownership.
  4. Test full loadRun the heaviest real scenes and log render FPS, skipped frames, network use, receive FPS, misses, and latency.
  5. Verify projectionCheck crop, scaling, warp, slices, blending, color, tearing, and full-screen behavior.
  6. Qualify venue TouchDesignerTest the packaged project on the exact venue Linux image, including controls, save, restart, and recovery.
  7. Test A/V controlConfirm normal, disconnected, restarted, and stale-data behavior.
  8. Rehearse fallbackSwitch to a pre-rendered asset, safe still, or black frame without exposing the editor.
Visual sources Venue, NDI, and optional TouchDesigner documentation supporting the delivery plan. 5 DOCUMENTS