Repository navigation
feat(gui): contextual GAIN/FX RACK and safe Sends-on-Faders console workflow - #604
3 commits merged into
Conversation
|
/arsonmix-ci ui 730cf9e |
|
/arsonmix-ci ui 274d0db |
…nice v9 and safe EdgeId tests
274d0db to
0bd69fe
Compare
|
/arsonmix-ci ui 0bd69fe |
|
/arsonmix-ci ui 3b2e4f0 |
|
Owner-approved contextual GAIN/FX RACK + SOF PRD/ARD merged into main in docs-only #609 ( Per current live integration plan, #606 already includes the browser contextual GUI changes from #604 and is the more advanced product branch; refresh current heads and reconcile there rather than double-merging this PR. Required future native work: actual ChannelId Input Gain before FX, true POST-INSERT PRE_FADER distinct from PRE_FX, selected EdgeId gain/tap/send ON controls with installed PCM ACK/readback, and physical FAT. SEND minimum/OFF retains WIRE; a demo Pages view is not native audio proof. No GUI asset redesign or duplicate mixer. |
|
Integration handoff from user-approved Harmonice v9 PFL FontMatched artwork, implemented separately in PR #610 without altering your active SOF branch. Important SOF contract to preserve when reconciling with latest main:
This deliberately does not push into or merge your branch while SOF is being developed; please forward-port these decisions during your own reconciliation. Contract: |
* Integrate MUTE/SOLO/PFL in SOF only while preserving MAIN PRE/POST and native cue safety * Use exact approved blue PFL OFF/ON raster and v9 OFF shadow in SOF key row * Ship the PFL FontMatched alpha PNG in the same Pages/native GUI assembler * Add exact approved PFL FontMatched OFF/ON transparent PNG sprite (2×57x30) * Account for approved PFL extension sprite in exact Pages/native asset inventory * Lock exact approved PFL raster hash and workspace/native safety in fast key contracts * Use explicit PNG signature bytes for approved PFL raster contract * Chromium verifies blue PFL raster, state and SOF-only visibility in existing Stage D session * Document approved physical key ownership, SOF PFL safety and PR #604 forward-port contract
|
P0 user correction now codified in PR #612 (#612): the approved v9 FontMatched physical key row must be MUTE / SOLO / PFL in default MAIN MIX, not just in SOF. PR #610 previously showed PRE/POST in MAIN, which the user explicitly rejected. Keep PFL in BOTH MAIN MIX and SOF and MASTER at MUTE/SOLO. The exact PNG files/CSS hardware owner must not be repainted. PRE/POST send tap is per-EdgeId in WIRE inspector and your contextual SEND CONTROLS, never replace the third physical PFL key or mass-retarget all sends. Browser cue remains visual-only and native requires independent MONITOR L/R with ACK. This is a forward-port requirement: merge/rebase from latest main (#612 after its tests) before integrating #604, without regressing GAIN/FX/SOF work. |
|
Heads-up: owner-approved tactile GUI correction is now merged as #613, main SHA dbade63. Forward-port before merging this draft: Main Mix source channel fader physical unity detent (7px capture/12px release, Alt bypass, final change to native ACK); taller shared source/MASTER/rail fader height; WIRE 460ms OUT→IN spring + 190ms settle; and fully continuous, brighter 5.6px selected real SVG jacket with transparent click hitbox. Preserve exact approved MUTE/SOLO/PFL PNGs and your distinct contextual SOF FX/GAIN/SonKu work. Do not cherry-pick an old index.html that reverts main key/fader/wire fixes. UI-only change, not evidence of physical PCM/ASIO. |
Purpose
A single contextual console based on the existing approved
/preview/GUI, grounded in Yamaha DM7 StageMix, Waves LV1 Fader Flip, Allen & Heath Avantis, and Studio One SEND racks. No duplicate mixer UI.Shipped on branch (browser reference UI)
Tests/evidence
Boundaries / follow-up
Sources