Home / Troubleshooting / Audio

Current version 0.9.10 · Last verified 2026-10-24

Azimuth audio problems

Two audio defects are in the devlogs. Update 0.9.6 addressed a crash when the device was not running at 48 kHz. Update 0.9.10 addressed Linux PipeWire using a large buffer, which could mean no sound or a crash. 0.9.6 0.9.10.

Update the stock wrapper before treating old workarounds as current requirements. The non-48 kHz startup crash was fixed in 0.9.6; the sources do not require a 16-bit output format or make 48 kHz mandatory in 0.9.10. The steps below are diagnostic checks, not a tested universal cure for crackling.

1. Update to Azimuth 0.9.10.
2. Check the active output device and operating-system/app volume. These are general audio checks, not a verified Azimuth-specific fix.
3. Match the launcher output layout to the actual speakers: Stereo, 5.1, 7.1 or System. The 0.9.9 notes say Stereo is the default.
4. For the historical sample-rate startup crash, compare with 48 kHz if the device offers it. The defect was fixed in 0.9.6; do not assume it explains all silence or crackling.
5. On Linux, update before editing PipeWire quantum settings.
6. If it still fails, mail the LOG to [email protected]; add the DMP if it crashes. Report requirements.

Crackling, timing and output-device changes

The 0.9.9 notes fix audio stutter by giving Windows audio threads the requested timing. The 0.9.10 notes restore sound after sleep, unplugging or output switching and correct video loudness. They do not document a new video-volume slider or a universal crackling fix. Keep data/logs/azimuth.log from a reproducible failure.

A quiet radio mix and complete silence are different symptoms. See language and audio settings for documented controls; no official custom-radio import control was verified.