ABLETON 12 SOUND DESIGN ATLAS

Performance & Live Set

Building a Session-view live set in Live 12 for a dark dub / trip-hop or techno show — scene design, launch modes and quantization, follow actions, Looper, dummy clips, Push macro racks, External Instrument and External Audio Effect for a TD-3 and eurorack, latency, crossfader and kill-EQ racks, a performance FX return, safety limiting, dub mixing moves, sync, set organisation and backups.

live setsession viewsceneslaunchquantizationfollow actionslooperdummy clipspushmacrosexternal instrumentexternal audio effecttd-3eurorackcv toolslatencybuffercrossfaderkill eqeq threereturnlimiterutilitydubtechnotrip-hoplinkmidi clockbackup

A live set is a sound-design problem with a time limit: every sound has to be reachable in under two seconds, survivable if you mis-hit, and interesting enough to improvise with for an hour. This page builds a Session-view set for a dark dub / trip-hop or slow techno performance (80–130 BPM) with a Push, a Behringer TD-3 and a small eurorack case alongside Live 12, but the structure is the same for a laptop-only set. The priorities, in order: nothing silent, nothing clipping, every move musical, and a way back from every move.

Concept

The set is a grid. Rows (scenes) are musical states: sections of tracks, or whole tracks. Columns (tracks) are roles: drums, sub, chords, dub FX, hardware, loops. The grid is launched, not played, so what can change between two scenes is decided in advance and how it changes is decided on stage with macros, the crossfader, sends and launch timing. Session view's job is to make the grid impossible to break: global quantization decides when things happen, clip launch modes decide what a pad press means, follow actions decide what happens if you do nothing, and a Limiter on the main decides the worst case.

Everything below assumes a 128–256 sample buffer at 48 kHz, Push used as both controller and (optionally) standalone backup, and a two-return minimum for dub work. All values are starting points.

Techniques

Scene design: tracks as columns, states as rows

Device: Session view · Level: essential · Genres: techno, dub, trip-hop

Decide the column roles first, then fill rows. For a dub/techno set a workable layout is 8–12 tracks: Kick, Drums (Drum Rack with layered chains), Sub, Chords/Reese, Texture, Vocal/Sample, Loops (Looper), TD-3 (External Instrument), Modular (External Audio Effect or audio in), Dummy FX, plus three returns. Each scene is a state of the whole set: "Track 2 intro", "Track 2 full", "Track 2 breakdown". Name scenes with the tempo and the key; Live 12 scenes carry a tempo and time-signature field and will change tempo when launched.

  1. One row per section, one section per 16–32 bars of intended playing time; the row-to-row change should be big enough to notice (new drum pattern + one new element) but not everything at once.
  2. Scene tempo: fill the tempo field only on the first scene of each track, so launching a mid-track scene after an unplanned detour does not snap the tempo.
  3. Leave one empty scene between tracks as a "stop" row, with Stop buttons in all clip slots: launching it stops everything on the next bar. Keep one at the very top as the panic scene.
  4. Colour by track: all scenes of one track in one colour; all clips of one role in one colour. Push shows both.
  5. Use Capture and Insert Scene while jamming to write a new row from whatever is currently playing. This is how the set grows during rehearsal.
For transitions between tracks, make a row that contains the outgoing drums with the incoming chords/texture. A two-scene crossfade (old drums + new harmony, then new drums) is the simplest musical transition and needs no crossfader.

Clip launch modes and quantization

Device: Clip launch panel · Level: essential · Genres: all

Global quantization (control bar) sets when launches happen. 1 Bar is the default for scene launches in techno; dub work wants 1/4 or 1/8 for fills and stabs; one-shots want None. Per-clip launch mode decides what a pad press is: Trigger (press = play from start), Gate (plays while held), Toggle (press to start, press to stop), Repeat (retriggers at the quantize value while held). Per-clip quantization overrides the global one.

Clip roleLaunch modeQuantizeLegatoWhy
Drum loops, chord loopsToggle1 Bar (global)OnLegato keeps the playback position when switching variations on the same track
Stabs, vocal shots, FX hitsTrigger1/8 or 1/16OffLands on the grid but feels played
Risers, reverse cymbalsTrigger1 BarOffMust start exactly one bar before the drop
Noise washes, held texturesGateNoneOffSounds only while the pad is held
Drum fills, stutterRepeat1/16 or 1/32OffHold for a roll at the quantize rate
Dummy automation clipsToggle1 BarOnAutomation moves land on bar lines
Live 12 Legato only works between clips on the same track. A drum variation on a different track will start from its own beginning. Keep all variations of one role on one track.

Follow actions for variation and safety

Device: Clip Follow Actions, Scene Follow Actions · Level: intermediate · Genres: techno, dub, IDM

Follow actions make a clip (or, since 11.1, a scene) do something after a set time: play the next clip, jump back, pick one at random. Two uses on stage: controlled variation (four hat clips cycling with Any at 60% / Play Again at 40%) and safety (a fill clip that automatically returns to the main loop with Previous after 1 bar so a mis-hit never leaves the fill running).

SettingVariation useSafety use
Follow Action TimeLinked (to clip loop length)1 bar, unlinked
Action A / chanceAny, 60%Previous, 100%
Action B / chancePlay Again, 40%—
Clips in the group4–8 hat or percussion variations on one track, same loop lengthFill clip directly under the main loop
Scene follow actions: a "breakdown" scene set to go Next after 8 bars means the set never gets stuck in a breakdown if you are busy on the modular. Set the chance to 100% and the time unlinked.
Random variation at the clip level hides the fact that a set is a grid: the drums are never exactly the same two bars in a row, and the variation costs no attention.

Looper as a live resampling instrument

Device: Looper · Level: intermediate · Genres: dub, trip-hop, ambient, techno

Looper records from any track (its own input, a return, the main) with tempo-aware length and overdub. In a dub set it captures a delay tail or a modular phrase, loops it, and lets you halve-time it, reverse it or feed it back into the returns. Keep it on its own audio track with input from a group or from Resampling.

  1. Looper on an audio track, Monitor In, Audio From the modular channel or Resampling to capture the whole mix.
  2. Song Control None (the loop never starts/stops the transport); Tempo Control Follow song tempo; Quantization 1 Bar; Record length fixed at 2 or 4 bars so a late press still gives a bar-aligned loop.
  3. Map the big transport button to a Push pad (Cmd/Ctrl+M to enter MIDI map mode): press = record, press = play, press = overdub. Map Speed (×2 / ÷2) and Reverse to two more pads.
  4. Feedback under 100% (80–90%) for overdubs that decay like a tape loop; 100% to stack.
  5. Drag the loop out of Looper into a clip slot (the "Drag me" area) to keep it as a clip for later in the set.
Looper does not follow a tempo change after recording unless Tempo Control is set to follow; and a loop recorded during a scene with a different tempo will be re-stretched with audible artefacts. Record loops after the tempo settles.

Dummy clips: automation you can launch

Device: Audio track with clip envelopes · Level: intermediate · Genres: all

A dummy clip is an empty audio clip whose only content is device-parameter envelopes. Put it on an audio track whose devices process audio routed in from another track, and launching the clip launches the automation: a 4-bar filter sweep, an 8-bar delay-feedback rise, a one-bar stutter. It turns every arrangement-style automation into a Session-view pad.

  1. Create an audio track "Dummy FX", Monitor In, Audio From the source track (Post FX). Set the source track's Audio To this track (or keep its own output and use the dummy track as a parallel path).
  2. Put the devices on the dummy track: Auto Filter, Beat Repeat, Redux, Echo. Record a few seconds of silence to get a clip, or drag any short clip in and Clip Gain −inf.
  3. In the clip's Envelopes box choose the device and parameter, draw the move. Loop length = the move's length. One clip per move; name them by the move ("filter down 4b", "stutter 1b").
  4. A "neutral" dummy clip (all envelopes flat at default) is the reset: launch it and everything returns.
  5. Launch mode Toggle, quantize 1 Bar, Legato on so moves chain seamlessly.
Because the dummy track is a normal audio track, its clips can also be launched by follow actions and by scene launches; a scene can therefore contain "the breakdown" and "the 8-bar filter rise into the breakdown" as one row.

Racks with macros on Push: eight knobs per role

Device: Instrument Rack, Audio Effect Rack, Push · Level: essential · Genres: all

On Push, a selected track shows its rack's macros on the eight encoders. Design every performable track as one rack with eight macros ordered from most-used (left) to least. Use Macro Variations for stored states (intro / full / breakdown) and macro randomisation with limited ranges for variation on textures. The Performance rack page has the general template; here is the per-track version for a dub chord track.

  1. Group the track's devices into one rack. Map the macros; set every macro's min/max range so the full knob travel is useful (no dead zones).
  2. Sends can be mapped to macros only via a MIDI mapping or a Max device; the clean solution is to put Send A/B on Push's mixer page instead and keep the macro list for device parameters. The rack above assumes a mapped send for illustration; in practice use the Push Mix page for sends.
  3. Store Macro Variations for each section. Launch a variation from Push with the variation buttons or map them to pads.
  4. Use the same macro order on every track (Filter, Res, Delay, Verb, Drive, Low Kill, Hi Kill, Decay) so the hands know where things are without looking.
Muscle memory is the real instrument. A consistent macro layout across tracks is worth more than any individual sound.

External Instrument, External Audio Effect and latency for the TD-3 and eurorack

Device: External Instrument, External Audio Effect, CV Tools · Level: intermediate · Genres: acid, techno, dub

External Instrument sends MIDI out and brings audio back inside one device, so the TD-3 behaves like a plug-in: MIDI clips sequence it, the audio returns on the same track and Hardware Latency compensates the round trip. External Audio Effect does the same for a eurorack effect path (send a track out to a filter or a modular delay, bring it back). CV Tools adds CV Clock Out, CV Triggers and CV Instrument for a DC-coupled interface.

  1. TD-3: set it to MIDI clock sync and MIDI channel 1 (or whatever the device menu gives you). External Instrument: MIDI To the interface port and channel; Audio From the interface input the TD-3 is plugged into. Gain to taste, HW latency: measure once with a click (see latency technique) and enter the value.
  2. For the TD-3's own sequencer instead of MIDI clips: skip External Instrument, use a plain audio track with Monitor In and send MIDI clock from Live (Preferences → Link, Tempo & MIDI → Sync out on the TD-3's port). The TD-3 starts on Live's transport start.
  3. Modular voice: audio track, Monitor In, Audio From the module output. If the interface is DC-coupled (ES-8/ES-9 class), add CV Instrument on a MIDI track to send pitch and gate, and CV Clock Out on an audio track routed to a spare output for clock.
  4. Modular as effect: External Audio Effect on any track, Audio To a spare output, Audio From the return input. Dry/Wet under 100% keeps a dry path; the device has a phase invert for cases where the module flips polarity.
  5. Wrap every hardware track in an Audio Effect Rack with an EQ Eight high-pass (60–80 Hz) and a sidechain Compressor from the kick, exactly as for an internal bass. The TD-3 can produce more sub than the set's actual sub.

Latency and buffer. The buffer decides how late the hardware comes back and how safe the CPU is. 128 samples at 48 kHz is 2.7 ms per direction and comfortable on a modern laptop with a 10-track set; 256 is the safe default when the set has plug-ins or Hybrid Reverb on returns. Measure, do not guess.

SettingValueWhy
Buffer size128–256 samples128 if CPU meter stays under 60% on the heaviest scene; otherwise 256
Sample rate48 kHz (match the interface)Avoid resampling in the driver
Driver Error CompensationMeasured (loopback test)Live's Audio preferences include a latency test: record a loopback, read the offset, enter it
Reduced Latency When Monitoring (Options menu)On for hardware tracksRemoves delay compensation on monitored tracks so hardware feels immediate; other tracks stay compensated
Delay Compensation (Options menu)OnKeeps lookahead devices aligned; never turn it off on stage
External Instrument HW latencyMeasured per device, typically 1–5 msCompensates the synth's own MIDI-to-audio delay
Multicore / Audio engineOnDefault; keep it
A set-wide latency budget: buffer round trip (≈5.5 ms at 128) + interface converters (≈1 ms) + the longest lookahead on a monitored track (0 ms if you follow the rule above). Anything under 10 ms is unnoticeable on hands; 15 ms is noticeable on the TD-3 accents against the kick.
External Instrument and External Audio Effect monitor through Live, so the whole chain's latency is the buffer round trip plus any lookahead devices on that track. Do not put Multiband Dynamics, Limiter or lookahead Compressor/Gate on a hardware track. See Hardware & modular integration.

Crossfader A/B and kill-EQ racks

Device: Crossfader, EQ Three, Audio Effect Rack · Level: essential · Genres: techno, dub, DJ-style sets

Every track has an A/B/off assignment under the crossfader. Assign the current track's drums and bass to A and the next track's to B and the crossfader becomes a DJ transition. Combine with a kill-EQ rack on each track (EQ Three with its Low/Mid/High kill switches) for the classic dub and techno mixer moves: drop the lows of the outgoing track, bring the new lows in, then cross.

  1. Put the kill-EQ rack last on every track (after the instrument rack). Save it as a default preset and drop it onto new tracks.
  2. Crossfader: assign tracks per transition by clicking A or B in the mixer; the crossfader is in the main track's mixer section. Right-click the crossfader to pick a curve; a slow fade curve suits dub, a constant-power one suits techno.
  3. Map the crossfader to Push's touch strip or a fader on a second controller. Map the Low Kill macros of the two tracks to pads.
  4. Transition recipe at 1 Bar quantize: launch the new scene with new drums muted via Low Kill; cross to 50%; kill the old low; un-kill the new; cross fully; stop the old.
Two full-range tracks summed at 50% crossfade have 3–6 dB more low end than either alone. Killing one set of lows before crossing is what keeps the limiter out of the picture during a transition.

The performance FX return

Device: Return track, Echo, Hybrid Reverb, Auto Filter · Level: essential · Genres: dub, dub techno, trip-hop

Dub mixing lives on the returns: a delay and a reverb that are instruments, with their feedback, filter and send amounts under the hands. Return A is the dub delay (see Dub delay send rack), Return B the reverb, Return C a "destroyer" (Beat Repeat, Redux, Roar, filter) that any track can be sent to for a bar. Returns also send to each other: A into B for delays that bloom into reverb.

ReturnRests atPerformed withSafety
A: dub delayFB 55%, LP 4 kHzFB to 90–110% for a self-oscillating throw, LP down to 800 Hz as it buildsLimiter or Compressor on the return; FB macro max 110%, never unlimited
B: reverbHybrid Reverb Dark Hall 3 s, Pre-delay 20 msFreeze button mapped to a pad; Decay to 20 s for a washHP 250 Hz, LP 6 kHz on the return
C: destroyerAll neutralOne macro at a time, one bar at a timeUtility Gain −3 dB; Beat Repeat Chance never saved above 0
Return A to Return B send at −12 dB and Return B to A at −inf: a one-way path so the delay feeds the reverb but the reverb cannot feed back into the delay and run away.

Redundancy, safety and backups: Limiter on the main, Utility mute, panic scene, fallback set

Device: Limiter, Utility, Glue Compressor · Level: essential · Genres: all

The main chain is not a mastering chain, it is insurance. Glue Compressor for a little cohesion, Utility as a one-button mute mapped to a hardware button (not a mouse click), Limiter at −1 dBTP ceiling to catch the one time the delay feedback goes past 100%. Nothing on the main should need adjusting during the show.

ItemSettingWhy
Limiter ceiling−1.0 dBTPHeadroom for the venue DAC; the FOH engineer limits again anyway
Limiter GR during normal playing0–2 dBIf it is working all night, the set is mixed too hot; drop Utility Gain
Utility MuteMapped to a physical button and to the panic sceneInstant silence that does not stop the transport
Panic sceneTop row: all Stop buttons plus the neutral dummy clipOne launch resets automation and stops clips on the bar
Main output level−6 dB peak target into the venueKeeps the house limiter idle
Spare setPush 3 standalone with the same set, or a stereo stem of the set as audio clips on one trackIf the laptop dies, the show continues

Set organisation and backups. The set that leaves the studio must be a self-contained project. Collect All and Save, then open it from a different folder on a different drive to prove it. Keep a frozen fallback and a stems fallback. Practise with the Push disconnected once.

  1. Collect All and Save (File menu) the day before. Check the File Manager for missing files and for files outside the project.
  2. Freeze CPU-heavy tracks that are not performed (textures, pads). Keep the unfrozen set as a separate version.
  3. Export a stereo stem of every track's full-length audio into a "fallback" set: one audio track per song, scene launches only. If a plug-in fails on stage, this set plays.
  4. Save the set as a template (Preferences → File/Folder, or File → Save Live Set as Template) once the routing and returns are stable; every new set starts from it.
  5. Copy the project folder to a USB stick and to the Push 3 standalone (if used); open both once to verify.
  6. Live writes automatic backups into the project's Backup folder; keep it but do not rely on it on stage.
  7. Pre-show checklist: audio preferences loaded, buffer size, sync outputs enabled, MIDI mappings present (they live in the set), crossfader at the right side, Return C macros at neutral, Limiter on.
Name every clip by its function and every scene by section + key + tempo. On Push you read names, not colours, when the lights are off.
Never use Space as the panic button; it stops the transport, which stops the hardware clock and re-starts every clip from the top. Mute the audio, keep the transport running.

Dub mixing moves and transitions

Device: Sends, Echo, kill-EQ, Looper · Level: intermediate · Genres: dub, dub techno, trip-hop

A list of moves that read as music, each one reversible within a bar. They assume the returns and kill racks above; quantize 1/4 for the throws, 1 Bar for the transitions.

  1. Snare throw. Send A on the drum track from −inf to 0 dB for one hit, back to −inf: one snare repeats in the delay. On Push: hold the send encoder, flick, release.
  2. Chord throw with filter ride. Send A up for one bar, then ride Return A's LP macro down while the feedback rings out.
  3. Delay feedback bloom. Return A FB macro to 95% for two bars with nothing new sent; the previous material grows. Bring FB down before the Limiter engages.
  4. Low kill breakdown. Low Kill on the kick and sub for 4–8 bars; everything else keeps going; release both on a downbeat. This is the cheapest drop in the book.
  5. Mute-stab. Utility Mute macro on the chord track hit in rhythm (Gate-mode dummy clip or a pad in Repeat mode).
  6. Loop and leave. Looper grabs 4 bars of the current mix; stop every clip; the loop is now the only thing playing; bring the next track's elements in over it; stop the Looper.
  7. Reverb freeze transition. Freeze Return B's Hybrid Reverb on a chord, kill the old track, launch the new scene under the frozen wash, unfreeze.
  8. Half-time drop. Scene with the same drums in a half-time pattern plus a dummy clip pushing Return C's Redux downsample for one bar; back to the full scene on the next bar.

Sync: Link, MIDI clock and CV clock

Device: Preferences → Link, Tempo & MIDI; CV Clock Out · Level: intermediate · Genres: all

Three clocks, from most to least stable: Ableton Link for another laptop, iPad or a Link-enabled hardware box; MIDI clock out for the TD-3 and any MIDI-synced pedal; CV Clock Out (CV Tools, DC-coupled interface) or a MIDI-to-CV module for the eurorack. Live is always the master on stage; let nothing clock Live.

TargetMethodSettingsOffset
Second Live / tabletLink (Preferences → Link, Tempo & MIDI)Start Stop Sync on if both should transport togetherNone needed
TD-3MIDI clock: Sync out on its port, Clock type PatternTD-3 in MIDI sync mode; Live sends start on playSync Delay in the MIDI port list, typically −2 to −8 ms to pull the TD-3 ahead
EurorackCV Clock Out on an audio track → DC-coupled out, or MIDI clock → MIDI-to-CV moduleRate 1/16, Offset to taste, Reset on startTrack Delay on that track in negative ms to compensate module trigger latency
Hardware delay / pedalMIDI clockSame port as the TD-3 if daisy-chainedUsually none
MIDI clock jitter is real and audible on 16th-note hats from a hardware sequencer. For the TD-3 it is fine; for eurorack drums prefer CV Clock Out, which is sample-accurate because it is audio.

Settings / targets

Starting points for the set as a whole, for a dark dub / trip-hop or slow techno show. Adjust the buffer and quantize columns first when switching genres.

ItemDub / trip-hop (80–100 BPM)Dub techno (118–125)Techno (128–135)Why
Global quantize1/4 (throws), 1 Bar scenes1 Bar1 BarSlower tempo = more room for off-grid moves
Buffer128128–256256Techno sets tend to carry more plug-ins and returns
Scenes per track3–44–65–8More sections at faster tempos
Return A delay time3/16 + 1/4, FB 55%3/16 dotted, FB 65%1/8, FB 40%Dotted times give the dub skank; straight times stay tight
Return A LP at rest3 kHz4 kHz6 kHzDarker delays for slower music
Reverb decay at rest4–6 s3–5 s1.5–2.5 sSpace scales with the gaps in the arrangement
Sidechain on returns4 dB6 dB8 dBFaster music needs the returns out of the kick's way
Main Limiter GR0–1 dB0–2 dB1–3 dBInsurance, not loudness
Main peak into venue−8 dB−6 dB−6 dBHouse system does the loudness
TD-3 roleDub bassline, HP 60 Hz, heavy delay sendSparse acid accentsMain acid line, Roar afterSame hardware, different band ownership
Looper length4 bars4 bars2 barsGrab length matches phrase length
Follow action variationHats: Any 40%Hats + perc: Any 60%Hats, perc, stabs: Any 60%Density of random variation grows with tempo

Timing reference: at 90 BPM a bar is 2.67 s, at 120 BPM 2 s, at 130 BPM 1.85 s. Every automated move in a dummy clip should be a whole number of bars so Legato chaining stays on the grid. See BPM to ms and Genre tempo map.

Common mistakes

Related