Description
R6 scope reconciliation: This MS5 #179 owns selected CHANNEL Focus, typed MIX bank navigation and safe Sends-on-Faders under canonical MS0–MS7 roadmap. Complementary PATCH/FX-truth issue #182 owns only capability-aware hardware I/O matrix, Master FX disabled-state honesty, and physical FX AUX identity; do not create duplicate inspectors or audio graphs. R6 detailed UX contract and L2 #176 are mandatory. Draft G5A #178 overlaps bridge/plugin-ui; read its live head before editing shared GUI files. No GUI-only claims of native processing.
Intent / authority
Dedicated operator-workflow milestone under product epic #170, based on official LV1 Classic guide and Fender Studio Pro 8 Console. Read L2 lock #176 first. Do not imitate third-party copyrighted UI.
Dependency: MS1 #173 for independently typed channel format; MS2 #174 for real GROUP/FX AUX semantics; MS3 #175 for independently routed monitor outputs. A focused inspector can be prototyped earlier using existing true native capabilities, but must never advertise future modes as LIVE.
Deliver one native-backed user journey, not a prettier placeholder
- Selecting any real CH1–CH10, AUX FX return, supported GROUP, or MAIN opens one compact non-modal CHANNEL focus over/alongside MIX. Show logical source + physical pin, processing mono/stereo, real insert chain, sends (PRE/POST gain/pan), destination bus + hardware output, and live/draft/rejected revision in actual signal order.
- All controls are driven from one existing native route/plugin/status/ACK publisher; no JS-only route graph, no restart/recreate of VSTs on navigation; CH1 Orbit and multiple inserts remain stable.
- Typed input/FX AUX/GROUP/MAIN banks display actual bus nodes only; no decorative 64/80 channels, invalid group, fake DCA or fake hardware. Selected channel identity survives bank changes, returning to FX preserves fader position.
- Optional safe SENDS-ON-FADERS: user chooses a real destination bus and explicit enter/exit mode; render fader controls that bus's sends, not channel main gain; confirm visual mode and values, exit/restore regular fader without gain jumps. Disabled until native sends target/ACK and test identity are correct. Do not reuse source fader value accidentally.
- Compact intelligent 1366/1440/1680 views, 1024 smoke, low-end integrated GPU/pointer budget; preserve original steel/BTN180, no blur. One shared L2 seven-row fader and meter geometry including MASTER under every mode; add regression to
tests/mixer_shell_geometry_smoke.py. - Focused selected-edge route trace instead of permanently drawing every routing wire; double-click FX invokes actual native editor, not fake EQ/dynamics. Use vendor VST GUI when processor has no audited native parameter map.
- Exact-head Chromium tests, operator walkthrough on Windows artifact, audio changes tested on real interface separately. Every unsupported control has honest disabled explanation.
Ownership
GUI integrator owns web/mixer-layout.js/css, web/mixer-io.js/css, web/bridge.js, web/monitor.js only with coordinated single owner; native graph interfaces shared with R5 owner, never concurrently edited without dependency reconciliation. No changes to existing 11 lower-strip geometry.
Activity
masarray commentedon Oct 31, 2026
MS5 cross-thread correction (31 Oct, canonical product reset): PR #219 correctly added AUX Sends-on-Faders UI/editing, but send fader release currently stages AUX send gain through
web/monitor.jsDRAFT→manual output MUTE→APPLY→native ACK. This is a structural route-edit workflow, not realtime live-performance send control like a professional console. Next integrated M1 must distinguishCONTINUOUS_RT_PARAM(bounded gain/PAN/send update with native ACK and smoothing, no global output mute/graph rebuild) fromSTRUCTURAL_MUTATION(AUX enable/new edge/device/output/Show, guarded MUTE→APPLY). Preserve native FX, selected AUX and MAIN fader values, device epoch and rejected-state rollback. Also implement selected-channel SOURCE→FX→SEND→BUS→HW OUTPUT focus and genuinely native AUX return/master. Do not mark this issue completed based on browser UI smoke only; physical ASIO/WASAPI FAT #15 remains necessary.masarray commentedon Oct 31, 2026
31 Oct 2026 — M1 REAL LIVE AUX SEND VERTICAL SLICE: PR #223 at exact head
f5650aeeeb40b907acf7fab5ca71711370afb223implements existing POST send gain as a native realtime parameter, rather than requiring MUTE→APPLY for every send fader. One bounded atomic gain per compiled AUX edge, 64-sample dezipper on the callback, control-thread epoch/revision and accepted-edge admission, positive native ACK updates acceptedRoute; MAIN gain/fader DOM, FX ownership, MONITOR/OUTPUT1 unchanged. New/removed PRE/PAN, AUX enable, physical source/output topology still structurally gated. Chromium exact-head #41155087583 SUCCESS. Windows MSVC/CTest/ZIP #41155087488 IN PROGRESS at checkpoint — PR stays DRAFT until native test/build succeeds. Hardware FAT instructions. This does NOT finish selected CHANNEL focus, live source PATCH2, AUX output fader flip, physical crackle #15 or product M1 as a whole.masarray commentedon Oct 31, 2026
M1 NATIVE LIVE AUX GAIN MERGED (31 Oct 2026) — PR #223 squash commit
e11a9799d5926567bedb8e4c8549ddc1d7b6dd62. PR exact-head Chromium #41155087583 and Windows native MSVC/CTest/package #41155087488 SUCCESS. New LIVE parameter pathroutingAuxSendGain/arMixAuxSendGainAckadjusts ONLY existing CH→AUX POST send coefficient during audio playback; 32 bounded atomics, callback-only <=64-sample smoothing, no global MUTE, plugin recreation, route revision increment, audio device restart or MAIN fader mutation. Browser reports LIVE level only after native ACK. Structural CREATE/REMOVE, PRE/PAN, AUX enable/driver pin still use guarded MUTE/APPLY. M1 operator/FAT contract. Next real-device candidate from post-mergemainWindows #41155784392, currently running; do not claim its binary exists until uploaded verified artifact. Physical #15 remains OPEN. This is the FIRST M1 realtime send-gain vertical slice, not a declaration that PATCH2 selected-channel quick-source, AUX master fader flip or full LV1 parity is complete.masarray commentedon Oct 31, 2026
M1 integrated operator milestone merged 31 October 2026: PR #231 → main
d3293af72eef029032a9138f26e6c71dc69967f7after reconcile of #228 custom ASIO/WASAPI device setup and now-closed superseded #226. Exact integrated PR head12582f29passed Windows MSVC/CTest/ZIP #41163412113 and Chromium UI #41163412112, not just separate-branch tests.Genuine operator journey: custom hardware driver/source/output ports → selected CHANNEL accepted SOURCE→FX→POST SEND→OUTPUT, single native controller/ACK, live CH→AUX POST send gain (#223) and independent AUX MASTER gain on selected bus. Four atomic bounded post-AUX-FX targets smoothly affect BOTH MAIN and MONITOR; no duplicated DSP callbacks, no runtime plugin re-instantiation or global mute for level changes. AUDIO I/O custom device work preserved in same files with exact standalone HTML module sync. #226 closed as superseded to prevent stale remerge.
Release gates still open: post-merge main Windows run #41164371465 in progress at initial check, only provide its verified ZIP after SUCCESS; hardware P0 #15 crackle 0FX unresolved; native MASTER insert/PDC, dynamic live channel >10, group/DCA/matrix, real device FAT and full professional parity remain unavailable. Do not call this user-certified full mixer.
masarray commentedon Oct 31, 2026
ISSUE RECONCILIATION (2026-11-01). Closed as duplicate/superseded (NOT a 'feature done' assertion). Selected channel focus, bank arrows, one-click SENDS and Sends-on-Faders are consolidated into canonical #192 operator Console deliverable; partial functions exist but remaining native-bus parity is NOT complete.
Single product/engine authority: PRD v5, ARD v5, #192. Physical audible quality: #15. This ticket's prior evidence remains searchable.