Audio Device Configuration

A display's volume control can use software processing, adjust its own speakers through a hardware controller, or adjust an associated native macOS audio device. This sheet helps you see which method is available, choose how supported mute operations work, and connect the display to the intended sound output. It also controls the display's keyboard volume feedback.

Where to find it: Settings > Displays > [display] > Device Control > Audio Device Configuration….

Available controls depend on the active controller and what it supports. Changes save per display without an Apply step. Closing the sheet does not discard them.

Feature Availability

The first box identifies the controllers. Hardware Volume Control names the available hardware volume controller, or the up/down controller when only relative commands are available. It shows Absent when neither is available. This identifies the hardware component even when software or combined volume is selected. With native hardware control enabled, it can name Native Audio. Add hardware controllers through Add or Remove Controllers… under Device Control, then use their Device Control cards for configuration.

Software Audio Controller shows Configured when Software Audio has been added to this display, or Absent otherwise. Configured does not mean that permission is granted or processing is active. Add it through Add or Remove Controllers…, then open Configure Software Audio… on its card.

Status messages appear beneath Software Audio Controller and use the same style on the Software Audio card and in its configuration. An information icon marks ordinary startup, active, disabled, idle-audio and system-sleep messages. A filled warning triangle marks problems such as missing permission, unavailable or ambiguous outputs, processing failures and hardware protection or readback failures. When permission status cannot be read, an informational hint explains that an explicit enable action can still request access.

A separate box immediately below shows Volume control and Mute control. Each reports Enabled (Hardware), Enabled (Software), Enabled (Native) or Enabled (Combined) according to its available provider. A missing or unavailable selected provider shows Disabled. The rows are independent, so combined volume can appear alongside software or hardware mute.

Hardware availability can mean relative up/down volume or toggle-only mute when that is all the controller supports. These commands do not supply an absolute volume percentage or a readable mute state. An unavailable software, combined or native route does not become enabled merely because a separate hardware command exists.

Associated Audio Device

The Associated Audio Device block follows Feature Availability, above the mute-method blocks. Associated audio device identifies the output used for Software Audio volume, mute and effects, optional native hardware audio control and keyboard audio-device matching. The field accepts a name or unique identifier and keeps the same label whether native control is enabled or disabled. Software Audio association and processing warnings appear beneath Software Audio Controller above.

Associate a native audio device

Use native volume and mute control for the associated audio device appears above the device field and defaults to off. It selects the output's native macOS controls as the hardware audio component. Software Audio’s hardware-priority preference selects available native capabilities before software fallback by default. Its Combined Volume Control methods take precedence when enabled. Enabling it immediately refreshes controller selection and menu controls, but does not change the Mac's current output or create a multi-output device.

Enter the intended output's name or UID in Associated audio device. This can help you coordinate native-volume devices alongside display speakers controlled by DDC or another integration.

Each native capability must be supported by the output. Unsupported native controls remain unavailable instead of falling back to another hardware controller. Mute is separate from volume, so one can work without the other. On this path, a native volume change above minimum requests unmute, while setting minimum requests mute when supported. The DDC/integration method groups are hidden.

Copy Current Device Name fills the field with the current default macOS output's name. Check that this is the device you intend to associate. The Mac's current output may be different from the output you want to control. Text edits commit with Return or when focus leaves the field, and Escape restores an uncommitted edit.

Audio Device Configuration showing native volume and mute enabled for MacBook Pro Speakers with Software Audio absent

Native association uses the named audio output and macOS volume controls. Hold Option when selecting Copy Current Device Name to copy its UID.

Matching and unavailable outputs

Use a distinctive full name or UID where possible. Partial strings work. When Software Audio is configured, native control uses the same uniquely resolved output as software processing. Otherwise the native matcher does not reject ambiguous matches. That native matcher first tries a case-insensitive exact full name. If none matches, it tries an exact normalized name, then the first partial normalized name match, ignoring spaces, parentheses and digits. Only if no name matches does it try a case-insensitive exact or partial UID.

When no exact full name matches, names differing only in model numbers can still collide. Even a UID has priority only after the app finds no matching name.

For a nonempty specified value, The specified audio device is not found or currently unavailable means that no output matches at that moment. The specified audio device does not have native volume controls appears when native association finds an output but it lacks native volume support. A matching output does not guarantee native mute support. Volume and mute availability are checked separately, and these messages do not change the Mac's selected output.

Audio Device Configuration with native control selected for a missing sample output, an unavailable warning and disabled volume and mute

A missing named audio output leaves native volume and mute unavailable.

Match the current output without native association

With native association off, Associated audio device helps Display with the same name as current audio device in keyboard target selection find this display. The volume operation still uses the display's controller. This field does not redirect DDC commands into an audio device.

Leave the field blank to compare normalized names using the display's original product name, rather than its custom displayed name. A nonempty override can match part of the current output's normalized name or UID. Several displays can match the same output and receive keyboard adjustments, which can be intentional in a multi-output setup. Each display must also allow keyboard control and provide the requested control.

Follow the monitor-and-headphone volume-key tutorial to combine this match with the separate listening policy and destination, then check both outputs safely.

Software and combined audio

Software Audio, including its optional Combined Volume Control routing, reuses the association field on this sheet. It stays editable when a route is unavailable. An exact UID is preferred for processing, and ambiguous matches must be resolved before interception starts. Its configuration sheet contains provision, routing and menu visibility settings, with tuning in Device Control.

Mute and unmute methods

Devices can respond differently to “set the volume to minimum” and “mute.” These preferences let supported controllers combine the two operations in the order your device needs. The three groups appear when the selected provider is hardware mute and native association is off.

DDC, custom Control Integration and the Yamaha AVR integration use these choices. Other stateful controllers, including LG webOS and Philips TV, may show the groups while continuing to use their own fixed volume/mute behavior. The choices do not rewrite those protocols.

Choose a Mute Method according to whether the device needs a minimum-volume write, an explicit mute command, or both:

“Lowest” means the configured volume range's minimum, which is not necessarily silence on every device. A separate mute command requires working mute support. When the DDC/integration path lacks a usable mute action, it can use minimum-volume control as its fallback.

The Unmute Method similarly determines how the volume level and explicit unmute command are combined:

Follow the mute and unmute tutorial to choose and test a sequence for your monitor, including its separate behavior at 0%.

Which level returns after mute

The restored level depends on the controller and the value retained at mute time. DDC uses its remembered last-mute volume when present. Control Integration uses the current nonminimum value first, falling back to the remembered value.

With DDC, the first adjustment while muted can therefore restore the remembered level instead of immediately applying the new level you requested. The unmute-only option is the exception when a volume change releases mute: it explicitly writes that adjustment. Do not assume that muting at 0% retains a previous audible level.

What happens at minimum volume

When Volume Reaches 0%… defaults to Use mute/unmute methods, making the configured minimum a mute operation in the paths above. Set volume to lowest setting writes the minimum without automatically invoking the mute sequence. Either way, the device can still have its own reaction to a minimum-volume setting.

Audio Device Configuration showing HDMI-CEC hardware volume and mute, Software Audio absent and native control disabled

HDMI-CEC supplies the hardware volume and mute controls in this setup.

Volume Control Settings

The final Volume Control Settings block contains Show volume OSD with keyboard control, which is on by default. Turn it off when the device already has a volume indicator and you do not want BetterDisplay's additional per-display volume/mute on-screen display (OSD). This does not turn off the monitor's own indicator, change the global OSD style, or suppress keyboard handling's separate current-output native fallback.

The OSD switch is available when ranged volume control is available or native audio association is enabled. An up/down-only controller does not enable it by itself.

Keyboard feedback

Feedback sound is independent of that checkbox. It follows the system's volume-feedback preference and applicable keyboard modifiers. When one affected display matches an audio output unambiguously, BetterDisplay can direct the sound there.

Sound routing uses a stricter match than native control. If there is no unique match, it may use the current output. If an explicitly resolved device becomes unavailable, it does not silently redirect that device's sound elsewhere.

Additional information

This section explains which features require Pro and how availability differs between Mac platforms.

Features requiring Pro license

The shared volume, mute-method, native-association and feedback preferences on this page do not themselves require Pro. A selected hardware or integration feature can have its own requirement.

Platform compatibility

All features described on this page are available on both Apple silicon and Intel Macs, subject to the selected audio device and controller. Native volume and native mute are separate capabilities. HDMI-CEC, if used as the underlying command-only controller, requires a supported Apple silicon HDMI path. Other hardware and network methods have their own compatibility requirements.