Skip to main content
Contributor I
Aug 14, 2022 1:21 PM UTC
Answered

After update to version 14.12, subwoofer sound problem, sound volume is low

After updating to version 14.12, I re-tuned the trueplay tuning, the result is that the subwoofer sound is small, position, sub audio is 0, but the volume is low. I'm using a Gen 3 sub woofer.

Hopefully sonos will fix this bug soon thank you

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.
Corry P
Corry PAnswer
Sonos Staff
Aug 15, 2022 8:20 AM UTC

Hi @bigboyz989 

Welcome to the Sonos Community!

We are aware of this issue, and are working on a solution.

More info can be found on the following thread:

 

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein

41 replies

Enthusiast II
Aug 31, 2022 8:57 PM UTC

I doubt that the “low volume” characteristic will be changed. There has not been any change in the maximum power output, only the output associated with lower levels of the control setting. Changing the control characteristic improves the ability to make small adjustments of Volume level at the low end.

You could make a similar judgement with respect to the accelerator in a car. The car will seem very powerful if a slight press on the accelerator results in an instant jump to high speed, but the car is difficult to control in bumper to bumper local traffic.

But this new volume mapping on just the Arc, does not match the rest of their products. Whether it's been done on purpose or not, the Arc is now the quietest thing in my house when everything else is playing the same thing at 25%. And they deem this intentional? The Arc has now been singled out from the rest of the product range by being on a different volume map and sound profile. Odd behaviour and certainly not progress in my eyes. It needs changing back, period.

Translate
Generalzod
Trending Lyricist II
Aug 31, 2022 10:42 PM UTC

Sonos has not yet released an update to address this. Nor will they talk about when it might (or might not) happen, as has always been the case for Sonos. 

Considering people have forked out a lot of money buying their stuff a little transparency can’t go to waste.

Translate
Avid Contributor I
Aug 31, 2022 10:42 PM UTC

I really don’t understand why its taking so long to address.  Clearly a lot of customers are livid. They should be able to fix it immediately by allowing customers to dial back the firmware to the previous version until they find a long term fix. Wake up. 
 

I have yet to purchase my system but waiting for this to be resolved before I risk spending US2$k on a system.

Translate
Generalzod
Trending Lyricist II
Aug 31, 2022 10:48 PM UTC

I really don’t understand why its taking so long to address.  Clearly a lot of customers are livid. They should be able to fix it immediately by allowing customers to dial back the firmware to the previous version until they find a long term fix. Wake up. 
 

I have yet to purchase my system but waiting for this to be resolved before I risk spending US2$k on a system.

How hard is it to restore back to the previous firmware update.

Translate
Avid Contributor I
Aug 31, 2022 11:17 PM UTC

Hi @bigboyz989 

Welcome to the Sonos Community!

We are aware of this issue, and are working on a solution.

More info can be found on the following thread:

 

While you look for a long term fix, can you allow customers to dial back the firmware? That can be done in minutes surely.

Translate
Airgetlam
Aug 31, 2022 11:19 PM UTC

Minutes?

 

Translate
Bruce
Avid Contributor I
Aug 31, 2022 11:33 PM UTC

Minutes?

 

Of course. They just need to move back to the old firmware while they find a long term fix  - more people seem to be unhappy about it than positive for sure otherwise you wouldn’t see hundreds of pages in numerous forums of customers venting their frustration.  No brainier.  Why they are being stubborn about it is beyond me. Not a good sign for potential buyers!

Translate
Airgetlam
Sep 1, 2022 12:09 AM UTC

I have been involved with lots of different pieces of software that change over time. There’s likely thousands of lines of code change, each with multiple dependancies, that have nothing whatsoever to do with this particular issue, but are part of the newer builds. With evolving software, it’s not “easy” or “minutes” to move backwards, it would require herculean effort, most of which is probably tasked with figuring out what happened, and how to make it better. Once that gets released, you normally then have time to figure out “how” it happened. 

It’s extremely unlikely that there was only a single change in the code release past 14.10. I’ve never seen such a beast in my 37 years of software management, although I suppose it’s possible. I don’t, however, work for Sonos, so I’m only basing my opinions on previous experience, not direct knowledge. 

Translate
Bruce
jgatie
Sep 1, 2022 12:37 AM UTC

I have been involved with lots of different pieces of software that change over time. There’s likely thousands of lines of code change, each with multiple dependancies, that have nothing whatsoever to do with this particular issue, but are part of the newer builds. With evolving software, it’s not “easy” or “minutes” to move backwards, it would require herculean effort, most of which is probably tasked with figuring out what happened, and how to make it better. Once that gets released, you normally then have time to figure out “how” it happened. 

It’s extremely unlikely that there was only a single change in the code release past 14.10. I’ve never seen such a beast in my 37 years of software management, although I suppose it’s possible. I don’t, however, work for Sonos, so I’m only basing my opinions on previous experience, not direct knowledge. 

 

30 years for me, and I concur.

Translate
Enthusiast II
Sep 1, 2022 8:38 AM UTC

I have been involved with lots of different pieces of software that change over time. There’s likely thousands of lines of code change, each with multiple dependancies, that have nothing whatsoever to do with this particular issue, but are part of the newer builds. With evolving software, it’s not “easy” or “minutes” to move backwards, it would require herculean effort, most of which is probably tasked with figuring out what happened, and how to make it better. Once that gets released, you normally then have time to figure out “how” it happened. 

It’s extremely unlikely that there was only a single change in the code release past 14.10. I’ve never seen such a beast in my 37 years of software management, although I suppose it’s possible. I don’t, however, work for Sonos, so I’m only basing my opinions on previous experience, not direct knowledge. 

14.10 is already written / saved somewhere/ published so it's not a herculean effort in my opinion to re-release it on just Arc and Sub at least. But let's face it, it'll never happen. Just like myself buying another Sonos product.

Translate