A Practical Guide To Sound Settings In elementary OS
Good audio is easy to take for granted until a video plays through the wrong device, a microphone records silence, or notification sounds become distracting. elementary OS keeps the main controls in a clean, beginner-friendly location, but several useful options are easy to miss if you only adjust the volume indicator in the panel.
The Sound settings area manages playback devices, recording hardware, volume levels, balance, and alert behavior. The exact appearance can vary slightly between elementary OS releases and between hardware setups, yet the basic workflow remains consistent. Understanding how these controls relate to applications and connected devices makes everyday troubleshooting much quicker.
This guide covers output and input selection, headphones and external displays, microphone privacy, system alerts, keyboard controls, and practical fixes for common audio problems. It also explains which settings belong to elementary OS and which may be controlled by the application you are using.
Opening The Sound Controls
Open the Applications menu and launch System Settings, then select Sound. You can often reach the same panel by clicking the speaker icon in the top panel and choosing the relevant settings option. The quick menu is useful for immediate volume changes, while the full Sound panel exposes device selection and configuration options.
The page is generally divided into output and input areas. Output refers to speakers, headphones, HDMI or DisplayPort audio, USB headsets, and Bluetooth speakers. Input covers built-in microphones, USB microphones, headset microphones, webcams, and other recording sources. If a device is connected after Settings was opened, close and reopen the panel if it does not appear immediately.
The panel normally displays a volume slider and a list of available devices. A selected device becomes the default route for ordinary desktop audio, although an application that was already running may continue using its previous route. This is why changing the default output sometimes appears to have no effect until a browser, media player, or meeting application is restarted.
Elementary OS relies on the Linux audio stack beneath this interface. Depending on the release and installed components, that stack may involve PulseAudio, PipeWire, or compatibility layers between them. In normal use, you should not need to manage those services directly; the Sound settings are the safest first place to make changes.
Choosing And Balancing Output Devices
In the output section, select the hardware where you want sound to play. Laptop speakers are usually listed by their internal audio controller, while a monitor connected through HDMI or DisplayPort may appear under the monitor’s name. USB headsets and DACs typically show up as separate devices, and Bluetooth speakers may appear only after pairing is complete.
Use the output volume slider to set the general level. If the interface provides a balance control, keep the indicator centered unless your speakers or hearing setup requires otherwise. A strong left or right bias can sound like a damaged cable, so checking balance is worthwhile before assuming that a channel has failed.
When a device offers multiple profiles or ports, the system may distinguish between stereo output, surround output, headset mode, or a digital connection. Select the profile that matches the hardware. For example, a monitor with built-in speakers needs an HDMI or DisplayPort output, while a 3.5 mm headset normally needs the analog headphone port rather than the laptop’s internal speakers.
| Audio task | Setting to check | Common symptom | Useful action |
|---|---|---|---|
| Laptop playback | Output device | No sound from built-in speakers | Select the internal speakers and raise volume |
| Headset listening | Output device and port | Sound remains on speakers | Plug in the headset, then choose its entry |
| Monitor audio | HDMI or DisplayPort output | Monitor image works but audio does not | Select the display audio device and check monitor volume |
| Voice recording | Input device | Calls or recordings contain silence | Choose the correct microphone and watch its level |
| Bluetooth listening | Paired Bluetooth output | Device connects without sound | Select it as output and reconnect if necessary |
| Quiet notifications | Alert volume and event sounds | Alerts are too loud or absent | Adjust alert behavior separately from media volume |
A display can accept video while rejecting audio, and a monitor can have its own muted volume control. Similarly, Bluetooth headphones may connect in a low-quality communications profile when an application opens the microphone. That profile change is often a limitation of Bluetooth audio rather than a fault in elementary OS.
If you regularly switch between speakers and headphones, make the change before launching the application you intend to use. Some programs select their audio route only at startup. When that is not enough, quit and reopen the program, disconnect and reconnect the device, or use the application’s own audio selector if one is available.
Setting Up Microphones And Recording
The input section lists the microphones known to the system. Select the source you want to use, then speak while watching the level indicator. A visible response confirms that the system is receiving a signal, although it does not guarantee that a video-call application has selected the same microphone.
Input volume controls recording sensitivity. If the level barely moves, raise the input volume or move closer to the microphone. If the meter stays at its maximum or recordings sound harsh and distorted, lower the level. Excessive gain cannot be repaired cleanly after recording, so aim for a strong signal that leaves some headroom during ordinary speech.
Built-in laptop microphones can pick up keyboard noise and fan activity. A headset microphone may produce clearer speech, but it can be hidden under a generic USB or headset label. Webcams also frequently include microphones, which can be selected accidentally when a camera is connected. Checking the live meter while speaking is faster than guessing from device names.
Applications such as video conferencing tools, screen recorders, and audio workstations may provide their own microphone menus. Set the preferred source in elementary OS first, then verify it inside the application. If the program has a mute button, a meeting-wide mute state, or a browser permission setting, those controls can override an otherwise correct system configuration.
Microphone privacy can also involve physical switches, keyboard keys, firmware settings, and application permissions. A crossed-out microphone icon or an unresponsive level meter may indicate a hardware mute state. Test the source in a simple recording application before diagnosing drivers or replacing hardware.
Managing Alerts And Desktop Sounds
Alert sounds are separate from the audio you hear from music, games, or videos. Depending on the elementary OS release, the Sound panel may offer an alert volume control, an option for event sounds, or a choice of notification behavior. These controls affect desktop feedback such as warnings, message notifications, and interface events rather than every sound produced by the computer.
Lowering media volume does not necessarily make alerts quieter. If a notification interrupts a presentation or a concentration session, adjust the alert level independently or disable event sounds where the available settings permit it. You can still leave media playback at a comfortable level while reducing the sharpness of system feedback.
If alerts are missing, first check that event sounds have not been disabled and that the selected output device is active. Some notifications are visual only, and individual applications may offer separate sound switches. A messaging app can therefore remain silent even while the operating system’s own test or warning sound works correctly.
Notification timing also matters. A Bluetooth device that has just disconnected, a monitor that has gone to sleep, or a headset that has been unplugged can redirect alerts to another available output. After reconnecting hardware, review the selected output and test a notification or other short sound before relying on it for reminders.
For a quieter desktop, consider the broader ways to customize elementary OS, including appearance and workflow choices that can complement a restrained notification setup. Sound preferences work best when they fit the way you use the rest of the desktop rather than being treated as an isolated volume adjustment.
Fixing Common Sound Problems
Start with the simple checks: confirm that the correct output is selected, raise the system volume, and make sure the hardware itself is not muted. Speakers, monitors, headsets, and Bluetooth devices often have independent volume buttons or controls. A muted monitor can make a perfectly configured HDMI connection seem broken.
Next, close and reopen the affected application. If that fails, disconnect and reconnect the audio device, then revisit the Sound panel. For Bluetooth hardware, remove excessive distance and interference, verify that the device is connected for audio rather than merely paired, and reconnect it if the profile appears incorrect.
When no device appears, check physical connections and restart the computer if the hardware was attached during boot or after a system update. USB audio equipment can be tested in another port. Headphones can be tested with another phone or computer, while the laptop’s speakers can be checked after removing the external device. These comparisons help separate an elementary OS configuration issue from a hardware problem.
If sound disappeared after installing an update, inspect whether the output device changed or whether the audio service needs a fresh session. Logging out and back in can reload desktop audio integration without requiring deeper commands. Advanced users can inspect audio devices with system tools, but changing low-level profiles or service files should come after the graphical checks.
Crackling, delay, or sudden quality loss often points to a Bluetooth profile change, an overloaded audio connection, or an application requesting a different sample rate. Wired USB or analog audio can help identify whether the problem is specific to Bluetooth. For meetings, selecting a dedicated headset microphone may also force a communications profile that trades music quality for reliable two-way speech.
Recommendations For A Reliable Setup
A small amount of preparation prevents most everyday disruptions. Use the Sound panel to establish sensible defaults, then verify them in the applications that matter most. Keep an eye on both output and input, since a change made for a meeting can affect music playback or screen recording afterward.
- Select the intended output and input devices before starting a call, presentation, or recording.
- Test microphones with the live input meter instead of relying on device names alone.
- Check monitor, headset, speaker, and Bluetooth volume controls in addition to the desktop slider.
- Restart an application after changing audio hardware if it continues using the old route.
- Keep event sounds at a comfortable level and disable unnecessary alerts during focused work.
These habits are especially useful on laptops that move between a desk monitor, wired headphones, a USB dock, and Bluetooth accessories. Each connection can create a new audio route, and elementary OS may choose the newest available device automatically. A quick inspection of the output list avoids sending private call audio through a room’s external speakers.
It is also worth identifying the microphone that gives the clearest speech before an urgent meeting. Record a short sample, listen for background noise, and note the input level that works well. Save those observations mentally or in a note, because the best device is not always the one the system selects by default.
Keep Audio Predictable
Sound settings become much easier to manage once output, input, alerts, and application controls are treated as separate layers. Choose the device in elementary OS, confirm the volume and level, then check the program that is producing or recording audio. That sequence resolves most routing problems without command-line intervention.
Use the Sound panel the next time you connect a headset, display, microphone, or Bluetooth speaker, and test each device before depending on it. A few seconds spent checking the route and input meter can prevent missed notifications, silent recordings, and awkward meeting delays.
