OpenJOC v0.3.0
[0.3.0] — 2026-08-15
OpenJOC 0.3.0 is a feature release focused on a spatial-rendering foundation,
an experimental JOC spatial bridge, and clearer user-facing profile selection.
Added
- Explicit spatial-scene rendering with validated 2D speaker layouts, 3D
explicit-triplet layouts, sample-accurate trajectories, and caller-owned
block outputs. - Static binaural rendering with a direct FIR reference backend, a uniform
partitioned-convolution backend, and strict localSimpleFreeFieldHRIR
SOFA import for the supported NetCDF classic CDF-1 subset. JocSpatialBridgefor codec-coordinate binding, spatial projection, Q32 gain
scheduling, and linear accumulation in the supported ordinary domain.
Changed
- User-facing
decodeanddecode-payloadprofile selection now defaults to
AUTO, which triesETSI_STRICTbefore selecting a fully admitted
OBSERVED_VENDOR_COMPATfallback. ETSI_STRICTremains explicit and strict; it never falls back. The canonical
observed-deviation policy name isOBSERVED_VENDOR_COMPAT.- Public bridge and profile names are stable functional names; maturity,
validation evidence, and unresolved semantics are documented separately.
Experimental
- 0.3.0 introduces an experimental implementation of the JOC spatial bridge
for the currently specified supported domain. Its
SemanticBindingStateremainsUnresolved, and official runtime-oracle
fidelity is not independently confirmed.
Compatibility
AUTOfalls back only when every blocking deviation is admitted by the
observed-vendor compatibility whitelist. Malformed, unknown, or
non-whitelisted failures remain failures.- Legacy compatibility spellings remain accepted only as intentional input
aliases where documented; canonical output usesOBSERVED_VENDOR_COMPAT. - Raw warp value 3 remains opaque and preserved, excluded from ordinary
projection arithmetic, and unresolved in meaning.
Known Limitations
- The bridge does not claim official vendor equivalence, bit-exact reference
renderer equivalence, or a resolved JOC semantic binding. - The supported domain is narrower than all JOC content. Some bridge rules and
constants remain experimentally specified rather than independently
vendor-validated, and no official runtime reference confirmation is
established. - Explicit renderer workflows use caller-supplied sources and do not turn
unresolved reconstruction rows into authored-object audio. - Platform validation and publication remain scoped to the local Apple-silicon
macOS release-candidate workflow; no 0.3.0 tag or remote release is created
by this source closure.
Verification
- GitHub Actions verified the exact version tag, source tree, and release artifact checksums.
- The published binary targets are macOS arm64, Windows x86_64, and GNU/Linux x86_64.
- Per-platform manifests remain internal verification artifacts; the public asset set contains one unified SHA256SUMS file.