Genre sound-design workflows: acid, dub techno, and beyond

You already know how to synthesize a kick, a sub, and a saturated timbre in isolation. This module is about the step that separates a sound designer from a producer: assembling those parts into a genre-correct workflow, where the aesthetic — not the patch — is the deliverable. In a live-coding set or a club-oriented studio session, nobody asks for “a low-passed chord”; they ask for something that reads instantly as acid or as dub techno, and that reading comes from a repeatable chain of moves you can execute under time pressure.

The arc runs through two contrasting case studies. Acid comes first because it isolates one idea: the sound is the automation. Guided by the 303 parameter recipe (resonance, cutoff, accent/slide) and the insight that continuous cutoff-and-resonance movement over a sequence defines the genre, your first exercise is a supported acid line where the sequence is given and only the filter ride is yours. Dub techno then inverts everything: the effects chain, not the source, does the creative work. You build each element just-in-time — the filtered 909 kick, the sub carved from the kick’s own tail, the one-note minor chord stab with its slow filter-envelope swell — then push them through the transferable saturation → coloured filter → delay → reverb recipe, with post-effects redline saturation for the mixing-board warmth. The capstone strips the scaffolding and brings the two case studies together: you produce and live-automate the full 16-bar dub loop yourself — macro moves on filter, delay feedback, and reverb decay — then lay an acid 303 line over the dub bed, riding its cutoff and resonance as part of the same performance.

The required atoms are load-bearing: every capstone element (kick, sub, chord, chain, macro automation, acid filter ride) maps to one. Supporting atoms widen the lens — hardstyle’s pitched, distorted kick as the contrasting “kick as designed object”, filter house, dubstep, DnB, glitch — showing the same effects-first, tool-agnostic principle recurring across genres, so the workflow transfers beyond the two case studies.

Runnable examples

Generated from the context/ instrument corpus by concept (redistributable idioms only). Do not edit — regenerate with gen-module-examples.mjs.

drone

osc 55 >> audio

_{punctual-0001 · CC0-1.0}

SinOsc s => dac;

_{chuck-0001 · MIT}

four-on-the-floor

s("bd*4")

_{strudel-0001 · CC0}

setcps 0.52

_{tidal-0044 · CC0}

lowpass-sweep

Noise n => LPF f => dac; 0.2 => n.gain;

_{chuck-0003 · MIT}

s("hh*8").lpf(sine.range(200,4000).slow(4))

_{strudel-0015 · CC0}

reverb-space

s("cp").room(0.6).size(4)

_{strudel-0019 · CC0}

out: mix ~a ~b >> plate 0.3

_{glicol-0008 · MIT}

chord-stab

chord("<Cm7 Fm7>").voicing()

_{strudel-0010 · CC0}

~stab: mix ~n1 ~n2 ~n3 >> mul ~env

_{glicol-0015 · MIT}

delay-throw

delay 1 0.375 (osc 330 * lfsqr 2) >> audio

_{punctual-0012 · CC0-1.0}

d1 $ off 0.125 (# speed 2) $ sound "bd sn"

_{tidal-0042 · CC0}

highpass-sweep

s("hh*8").hpf(saw.range(200,4000).slow(4))

_{strudel-0016 · CC0}

hpf (400 ~~ 4000 $ osc 0.1) 1 (saw 55) >> audio

_{punctual-0008 · CC0-1.0}

resonant-filter

SinOsc s => LPF f => dac; 400 => f.freq;

_{chuck-0002 · MIT}

play :e2, cutoff: 90, res: 0.9, release: 0.3

_{sonicpi-0022 · CC0}

build-up

out: arrange ~intro 4 ~main 8 >> mul 0.6

_{glicol-0014 · MIT}

SinOsc s => Envelope e => dac; e.duration(500::ms); e.keyOn();

_{chuck-0027 · MIT}

breakbeat

out: speed 4.0 >> seq 60 _ _ 60 _ 60 _ _ >> bd 0.2 >> mul 0.6

_{glicol-0035 · MIT}

setcpm(174/4)
stack(
  s("amencutup*8").chop(8).sometimesBy(0.3, x => x.speed(2)),
  note("c1 ~ ~ c1 ~ g1 ~ ~").s("sawtooth").lpf(500),
  s("~ cp").room(0.2)
)

_{strudel-0050 · CC0}