Skip to content

[CHECKPOINT] SonKu P9.1 + P9.2 — operator-confirmed Windows FAT, reconciled main (2026-11-16) #720

Closed

Description

@masarray

Milestone B verified triage — 2026-11-17: checkpoint / spatial / checkpoint / archived. Classification ≠ completion of product feature or physical FAT.

Scope / release boundary: Completed historical reference; keep exact SHA and checkpoint branch immutable.

Exit criteria:

  • Preserve verified P9.1/P9.2 checkpoint SHA 763706a and its branch unchanged.
  • Close issue as completed reference only; do not claim the original stacked PR was merged.

Canonical issue ledger. Preserve historical evidence below; no speculative merging or rewriting approved audio.


Frozen engineering checkpoint — SonKu P9.1 + P9.2

Date: 2026-11-16 (Asia/Jakarta) · User-confirmed GUI screenshot v0.5.0-dev+g763706a1.

Restore references (DO NOT MOVE THE CHECKPOINT REF)

  • Exact qualified source commit: 763706a15a2617a10d23b5e2e43eb5689e454ccb
  • Recovery branch: checkpoint/sonku-p91-p92-operator-confirmed-20261116; created directly from exact commit above. Never force-push or develop on this branch.
  • Active research branch: research/sonku-p91-p92-fidelity-bass-reconciled-20261116 at same SHA during checkpoint.
  • PR stack: #719 P9.1/P9.2 (draft, base research P9.0), #717 P9.0 (draft, base P8.9).
  • main: 37985f02caecd93b22f853183888d81e18dc6736. Verified main...checkpoint behind_by=0, merge_base=37985f02...; 279 commits ahead of main in the experimental ancestry. NOT merged to production.
  • Reconciliation merge: ea0a7c0a5bb3afb2c4295176447c2eb78bb6835b, parents cd85ffee054dad6b3b752b5351d34921ddc92717 (P9.0) and 37985f02caecd93b22f853183888d81e18dc6736 (current main). Preserves merged #713 ASIO/WASAPI Audio I/O continuity, GUI/operator routing, session and global FX baseline.
  • Exact-SHA CI: GitHub Actions run #43773841088, overall success, scoped P9 PCM preflight success, fast native contracts success, Windows JUCE GUI & five CTest success. UI Chromium smoke also succeeded. Separate historical P8.3 physical-speaker diagnostic reports failure and was already failing before this checkpoint; not proof all repository checks are green.
  • Windows FAT artifact: artifact #14185078724, ZIP SHA256 2ea2a637cd8a2fd0cd7f8c148317d90eb799b4ff583388a29ac0dbe3fa8318f7, source provenance 763706a1.... Artifacts expire; reproducible source/checks are preserved by the branch, not the ZIP retention period.

Confirmed at this checkpoint

  • Operator confirmed latest Windows build's render-mode dropdown properly shows P9.1 + P9.2 · MUSIC / BASS and screenshot shows stage caption P9.1 + P9.2 · MUSIC FIDELITY · WORLD BASS · ROOM MODES. This is one combined native mode renderMode=9, not separate modes.
  • GUI capability flag p91p92MusicBassFoundation=true emitted only by reconciled prepared native mode; old P9.0 can retain P9.0 label. Native readback cannot make the open dropdown flicker.
  • P9-only direct HRIR / complementary LF crossover around 165Hz and separately positioned world-speaker low band, stereo L/R early reflections, bounded axial LF room response, legacy bass-shelf double-gain removed, protected gain. No second audio graph; no manual +7dB imposed on all sessions.
  • Native 44.1/48k source PCM tested anti-phase, 70Hz head-rotation ear dominance, block parity, bounded peaks, room-off zero modes, P8.9 regression, JUCE state ACK and legacy session restoration.
  • User screenshot shows test settings, not new factory defaults: Speaker Angle 82°, Spatial Mix 100%, Output Gain +7dB, Large (28.8×28.8m), source distance 1.6m, reflections 100%, reverb 62%, head yaw 0° and revolution 8.5s. These operator-adjusted settings are NOT an evidence-backed canonical factory preset; saved .smix states must remain honored.

Guardrails / unresolved

  • Do not rewrite the checkpoint branch, merge draft [SELECTED P9.1/P9.2 AUDIO BASELINE — DRAFT] Reconciled music fidelity and world bass #719 directly into main, or overwrite UI/audio changes with old P8 branch snapshots.
  • Project still lacks loudness-matched real music/headphone FAT against raw stereo/dearVR, personalized HRTF/BRIR qualification, field ASIO/device qualification and proof of physical subwoofer parity. Do not claim SonKu matches dearVR just because GUI is accepted.
  • Historical P8.3 diagnostic red is tracked separately. P9-specific tested job is green; do not re-enable/alter rejected P8.3 DSP merely to force a green badge.
  • On next work: 1) compare latest main and checkpoint before development; 2) create a new feature branch from the verified checkpoint if needed; 3) preserve main ancestry and old .smix migration; 4) run fast exact-source PCM and UI gates followed by Windows CTest/FAT; 5) only publish a newly verified artifact, keeping the prior SHA as rollback.
  • Field handoff and testing requirements: docs/SONKU_P91_P92_RECONCILED_MUSIC_FIDELITY_BASS_FAT_20261116.md.

Acceptance boundary: This is a reproducible source + operator-confirmed GUI checkpoint, not a public release, irreversible merge, or acoustic/dearVR equivalence certification.

Activity

  1. masarray commented on Nov 16, 2026

    @masarray
    OwnerAuthor

    Research-consumer link / CI clarification (2026-11-16)

    This immutable operator-confirmed P9.1/P9.2 checkpoint remains pinned to commit 763706a15a2617a10d23b5e2e43eb5689e454ccb and branch checkpoint/sonku-p91-p92-operator-confirmed-20261116 (unchanged). Active consumer ImerSip uses the same P9 PCM core through PR #722, stacked on selected PR #719. The earlier ImerSip #706 and divergent P9 trial #718 are closed as nonmerged research archives; their branches remain available. The historical P8.3 negative acoustic gate is now scoped to explicitly named P83 PR branches/manual run, rather than blocking unrelated P9/ImerSip work. Details and enforced source contract: docs/SPATIAL_AUDIO_AUTHORITY.md. Operator screenshot settings (+7dB gain, ER 100%, reverb 62%) are a listening checkpoint, not ImerSip factory defaults (0dB, ER 78%, late 33%). No changes were made to this frozen source/branch or to production main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions