`copy.mts` lived in `plans/` and was read by one build script. Moving it
to `packages/core/src/audioFxCopy.ts` puts it beside the registry it
describes, and turns the coverage into `audioFxCopy.test.ts` — every
shipped effect, every one of its parameters, and every preset has to have
copy. That check existed before as a step in `build-preview.mts`, which
means it only fired when somebody remembered to rebuild the review page.
Now it fires on the commit that adds an effect without a plain name for
it, which is the only moment it can still be cheap to fix.
Four more assertions the build step never made, each of which was a real
hole: copy for an effect the registry no longer ships (dead text that
reads as coverage), a `SUMMARY` missing for an effect that has one
everywhere else, a summary that renders `undefined` or `NaN` at the
effect's own defaults — which is the first thing an author reads after
adding one — and a gap or overlap in the shared frequency ruler, which
would be a band the rack can name in one module and not in another.
`PROFILES` deliberately did NOT come along. Its figures are proposed, not
measured, nothing derives from them yet, and they want the same
before/after listen the clip-before-duck fix got before a knob is wired
to them. So it stays in `plans/audio-fx-ux/copy.mts`, which is now all
that file holds, and `build-preview.mts` imports the shipped four from
core and that one from beside itself.
Landing the data is not wiring it: nothing in the studio reads this yet,
and it should not until the three open UX questions are settled — whether
the plain name replaces the DSP name or sits beside it decides what the
rack renders. The README says so where the status used to say the layer
had not landed.
Falsified: deleting one parameter's entry fails the highpass case.
core 1745 passing (111 files), studio unchanged at 3674 / 18 todo.
De-esser is deferred with its two design constraints written down, because
neither is visible until you try to build it: analyseCarveDynamics' 85-150 ms
hop cannot land on 50-150 ms sibilants and needs re-parameterising, and
MAX_AUTOMATION_POINTS is 512 while a long voiceover holds hundreds of sibilant
events at three or four points each — so a naive lane blows the cap and the
scheduler truncates it silently, leaving an envelope that stops partway through
the clip. The leveller is its structural template.
Tone match is superseded for v1. It existed to let a casual author fix a
track's tone without understanding frequencies, and the Tone EQ now does that
with a control they already know and does it predictably. What is left is
matching one track to another, which is genuinely advanced and carries real
unknowns nobody has asked us to resolve.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The EQ, the named jobs and the levelling script are built, and the docs still
described them as proposals. Adds a "what shipped" table and carries forward
the three findings worth keeping:
- parseAudioFxChain silently dropped fromPreset until 29f53f935, because the
round-trip test compared only node types. Any new node tag has to be added to
both the parser and the serializer AND compared in that test.
- The single-knob rule broke on `peaking` — "how much" cannot be the one knob
when the range is the first decision. Making the range the module fixed it
and dissolved the duplicate-name problem at the root.
- The levelling target must be a level the track already reaches; an absolute
one turns levelling into a volume change.
Also records why copy.mts has no entry for Tone or the leveller: both carry
their own summaries in core, which is the right home for copy that has to read
the chain to write itself.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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>
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>
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>