Repository navigation
Description
Milestone B verified triage — 2026-11-17:
P2/vocal-throw/feature/backlog. Classification ≠ completion of product feature or physical FAT.Scope / release boundary: Optional BPM Music BUS analysis; no fake beat phase.
Exit criteria:
- Estimate BPM and phase from actual native Music BUS on worker thread with confidence/hysteresis and tempo holdover; no FFT/IO in ASIO callback.
- Verify variable-tempo and stop/restart behavior and bounded precise readback to Vocal Throw inserts at 44.1/48 kHz.
Canonical issue ledger. Preserve historical evidence below; no speculative merging or rewriting approved audio.
Product goal
Automatic tempo detection from the actual music/backing BUS, not from the lead vocal microphone. ArSon Vocal Throw currently has real native phrase-end Manual/Auto/Hybrid and BPM/TAP, but no auto music tempo. This issue owns that remaining explicitly requested function.
Architecture / realtime contract
- Add an explicit user-selectable tempo source (a live music/backing bus
ChannelId), never silently sample MAIN or echo return. - Source PCM remains in the already authoritative native graph; a bounded nonblocking block-level/onset summary crosses to a dedicated analyzer off the ASIO audio callback. Do not run FFT/autocorrelation/model inference in the callback.
- Analyzer estimates BPM and musical beat phase with confidence, half/double-time ambiguity protection, stable hysteresis, and holdover during intro/gaps. No tempo oscillation when backing stops.
- A single versioned tempo transport/snapshot publishes accepted BPM/phase to participating VocalThrow inserts with device epoch and graph revision fencing. No second routing authority or secondary audio callback. VST3 latency compensation and MONITOR dry bypass stay intact.
- Priority when source is unavailable/unreliable: explicit/song BPM or accepted TAP; never invent a tempo. UI must visibly distinguish Auto BPM locked, listening, and manual fallback.
- Correct handling of tempo changes between throws without truncating active echo tails. Active tail retains its frozen BPM schedule; new tail uses next validated transport state.
- Controls follow the existing approved
/preview/compact FX editor and accepted DSP ACK/readback; no browser DSP and no separate mixer page.
Acceptance
- Deterministic backing tracks at 72, 95, 120, 160 BPM (4/4, syncopated, sparse drums), 44.1/48/96 kHz, 64/128 sample ASIO callback: select backing BUS -> lock BPM (confidence/phase evidence) -> beat-aligned throws.
- Half/double-time, silent intros, held notes, tempo ramp, unpitched percussion and live vocal bleed do not cause unstable tempo jumps; clean fallback to TAP/manual.
- Source changes, WIRE retarget, SOURCE ONLY, bus mute/solo, device restart, sample-rate change and graph epoch rejection cannot leave stale auto BPM.
- No allocations, waiting, FFT, locks or logging in ASIO callback; bounded memory and SPSC overrun counters; CPU/xrun measurement vs Vocal Throw disabled.
- Manual/Auto/Hybrid phrase detection works independently of auto BPM; changing tempo never steals already sounding dual-tail phrases.
- Windows native CTest + Chromium /preview/ contract + physical singer/ASIO qualification before release.
Dependencies
M1 native Vocal Throw implementation in PR #469. Do not merge this issue into M1 test qualification or claim auto tempo exists until bus routing and analyzer are truly integrated and tested.
Activity
masarray commentedon Nov 8, 2026
Progress 2026-11-09 — Music BUS Auto-BPM + beat-phase native PCM milestones
39ba9a48de8fe87270f9ed0cf9cac49fb004dfedpassed Windows JUCE/MSVC 64/64 CTest (run #42499813920).33364fe74c188ca4bb1d9bbe2ca8142aeb36b9fbpassed Windows JUCE/MSVC 64/64 CTest (run #42524993708) plus real desktop/mobile Chromium FAT.Keep the issue OPEN and both PRs DRAFT. Remaining acceptance requires physical ASIO 64/128-frame 44.1/48/96k xrun/CPU, real musical syncopation / half-double-time stability, singer bleed, PDC, source/restart and practical listening. The 10ms onset window cannot be honestly described as sample-perfect beat detection. Do not merge PRs out of dependency order or confuse green CTest with live stage certification.
masarray commentedon Nov 8, 2026
2026-11-09 — M3 stabilization and VST GUI checkpoint: draft PR #476 exact head
8dbf6d575cd8e37de5a5249743bdc86902bc1960passed Windows MSVC/JUCE native 64/64 CTest (Actions #42529534785), including new strong-offbeat ambiguity/phase-lock recovery/no-false-steady-pad fixtures. Native editor Chromium desktop/mobile PASS (Actions #42529379402), premium VST UI and shared exact Close/Power chrome for EQ, Compressor and Vocal Throw. Full PR evidence. PR restored to its stacked M2 base and remains Draft. Keep this issue open until actual music + physical ASIO 64/128 frame xrun/CPU, live singer bleed and PDC latency evidence is available; a 10ms onset estimate is not sample-perfect detection.masarray commentedon Nov 9, 2026
ARSON VOCAL THROW — AUTHORITATIVE M1–M4 RECONCILIATION / SAFE HANDOFF
Date: 2026-11-09 (Asia/Jakarta)
Repo:
masarray/arsonmixThis is a progress-preservation checkpoint, NOT a merge, release or CI claim. All SHAs, branch ancestry and GitHub status were rechecked LIVE before posting.
1) Authoritative milestone chain — DO NOT LOSE
feature/arson-vocal-throw-native-202611084db384851e6f6378cca4fd037b744c98bd1f0ba3main, DIRTY (conflicting with newer main)feature/arson-vocal-throw-music-tempo-m2-2026110839ba9a48de8fe87270f9ed0cf9cac49fb004dfedmain, DIRTY; contains M1 ancestryfeature/arson-vocal-throw-phase-grid-m3-202611098dbf6d575cd8e37de5a5249743bdc86902bc1960feature/arson-vocal-throw-hardware-face-m4-202611095f6b1b01ba41a5cc559f0335d38b052967949f55Verified strict ancestry: M1 → M2 (+24 commits), M2 → M3 (+32), M3 → M4 (+30); each compare is
aheadwithbehind=0. The current M4 head includes all three previous milestone histories, not just artwork. DO NOT cherry-pick M4 alone onto an incompatible main without M1–M3 native contracts.2) Latest main and reconciliation BLOCKER
mainHEAD:381c140200d2f4ecb965183a2da1ba1e46d5d9c2, most recent Compressor restart reliability Compressor P0 reliability: retain applied DSP settings across device restart and unpolled ACK #489.dirtyagainst currentmain: the branches diverged (13 newer main commits since M1 history). This is the real conflict; old green tests do NOT qualify a new merge resolution SHA.src/Main.cpp,src/LiveAudioEngine.h,CMakeLists.txt,.github/workflows/ui-smoke.yml,site/preview-v2/assets/mixer-fx-rack.css,mixer-contextual-buttons.css,web/approved-native-bridge.js, and FX session restore. Preserve all merged main fixes while porting Vocal Throw.main.3) Feature checkpoint: native + UX
/preview/, not a parallel fake mixer.site/preview-v2/assets/mixer-native-vocal-throw.js,mixer-fx-rack.css, five SVG assets andtests/approved_native_vocal_throw_smoke.pycompared with M3. M4 did NOT change native audio engine.4974954.aiwas inspected but is not committed. Lightweight derived SVGs, including a cropped source-lit icon embedded insidearson-vocal-throw-performance.svg, ARE committed; the UI can be rebuilt from the repository.4) EXACT safe continuation sequence
mainin a separate integration branch (or a carefully reviewed M1 rebase), preserve newest merged compressor/harmony/player/device/FX code. Resolve M1 conflicts semantically, not by blindly accepting ours/theirs; verify native bridge → dispatcher → PCM graph → callback → ACK.mergeable=truevs parent proof againstmain.5) State of this reconciliation
No code, branch HEAD, PR base, installer or release has been changed; NO extra CI was dispatched. This issue comment is the durable cross-thread handoff; M4 PR #479 remains the latest reviewed GUI proof. Future agents should audit live
mainand all four PR heads again before touching conflicts, then continue from this exact chain. Do not mistake a checkpoint for a release or a merge.