External Speakers and Monterey

[liam_bowers]

Originally Posted by g716

Kate K from DisplayLink tech support got back to me suggesting I use Activity Monitor to quit "coreaudio". I don't have that as a process, but do have "coreaudiod". I forced that process to quit and it immediately started back up and the sound came through the DisplayLink audio jack just fine.

I've got a D6000 dock and I've just upgraded to Monterey and my external audio output no longer works.

Killing the coreaudiod process 'fixes' the issue for me too although it's obviously far from ideal.

[cibelly]

Here it stopped working even killing the process now. Nothing has changed, no updates recently. So weird...

[dhokes]

I've got the same issue. Has anyone actually raised a support ticket for this as the DisplayLink team don't actively look at these forums?!

[dhokes]

Update: I've just changed the Sound settings on my MBP and set the Output to Dell USB Audio and that appears to work!

[mgroshong]

Originally Posted by dhokes

Update: I've just changed the Sound settings on my MBP and set the Output to Dell USB Audio and that appears to work!

Can you tell me how to do that?

[GoodGuy2Know]

Originally Posted by liam_bowers

I've got a D6000 dock, and I've just upgraded to Monterey, and my external audio output no longer works.

Killing the coreaudiod process 'fixes' the issue for me too although it's obviously far from ideal.

Killing the coreaudiod also worked for me - I was having the same issue. Not great that you have to do that every time you unplug the Mac from the hub - but it beats restarting it

[mgroshong]

How do you kill the coreaudio?

[Designwonk]

Originally Posted by mgroshong

How do you kill the coreaudio?

On a Mac, go to your "Activity Monitor" and search for "coreaudiod" if it's not at the top. Hit the circle X in the top of the panel to quit the process.

Following these steps fixed the problem for me. While it's not ideal, it's a lot better than disconnecting or restarting every time my MacBook wakes from sleep! Thanks for "fix" everyone!

[michaellau]

Originally Posted by mgroshong

How do you kill the coreaudio?

Open your terminal and type the command "sudo pkill coreaudiod". It will prompt you for your password before it kills coreaudio.

I've added an alias to my shell config:

alias resetAudio="sudo pkill coreaudiod"

But you can also create your own mini application to do this using the Script Editor application.

In script editor, enter the following

do shell script "pkill coreaudiod" password "blah" with administrator privileges

but replace 'blah' with your password. Then from the File menu, choose Export..., then for File Format choose Application, and for Export As give your application a name you'll remember. I chose "Reset Audio"

This will create a simple application that will reset your audio and then immediately close.

Now whenever I plug in my display link I can simply use cmd+spacebar to open up spotlight search, quickly search for "reset audio" and press return. I don't even have to type the whole thing, spotlight search will usually find it just after "re".

[Basirk]

This is my first experience of DisplayLink having just bought a Dock.
I should have known. I was wooed be the "one cable" panacea, but deep down I knew that I was going to get annoying problems requiring ridiculous work arounds until someone fixes the drivers. Then wait for the next OS update to break something else.

So yeah, +1 with no audio. And back to two cables plugged into my Mac :/
... and a whistling PSU on the dock.
... and visual "jpeg" artefacts in my editor.
Apart from that it's awesome.

How long typically before these things get fixed? This thread is already nearly 6 months old!