Looping, spatial audio, and immersive visuals

This guide separates the project into two technical workstreams: an audio system that turns loop tracks into movable sound objects, and a visual system that delivers a TouchDesigner composition to the venue's large projection surface.

The system in one minute

Audio and visuals are separate delivery systems. They meet through timing, control data, rehearsal procedure, and operator coordination—not by sharing one application or computer.

Audio system

Keep hands-on loop creation on the RC-505mkII. Route its five tracks as five mono signals so the WFS system can position them independently. Add Ableton only when recording or expansion beyond five objects is needed.

  1. RC-505mkII
  2. 5 mono tracks
  3. 5 WFS objects
Open the audio brief →

Visual system

Run the working TouchDesigner project on a prepared workstation and send the finished image to the venue over NDI. Qualify the venue's experimental Linux runtime as an alternative rather than treating it as a drop-in replacement.

  1. TouchDesigner
  2. NDI transport
  3. Projection system
Open the visual brief →

Recommended division of responsibility

The starting configuration keeps each specialist working in the system they know, while making the technical handoffs explicit.

Loop performance

Owns loop recording, overdubbing, stopping, undo, faders, and looper effects on the RC-505mkII.

Spatial audio

Owns channel ingest, WFS object assignment, object position, movement, monitoring, and audio recovery.

Visual performance

Owns the TouchDesigner project, live controls, NDI output, projection framing, and the visual fallback state.

How to use the briefs

Work from the recommendation outward. Do not prototype the more complex alternatives until the basic venue interfaces and artistic requirements are known.

  1. Understand the baseline Read the main diagram and confirm that its division of control matches the intended performance.
  2. Resolve the open decisions Answer the interface, channel, object-count, projection, network, control-data, and monitoring questions.
  3. Build the smallest complete system Prove five separate loop objects and one stable visual route before adding Ableton handoff or venue-Linux deployment.
  4. Rehearse failure and recovery Test audio isolation, monitoring, visual fallback, restart behavior, and the operator handoff under show conditions.

Shared decisions before rehearsal

These items affect both workstreams and should be captured in one versioned venue sheet.

  1. Venue I/O contract Audio inputs, sample rate, WFS object count, video canvas, frame rate, receiver, and physical connection points.
  2. Operator positions Who controls loops, sound-object motion, TouchDesigner, venue ingest, and emergency fallback—and from where.
  3. A/V control link Whether visuals need tempo, track state, levels, sound-object positions, or only live audio analysis; plus the chosen MIDI or OSC route.
  4. Monitoring and preview Low-latency performer monitoring, WFS confidence monitoring, visual operator preview, and a projection-safe work surface.
  5. Fallback states A safe audio state, a pre-rendered visual or still, a black-frame option, and a documented switch-over procedure.