3.1 Pre-produced "top loops"

The split he committed to: backbone live, groovy layer baked. Kick and snare come from the mic and get live-looped. Hi-hats, percussion, crashes, cymbals are pre-produced in Ableton and triggered from the clip grid.

• What lives in the top layer: hi-hats, percussion, crashes, cymbals - the groovy layer on top of the live-looped kick+snare backbeat
• Where they were built: pre-produced in Ableton, not live-looped
• Why this split: tight electronic groove + ghost notes + unfamiliar stages = impossible to keep tight live with beatbox alone
• How he frames it: "I treat them like a drum machine - I picked my poison"

"I treat them like a drum machine - I picked my poison." - Kristof7s, on accepting baked top-loops over live-looping everything

3.2 Step Dial cycles preset packs

One Step Dial widget walks the top-loop column through genre-shaped packs. Each click of the dial swaps the loaded clip set for a different stylistic family, so the same button column can mean four different drum personalities depending on dial position.

The Step Dial is the macro-level genre selector - everything else (live kick/snare, Looperator, fills) stays the same; the dial just retargets what flavor of top loop sits underneath the performance.

3.3 Looperator on the drums - the #1 favorite plugin

Sugar Bytes Looperator sits on the drum bus and turns linear loops into generative mutations - re-slicing, auto-groove, half-time conversion, jungle patterns. Kristof calls it his single favorite plugin inside the Loopy ecosystem.

"There should be an individual tutorial for Looperator, because what you can do with that effect inside of Loopy is the best thing ever." - Kristof7s, naming his desert-island plugin

3.4 Amen breaks + fills - "I'm the drummer at the same time"

Where the top-loop column handles groove, a second arsenal handles drama and transition: Amen breaks, tom rolls, manual snare slices, and risers. None of them are played on a drum pad - they all live on buttons.

"I'm the drummer at the same time - without playing the drums manually." - Kristof7s, on solving the one-person-band problem with buttons

3.5 Session start - 3 methods to get the train moving

Every set has to begin somewhere - first downbeat, first loop, first feel. Kristof has three different starts tuned to three different moods. None of them is "press play".

   METHOD                  TRIGGER                    FIRST SOUND        WHAT STARTS                LOOP CLOSES ON
  +----------------------+----------------------+------------------+----------------------+----------------------+
  | KICK-FIRST           | audio threshold        | kick from mic    | session + metronome  | downbeat             |
  | HARMONY-FIRST        | tap-to-start           | piano (1 cycle)  | metronome in ear     | end of harmonic cycle|
  | AUTO-GROOVE          | Looperator engaged     | bare kick + groove| Looperator from t=0 | with first phrase    |
  +----------------------+----------------------+------------------+----------------------+----------------------+

3.6 Signal flow synthesis - how the drum brain actually wires up

Putting all five sub-mechanisms in one picture: the live backbone, the baked top, the Looperator mutator, the fill arsenal, and the session-starter.

                              KRISTOF7S DRUM ENGINE
   ___________________________________________________________________________

      MIC (kick + snare from mouth)
         |
         v
   [ LIVE LOOP - kick+snare backbone ]----+
                                          |
      STEP DIAL  -->  [House|DnB|Swing|Aggressive|...]  selects pack
                              |
                              v
   [ PRE-PRODUCED TOP LOOP COLUMN ]  (hi-hats, perc, crashes, cymbals)
                              |
                              +--------+
                                       |
                                       v
                              [  LOOPERATOR  ]  re-slice / auto-groove / half-time / jungle
                                       |
                                       v
                              [ DRUM BUS SUM ]
                                       |
              +------------------------+------------------------+
              |                                                 |
       +--------------+                                  +--------------+
       |  AMEN BREAKS |  on buttons                      | FILLS+RISERS |  on buttons (toms, snare slicer, buildups)
       +--------------+                                  +--------------+
              |                                                 |
              +------------------>  TO MAIN BUS  <--------------+

   SESSION STARTERS:
      [1] Kick-first      threshold detect -> start + metro -> close on downbeat
      [2] Harmony-first   tap-start -> metro -> 1 piano cycle -> close
      [3] Auto-groove     Looperator on from t=0 -> bare kick already grooves
    

Key takeaways - the drum-engine philosophy in 5 lines

• Don't loop everything live. Bake the layer that demands tight ghost-note timing; loop the layer that gives the show its identity (kick/snare from your own mouth).
• One column, many genres. A Step Dial in front of the top-loop column gives a single button row five drum personalities.
• Looperator is the multiplier. A linear loop becomes a generative loop the moment Looperator is on the drum bus.
• Every fill is a button, not a pad. Amen, toms, snare slices, risers - all on buttons in various lengths so you grab the one that fits the bar count.
• Three starts, three moods. Kick-first for energy, harmony-first for statement, auto-groove for the lazy-but-impressive open.

The bass architecture in one picture

PURPLE BASS LOOP   <- single source, recorded once in Loopy
       |
       +---> [ BUTTON A: NEURO chain (4-6 FX) ]   ---+
       |                                              |
       +---> [ BUTTON B: COLOR resonator (chord) ]  --+--> OUT
       |                                              |
       +---> [ GRAY: resample bass to new clip ]    --+
       |                                              |
       +---> [ XY PAD: noise synth, tremolo+bandpass ]+

  Combine A + B independently  =>  4 flavours:
   ( clean )   ( color only )   ( neuro only )   ( color + neuro )

One button, 4-6 FX, instant wobble

• A single Loopy button arms a chained stack of 4-6 effects sitting after the purple bass loop. Press = enable all; release = disable all (momentary). The same button can be configured tap = toggle, hold = solo.
• The chain turns any bass loop into a distorted wobble. The source does not have to be neuro-shaped; the FX stack does the shaping.
• Core mechanism = intermodulation. When bass and melody play together, the bass overpowers the melody; when the bass drops, the melody re-emerges through the leftover distortion. This is the entire reason neuro feels so "alive" under a vocal or lead.
• Loopy-specific shortcut: the loop is the source. You skip the synth stage entirely. There is no oscillator to design, no neuro reese to construct - the recorded bass loop feeds straight into filter -> distortion.

Reference chain (full recipe in Part III)

The "Neuro Bass Generator 2000" is one Loopy button toggling this 7-stage chain on/off:

Bass loop (purple)
  -> [1] TB Equalizer (+12 dB on 200-2000 Hz band)  or  Mela Volume module
  -> [2] BLEASS Filter (notch, LFO on cutoff, random mode)
  -> [3] FAC Clipper (hard, ~3 dB clip)
  -> [4] BLEASS Filter (bandpass, different LFO rate, slower)
  -> [5] Fosfat (waveshaper character)  or  Turnado distortion preset
  -> [6] BLEASS Multiband Compressor (OTT-style, all frequencies forward)
  -> [7] FAC Clipper or KNOCK (output taming, ceiling -0.3 dBTP)

CPU notes from Kristof's stage rig

If you can only afford one cut on a tight iPad: drop the multiband and lean on the second clipper plus a steeper Fosfat.

Bass-as-chord, via a tuned resonator

• A resonator is inserted on the bass bus, tuned to a chord = root + 3rd + 5th. The bass then sings like a held chord while still pumping at the original bass rhythm.
• The resonator and the neuro chain are toggled independently. That independence is the design point: one purple loop, two binary switches, four playable states.
• This is the colour of the section name. "Color Bass" is not a genre label here; it is the specific trick of pitching a tuned resonator into the bass path.

Four flavours from one loop

Gray = a frozen copy of what the bass just did

• The gray buttons resample the bass - they capture the current output of the purple loop (after any FX that are armed at that moment) and store it as a new playable clip.
• Gray is wired exclusive to purple. When a gray clip fires, the purple loop stops. This is a Loopy-Pro group-exclusivity setup, not a manual mute.
• The point is performative: he can grab a particular flavour (say, "purple + neuro + color, bar 3") into a gray slot, then drop purple out from under it. The frozen variant keeps singing while the live bass is repurposed.

One brown pad, two axes, immediate texture

• A dedicated XY pad in the template is brown colour-coded - a distinct band in the visual grammar of his template so the eye lands on it instantly.
• Axes are mapped to the noise-synth engine:
  • X = tremolo rate (how fast the texture pulses)
  • Y = bandpass center (where the noise sits spectrally)
• Touch unmutes, release stops. The pad is gestural - sound exists only while a finger is on it. No latching, no fade tail.
• Underneath the pad: Dragonfly drives the tremolo engine that XY is steering. Dragonfly is the modulator; the pad is the human surface.

Where this goes next

The overview above is the map. The full method - sound source design, filter movement, distortion staging, the EQ-distortion interaction, and six complete recipes (Classic Neuro, Freeze Neuro, Color + Neuro combo, Reese Pad ambient, Mela mega-chain) - lives in Part III: Bass Design Laboratory. That is where the concrete plugin settings for your arsenal get spelled out.

The four facts of this layer

Kristof states the section as four bullets. Each one is small in print and large in consequence.

• Every color channel can route through track effects or bypass them. The decision is per-channel and live-switchable.
• Channels not going through track effects sit "more in background". This is the foreground/background split.
• Buses-to-buses routing: a track-FX bus can feed another bus, not just the master. This is the move that enables CTZ (Chapter 7).
• Stacked Looperators: a Looperator on top of a Looperator. Stacking presets instead of varying from the original gives him "a variation of a variation".

How the routing actually flows

Each color channel makes one boolean decision: through the track-FX chain, or straight to a bus. Both paths can co-exist live. Buses can in turn feed other buses, which is what later lets the drum bus and the mix bus share the clip-to-zero load (-20 dB each, see Section 7).

• Foreground path: channel -> TFX chain -> bus -> (optional) another bus -> master.
• Background path: channel -> bypass -> bus -> master. Drier, less present, sits behind.
• Bus-to-bus chain: a track-FX bus output is itself a source for another bus's processing. Enables the CTZ drum-bus + mix-bus split.

[COLOR CHANNEL]      foreground                  background
                |                            |
        TFX BYPASS  ?  ----- bypass ON ---------+
                | (off)                      |
                v                            |
        [TRACK-FX CHAIN]                       |
        Looperator / EQ / saturation / etc.  |
                |                            |
                v                            v
              [BUS]  ----- bus-to-bus routing ----->  [OTHER BUS]
                |                                              |
                +-------------------- MASTER <-----------------+
              (CTZ stage lives here - Sec. 7)

Looperator - the #1 favorite

Kristof names Looperator (Sugar Bytes, full price 29,99 EUR) as the #1 favorite plugin in the entire rig. He says it deserves an individual tutorial. It is the beat-slicer, the auto-groover, the fills-machine, the jungle-converter, and on this layer it also gets stacked on top of itself.

"There should be an individual tutorial for Looperator, because what you can do with that effect inside of Loopy is the best thing ever." on Looperator - Section 3 (drums), reinforced in Section 5

"Variation of a variation" - the stacking mechanic

The default Looperator use is to load a preset and toggle through its variations. Kristof's move is the next layer: instead of always varying from the original loop, he stacks a second Looperator after the first one. The second instance can never know what the first one will spit out, so the result is non-repeating.

[DRUM LOOP]
     |
     v
[LOOPERATOR A]  preset "Auto-Groove"   --> variation 1, 2, 3...
     |
     v
[LOOPERATOR B]  preset "Half-time Jungle"  --> variation 1, 2, 3...
     |
     v
A.var x B.var matrix = "variation of a variation"
     |
     v
[BUS]  ---->  CTZ drum bus (Sec. 7)

• The standard Looperator workflow is load preset -> switch variations. Two presets stacked = the variation grid is multiplied.
• The stack is order-sensitive: half-time on top of auto-groove is not the same as auto-groove on top of half-time.
• Same trick works on post-FX neuro bass: see Part III "Stack Looperator on processed output - chop the neuro into rhythmic patterns" (Recipe Index row 28).

Foreground vs background by routing

Your-rig map: do you already own this?

The two ingredients of this section: a router that allows per-channel bypass + bus-to-bus (any modern host - Loopy Pro, AUM, Drambo all qualify) and Looperator itself. You already own Looperator, so the stack is a direct copy.

What this layer unlocks downstream

This section is short on the page and load-bearing for the rest of the doc. Three later mechanics depend directly on the bus-to-bus + bypass-per-channel + Looperator-stack pattern set here.

The mixer layer in the wild

whf-J9 01:38:30 - Loopy Pro AUv3 mixer with audio inputs and colored bus columns. The TFX layer lives on these columns: every color decides whether it routes through its chain, every bus can feed another bus, and Looperators stack inside the chains. This is the entire Section 5 in one shot.

Section distilled

The tool

A free LFO/envelope-shaper AUv3 from Caelum Audio. Kristof's stack proves the point: production-grade pump does not require a paid sidechain compressor. He pays for nothing here and ships it on stage.

How the multi-instance trick works

• 2-3 Flux Mini 2 instances sit ready in the template, each with a stored envelope shape matched to a specific kick pattern.
• When Kristof changes the drum pattern, the sidechain preset auto-switches with it - the pump-curve always lines up with whatever the kick is doing at that moment.
• This is currently tied to fixed kick patterns, not to MIDI input. The duck shape is baked into the envelope.
• Wishlist (Kristof + Michael confirmed feasible): MIDI-triggered sidechain, where the duck fires off an actual kick MIDI note instead of a stored shape. Future feature, not yet shipped.

The five sidechain presets

One preset per kick pattern. The drum pattern picker effectively becomes a pump-style picker.

The probe procedure

1. Insert Flux Mini 2 in the signal chain after the plugin you are testing.
2. Set the display to 1/8 note resolution on the grid.
3. Play a drum loop through the chain. A clean kick should land exactly on the downbeat.
4. Read the shift: any visible offset from the downbeat is the latency that plugin introduces.
5. Switch to 1/16 grid divisions for finer resolution - the ms value is then estimable from the BPM.
6. Compare against the target: under 10-12 ms total across the whole chain. Above that, the rig starts feeling sluggish on stage.

BPM to ms cheat (1/16 grid)

A shift of less than 1/8 of a 1/16 grid square at 120 BPM is roughly in the 10-12 ms budget. Rule of thumb: if the eye can see the offset, you are probably already past the target.

Why this matters in Kristof's rig

He runs the whole show off an iPad. Every plugin in the chain spends a few ms of his latency budget. Flux Mini 2 turns a normally invisible spec sheet number ("plugin X reports N samples of latency") into a live, visible offset on a grid - which is what your hands actually feel when you trigger a loop. The 10-12 ms total ceiling is the gate; anything slower than that and the rig stops feeling playable.

What it does

A wavetable synth that Kristof treats as hardware Serum - but where the Serum logic gets pushed out into the keyboard layout itself. The patch he plays from is built so the keys do three different jobs depending on which octave you hit.

• Wavetable engine - "like hardware Serum". Full wavetable scrubbing on the front panel, no laptop required.
• One octave = same bass note, different textures - the patch is layered so a single octave gives you the same pitch with different wavetable positions / samples mapped key-by-key. Walk up the white keys, same root, different timbre. Loopy records the texture you want, on the pitch you want, in one gesture.
• First octave = chords correlated to the key - the bottom octave is not single notes. Each key fires a full chord that fits the session key. One-finger harmonic pads.
• Chaos Pad on the front panel for real-time manipulation - the XY surface drives wavetable position, filter, FX in performance. This is the live-mangling layer that you cannot get from an AUv3 synth without dedicating an external MIDI controller.

How he connects it to the iPad

This is the design choice that defines the whole hybrid rig. Read it twice:

• Connected via audio - NOT MIDI to Loopy.
• Loopy records the audio output of the Modwave, then processes it further - clip reverse, Looperator slicing, Turnado mangling, the whole AUv3 chain downstream.

 Modwave keys + Chaos Pad
 (wavetable + chord layer + texture layer)
            │
            │  AUDIO OUT (1/4" jacks, no MIDI cable to iPad)
            ▼
 iPad audio interface input
            │
            ▼
 Loopy Pro input channel  ─►  RECORD into clip
            │
            ▼
 AUv3 chain: Looperator / Turnado / Flux Mini 2 / CTZ bus
            │
            ▼
 Loopy mixer + master + speakers
    

Why this matters: Loopy never has to sequence the Modwave, the Modwave never has to obey Loopy. They run on independent timing surfaces - Kristof's hands handle the sync. The Modwave is treated like a vocal mic that happens to be a synth: you sing into it, Loopy captures the take. No DAW transport coupling, no MIDI clock drift, no patch-change latency.

The three-zone keyboard map

One patch, three jobs - that is the unlock. Most iPad-only setups need three separate AUv3 synths or three MIDI tracks to do what one Modwave patch does in hardware:

Why hardware, not an AUv3

Kristof owns a maxed-out iPad and uses heavy AUv3 stacks elsewhere in the rig. The Modwave stays because it solves three things software cannot match on this iPad:

• CPU offload - wavetable synthesis happens in the Korg's DSP, not in Loopy's audio thread. The iPad keeps its headroom for Looperator, Turnado, KNOCK, FAC Clipper, the CTZ bus chain.
• Physical Chaos Pad beats any on-screen XY pad - it sits next to the keys, you hit it without looking away.
• 37 keys = real two-hand chord work, the patch layout is wired to that range. No iPad on-screen keyboard, no compromise MIDI controller.
• Audio path means the Modwave occupies an interface input, not a Loopy plugin slot. The plugin slots stay free for FX.

Your-rig equivalent: how to copy this without a Modwave

You do not own a Modwave (it is in Part II Substitutions as an "edge case" - Kristof's hardware is yours to replace, not to mimic 1:1). The substance to copy is the audio-not-MIDI philosophy and the three-zone patch layout. Your arsenal can rebuild it on the iPad:

What gets lost if you cut the Modwave from your study of his rig

Read this section through the lens of the audio-not-MIDI design choice, not the brand name. The point is not "buy a Modwave". The point is:

• Synths are audio sources for Loopy, not slaves of it.
• Hardware is a way to offload CPU and offload patch logic - the patch already knows what each key does, the iPad does not have to compute it.
• The Chaos Pad gesture gets printed into the clip - performance, not automation.
• One physical object can serve three musical roles if the patch is designed for it.

The Modwave is the proof that Kristof's rig is not iPad-purist. He is happy to lift a function off the iPad onto a piece of hardware when the gain is clear - CPU, tactile control, three jobs from one object. The rest of the rig is iPad-heavy because the rest of the rig does not benefit from hardware. The Modwave does.

Current minimal rig (post-streamlining)

Five pieces. That is the whole signal source list. Everything routes through the iPad.

• iPad M4 running Loopy Pro as the host, mixer, FX rack and looper
• MOTU M4 audio interface, 4 inputs feeding the iPad
• Korg Modwave synth, the one piece of dedicated hardware left on the table (see Sec. 10)
• Microphone with no physical on/off switch, muted via a Loopy button instead
• Guitar into Rhino amp sim (AUv3) + a free IR loader (the built-in IR is bypassed to save CPU)

Rhino AUv3 with the built-in IR section bypassed. External IR loader feeds the cab convolution at roughly one third of the CPU cost.

Previous setup (much bigger)

"And now it's just a sound card, ModWave, and the iPad and the guitar."

- Kristof, on what survived the cull

iPad performance settings

The numbers he runs live. None of these are guesses. He has been gigging this exact profile.

The Loopy Pro DSP Statistics overlay - this is how you find the plugin that is eating your CPU, not vibes. Magic Dice, Turnado, Looperator instances, Other Desert Cities, WOW, BLEASS Dragonfly, Perforator all listed with live CPU %.

Signal chain at a glance

  GUITAR ---->  Rhino AUv3 (IR section OFF)  -->  free IR loader  -->  +
  MODWAVE -->  MOTU M4 in  ---------------------------------------->  |
  MIC ------>  MOTU M4 in (mute via Loopy button) ------------------>  +--> Loopy Pro mixer
                                                                       |
                                                                       v
                                                          [CLIPPERS, not limiters]
                                                          [ProL/ProQ = meter only, off]
                                                                       |
                                                                       v
                                                          MOTU M4 out --> FOH ("just turn up")

Sound-engineer management

• Arrive with a fully mixed output on the MOTU - the mix is already done before the signal leaves the iPad
• Single directive to the booth: "just turn up the volume"
• No per-channel EQ requests, no per-instrument level fader on the FOH desk - he hands them a stereo master and expects gain only

The whole "clippers, not limiters" + "metering-only ProL" stance only makes sense in this context: he is the mix engineer. The FOH person is a volume knob.

Mic mute button

• His mic has no physical on/off switch
• Workaround: a dedicated Loopy button wired to mute the mic channel
• Single tap = mute, single tap = back live. No fishing for the right slider mid-performance.

What to copy

The three modes, side by side

Every block of the template is shared. What changes is which inputs are armed, which buttons get pressed, and whether the loop counter is moving. The CTZ master chain (chapter 7) is identical in all three.

Mode B · Loopy as pure FX processor (no looping)

Sometimes the gig isn't a looping gig - it's a normal band slot, a DJ guest spot, a corporate event. Kristof still wants his exact FX vocabulary on the same buttons. Solution: load the master template, never press a record button. The Looperator stacks, Flux Mini 2 sidechains, modwave routing and CTZ master chain all stay alive - the loop tracks just stay empty.

• Loopy Pro runs as a pure effects processor - reverb, delay, filters bound to the same colour-coded buttons.
• Used for gigs where he doesn't loop but still wants his effects vocabulary on stage.
• The Looperator stays useful: stacked Looperator presets still chop and re-time live signal (chapter 5).
• Flux Mini 2 sidechain presets still pump live signal against an internal kick pattern (chapter 6).
• The whole CTZ bus-to-bus master chain (chapter 7) still does the gain-staging and clip-to-zero limiting before FOH.
• Mic mute still lives on a Loopy button (chapter 11) - the mic itself has no on/off switch.

"Sometimes I use Loopy Pro purely as an effects processor - no looping, just reverb, delay and filters on buttons." on gigs where he doesn't loop

FX-mode · what stays live, what goes silent

Same .lpproj. Different parts of it powered up. The "stays live" column is everything that processes signal in real time; the "goes silent" column is everything tied to time-stretched loop playback.

Mode C · Playing with bands

The same rig deployed as a band replacement: a real drummer in the back, a real singer in front, and the looper holds down everything in between. The drummer needs a click. The singer needs a band. Loopy does both at once.

• Loopy Pro acts as the band replacement - loops the instrumentals (bass, modwave, pads, FX).
• Sends a dedicated kick / click to the drummer (in-ears or wedge feed), so the human drummer plays in time with the looped instrumentals.
• The singer is acoustic-natural - voice on top of the looper + drummer.
• Pure FX-mode is also available inside a band setup (Mode B above) when the night calls for it.

The signal flow on stage

[ KRISTOF ]                     [ DRUMMER ]          [ SINGER ]
     |                                |                       |
     v                                v                       v
guitar + modwave +              acoustic kit             vocal mic
mic into MOTU M4                following click
     |                                                        |
     v                                                        v
[ Loopy Pro iPad M4 ]  <------- click bus -------->  (FOH gets singer +
  - loops instrumentals           ^                            drums + looper sum)
  - kick / click out              |
  - FX racks live                 |
  - CTZ master chain              |
     |                            |
     +----- click feed -----------+   (drummer in-ear / wedge)
     |
     v
[ FOH ]  full instrumental loop bed + processed mic if used

The economics · why the math works

"Looper + drummer + singer earns more per person than a full band." on the band-replacement math

Why this section matters · the template is the product

Every other chapter in this compendium described how Kristof built one Loopy Pro session. This chapter is the payoff: that one session is three different shows. The investment in the master template (chapter 2) pays back across every gig type he books, not just the looper gigs.

The same .lpproj, the same colour-coded buttons, the same gestures (1 button = many actions, chapter 2), the same CTZ master chain. Mode-switching is mental, not technical. There is no "FX template" and no "band template" - just the master template, with different buttons left untouched.

Applying it to your rig

You don't need a new session to copy this. You need discipline about not pressing record, plus one extra output bus for the drummer click. The template you already built for solo looping is 95% of the work.

FX-mode + Bands · the distillation

Improvisation-first

Songs do not start on a DAW grid. They start on a stage, in front of a crowd, on a synth that happens to be patched in that night. If the audience reacts, the moment gets battle-tested into a song.

• Many songs originated from live moments that worked with audiences.
• "Suddenly": a freeze-bass idea was played live, the singer reacted positively on the spot, and the moment became a recorded song.
• Ideas are battle-tested live before they get committed to a song file. The crowd is the A/B test.

"Finding the real meaning of looping for me right now is a big focus." SpeshFX 2025

360 camera review

The 360 camera is the secret writing tool. Every gig is documented in full panoramic capture, then mined later for ideas the conscious mind missed in the moment.

• A 360 camera records almost every gig.
• He reviews footage when stuck to extract inspiration.
• The camera turns ephemeral stage accidents into a searchable archive of happy-accident raw material.

Album "Shocked"

The latest record is on every platform. The interesting part is how Loopy Pro fits into a studio workflow that ends in Ableton: not as a final destination, but as a pre-juice tone shaper on the way in.

Error recovery (Barcelona story)

The defining test of a live-looper is what happens when the rig dies on stage. Barcelona is the case study.

[1] SOUND DIES MID-SET            barcelona, full silence, crowd staring
        |
        v
[2] CALMLY RESTART                  Loopy Pro + soundcard, no panic, no apology
        |
        v
[3] BURST BACK WITH BEATBOX         no waiting for the rig - mouth is the backup synth
        |
        v
[4] SET CONTINUES                   the failure becomes part of the show

• Sound died mid-set in Barcelona.
• Loopy + soundcard were calmly restarted, no on-stage panic.
• He burst back with beatbox. The voice is the always-available backup instrument.

Philosophy quotes

Four direct quotes. These are not poster slogans, they are the operating contract behind the rig. The Loopy choice, the analog signal chain, the 360 camera and the freeze-bass technique all back-fit into these sentences.

The mindset distilled