Hub / Hardware / Spatial audio

planned

Spatial audio

Two-PA prototype path plus local MONO/QUAD speakers; eight-PA venue plan.

Spatial audio concept
Concept illustration — not a wiring reference

Engineering

Arena audio — PA and local obstacle sound code / bench designs

Reviewed 2026-11-11. Room PA and local obstacle audio are separate paths. audio_controller/ and the gateway audio bridge exist, while physical commissioning and measured latency are not established by code presence. Canonical: REAL_ARENA.md.

Current prototype choices

PathHardwareStatus
Room PAMac → USB interface → two powered PA; Pi is an alternative hostSeparate software/audio path; validate output hardware and latency
Obstacle MONODFRobot DFR0299 → PAM8610 → one FR10HM 8 ΩDFPlayer commands exist; v3 wiring/checksum and timing need acceptance
Obstacle QUADTeensy 4.1 + two PJRC Rev D2 + TCA9548A → four PAM8610 / FR10HMFour independent outputs proposed; new engine and protocol required

Audio files stay on local microSD. Wi-Fi carries effect commands, not live audio samples. TCA9548A selects the same-address adapters over I²C; I²S carries audio with common clocks. Four amplifiers behind one DFPlayer would not create four independently mixed outputs.

Synchronization to validate

Current block playback starts when an FX command arrives. Four gains, scheduled start/stop and acknowledgements are not in the present firmware. A common QUAD audio clock does not synchronize separate obstacles or PA over Wi-Fi.

Measure audio onset and LED/audio skew; <50 ms is a target, not a demonstrated DFPlayer result.

Long-term hybrid plan

The older venue model scales two PA toward eight, optionally sixteen, with future tactile-exciter experiments on obstacles. Current FR10HM speakers are not exciters. The dated ~12–20k CZK prototype / ~75k CZK venue audio estimates are not current quotes for v3 QUAD.

No Pi is required inside each obstacle. Per-wall network audio fleets remain an unselected alternative.

Gateway audio positions/events use UDP :4120/:4121. Current obstacle FX use WebSocket /smart_block; floor control uses the separate authenticated /floor_led RGB frame stream. Obstacle design · Implemented contract.