mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-17 07:05:28 +00:00
docs(design): record the rack UX rules and what drawing them exposed
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>
This commit is contained in:
co-authored by
Claude Opus 5
parent
9434222861
commit
0b0fd3b7dc
@@ -0,0 +1,69 @@
|
||||
# The casual author's view of the FX rack
|
||||
|
||||
The schematic direction won because it *adds information* — signal order,
|
||||
routing, what is driven versus set. But information a casual author cannot read
|
||||
is decoration, and the rack speaks entirely in Hz, dB and ratios. So the drawing
|
||||
stays and the **language changes**.
|
||||
|
||||
`copy.mts` is the design work: a plain-language layer over every effect in the
|
||||
registry. `build-preview.mts` renders the review page from it **plus the real
|
||||
registry and preset catalogue**, and **fails** if any effect, parameter or
|
||||
preset lacks copy — so the page cannot quietly omit something that ships.
|
||||
|
||||
```bash
|
||||
bun plans/audio-fx-ux/build-preview.mts /tmp/rack-ux.html
|
||||
```
|
||||
|
||||
## The three rules
|
||||
|
||||
1. **Two faces.** Every module opens plain: a name that says the outcome, one
|
||||
line about what it is for, and one control. The real parameters are one click
|
||||
away and never in the way. Nothing is hidden — it is ordered.
|
||||
2. **One knob that matters.** A compressor has seven controls and an author
|
||||
wants one. Multi-knob modules get a single derived control, exactly as
|
||||
`carveProfile(strength)` already turns one number into six.
|
||||
3. **Name the outcome, not the mechanism.** "Remove Rumble", not "High-pass".
|
||||
The DSP name stays in the corner of the module, so the vocabulary is taught
|
||||
rather than withheld — an author who learns "high-pass" here can carry it to
|
||||
any other tool.
|
||||
|
||||
## The shared vocabulary
|
||||
|
||||
Frequencies mean nothing to somebody who has not been taught them. `BANDS` names
|
||||
the ranges in the words the same person would use unprompted — rumble, weight,
|
||||
mud, middle, presence, edge, air — and every filter shows where it acts on that
|
||||
one ruler. Naming them once makes the whole rack legible.
|
||||
|
||||
## What laying it all out exposed
|
||||
|
||||
**A preset can use the same module twice for different jobs.** "Clean Voice"
|
||||
runs *Shape One Range* at node 02 (cutting mud at 250 Hz) and again at node 04
|
||||
(adding 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: a preset's node needs its own
|
||||
**role label** — "Reduce Mud", "Add Clarity" — which means copy belongs on the
|
||||
preset node as well as on the effect. This is invisible in a catalogue of cards
|
||||
and obvious the moment every preset is drawn as the chain it actually builds.
|
||||
|
||||
## What still needs deciding
|
||||
|
||||
- Does the plain name **replace** the DSP name or sit beside it? Replacing is
|
||||
friendlier but strands what the author learns.
|
||||
- Should the **menus** be organised by complaint ("my voice sounds boomy")
|
||||
rather than by effect family? The rack itself must stay in signal order,
|
||||
because order is audible — but the menus have no such constraint, and the
|
||||
preset section of the preview is written that way to show the difference.
|
||||
- How much should **hover audition**? Hearing a preset before committing is the
|
||||
single strongest affordance here. Cheap for static presets; a measuring script
|
||||
has to analyse first and cannot preview instantly.
|
||||
|
||||
## Status
|
||||
|
||||
`copy.mts` is a proposal, not shipped code. When it lands it wants to be
|
||||
`packages/core/src/audioFxCopy.ts` beside the registry, with the completeness
|
||||
check as a test rather than a build step.
|
||||
|
||||
The `PROFILES` figures — what one knob derives at gentle/middle/strong — are
|
||||
proposed values, not measured ones. They want the same before/after listen the
|
||||
clip-before-duck fix got.
|
||||
Reference in New Issue
Block a user