Quickstart · development build
Development build · one-track Max for Live tester
Exercise the actual Arrangement and review the processing load. A sampled test is not a show-stability guarantee.
This quickstart is based on the current development documentation. It is not a release announcement or a replacement for rehearsing and verifying your own setup.
Obtain the current device from CLR. Public download, pricing and licence details are not yet announced. Use a saved, backed-up rehearsal copy of your show Set in regular Ableton Live with Max for Live.
The test generates audio and MIDI. Its tone and notes can pass through your existing processing and output routing. Prepare safe monitoring levels and verify output destinations before starting; never begin an unattended test on a performance system.
No sender-bank helper devices are needed. Remove the temporary tester track after testing.
Press Analyze Set and wait for analysis to finish. Analysis is read-only. It inventories Arrangement clips, active live audio inputs, instruments, samplers and Drum Racks, including nested and return chains.
Read the list of detected and prepared targets. An external audio input is active when monitoring is In, or Auto while armed/implicitly armed. Instrument Track In also follows Live monitoring. Blocked or unassigned routes are named and prevent playback, rather than being silently counted as exercised. Correct the rehearsal Set’s intended state yourself, then analyze again.
Quick Scan plays selected real-time windows distributed across the timeline. Defaults are a five-minute wall-clock budget, 20 measured seconds per window, and eight seconds of lead-in. It can miss a problem between windows or omit effect/sustain history from before a seek.
Full Rehearsal starts at the beginning and plays the entire Arrangement in real time, plus an eight-second tail. A long show therefore takes its real duration to test.
Existing backing tracks, MIDI clips, automation, group/return/Main processing and routing run as authored. Generated tone supplies prepared live audio inputs; generated five-note chords or populated pad groups supply prepared MIDI targets. Rack selectors and their automation remain in control, rather than enabling every stored preset.
Review average and peak processing usage, then use View Results or Export JSON. Live’s processing telemetry is sampled about four times per second. Disk streams are an estimate of overlapping unmuted audio-clip tracks—not measured disk usage or Live’s disk-overload flag.
The report identifies the timeline windows and workloads actually prepared. Notes, zones, unusual MIDI remapping and song-specific kit banks may leave some instrument branches unexercised; validate those paths separately.
Press Abort when needed. The run also stops for recording, Arrangement override, transport interruptions, audio-engine stop, the CPU ceiling, or controller removal. Cleanup releases generated notes, silences tone, restores the original song position, insert marker and loop state, and leaves playback stopped. Check the cleanup status and actual output silence.
Remove the temporary test track when finished. Keep your report with the rehearsal evidence and do not overwrite the original show Set accidentally.
The latest nested/automated-rack extension has automated tests and package verification but still awaits Live host acceptance. Earlier disposable host testing covered a small number of audio/instrument targets; it is not qualification of your show, all targets or every Drum Rack. A successful Quick Scan does not prove the unplayed timeline. A full rehearsal covers the timeline, not every possible performer action or failure mode.
Interface images are static native-source previews with no measured values, not captured test sessions.