Performance system
  1. Overview
  2. Audio

Five RC-505mkII tracks as five WFS objects Keep looping on the hardware; spatialize each track independently.

The loop performer continues using the RC-505mkII normally. Each of its five tracks leaves through a separate mono output and becomes an independently movable sound object. Ableton is optional for this baseline.

Preferred solution 5 mono loop objects Ableton optional

Important: one RC track equals one spatial object. Multiple overdubs recorded into the same track remain combined.

Preferred: RC-505mkII owns the loops

Lowest disruption to the performance workflow and the simplest path to five separate sound objects.

RECOMMENDED BASELINE
audio control optional
Microphone and sources enter the RC-505mkII. Its five tracks leave through five separate outputs and become five independently positioned WFS objects. The loop performer controls the looper, the spatial operator controls the sound field, and Ableton is an optional capture or expansion stage.
Five parallel track paths preserve loop control on the RC-505mkII while the spatial operator controls position, movement, and level downstream.
What changes for the performer?

Almost nothing. Recording, overdubbing, stopping, undo, memories, faders, and effects remain on the RC-505mkII. The artistic constraint is that sounds needing different spatial positions must occupy different RC tracks.

Track and overdub are not the same thing

This distinction determines what the WFS operator can move independently.

Separate RC tracks produce separate WFS objects. Beat, bass, and voice overdubbed into one RC track produce one combined object.
Separate musical elements only remain separately positionable when they are recorded on separate tracks.

Direct Ableton option

Use Ableton as the loop engine when object count, routing, recording, and automation matter more than preserving the RC audio workflow.

MORE FLEXIBLE
audio control
Microphone and sources enter an audio interface and then Ableton Live. Separate Ableton loop tracks become separate WFS objects. A MIDI controller operates looping while a spatial operator controls object positions.
Each independently movable layer must be recorded into its own Ableton track, clip, or Looper instance. Repeated overdubs inside one Looper buffer still form one combined object.

Choose direct Ableton when

  • more than five independent objects are required;
  • detailed automation or recording is central;
  • a purpose-built MIDI control workflow is acceptable.

What it changes

Loop audio lives in Ableton rather than the RC-505mkII. The performer uses a MIDI controller or pedal for record, stop, undo, clear, and track selection.

Control ownership

The recommended system keeps three responsibilities separate.

Loop performer

Creates and performs loops; owns the musical timing and gestures.

Spatial operator

Positions, moves, balances, and recalls the WFS objects.

Audio system operator

Maintains isolation, gain, monitoring, synchronization, and recovery.

Technical details

Use these foldouts for patching, planning, and rehearsal. The preferred architecture above does not depend on reading them first.

Exact RC-505mkII output routing One track, output jack, interface input, and WFS object per row. 6 CHANNELS
RC track Output jack Interface WFS role
Track 1MAIN LInput 1Object 1
Track 2MAIN RInput 2Object 2
Track 3SUB 1 LInput 3Object 3
Track 4SUB 1 RInput 4Object 4
Track 5SUB 2 LInput 5Object 5
Optional live sourceSUB 2 R or mic splitInput 6Object 6 after isolation testing

Disable output stereo linking and exclude dry input, rhythm, master effects, and unintended tracks from each object output. Store the routing globally if memory changes would otherwise alter the patch.

When Ableton becomes useful Direct looping, optional recording, or a synchronized RC-to-Ableton handoff. 3 ROLES
Use Why choose it Main cost
Optional receiver / recorderThe RC remains the loop engine; Ableton records or routes the five incoming tracks.Additional computer and monitoring complexity.
Direct Ableton loopingIndependent object count scales with the session, interface, computer, and WFS renderer.Custom controller workflow and greater computer dependence.
Hybrid handoffA completed RC loop is captured into Ableton, freeing the RC track for new material.Clocked capture, mute/start handoff, latency compensation, and loss of RC control after commit.
Stereo and effects trade-offs Five separate loop objects require mono outputs. DECISION

The RC-505mkII provides three stereo output pairs. Unlinking them creates six mono outputs, which is appropriate when the WFS renderer creates the spatial image. If stereo delays, reverbs, panning, or stereo instruments are essential, test the presets in mono or choose a mixed layout such as one stereo object plus three mono objects.

Live microphone and monitoring Keep live sound isolated from loop capture and provide predictable low latency. SIGNAL PATH

A microphone split before the looper is safer than assuming the spare RC output can always provide an isolated dry source. Test INPUT THRU, dry-input routing, the performer headphone path, the WFS return, feedback, latency, and comb filtering with the actual performance setup.

Questions for the loop performer Confirm how the five tracks, effects, memories, and older loops are used artistically. 5 QUESTIONS
  1. Are sounds needing different positions already kept on different RC tracks?
  2. Which stereo effects or panning behaviors are essential?
  3. Must the live, unlooped microphone be a separate WFS object?
  4. Are completed loops still faded, undone, overdubbed, or effected later?
  5. Are more than five independently movable loops needed at the same time?
Questions for the venue Confirm the WFS ingest, object model, monitoring, and session contract. 7 QUESTIONS
  1. What analog or network inputs does the WFS chain accept?
  2. How many simultaneous objects are available?
  3. Does one mono input map directly to one object?
  4. Where are azimuth, elevation, distance, level, and automation controlled?
  5. Is Ableton required by the renderer or only optional?
  6. What sample rate, buffer size, channel naming, and session format are required?
  7. What monitoring and fallback paths are available?
Audio test plan Prove isolation and monitoring before adding Ableton handoff or complex control. 7 STEPS
  1. Confirm the contractRecord inputs, object count, renderer location, sample rate, buffer, output patch, and monitoring.
  2. Build the patchDisable stereo linking; assign one track to each jack; exclude unintended routes.
  3. Prove isolationRecord a unique spoken identifier on every RC track and check every downstream meter.
  4. Test real useRehearse memories, faders, stop, undo, overdub, effects, and the live microphone.
  5. Measure the pathCheck latency, gain, noise, feedback, comb filtering, and headroom.
  6. Add Ableton if justifiedPrototype capture, clock, loop boundary, muting, confirmation, and recovery.
  7. Freeze and documentSave routing, labels, gains, ownership, monitoring, and fallback procedure.
Audio sources Manufacturer and venue documentation supporting the architecture. 7 DOCUMENTS