Fix Mac sound problems in two questions.

Restart the app’s audio path.

When other apps play normally, the problem is usually inside the silent app or its assigned output.

1. Play something in the app, then check its own mute and volume controls.
2. In Sound settings—or SOUND if you use it—return that app to the System output and try again.
3. Quit and reopen the affected app after changing its output.

Check the Mac’s system output first.

If every app is silent, start with the shared output rather than changing individual apps.

1. Open Control Centre → Sound and make sure the Mac is not muted.
2. Select the intended connected speaker or headphones and raise its output level.
3. Disconnect and reconnect the device, then test with a second app.

Move the microphone off the headphones.

Using a Bluetooth headset microphone can switch playback to a lower-quality two-way mode.

1. In System Settings → Sound → Input, choose the Mac microphone or a separate USB microphone.
2. Choose the same input inside the calling app, then end and rejoin the call.
3. Keep the Bluetooth headphones selected only as the output.

Reconnect the Bluetooth audio path.

Persistent muffling is more likely to be a connection, device, or source-quality problem.

1. Quit apps that may still be using the headset microphone.
2. Turn Bluetooth off and on, then reconnect the headphones.
3. Compare the same audio through the Mac speakers; if only the headphones sound wrong, remove and pair them again.

Adjust that app independently.

macOS has one main output level; an individual app needs its own control.

1. Check whether the app already includes a volume slider and set it near a neutral level.
2. Use SOUND to give the active app its own volume without changing calls, music, or browser audio.
3. Compare at a comfortable system level before adding EQ.

Set a stable system level.

When everything is too loud or quiet, fix the shared output before tuning individual apps.

1. Use the keyboard or Control Centre to set the main output volume.
2. Check the hardware volume on external speakers or an audio interface.
3. Only then balance unusually loud or quiet apps independently.

Route only that app.

Changing the macOS output moves everything; per-app routing keeps the rest of your setup in place.

1. Make sure both output devices are connected and visible in macOS.
2. In SOUND, select the active app and choose the intended output.
3. Return it to System output whenever it should follow the Mac again.

Change the Mac’s main output.

Use the system output when every app should move together.

1. Open Control Centre → Sound.
2. Choose the intended speaker, headphones, display, or audio interface.
3. If it is missing, reconnect the device before changing app settings.

Separate the device from the Mac.

A one-sided external device is often caused by balance, a cable, pairing, or the device itself.

1. Check the left/right balance in System Settings → Sound for that output.
2. Reconnect the cable or Bluetooth device and test it on another source if possible.
3. Try another pair on the Mac; whichever device keeps the fault identifies the likely cause.

Check balance and compare sources.

Built-in speakers should receive both channels from every normal app.

1. Open System Settings → Sound and centre the output balance.
2. Test a different app and a known stereo recording.
3. Restart the Mac; if one side stays silent everywhere, contact Apple service.

Separate the microphone from the headphones.

A Bluetooth headset can switch to a narrow two-way mode when its microphone becomes active; that is different from ordinary volume ducking.

1. In System Settings → Sound → Input, choose the Mac microphone or a USB microphone.
2. Choose that same microphone inside the calling app, then leave and rejoin the call.
3. Keep the Bluetooth headphones selected only as the output and replay the same media.

If clarity returns but media is still quieter, test the any-output path: the calling app may also be ducking other audio.

Confirm which calling app is applying the ducking.

FaceTime, WhatsApp, and other calling apps can lower competing audio independently of the Mac’s normal volume controls.

1. Play the same short clip before and during the call and note whether its app slider actually moves.
2. Repeat once with another calling app or its browser version; if the drop disappears, the first app owns the behaviour.
3. Use per-app volume to rebalance the media source when possible, or keep the call and media on separate outputs.

The VoiceOver audio-ducking preference controls accessibility speech, not call-app ducking, so changing it is not a reliable test.

The display may not expose software volume control.

HDMI and DisplayPort often send a fixed-level digital signal and expect the display, TV, or attached speakers to control loudness.

1. Check the display’s own volume control and whether it supports DDC/CI volume commands—not only brightness.
2. Test Mac speakers or headphones connected directly to the Mac; working keys there confirm the display path is the limitation.
3. For finer control, adjust the active app before it reaches the display or use a display utility that supports your monitor.

A frozen macOS volume indicator does not necessarily mean audio is broken; the selected output may simply provide no software volume endpoint.

Check whether the interface expects hardware volume.

Many USB DACs and audio interfaces expose a fixed digital level and reserve listening volume for their physical knob or control app.

1. Use the interface or DAC’s hardware output control and verify that its control app sees the device.
2. Open Audio MIDI Setup and confirm the intended output channels and a sample rate the device supports.
3. Connect directly to the Mac instead of a hub for one test; if control returns, the hub or dock is part of the path.

Stabilise the Mac’s main output path.

When the selected device disconnects during sleep, docking, or Bluetooth handoff, Core Audio falls back to another available output.

1. Reconnect the preferred device first, then select it in Control Centre → Sound before reopening media apps.
2. If a display without speakers keeps taking over, disconnect its audio path or select a different system output after docking.
3. For AirPods used across Apple devices, change automatic switching to connect when last connected, then test another wake cycle.

The useful confirmation is repeatability: sleep and wake once after the change and see whether the same output remains selected.

Reset that app to the system output, then pin it again.

An app can retain its own device choice even after the Mac’s main output changes.

1. Set the affected app to System or Automatic output and confirm it follows the Mac.
2. Quit and reopen the app, then assign the intended specific output again only if you need per-app routing.
3. Remove or disable stale virtual audio devices if they remain selectable after their software was uninstalled.

Reduce the output path to one known-good device.

System-wide clicks or dropouts usually point to the shared device, cable, hub, sample rate, or audio service rather than one app.

1. Test the Mac’s built-in speakers, then reconnect the affected device directly without a dock or hub.
2. In Audio MIDI Setup, choose a supported sample rate such as 48 kHz and make sure the active device is not changing formats between apps.
3. Close apps that install or hold audio devices, reconnect the output, and compare the same clip again.

If built-in speakers also break up after a restart, stop changing app settings and check for a macOS or hardware fault.

Match the clock, sample rate, and buffer before changing plugins.

DAW and interface dropouts are often caused by an overloaded buffer or devices running from incompatible clocks.

1. Match the DAW project, interface control app, and Audio MIDI Setup sample rate.
2. Raise the I/O buffer one step and test the same passage with the performance meter visible.
3. For an Aggregate Device, choose one reliable clock source, match every subdevice’s sample rate, and enable drift correction only for devices without hardware sync.

Test one interface by itself before rebuilding the aggregate; a clean single-device test separates clocking from CPU load.