Lesson 001 — One patch, one story

Class 1 · clocked phrase · recalibrated 2026-07-19

The first cut of this lesson handed you one voice and one knob. Then the level evidence came in — 168 clips of full-system krell fluency — and the premise died. You don’t need a small patch. You need your whole patch to tell one story. Patch at your density; the discipline is everything the patching isn’t.

Musical move

Take a patch as dense as you actually make them and hold it to a 2–3 minute piece with a phrase that makes a promise, an arc that moves through three distinct energy levels, and an ending that reads as chosen. Performed live into the Bluebox, one take.

Why this is interesting

Repetition is a promise. The first two passes of a phrase tell the listener what the world is; every pass after that either keeps the promise or breaks it, and both are moves. Your patches already have worlds — what they don’t have is weather.

Here’s the measurement: most of your TikTok clips sit at a loudness range of 1.0–2.6 LU. That’s one energy level, held. Beautiful texture that never chooses. The single widest arc in the sample — 5.0 LU — is “Last Christmas,” the one time you played a song. That’s not a coincidence; that’s the whole finding. Dynamics is not a mix afterthought, it’s a parameter you perform — mutes, VCA rides, filter closes, a voice sitting out for eight bars. Arrangement is playing the patch’s population, not its timbre.

The target: LRA ≥ 6 LU on the capture. Wider than anything on your feed. I’ll measure it when the recording lands.

The constraints

No recipe — you know where the cables go. These are the composition rules, and they’re the entire lesson:

1. One clock. Everything obeys it or it doesn’t play.
2. The promise: a 2- or 4-bar phrase somewhere in the patch that repeats, with at least one rest. The rest is load-bearing — a phrase with no silence has no shape.
3. A stated harmonic relationship: at least two voices, and before you patch them, write down the interval between them — fifth, octave, unison-detune, a third if you’re feeling brave. Anything, but chosen and named. This is the class-2 door, cracked open.
4. Three energies: the piece must exist at three distinguishable levels — call them floor, peak, and changed-floor. Not louder-and-back: the last floor should be missing something the first floor had, or carrying a scar from the peak. Moves that count: mutes, VCA rides by hand, a filter that closes and stays closed, a voice that enters once and leaves.
5. End on purpose. The one thing the corpus never does. Last-pass mute, held final note, hard stop on the downbeat — your call, but it must read as finished, not abandoned.

Setup

One pre-flight check: the clock has to survive the trip from Pam to the recorder. The chain is Pam → PPEXP2 → Hermod+ → Bluebox, and it has three places to silently die:

1. Hermod+ listens to Pam. All of Hermod+‘s global settings live behind one door: press track, then Y. Go to SYNC IN → CLOCK SOURCE = MIDI. (Hermod+ manual §§7.1–7.2, pp. 80–81.)
2. Verify the link with the tempo display. Set Pam to a tempo you’d never default to — 111 — with Pam running. Hermod+‘s BPM should snap to it and follow the knob. That’s the whole proof: cable, wiring type, and clock confirmed in one move. Note: PPEXP2 sends clock only, no start/stop (Pam manual §10.3.1, p. 27) — you still press play on Hermod+ yourself; that’s not a failure.
3. If the BPM doesn’t move: TRS MIDI has two incompatible wirings, Type A and B, and PPEXP2’s selector switch is on its rear — a module-pull to flip. Before pulling: the Bluebox’s MIDI In accepts either type, so patch PPEXP2’s TRS straight into it. Bluebox locks → PPEXP2 is alive, flip the switch for Hermod+. Bluebox doesn’t lock → it’s the cable.
4. Hermod+ feeds the Bluebox — SYNC OUT, not THRU. Pam’s clock carries no start/stop, but Hermod+ adds its own: same settings menu, SYNC OUT → MIDI = CLOCK+TRANSPORT (§7.3, p. 82). Leave MIDI THRU off so the Bluebox doesn’t hear two clocks.
5. The payoff — synced punch-in. Arm Bluebox tracks, set levels before the take, push REC: the Bluebox waits, then starts recording the moment MIDI Play arrives (Bluebox manual p. 54). Press play on Hermod+ and the sequencer and the recorder start on the same downbeat. One take, no dead air, no scissors. (At-rack check: confirm the Bluebox’s BPM display follows while Hermod+ is slaved to Pam — the manual doesn’t state whether Hermod+ re-transmits clock while following an external source. If it doesn’t, fall back to MIDI THRU and start the recording by starting Pam.)
6. Save the settings or lose them. Hermod+‘s global settings persist only if you scroll to SAVE at the far right of the settings menu and press it — they live on the SD card (§7.1, p. 80). RMR, from experience: “I forgot to do that and it tripped me up.”

Two more Hermod+ gestures worth having back: hold the play button to set tempo, and track + hold a track switch opens that track’s own configuration.

Alternative wiring, zero unknowns (adapted from RMR’s Hermod+ video): flip the hierarchy and make Hermod+ the master. RMR’s loop is Hermod+ → Bluebox → ALM MIDI adapter → Pam — “when I hit play on the hermod the two are synced” — but his Pam-over-MIDI leg doesn’t port here: PPEXP1/PPEXP2 are MIDI clock outputs only, and the Pro Workout has no documented MIDI input (Pam manual §10.3.1, p. 27). The rack-native version: Hermod+ internal clock, SYNC OUT → MIDI = CLOCK+TRANSPORT into the Bluebox, and slave Pam on the analog side — Hermod+‘s Clock out at 24 PPQN → Pam’s Clk, Reset out in RUN mode → Pam’s Run (Hermod+ §7.3, p. 82) — exactly the 24 PPQN + separate Run pairing ALM itself recommends for external sync (Pam manual §§6.1–7.1, pp. 19–23). Every link documented, the Bluebox punch-in demonstrated on video. Costs you Pam as the rack’s tempo brain for the session; your call at the rack.

The experiment

1. Plan the arc on paper first — draw it. Five words per energy level, plus one sentence: where the peak lands, and how it ends. A literal drawn shape is even better: sketch the arc on the reMarkable (or paper) and drop it in the shitrat inbox — reMarkable Share → Dropbox, or just photograph the page. The sketch becomes part of the learning record, and the recording gets judged against your own drawing. This is the arrangement decision made before the hands are busy.
2. Patch it. Whatever density you want — the plan is the constraint, not the module count.
3. Record 2–3 minutes, one take, no edits. The performance is the piece. If it falls apart, that’s a take worth keeping too — note where.
4. Stop. Don’t re-record more than twice. The lesson is the arc, not the polish.

Listen for:

• What promise do the first two passes make? Say it in words: “this is a piece about ___.”
• Is the peak a place — something happens there that couldn’t happen at the floor — or is it just more?
• Does the changed-floor actually differ from the floor, or did you go home unchanged?
• Does the ending land as an arrival, or does the piece just stop being there?

Report back → learning record 0001

Write it while the capture is fresh:

• The interval you named in constraint 3 — could you hear it as a relationship, or did it dissolve into timbre?
• Where did the peak land versus the plan? If it moved, what moved it?
• Which single arrangement move did the most work? Which was decoration?
• What did the changed-floor lose or carry?
• Did the ending arrive? Play it back cold before answering.
• One surprise.
• Drop the capture where I can reach it — I’ll run the LRA measurement, hold it against your arc sketch, and we’ll see if you beat your own feed.