Loop performer
Creates and performs loops on the RC-505mkII.
Performance system RC-505mkII looping, wave field synthesis, and external NDI visuals
Keep loop performance on the RC-505mkII, expose its five tracks as five independently movable WFS objects, and deliver the finished visual output from the visual artist's own hardware and software over wired NDI.
Recommended baseline
Direct Ableton option
Venue test required
The baseline in two lines
Who controls what
Each operator keeps a clear domain. The handoffs happen through audio channels, control data, and rehearsed cues.
Spatial operator
Moves, balances, and recalls the WFS sound objects.
Visual operator
Runs their own hardware and software, and sends the finished NDI output.
Before the first rehearsal
Five decisions need owners and written answers. Open an item for the questions behind it.
WFS inputs and object count Confirm how five mono signals become five controllable objects.
- What physical or network inputs does the WFS chain accept?
- How many simultaneous objects are available?
- Does one mono input map directly to one object?
- Where are position, movement, level, and scene recall controlled?
Performer monitoring Provide a predictable, low-latency path for live and looped sound.
- Does the performer monitor from the looper, a dedicated mix, or the WFS return?
- How is the live microphone separated from the loop-object outputs?
- What latency, feedback, and comb-filtering checks are required?
Projection canvas Lock the image dimensions and venue handoff before scene optimization.
- What are the native dimensions, aspect ratio, frame rate, and color space?
- Does the venue expect one frame, multiple slices, or a pre-warped image?
- Which device receives the final signal?
NDI receiver and network Prove the complete sender-to-projection path at representative load.
- Which NDI receiver and version are used?
- Is a dedicated wired path available?
- How are discovery, IP addressing, stream naming, and firewall rules handled?
- What frame-loss and end-to-end latency thresholds are acceptable?
Operators and fallback Define control ownership, preview positions, and safe recovery states.
- Who controls loops, WFS movement, visual playback and rendering, venue ingest, and emergency fallback?
- Does the visual operator have a private preview and input devices?
- Which audio state and visual asset are used after a failure?
- Which loop or WFS data, if any, should reach the visual system over MIDI or OSC?
Technical briefs
The essential answer stays visible on each page. Exact routing, alternatives, tests, and sources are available in foldouts.