Shape One Range has three controls (where, how much, how wide) and the copy
nominated "how much" as the one that matters. That is incoherent: boosting an
unspecified frequency means nothing. The range is the FIRST decision, not the
second, and the rule broke on this module without my noticing.
Two ways out, both drawn. A keeps the module generic and makes "where" a word
from the shared vocabulary instead of a frequency field — honest, but still two
decisions with the first one jargon in a friendly coat. B makes the range the
module: the add menu offers jobs — Reduce Mud, Add Clarity, Tame Harshness —
each a peaking node with its frequency already chosen, so one knob is honest
rather than a simplification hiding the real choice.
B is the answer, and it is the same insight as the multi-band EQ: an author
does not want a parametric equaliser, they want to fix a thing. It also
dissolves the duplicate-name problem at the root instead of papering it with a
role label — Clean Voice now reads Remove Rumble, Reduce Mud, Even Out
Loudness, Add Clarity, Peak Ceiling, and nothing repeats.
Option A is not wasted: its band picker is the right control for moving the
frequency under Details.
This changes the catalogue rather than only the copy — presets should reference
named jobs, and EFFECT_COPY.peaking stops being a single entry.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The clearest failure this exercise surfaced is a rack holding two Shape One
Range modules doing different jobs. A multi-band EQ answers it better than a
per-node role label would, because an author already understands it — bass,
middle, treble is the most widely used audio control there is.
Its bands can BE the shared vocabulary: three are Bass / Middle / Treble, five
open to Bass / Warmth / Middle / Clarity / Air. So using the EQ teaches the
words the rest of the rack relies on, rather than the vocabulary living only on
a ruler somebody has to go and read.
Built like the carve, not like a new effect. Carve already owns several tagged
nodes and presents as one module; an EQ does the same with `fromEq`. Three
bands are a low shelf, a peaking and a high shelf — all already shipping. There
is nothing new in the graph or the render, and the nodes stay ordinary, so an
author who opens the details finds the filters they could have added by hand.
That route also sidesteps a real constraint: the registry's parameter model is
flat key/value, so an `eq` effect TYPE with N bands would need array-shaped
params it does not support.
Drawn with vertical faders around a centre detent, because that is what an
equaliser looks like to everyone who has met one. Collapsed, it reads like
every other module — "Bass +3, Middle -2, Treble +2", or "Flat" when nothing
has been touched.
Design only; not built.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The first rack pass carried module identity in per-family type — filters as
tracked-out caps, dynamics heavy and tight, nonlinear an italic serif, time
light and airy, smart monospace. Moving to the schematic direction lost it:
everything ended up lettered in the same condensed caps, with family shown only
by the node ring.
It is back, inside the schematic skeleton rather than instead of it, so the
drawing still carries order and routing while the type carries kind. You can
tell what sort of module you are looking at with the label out of focus.
Two faces, as budgeted. The condensed sans separates four families by weight,
case, tracking and size; the serif is spent on the one family that is
generative rather than corrective, because it is the one that behaves
differently.
Adds a tint step per module WITHIN its family, derived from position in the
registry so adding an effect never re-colours its siblings by hand. Seventeen
distinct module hues across the rack, and two filters read as different modules
without reading as different families.
The Broadcast preset is the test: seven nodes across three families in one
rack, each identifiable before it is read.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Adds the eight states a module can be in — collapsed, open, open with details,
bypassed, automated, from a preset, preset-edited, and measuring — drawn as
real rack panels rather than described.
Collapsed turned out to be the state that needed designing most. It is the
most-seen by a distance: a rack of six modules is six collapsed lines and
nothing else. So each one is now a sentence about what is happening to the
sound — "Cutting everything below 80 Hz", "Evening out — moderate", "A medium
room, lightly" — rather than the parameter that happens to be first. Numbers
stay because they make it checkable, but they arrive inside a phrase, and an
author can read their own mix top to bottom.
Rendering all fifteen at their defaults caught one immediately: a freshly added
Peaking EQ sits at 0 dB, and "Lifting 1 kHz by 0 dB" describes a non-event as
though it were a setting — while being the first thing an author reads after
adding one. Now "Sitting on 1 kHz, doing nothing yet".
Also root-causes three rendering bugs that looked unrelated: Bun escapes every
non-ASCII character in a String.raw template into literal \uXXXX text, so
em-dashes, curly quotes and CSS content glyphs printed as their escape
sequences. The template is a plain literal now, with HTML entities for
typographic characters, and the trap is written down.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The three rules the plain-language layer applies, the shared frequency
vocabulary, and the finding that only appeared once every preset was drawn as
the chain it actually builds: a preset can use the same module twice for
different jobs, so one plain name per EFFECT is not enough and a preset's node
needs its own role label.
Also records that the completeness check belongs as a test once copy.mts lands
as packages/core/src/audioFxCopy.ts, and that the PROFILES figures are proposed
rather than measured.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Replaces the documentation-card layout with real 292 px rack panels in the
schematic language. Each effect is shown as the module an author meets — node
ring, plain name, the DSP name in the corner, one control with both ends
described as sensations, its band on the shared ruler, and the real controls
folded behind a disclosure. Each preset is drawn as the chain it writes: IN,
numbered nodes with plain names and one honest value each, OUT, braced with the
preset's name.
Drawing them all is what produced the finding: a preset can use the same module
twice for different jobs. "Clean Voice" runs Shape One Range at node 02 to cut
mud at 250 Hz and again at node 04 to add clarity at 3 kHz. Read down the rack,
an author sees the same words twice and cannot tell them apart — so one plain
name per EFFECT is not enough, and a preset's node needs its own role label.
That is invisible in a catalogue of cards and obvious the moment the chains are
drawn.
Also fixes a rendering bug the card layout hid: a CSS `content` glyph does not
survive this file being generated, so the disclosure marker was printing as
literal escape text. Uses the native marker instead, which is accessible and
already animates.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
An earlier pass drew each automation lane's envelope shape inside its module.
Dropped: the lane already has a home in the timeline, and a second small
drawing of it in the rack is decoration. What the rack is actually missing is
the CURRENT value.
The panel already receives that — FxSectionProps.liveAutomationValues exists
because "an automated parameter's stored number is only the seed the lane
replaced, so a rack that shows it stands still while the carve is audibly
working". So an automated row is now an ordinary parameter row whose number is
live at the playhead, marked `~` to say it is driven rather than set, with the
marker moving with it. Stopped, the values go grey and hold.
Better on its own terms and cheaper to build: no new drawing, and it consumes
a prop that already exists for exactly this.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Four directions were mocked at the real 292px panel width — hardware
silkscreen, vintage test equipment, risograph, schematic — and schematic was
chosen.
It won because it is the only one that adds information rather than decoration.
Chain order is load-bearing in audio (a limiter first and a limiter last are
different sounds) and nothing in the panel said so. Drawing the rack as its
signal path also lets bypass be a route rather than an opacity, gives a preset
a visible brace over the nodes it wrote, lets an automated parameter draw its
lane instead of showing the stale number the lane replaced, and marks a
measuring module with a second ring — which is the static-versus-script
distinction from section 4 delivered as drawing rather than prose.
Drops the 3px coloured rail from the first pass. It is the single most overused
device in dashboard UI, and forcing each direction to find another answer is
what separated them.
Adds .impeccable.md with the design context the direction was chosen against —
users, personality, principles, palette, anti-references — so the next session
does not re-derive it or re-ask.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The rack is a 292px column of stacked modules, which is near enough a Eurorack
case — so each effect gets a faceplate: a 3px family-hue rail, lettering per
family, and a tint step per module within the family.
Costs almost no plumbing. `group` is already on every effect in the registry so
hue and lettering are derived rather than hand-assigned, and every module
already renders `data-fx-node="<type>"`, so the identity layer is CSS on an
attribute that exists today. Only the Smart family is new, and carve already
lives there in spirit.
Records the type budget as the real decision (self-hosted only, two faces
recommended — one is too subtle at 11px, five reads as a collage), and the
preset menu design: grouped by the same families, module counts per row so a
preset visibly IS a chain, and "measures" instead of a count on the adaptive
ones, which delivers the static-vs-script distinction in one word.
Mockup published as an artifact at the real panel width.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Voice carve made a pile of effects into one understandable feature. This asks
what else can, using only the 15 effects already in the registry.
Surveys what consumer tools ship and splits it into three tiers: ML enhancement
(Adobe/Descript — NOT reachable, and it is the most-requested thing in our own
internal feedback, so the doc says so plainly rather than dodging it), intent
panels over conventional DSP (Premiere's Essential Sound — the model worth
copying), and character effects (CapCut — fully reachable, except the pitch and
formant half, which needs DSP we do not have).
Proposes ~20 static presets with concrete values, all inside the registry's
declared ranges and in the node order the audio skill already fixes, plus five
adaptive scripts. The load-bearing finding: none of the scripts needs new DSP —
de-ess, leveller and tone-match are different questions asked of
analyseCarveDynamics, windowDb and powerSpectrum, which already run in the
panel. Carve is not one feature, it is the script engine.
Framed against the VST cancellation, which is the governing precedent: that was
killed for a sidecar process, an external repo, an unbundled dependency and
render-path liability. Preset values are data and the scripts reuse shipped
analysis, so this is the inverse of all four.
Four traps recorded so they are not hit later: a de-esser cannot be a static EQ
cut; boost presets must end in a limiter (yesterday's overshoot sweep is the
rationale); the leveller's lane must ride a `gain` node because VOLUME_RANGE is
0..1 and normaliseEnvelope clamps to it, so a volume lane can only attenuate;
and analyseCarveDynamics' 85-150 ms hop is too coarse for 50-150 ms sibilants,
so de-ess needs it re-parameterised rather than called as-is.
Nothing built. Research and design only.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Verified by ear 2026-08-09: barely detectable at 1.35x overshoot, heard very
clearly once the chain was pushed. The mechanism is confirmed and the fix does
what it claims; the severity really is conditional on how far past full scale
the chain runs, rather than the original pair having been a bad test.
§4a-1 is fully closed — implemented, tested, mutation-falsified, and now
confirmed audibly.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The before/after pair was listened to and the difference was barely
detectable. That is a real result, not a bad test: sweeping the chain's
overshoot shows the damage scales with it, and the pair happened to sit at the
bottom of the range.
chain peak 0.48x -> nothing clamped, -70 dB (16-bit rounding only)
chain peak 1.35x -> 2.1% of samples, -25.1 dB <- what was listened to
chain peak 2.69x -> 19.3% of samples, -9.1 dB
chain peak 4.00x -> 48.8% of samples, -3.3 dB
So a chain that stays under full scale is completely unaffected — the fix
changes nothing for it — and 55f852a72's "audible distortion" framing is
overstated for mild chains. The fix is still right: it destroys data the lane
was about to scale down anyway. But it belongs with correctness work rather
than with "renders sound wrong today", and the handoff now says so plainly so
nobody re-derives the severity from the commit message alone.
The commit itself is left alone rather than rebasing 15 commits over an
adjective; the measurement lives here instead.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The command as written would have wasted the time it was added to save. The
`stages/*.test.ts` glob sweeps in the vitest files sitting in the same
directory — bun cannot load them, and the run reports 37 failures and 5 errors
that are purely the wrong runner meeting the wrong file. It also omitted
planV2.test.ts, so it could not have produced the 203 it claimed.
The 49 bun files and the vitest files are interleaved through the same
directories with no path that separates them, so the list is spelled out and
both ways of getting it wrong are named.
Re-run at this HEAD: 203 passing across the 12 files. That also makes the
figure current — it was last measured three commits ago, before the 4c
refactors touched core.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Four of the nine cleanup items are done in three commits. The
enabledAudioFxNodes consolidation is worth reading as more than tidying: it
exposed that buildFxChain's update() filter had no test, and the failure it
prevents is silent.
The five left each carry a reason rather than a line item. The two WAV chunk
walkers are genuinely duplicated but differ in four behaviours, in the parser
every render's audio passes through. The FlatSlider reuse is a merge of two
behaviours rather than a swap, and is entangled with the held-back throttle
fix in PR #2190. The wet/dry shells want doing after the LFO rework, not
twice. The 30/s curve sampling is an audio-changing decision, not a cleanup.
Verified at this HEAD: studio 3662, core 1672, engine 736, producer 534 under
vitest plus 203 under bun test; tsc and oxlint clean across all five packages.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Producer's suite is split across two runners, not half broken: 49 files import
`bun:test` and vitest reports them as collect failures. Both halves are now
recorded with the commands to run them, including the `./` prefix `bun test`
needs to treat arguments as paths rather than name filters — without it the run
exits 0 having run nothing.
That half was the real blind spot for b1faacb3a: `plan.test.ts` and the
`plan-parity-*` suite cover `applyDistributedAudioWarningPolicy`, the consumer
whose input that commit changed. Run and green — 203 passing.
Also copies the A/B generator next to the wavs it produced, so the pair can be
rebuilt with a different chain or the user's own audio instead of dying with
the session's scratchpad.
All four suites re-run at this HEAD, so the baseline block is true at the
commit it names: studio 3662, core 1669, engine 736, producer 534 + 203.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
All four of section 4a and six of 4b are done. Adds section 3b with the
commits and the three judgement calls behind them: 4a-1 changes rendered
audio and its before/after pair is written but unheard; 4a-4's striding was
measured, found to move the carve's band selection, and rejected; 4a-2's
size ceiling has no test because reproducing it needs a 256 MB payload.
Rewrites 4b around what remains — the chorus/phaser LFO phase, which needs a
buffer-source rework and its own listen, and the per-element browser setup —
and records why the over-broad media.ts health ignore was left alone.
Refreshes the baselines (studio 3662, core 1669, engine 736) and adds
producer, which was never in the set: 534 passing plus 50 pre-existing
collect failures from files importing bun:test.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Eleven of fifteen findings fixed on wa-19-review-fixes; the four left open are
recorded with the analysis already done on each, including why the clip-before-
volume-lane one was started and deliberately stopped. Also carries the cut list,
the cleanup list, the carve-reconcile-wip undo regression, and the nine traps
that cost time — the published-CLI-is-not-a-symlink one above all.
Where the branch stands, what the feature does now, the architectural facts worth not
re-deriving, the traps that cost time (the studio reads core from dist; Number(null)
is 0; the fallow gate already failed before this work), the premises this session
falsified so nobody re-measures them, the stack force-push and what PR #3058 now is,
and the four remaining steps for shared lane rows.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Four clips on one row made a per-clip lane read as governing the whole track. Track-
level FX was considered and rejected — `data-track-index` picks a row and nothing
else, and both runtimes build audio per element, so there is no track to own a chain
— which leaves the fix in the timeline's presentation: lane rows keyed by the
property they drive, shared by every clip on the row that automates it.
Written down rather than started, with the parts that are not obvious until you look:
the grouping key cannot be the lane target, because node ids are minted per chain.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>