Fixing Audio That Isn't Working on Haiku

No sound can originate in the application, mixer, selected physical output, Media Kit graph, media services, or kernel driver. Test those layers in order. Restarting services cannot create a missing driver, while changing driver settings is unnecessary when only one application’s stream is muted.

Establish the scope with a known file

Play a local audio file in MediaPlayer. Avoid a browser stream for the first test because network, codec, and website behavior add unrelated failure points. Then test a second native application or a system sound.

If one application is silent but another plays, the device and main media path work. Check that application’s mute, output, codec, and per-stream mixer control. If every application is silent, continue at system scope.

Record whether playback advances normally, stalls, errors immediately, or plays at the wrong speed. Those symptoms distinguish silent routing from format/timing failure.

Check mixer and physical outputs

Open Preferences → Media. The official user guide documents Audio settings, an Audio mixer, and hardware-specific panels. Confirm the intended audio interface and output are selected. A machine may expose analog, digital, USB, or another interface even when only one is connected to speakers.

Open the mixer while audio is playing. Verify the master and application stream are not muted and their levels move. Inspect the hardware panel for speaker/headphone output levels and channel mapping. Duplicate or unclear hardware controls can appear; change one setting at a time and note the original.

Check the physical path: power, cable, headphone jack, amplifier input, and speaker. Test headphones or another known output if available. A visible software meter does not prove the analog path is connected.

Restart Media Kit services once

Media preferences provides Restart media services, explicitly recommended by Haiku’s user guide for a derailed audio/video system. Stop playback, use that button, wait for devices to reappear, reselect the correct output, and retry the local file.

This resets media-server/add-on state and invalidates existing node graphs. Relaunch applications that held old media handles. Do not loop the restart repeatedly; if one restart has no effect, collect evidence at the next layer.

If restart fixes the problem temporarily, record what preceded the loss—sleep, USB removal, output switch, particular application—and report that lifecycle sequence. “Restart fixes it” is evidence of a service/add-on state bug, not a permanent solution.

Determine whether hardware is detected

If Media preferences shows no usable audio node, inspect hardware enumeration with the system’s device tools and preserve their output. Built-in PCI/HDA hardware should appear in device enumeration; a USB interface should also appear in USB enumeration. Detection on the bus does not prove an audio driver bound successfully.

Review /var/log/syslog for audio-driver, media_server, and media_addon_server initialization errors. Capture the complete relevant block, hardware vendor/device identifiers, Haiku revision/architecture, and whether the device works after cold boot.

Try a current supported Haiku build or live image without modifying the installation when practical. If the same exact hardware is absent there, consult current compatibility and file a driver report. Avoid installing an old third-party kernel driver from an unknown revision.

Isolate hot-plug and format problems

For USB audio, connect before boot, then test hot-plug separately. Use another port and direct connection rather than an unpowered hub. Record whether the device appears/disappears in Media preferences and whether restarting services is required. Device enumeration, audio-node creation, playback, and removal are four separate milestones.

If only certain files fail, the output driver is probably not the first suspect. Compare formats and test a simple known-supported file. A decoder/translator failure should produce application or media logs while other content plays.

If audio plays distorted or at the wrong rate, record the negotiated sample rate, channels, and format where tools expose them. Do not compensate with random mixer levels before establishing the format mismatch.

Report a reproducible audio defect

Attach the Haiku revision, architecture, exact controller/device IDs, Media preferences screenshots, listdev/listusb text where relevant, syslog excerpt, selected interface/output, and a minimal sequence. State whether a local file plays, meters move, service restart helps, and hot-plug changes it.

For one application, include its package/version and failing format. For system-wide loss, file against Haiku with driver/media evidence. Remove personal paths or unrelated log data before public attachment, but do not replace exact error text with a summary.

The reliable branch is: one app versus all; mixer/output versus no node; media restart versus persistent absence; bus detection versus driver binding. Each result eliminates whole categories and prevents needless system changes.

Related:

Sources: