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>
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>