Repository navigation
Description
Reconciled 2026-11-08 — GUI/implementation scope completed. Current approved operator chrome and compact toolbar are assembled in scripts/compose_operator_ux.py and protected by Chromium native/Pages visual checks; later merged #433/#439/#458 supersede this 2026-11-04 GUI hierarchy proposal. Do not restore old extra bars or alternative console. Remaining feel/precision issues are independently tracked in #347/#349.
Current main at audit:
c57720ea25585c861af89802e1365ffef7d03d17. No statement of physical hardware FAT.
Owner-observed UX defect
In the 2026-11-04 1378x911 screenshot, top controls are functional but feel visually noisy: Plugins F8, bank and view, Sends on Faders, target BUS, PFL, Snapshot/save/recall, More, and an independent WIRE/MAIN/VIEW/Routes/Matrix/channel-count row compete at almost identical visual priority. A beginner cannot quickly tell what to do first vs what changes an active live mix.
Product design direction
Preserve approved graphite/navy machined-console visual language, small typography, accepted BTN-180/physical controls, original fader/pan/identity assets, equal-width pinned Master and ONE vertical console (PR #278 V8). Benchmark Waves LV1 mode/layer separation: what channel bank, what operation, what current live status must be legible separately.
Intent groups (not another row of unrelated buttons)
- Channels & View (left): BANK arrows + exact current bank + density selector. Keep Plugins/F8 as a clearly discoverable nearby tool, but don't let it visually interrupt the bank control group.
- Mix & Monitor (central): Sends-on-Faders mode with clearly active state + actual target bus, Clear PFL as visible contextual safety action only when meaningful. Distinguish temporary mixing mode from permanent audio route. Show concise role/status, no constant caption wall.
- Show & Safety (right): current Snapshot/Show, Save, guarded Recall, More overflow. Never hide essential safety information or use identical affordance for harmless view mode vs destructive live Recall.
- Context row / WIRE: dedicated small visual group for Follow Fader vs independent Pre FX, selected source/MAIN route, VIEW Focus/All, Routes/Matrix; avoid a second, visually competing application toolbar. Progressive disclosure for advanced patch matrix; retain one-click direct in-strip workflow.
- Novice journey: on empty/unpatched channel, show one contextual next action IN -> FX -> OUT; on configured channel show actual verified route/status, no permanent instructional copy. Demo clearly states SIMULATED; native status only if native ACK/PCM verifies it. Preserve beginner discoverability with titles, focus hints and keyboard labels.
Geometry and visual acceptance
- Do not expand bulky header indefinitely: honor PR GUI M3 — 70px aligned meters, clip lamps, safe multi-wire inspection and operator controls #343's responsive two-row/collapsible mixer header work and measure whole-screen layout budget (1366x768 must keep FX and fader minimums). No overlapping buttons, clipped legends, large new cards, or invisible functionality.
- Meaningful physical alignment: common control heights, aligned group baselines, regular gap rhythm, shared text baseline, subtle separators, consistent primary/secondary states; never globally enlarge/embolden labels.
- At widths 1024/1366/1680/1920 and heights 768/900/1080, especially with bank pages, expanded WIRE and plugin browser, primary controls remain visible; secondary controls progressively move into existing More rather than shrink to illegibility.
- Match Comfort/Standard/Compact and Master pinned bank; disabled vs active vs focus vs danger semantic states. Keyboard tab order matches visual ordering, no traps, fixed hover/focus visibility.
- Match screenshot of old vs new with explicit acceptance: the operator should locate BANK, MAIN, FX/Plugins, PFL and Snapshot without a tooltip; simple route/setup should be achievable from one console screen.
Ownership and dependencies
- Don't duplicate PR #343 (already reworks
.mixer-titletwo rows and meter geometry/clip). Wait for exact-head PR QA + merge, then design toolbar grouping on current merged main (or coordinate directly with PR owner). Reuse the existingmixer-chrome-material.cssand component-owned CSS, not a new cascade tail. - PR #278 is visual reference; PR #271 is native WebView adaptation; issue #268 retains native UI authority. No direct edits to
engine/core/**orsrc/**. - Source of truth:
site/preview-v2/index.html,site/preview-v2/assets/mixer-chrome-material.cssand current header/section owners; public aliases throughscripts/build_pages.py. Respect V48 checkpoint and PR GUI M3 — 70px aligned meters, clip lamps, safe multi-wire inspection and operator controls #343 CSS owner regression ledgers.
Done = evidence
Playwright screenshots and interaction runs at all viewport/density combinations; compare old vs new toolbar on an actual rendered browser; no horizontal overflow, no fader/meter collision, no title/More overlay, no broken PFL/SOF/Scene semantics; current same-SHA CI and public Pages deployment PASS. Native release not claimed until #271 + #266 + #270 + physical FAT #15.
Activity