docs: define mixer-first editor workflow

Specify ordered fader and separator layout, hide/show semantics, guided capture and MIDI binding controls, and the single-screen migration backlog.\n\nValidation: git diff --cached --check
This commit is contained in:
Dandaedre 2026-10-15 17:40:17 +02:00
parent fbea588e67
commit ef60da3953
Signed by: Dandaedre
GPG Key ID: 440C6592E8A26D99
2 changed files with 53 additions and 4 deletions

View File

@ -393,11 +393,40 @@ and is not persisted in the audio profile. Each palette defines background,
foreground, accent/selection, secondary meter, muted, warning, error, and meter
track colors so status meaning remains consistent across themes.
TUI tabs:
The TUI is mixer-first rather than exposing the profile's normalized tables as
separate tabs. Its main list is an ordered presentation of logical faders and
named separators. A layout entry references a stable fader ID or defines a
stable separator ID and label. Fader entries retain their position while
hidden; hiding is presentation-only and never deletes the target, selectors,
MIDI bindings, or saved state. Profiles without an explicit layout synthesize
one visible entry for every declared fader in declaration order. Validation
rejects duplicate layout IDs, duplicate fader references, and dangling fader
references.
- **Mixer:** faders, resolved applications/streams, volume, mute, mixed/offline/pending/errors, pickup status.
- **Editor:** create/edit/delete application selectors, groups, faders, surface bindings, and MIDI learn; preview matches and conflicts. Draft changes do not affect audio; Validate, Apply, Save, Cancel are distinct. Referenced deletion requires reassignment or explicit cascade confirmation in the UI.
- **Devices / status:** MIDI assignments and ambiguity resolution, manual/auto backend choice, capability/probe errors, active profile and persistence errors.
The selected main-list entry can be moved directly, separators can be added,
renamed, moved, or removed, and a hidden-items view restores hidden faders at
their retained positions. Editing a fader presents domain fields rather than a
serialized command:
- **Capture:** application selector field, exact/regex mode, and pattern; group
faders instead present member faders and the currently available group mode.
- **Volume control:** current surface/message assignment with Learn and Unset.
- **Mute control:** current surface/message assignment with Learn and Unset.
- **Visibility:** Hide from mixer or Show in mixer without changing routing.
Groups select application-targeting faders in the UI; the server stores their
deduplicated application IDs because group membership is an audio-domain
relationship, not a dependency on a particular physical control. The editor
shows this translation and prevents group or output faders from being chosen as
members. Absolute remains the only selectable group mode until the reserved
relative-mode runtime work is complete.
Draft changes do not affect live routing or audio. Apply and Save remain
distinct server-owned revisioned operations, validation errors preserve the
draft, MIDI learn reserves the selected action and suppresses its normal action,
and Unset removes only that fader/action binding. Device/backend status remains
available from the mixer without requiring a separate configuration table
browser.
MIDI learn reserves the selected control and suppresses its normal action while learning. Save sends a revisioned request to the server; it never writes files from the TUI. Restore terminal state on errors and exit. Use logs away from the active terminal display.

20
task.md
View File

@ -351,6 +351,26 @@ Dependencies: M8, M2, M1.
`P` applies the validated draft without writing audio or disk; `S` atomically
saves it only when the on-disk bytes still match the server baseline. Draft,
live, and durable state remain separately visible after failures.
- [ ] **M9.4 Mixer-first layout:** persist ordered logical-fader and separator
entries, synthesize declaration-order entries for old profiles, and retain
hidden faders in place. The main mixer can reorder either entry type, add/edit/
remove separators, hide visible faders, and restore hidden faders without
changing targets or bindings. Tests: invalid/duplicate/dangling layout entries
fail; reorder and hide/show round trip through comment-preserving drafts; a
hidden application remains routable through a visible group.
- [ ] **M9.5 Guided fader editor:** replace pipe-delimited table commands with a
selected-fader form. Application faders edit capture field/mode/pattern;
groups select eligible application faders and show the absolute group mode;
volume and mute assignments each expose Learn and Unset. Tests: editing one
field preserves unrelated selectors/bindings, unset removes only the selected
action, learn conflicts preserve the draft, and group selection translates to
deduplicated application IDs.
- [ ] **M9.6 Single-screen configuration workflow:** remove the normalized
Config table browser once all its operations are reachable from the mixer,
keep Apply/Save and draft/live/durable status visible, and expose hidden-item
restoration and device/backend diagnostics without a separate primary tab.
Tests: keyboard navigation and every modal work at small terminal sizes;
Escape backs out one level and never quits; invalid edits retain form input.
## M10 — Transactional profile swapping