elementary OS sound settings: input, output and app audio
elementary OS usually presents sound controls as one tidy panel, but the controls sit on top of several layers. Applications create playback or recording streams, a desktop audio server manages them, and ALSA ultimately talks to most analogue, USB and built-in hardware. Bluetooth adds another path. Understanding those layers helps when a speaker works while a microphone does not, or when one application is louder than another.
This guide covers selecting inputs and outputs, balancing application streams, pairing wireless headsets and diagnosing faults across elementary OS releases. It also uses examples familiar in Australia, where laptops often move between a desk, a meeting room and public transport. Begin with Settings for routine choices; use the detailed mixer only when the simple controls cannot express what you need.
How the sound stack fits together
Most elementary OS systems route desktop audio through PulseAudio or PipeWire, depending on the release and installed packages. ALSA, the kernel-facing sound layer, handles many local devices, while BlueZ manages Bluetooth connections. Applications normally ask the desktop server for a stream rather than driving hardware directly. That arrangement is why changing the output in a music player may not override the system selection, and why one device can receive sound while another remains silent.
Open Settings from the applications grid and choose Sound to set the default output, default input and master levels. The panel is the best first stop because it expresses the choices most people need without exposing technical controls. Each application then inherits that default, although browsers, recording software and conferencing clients may keep their own selected device. Check the application’s audio menu if its sound differs from other programs.
Advanced controls live in PulseAudio Volume Control, usually installed as pavucontrol, and in command-line tools such as pactl. On PipeWire installations, wpctl and the native mixer provide equivalent detail. Do not replace the audio server merely because a guide names a different one; first check which stack the release uses. Mixing PulseAudio and PipeWire instructions can produce changes that appear correct but never affect the active stream.
Choosing and testing output devices
Select the output device in Settings, then test it before changing volume or adding effects. Built-in laptop speakers, a 3.5 mm headset, a USB interface and a Bluetooth headset should each appear separately when connected. The chosen device becomes the default, but its volume and mute state are remembered independently. After unplugging a USB adapter, reconnect it and confirm the selection because some systems revert to built-in speakers.
Use the Sound panel’s test control if your release includes one. Failing that, play a familiar recording and listen on each speaker rather than relying on a visible volume bar. A balanced test should reach both sides without one channel being much quieter. For HDMI or DisplayPort audio, the display must be selected as the output, and a television or monitor can silence audio when it enters standby. Reactivating the display often restores the stream.
Australian buyers commonly encounter USB-C headsets and adapters from JB Hi-Fi, Officeworks and online retailers. Check whether the dongle presents a USB audio device rather than only changing headphones or charging a phone; a USB-C port does not guarantee analogue audio support. Keep the product listing and packaging because misleading conduct, including false compatibility claims, is regulated by the Australian Consumer Law.
Setting microphones and other inputs
Choose the microphone in the input section of Settings. A built-in array, a wired headset, an external USB microphone and the headset half of a Bluetooth device are different sources. Connect the microphone first, then select it, raise its input level and watch the meter in the detailed mixer. A muted stream remains silent even when the microphone’s physical mute button is off, so check both software and hardware controls.
Test the source with elementary OS’s Sound Recorder and play the result back on a different output. If the recording captures a person but sounds distorted or very quiet, reduce the gain, move the microphone away from air vents and avoid extreme boost. Many Australian creators use USB microphones made by Sydney-based RØDE, and such class-compliant models usually appear immediately; older models or interfaces may need a compatibility check.
Noise is often mistaken for a faulty microphone. In an open-plan Australian office, keyboards, desk fans and voices from nearby desks can enter a wide-range microphone, while shared meeting rooms add reflections. Commuters on Sydney trains and Melbourne trams encounter platform announcements and wheel noise that can contaminate a call. A directional microphone, a close position and steady input gain solve more problems than installing another effect.
Controlling sound in individual applications
Install and open pavucontrol with sudo apt install pavucontrol to see each active stream. Its Playback tab lists applications and their volumes; the Recording tab does the same for microphones. Right-clicking a playback stream can move it to another output, which is useful when a browser is set to the wrong device. Mute or adjust the application there without changing every other program.
Some applications provide better controls of their own. A browser can override the default output, OBS can assign sources to separate devices, and a conferencing client can select a specific microphone and speaker. These settings may override the desktop default, and they can be saved between sessions. When recording, remember that some apps record the processed mix rather than the raw source, so monitor levels cannot be judged only by what is heard during playback.
Flatpak applications normally join the same desktop audio server, but their own settings still matter. Privacy controls in the application determine whether it can capture a microphone; an ALSA or Bluetooth device can be visible to the system yet unavailable to that app. A stream can also linger briefly after an application crashes, leaving an apparently busy mixer. Closing and reopening the app usually clears the stale entry.
Bluetooth audio for calls and headphones
Pair a wireless headset through Settings, then choose it under both output and input as needed. Pairing alone does not guarantee that it becomes the active device. Many headsets offer separate profiles for high-quality music and microphone calls, and the desktop may switch between them when a call begins. If sound disappears during a meeting, inspect the active source and sink in the detailed mixer while the call is running.
Bluetooth microphone quality can be much lower than wired quality because the headset may use a hands-free profile with narrow bandwidth and heavier compression. That limitation is noticeable on crowded Sydney or Melbourne public transport, where platform announcements and carriage noise compete with the speaker’s voice. Using the headset microphone for calls but built-in speakers for music is sometimes cleaner, although it can create an echo if both are active.
For recurrent connection problems, remove the headset in Bluetooth settings, forget it and pair it again after checking the battery. Multipoint headsets can remember two phones but may favour a recently active device. If audio connects but sounds intermittent, move the dongle away from USB 3 storage and cables, whose electrical interference can affect inexpensive receivers. A short USB extension can also improve a marginal connection.
Diagnosing common audio problems
Begin with a simple no-sound check: confirm the intended output in Settings, unmute the master stream, raise the application volume and play a new file. Then open pavucontrol and verify that the file has an active playback stream and is routed to the selected sink. The commands pactl list short sinks and pactl list short sources provide quick device names when the mixer display is unhelpful.
Crackling, clicks or distortion often come from a mismatched sample rate, an aggressive effect, a loose analogue connection or a congested Bluetooth link. Test with effects disabled and compare 44.1 kHz and 48 kHz material. A USB interface placed beside a power supply may also introduce hum. If only one game or call fails, repair that application’s settings before altering the entire desktop stack.
For a silent microphone, check source selection, mute state, input gain and the application’s permission to record. Watch the input meter while speaking: no movement points to routing or hardware, while movement with silence in the recording suggests a device-specific problem. Disconnect and reconnect the microphone, test it on another computer and try the internal microphone as a comparison.
Include the elementary OS version, desktop audio server, device name and exact symptom when seeking help. ElementaryNOW’s news, guides and community discussions are available through community support resources. Searching for the same release and hardware combination can reveal a known driver or configuration issue. Update the system and audio packages through the normal software updater, but avoid stacking unrelated fixes that make the original cause harder to isolate.
Creating a dependable daily setup
A dependable setup starts with one output and one input chosen as defaults. Set comfortable master levels, then check browser video, a local music file, a microphone recording and an actual call. Keep the microphone a little below the level needed to trigger clipping. If Bluetooth is part of the routine, repeat the call test after pairing because a successful music test does not guarantee a usable hands-free microphone.
Keep the advanced mixer available for exceptional cases rather than making it the main control panel. Familiar names such as built-in speakers, desk headset and recording microphone prevent accidental changes, while remembering the intended default makes recovery faster after an update. Applications that regularly use different devices should be configured directly, and their own mixer settings should be reset whenever the system default changes.
Open Sound Recorder, make a ten-second voice recording with the microphone you expect to use, and play it through your chosen output.
