MiniAudio backend
Section titled “MiniAudio backend”The MiniAudio backend implements the neutral audio device using miniaudio’s engine, resource manager and node graph. Game code uses audio playback; host composition chooses the backend and owns its device generation.
Choose the operating mode
Section titled “Choose the operating mode”| Mode | What runs | What it demonstrates |
|---|---|---|
| Ordinary output | Native graph and the selected operating-system output device | Playback through that device when initialization succeeds |
noDevice |
Native graph advanced by explicit PCM reads during updates | Native preparation, clock, scheduling and completion without opening audio hardware |
| Neutral muted device | The separate managed muted implementation | Neutral runtime behavior without claiming native execution |
Hardwareless MiniAudio is not a skipped native test. It still requires matching native binaries, creates native clips and advances the native graph. Conversely, success in this mode does not establish that a physical output device works.
Supported adapter behavior
Section titled “Supported adapter behavior”The adapter supplies WAV/FLAC/MP3 preparation, decoded and streamed loading, independent voice cursors, scheduled playback, two-dimensional pan and basic three-dimensional distance/cone/doppler behavior. It supports one to four listeners, bus routing and the eight standard filter/delay processor families. Actual product/target composition and successful device creation determine availability.
Use the device project for options and disposal. The native reference is for backend authors, not an expanded gameplay API. Native library production belongs to the component toolchain.
Upstream and provenance
Section titled “Upstream and provenance”The inspected engine source pins miniaudio revision 9634bed, corresponding to its 0.11.25 header. Bindings and native source must move together. An upstream feature does not become an InnoEngine promise merely because a raw symbol exists.
The original miniaudio license is preserved without translation. Platform providers own target SDK selection; this shared backend does not maintain a second target-selection table. Current declarations and a buildable target are separate from completed hardware or platform acceptance.