Skip to main content
Contributor I
June 10, 2024

Sonos Ace - Mic issues with Slack

  • June 10, 2024
  • 32 replies
  • 1932 views

Hi everyone,

Got my Ace headphones last week and really like them.

A big issue I’m having is with the microphone, specifically with Slack (I don’t seem to have this issue with teams, google meets, phone calls, etc.).

During slack calls, within a few minutes the Ace microphone seems to stop picking up audio. I’ve had several calls now where other people in the call suddenly stop being able to hear me. If I disconnect and reconnect to the call, that will usually buy me another few minutes before it happens all over again.

I’ve checked all of my macbook audio/slack audio settings, and everything is how it should be.

Wondering if anyone else has experienced this and/or found a way to fix it.

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
Pinned Reply By Corry P

Hi @Andre17 et al

Thanks to your reporting we have identified an issue affecting the system volume setting of Ace’s microphone when connected to macOS and are investigating.

Please be aware of the following workarounds:

  • Use a USB-C cable for line-in (not the 3.5mm cable, which doesn't carry microphone audio)
  • Configure the macOS sound settings input to use the built-in Mac microphone while using Sonos Ace for output

I hope this helps.

32 replies

Lyricist I
July 25, 2024

I am facing the same issue on my work laptop while using Chime on a Macbook Pro, the mic works fine for a couple of minutes and then stops working. I have to disconnect and connect again to get it working. I am connected using bluetooth and have multipoint connection enabled.

Corry P
Sonos Staff
July 26, 2024

Hi @melvimbe 

Thanks Danny - I’ll pass that on too!

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
Corry P
Sonos Staff
August 1, 2024

Hi @Andre17 et al

In our testing, we have not been able to reproduce this issue.

A thought, however - multiple applications were mentioned with macOS. Combine that with @melvimbe’s report indicating the issue showing in Windows’ system settings, and it implies that it is not an issue with these apps, rather an issue with remaining connected to your computers.

As we could not recreate this issue, and as it takes two devices to do the “Bluetooth tango”, I recommend that you try restarting your computers. I am not overly-familiar with Macs, but I know that a Shutdown of Windows doesn’t restart the kernel of the operating system in the way that a restart does - instead, it closes programs and saves the current state to disk, reloading it when turned on again. This is no good - we want a full restart of the operating system so that all the drivers are reloaded. A quick Google search suggests to me that macOS is the same.

I am aware that @melvimbe reported that he has tried restarting already, however, so if that does not help, please try unpairing Ace from your computer, then pair them together once more.

 

@melvimbe - The error you see when using USB is a concern - I do not see the same when connecting my Ace to my PC with USB. Please ensure Bluetooth is not connected to the same computer when you use USB, and perhaps try a restart (hold power for 10 secs) or a reset of Ace. 

 

I hope this helps.

 

 

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
melvimbe
August 15, 2024

@Corry P I was able to get my Ace working correctly via bluetooth with my windows laptop again.  

 

1 - Go into settings tell windows to forget the bluetooth connection.

2 - Restart your windows machine.

3 - Re-establish the bluetooth connection between Ace and windows.

 

It seems that windows doesn’t really forget the bluetooth connection, it’s stored in cache or something similar, until the machine is restarted.  This work around may work for Mac machines as well, I have no idea.

I call it a work around because the issue could very well happen again.  I’m not sure that Sonos could do anything to permanently fix the issue.

Danny
Corry P
Sonos Staff
August 16, 2024

Hi @melvimbe 

Fantastic - thanks for updating the thread!

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
Lyricist II
September 13, 2024

I think I found the issue on Mac. I just received my headphones today and attempted to use them during a few meetings and noticed the same issue. I’m running a mac, using Chime, and saw that after a few minutes the input volume on the headphones went to “zero”. You can see this in the sound setting of the mac under the output & input section. Select Input and then the headphones and you’ll see the slider incrementally move left to where there is no input volume. When this happens people can’t hear you speaking but if you increase the input volume people start to hear you again. However, this continues to happen again and again which you have to constantly adjust the input volume for people to hear you. 

I tested this by my old bose headphones and this issue did not happen. Also tested it with airpods and the issue didn’t happen. So, it’s clearly something between the Sonos headphones and the OS. 

 

Hope this helps and that a fix is made quickly. Without a fix these headphones are useless to me and I’ll just go buy another pair from bose or sony. 

Lyricist I
September 16, 2024

I think I found the issue on Mac. I just received my headphones today and attempted to use them during a few meetings and noticed the same issue. I’m running a mac, using Chime, and saw that after a few minutes the input volume on the headphones went to “zero”. You can see this in the sound setting of the mac under the output & input section. Select Input and then the headphones and you’ll see the slider incrementally move left to where there is no input volume. When this happens people can’t hear you speaking but if you increase the input volume people start to hear you again. However, this continues to happen again and again which you have to constantly adjust the input volume for people to hear you. 

I tested this by my old bose headphones and this issue did not happen. Also tested it with airpods and the issue didn’t happen. So, it’s clearly something between the Sonos headphones and the OS. 

 

Hope this helps and that a fix is made quickly. Without a fix these headphones are useless to me and I’ll just go buy another pair from bose or sony. 

 

This is a good catch! I just looked at my Mac OS volume settings too, confirmed, this is the exact issue at hand. I started a Chime call with the Sonos Ace, the OS level “Input volume” is randomly decreasing a little at a time whenever I talk through the microphone. Slowly decreasing till it hits 0 volume.

+1 to this needing to be fixed, else these headphones are useless. This has not been an issue with my previous Bose headphones either. I’ve been switching to my AirPods because of how unreliable the Ace is in meetings.

Corry P
Sonos Staff
September 17, 2024

Hi @dfarm3r 

That’s interesting! Could I ask you to please record a video demonstrating this behaviour, submit a support diagnostic from the Sonos app running on the Mac afterwards and get in touch with our technical support team? Thanks.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
Corry P
Corry PPinned
Sonos Staff
September 20, 2024

Hi @Andre17 et al

Thanks to your reporting we have identified an issue affecting the system volume setting of Ace’s microphone when connected to macOS and are investigating.

Please be aware of the following workarounds:

  • Use a USB-C cable for line-in (not the 3.5mm cable, which doesn't carry microphone audio)
  • Configure the macOS sound settings input to use the built-in Mac microphone while using Sonos Ace for output

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein
Lyricist II
September 27, 2024

Tried the USB and had an experience where after joining a call I removed the usb connection and then reconnected which caused the same behavior to occur. If I left it connected then the workaround worked. 
 

At any rate, this isn’t sustainable and I am looking for an update on when this will be fixed.