Getting the Most From elementary OS Sound Output Settings

elementary OS ships with a clean, focused desktop environment where every default panel is designed to expose only the controls most users actually need. The Sound section of System Settings is no exception: it offers a stripped-back view of audio inputs and outputs that hides much of the underlying plumbing from view. Underneath that tidy interface sits PulseAudio on most installations, with PipeWire available on newer releases and certain community spins. Either way, the goal is the same — to give users a reliable way to send audio to the right device without having to drop into a terminal.

For many Australians, the laptop is a portable workstation that moves between the kitchen bench, the home office, and the local café down the road. A typical arvo spent working from a Melbourne laneway cafe might involve Bluetooth headphones connected to the laptop, a USB speaker on the desk back home, and an HDMI display in the spare room that doubles as a TV for conference calls. Switching between those outputs without rebooting an application or pulling out a cable is exactly what the Sound Settings panel is built for, and getting comfortable with its layout saves a lot of friction.

This walkthrough looks at how the output controls are organised, how to pick the right sink for different environments, and how to troubleshoot the common gremlins that appear when devices refuse to show up. The advice applies whether you are running elementary OS 8 Circe, an older 7.x installation, or a fresh daily build, and assumes nothing more than a working desktop session and a willingness to click around the panel.

Understanding the Sound Settings Panel

The Sound Settings panel lives inside the main System Settings application, accessible from the wingpanel or the Applications launcher. When opened, it presents two tabs: Output and Input, with the Output tab loaded by default. At the top of the Output tab is a drop-down menu listing every audio sink the system can see, followed by a horizontal volume slider and a balance control underneath it. Beneath the slider sits a small icon strip that lets you test each output by playing a short sample tone.

The drop-down menu is the heart of output management on elementary OS. It does not merely mirror the list that PulseAudio or PipeWire exposes internally — it filters that list to remove phantom sinks, disabled devices, and monitors, leaving only the destinations a user is realistically going to want to send sound to. Selecting an entry from the drop-down immediately reroutes every application currently playing audio to the new sink, provided those applications are configured to follow the default output. Applications that have pinned themselves to a specific sink will not move, which is occasionally the cause of a head-scratching moment when one app plays through the new device and another stubbornly stays on the old one.

The balance slider below the volume control adjusts the left-right balance for stereo outputs. It is centred by default and snaps to the middle when the user clicks and drags past the neutral point. For users with hearing asymmetry, or those running a speaker setup where one monitor is closer than the other, the balance slider offers a quick correction without needing to open a third-party mixer.

Selecting the Right Output Device

Picking the right output is usually a matter of choosing whatever is plugged in or paired, but the order of preference can matter. The built-in speakers on most laptops are convenient but rarely the best-sounding option, especially on a warm Australian afternoon when the cooling fan kicks in. A USB DAC paired with a decent pair of headphones tends to deliver cleaner audio and bypasses the noisy internal amplifier, which is why they are popular among users who spend hours on video calls.

When the drop-down shows more than one USB DAC or HDMI output, elementary OS remembers whichever device was most recently selected and restores that choice on next login. This behaviour is convenient in a fixed setup but can be confusing in a multi-room environment. A user who works from a coworking space might find their laptop defaulted to the HDMI output of a meeting-room display they used the day before, even though they are now sitting at their usual desk with headphones on. Switching back is just a matter of reopening the drop-down and selecting the headphones.

For users who frequently move between locations, the most reliable approach is to make a habit of opening Sound Settings whenever a new device is connected. The panel responds to plug events within a second or two, and a quick glance at the drop-down confirms that the desired sink is selected before the user opens their browser or starts a video call. Keeping a small pair of wired USB headphones in the laptop bag is a common fallback when Bluetooth misbehaves in transit.

Managing Bluetooth and Wireless Audio

Bluetooth audio on elementary OS relies on the same BlueZ stack and PipeWire or PulseAudio modules that other modern Linux distributions use. Pairing a headset through the Bluetooth panel adds it to the list of available output devices in Sound Settings, but the order in which it appears depends on the connection state. A paired device that is not currently connected will not show up in the drop-down until the user reconnects it from the Bluetooth panel.

For users who rely on wireless headphones during a long commute on the Sydney or Melbourne train networks, the most common source of frustration is the headset dropping off the list after the laptop wakes from sleep. elementary OS does not aggressively reconnect Bluetooth peripherals the way some mobile operating systems do, so the user often has to either click the device in the Bluetooth panel or trigger a manual reconnect from the Sound Settings drop-down. Once reconnected, audio resumes from the same application that was playing before the sleep event.

Latency is another consideration. Bluetooth codecs such as SBC and AAC are supported out of the box, but aptX and LDAC may require additional packages depending on the version of elementary OS and the underlying audio server. Users who need low-latency audio for music production or live streaming should generally avoid Bluetooth altogether and use a wired USB or 3.5 mm connection instead. The Sound Settings panel will not warn about codec mismatches, but a stuttering or delayed signal is usually a clue that the wireless link is the bottleneck.

Configuring Volume and Balance Per Application

The system-wide volume slider in Sound Settings sets the master level, but elementary OS also exposes per-application volume controls through the Multimedia Indicators extension in the wingpanel. Clicking the speaker icon in the top-right opens a list of every application currently producing sound, with its own slider next to it. Adjusting those sliders does not affect the system volume; it only changes the level for that specific application, which is useful when a video call is louder than the music playing in the background.

Per-application levels persist across sessions, so a user who has dialled down their browser to 60 percent one day will find it at 60 percent the next. This is helpful for apps that always launch at full volume, but it can also cause confusion if a user expects every application to start at the same level. The underlying audio server stores these settings in a small database file, and clearing that file resets all per-application volumes to 100 percent. elementary OS does not expose a button to do this in the GUI, so users who want a clean slate need to remove the file manually or use a command-line tool such as pactl or wpctl.

For users running a desktop speaker setup where one monitor is significantly closer than the other, adjusting the balance slider for the system as a whole is usually enough. For setups with more than two channels, however, balance adjustments in Sound Settings only affect left and right. Anything beyond stereo requires a different tool, such as PulseAudio's paprefs or PipeWire's wpctl invoked from a terminal.

Troubleshooting Common Output Problems

The most frequent issue users encounter is an output device not appearing in the drop-down at all. The first step is to check whether the device is physically connected and powered on, and whether the cable or wireless link is functioning. A USB DAC plugged into a front-panel port on a desktop tower in a hot Adelaide garage, for example, may disconnect intermittently if the USB controller overheats. Moving the device to a rear port usually resolves this kind of thermal dropout.

If the device is connected but still not listed, opening a terminal and running pactl list sinks short (or wpctl status on PipeWire) confirms whether the audio server sees the device. If the device appears in that listing but not in the Sound Settings panel, the most common cause is that the panel is filtering it out because it is set to off or unplugged. Forcing it on with pactl set-sink-mute 0 false brings it back into the GUI on most installations.

Another common problem is audio playing through the wrong sink after a display change. Plugging an HDMI cable into a lounge room TV immediately routes audio to that sink, even if the user intended to keep listening through headphones. Unplugging the cable sends audio back to the default, but users who frequently hot-desk between rooms often prefer to set a specific sink as the permanent default. This can be done through pavucontrol or by editing the user's WirePlumber configuration to set a default sink by name, which is then respected by every application that follows the default.

Finally, audio that is crackling, popping, or distorted usually points to a sample-rate mismatch or a buffer underrun. elementary OS sets a reasonable default for most hardware, but USB DACs that support higher sample rates than the system expects sometimes negotiate the wrong format. Opening the configuration for the affected sink and forcing it to 48000 Hz at 16-bit usually clears up the distortion without any other intervention.

A solid next step is to open Sound Settings on your own machine right now, list every sink currently visible in the drop-down, and identify which one you would want to be the default after every reboot. Once you know the name of that sink, the pavucontrol or wpctl set-default command can lock it in, and your audio will follow you wherever the day takes you.