Designing a DAWless live techno rig
Learning objectives
- learner can distil a studio into a minimal, self-running, redundant standalone hardware rig
- learner can assign focused single-purpose roles and prioritise sequencing over sound sources
- learner can plan effects, mixing, and recording so the rig controls its own energy and captures a set
Capstone — one whole task that evidences the objectives
Draft and document a complete DAWless live techno rig on paper/ModularGrid: name each device's single role, show the self-running signal/clock flow, the redundancy split, the in-rig FX/mix strategy, and how you will record the set.
Prerequisite modules
The whole task here is the one every hardware techno act eventually faces: a studio full of synths and drum machines has to become a rig you can carry into a club, plug in behind a stranger’s mixer, and trust for ninety minutes with no laptop to fall back on. That translation — from collection to instrument — is a design discipline of its own, and this module has you practise it on paper before you spend a euro.
The arc starts supported. First, study how working artists distil a dozen-plus machines down to two samplers, a drum box, and a mixer (“a DAWless live rig distils a large studio down to a compact standalone subset”), and adopt the flipped mindset that the groove should keep running even when you touch nothing (“a live techno rig should keep producing sound with no input”). From there, exercises tighten the constraints: cap your voices, weight the rig toward sequencing and manipulation rather than oscillators, and give each device one or two roles it does in the best possible way. Mid-module, you plan the survival and capture layer — splitting the rig into two independent halves, running filter fades inside the rig so the house desk is just summing, playing reverb as a build/breakdown instrument, and choosing a point on the recording spectrum from stereo SD capture to multitrack.
The capstone is unsupported: draft the full rig with roles, self-running clock/signal flow, redundancy split, FX/mix strategy, and recording plan. Every required atom gates one of those boxes on your diagram — skip one and the design has a hole. Supporting atoms enrich the choices inside the boxes: incremental growth principles for gear reasoning, looper-as-spine and Octatrack-hub archetypes, effects-chain versatility, encoder-versus-pot ergonomics, and the prepared-versus-improvised sequencing spectrum.
Runnable examples
Generated from the context/ instrument corpus by concept (redistributable idioms only). Do not edit — regenerate with gen-module-examples.mjs.
reverb-space
s("cp").room(0.6).size(4)
strudel-0019 · CC0
out: mix ~a ~b >> plate 0.3
glicol-0008 · MIT
Atoms in this module
Required — these gate the capstone
Supporting — enrichment, not gating
Part of curricula
- Dawless Performer — hardware jam to recorded live take — Build the self-running rig and design its sound required
Unlocks — modules that require this one