How to fix the audio output from the DisplayLink Docking Station is not working as expected on macOS 12 Monterey.

Our products based on DisplayLink technology have the ability to send an audio signal out via their 3.5mm analog audio jacks or via their HDMI or DisplayPort video output ports (which can also carry an audio signal). 

When a Mac running macOS 12 Monterey is used with DisplayLink-based products, there may be instances where the audio signal cannot be heard upon switching to the DisplayLink-based device.

It seems that this issue is related to the sequence of selecting and using an audio output device in macOS. Please note that the audio driver used for the audio device in any DisplayLink-based product is provided by Apple and is already integrated into macOS.

To elaborate further, consider these two scenarios:

'Successful' scenario

1. A Mac system is turned on with a DisplayLink device already connected.
2. The DisplayLink device is set as the default audio output device in the 'Sound' macOS System Preferences application.
3. An application plays an audio file.
4. The audio signal is properly heard through the DisplayLink device.

'Unsuccessful' scenario

1. A Mac system is turned on without a DisplayLink device connected.
2. The Mac's built-in audio output device is set as the default audio output device in the 'Sound' macOS System Preferences application.
3. An application plays an audio file.
4. The audio signal is properly heard through the Mac's built-in audio output device.
5. A DisplayLink device is connected to the Mac.
6. The default audio output device in the 'Sound' macOS System Preferences application is changed to the DisplayLink device.
7. An application plays an audio file.
8. The audio signal is NOT heard through the DisplayLink device.

Currently, there are three possible solutions to address this issue:
1. Restart your Mac.
2. Close the affected application entirely, then reopen it.
3. Run this command in the macOS Terminal application (without quotes): "sudo killall coreaudiod".


Note:

As far as we know, the macOS 12.4 update has resolved the issue regarding the unexpected behavior described below. Despite this, the following information has been kept for historical purposes.

コメントを書く

全てのコメントは、掲載前にモデレートされます

このサイトはreCAPTCHAによって保護されており、Googleプライバシーポリシーおよび利用規約が適用されます。