Trueplay - Surround Distance Isn’t Accurate

My surround distance settings are greyed out, as are the sub phase settings. I updated the firmware in the speakers and teh S2 app,

So I just re-did the test with the phone right next to the left speaker and it still shows more than 10 ft away. 
 

The left speaker is too loud…if I turn off Trueplay and set it to 2-10 ft it lowers…but when I turn Trueplay back on it reverts back to 10+ feet. 
 

Very disappointing that Trueplay can’t get the distance of the surround correct. 

I had this issue when I had the Arc connected to my system but it’s now greyed out in Arc Ultra. But like you, the distances say more than 10 ft when they are definitely under 10. I hit reset in that page and it switched to between 2-10ft, but I wonder if that messes up the Trueplay tuning.

Even with the wrong distances - how does your system sound?

The left one (right next to my head) is too loud. I had to turn off Trueplay and lower that speaker to the middle setting of 2-10 feet. 

I see what is going on, When you toggle TruePlay off, the distance choices and phase for the sub, come back. I remember it used to be this way a year or so ago (Trueplay precluding having the option to change the distance and phase). 

Then in one of the updates, I think this year, they brought distance choices/phase back when TruePlay was engaged.

Now it appears TruePlay is setting the distance and the sub phase. My distances sound fine.

To @106rallye point: My system always sounds great (Room1: Arc/E300s/Sub3 and Room2: Pair OneSLs/Submini)

I’ve simply learned, over the years, that Sonos isn’t a software company, lol. Don’t upgrade the app stuff until the YT influencers say so. I always get my 2 room system to work, by fiddling around with it.

So I just re-did the test with the phone right next to the left speaker and it still shows more than 10 ft away. 

I’m curious, the surround spacing choices are choices, manually made and not determined by TruePlay or changed by TruePlay - at least in my experience. I’ve never heard of the Trueplay picking the “shows more than 10ft” or other choice.

• Can anyone confirm/correct my above for bignick?

Certainly, I could be incorrect here. If I’m understanding you bignick, maybe your expectation of this feature is incorrect?

 I don’t think any room correction software can compensate for a surround speaker close to one’s head.

What does all this mean? If it’s saying the speaker is more than 10 feet away and it isn’t, and the sound out of the closer speaker is too loud, what happens when I turn off trueplay, manually fix it to under 10 ft, then turn TP back on. Doesn’t that mess up the TP tuning?

I sit way closer to my left speaker compared to my right, so I Trueplay tune everything to where I’m sitting. 

If the Trueplay was accurate, it would show 2-10 feet on the left and more than 10 feet on the right.

I literally had to disable Trueplay to get the sound balance corrected. Can anyone at Sonos look into this?

My understanding is that Trueplay sets the distance much more accurately than is displayed in the Sonos App and the display for surround distance is set to ‘inactive’ when TP is enabled.

The fact the inactive display shows a ‘default’ display of more than 10ft is really irrelevant IMHO  - Only when Trueplay is disabled can the user then go onto adjust the surround distance of the left/right surrounds. The App provides 3 options only. What you are seeing in its inactive state is irrelevant from the things I’ve seen/read here in the community in the past. 

Maybe it would be better if the surround speaker distance was hidden from view when Trueplay is enabled to save any confusion here🤔?

My test isn’t scientific, just opinion based. 

But I turned off TruePlay and messed with the left speaker at all three distances…I kept it at 2-10 feet for a while and everything sounded pretty good. 

I did another TruePlay tuning and immediately the left speaker was blasting again…noticeably louder and showing a distance of 10+ feet. 

And if I’m being completely honest, I wish there was another option other than 2-10 feet…maybe 2-5 then 5-10. 

All in all I had to disable TruePlay. 

i guess if a user moves the ‘sweetspot’ slightly in the first stage and walks around the room differently in the second stage, then there might be some noticeable differences and note the changes can be subtle initially and change as you use the HT setup. So another TP tuning may sound different, but I don’t believe it’s anything to do with the manual change in surround distance as I’m pretty sure that setting is usually ignored when TP is enabled. Otherwise you would end up with a skewed audio output.

Being positioned at the ‘sweetspot’ in the first stage of tuning is usually what balances all the speakers in the HT setup.

Previously in S2, you could disable Trueplay, amend respective surround distance and turn Trueplay back on.

Shorter distance reduced the surround volume, larger distance increased it.

The new app no longer allows this workaround to adjust a specific surround volume, as the surround distance set with Trueplay off, no longer have any effect when Trueplay is subsequently enabled.

The app should have a surround balance slider to cater for such adjustments as Trueplay does not get the balance correct.

I think these are likely some software bugs that Sonos may still need to resolve - I have even seen the surround distance settings ‘active’ whilst Trueplay is enabled. Probably a screen refresh issue and if the speaker balance is not correct for the chosen ‘sweetspot’ position used in the first stage of TP tuning, then that likely is a TP issue that needs to be looked into aswell. Hopefully Sonos will have seen these things reported and will hopefully look into the issues.🤞

The TP speaker balance for chosen “sweet spot” has been incorrect for years. It’s not a new issue.

I don’t appear to suffer with that issue @Mr. T, personally speaking, but if it’s happening in your case, then here’s hoping Sonos can fix it for you and any others affected too.

Like you i would like to see a front/rear - left/right balance control too in the Sonos App, that’s just because I do tend to sit at different locations in our living room when watching TV, but when sat at my ‘preferred’ chosen sweetspot the HT speakers do seem reasonably well balanced via Advanced Trueplay here.

I notice a new iOS App 80.12.02 today on App Store, release notes say “Ongoing improvements to Trueplay”

I would assume that is potentially related to the recent reports of low bass with Arc Ultra/Sub after Trueplay has been enabled 

It would be nice if Sonos would be transparent on what these new updates are doing rather than leaving us all guessing. I’ll let you download it first 🙂

There are the Release Notes to refer too.

Plus discussions on Reddit say Advanced Trueplay has been fixed for Arc Ultra:

https://www.reddit.com/r/sonos/comments/1gqf9q3/new_sonos_app_update_available/

In my testing trueplay does not set the surround distance correctly. Previous app version was allowing us to set the distance even after running the true play , where I was able get the system sound right. now it has been disabled as usual . I’m not talking about the surround distance showed when it is greyed out , but how it sounds after running trueplay. It sounds louder and tiny(quality is jus not there). Very

frustrating! It would be great if you allow us to change the distance even after running trueplay like how it was in versions released in October . People keeping surrounds very close to LP will have this issue I guess. 

I noticed this on my system yesterday as well…

The surrounds are much louder than they used to be, so I checked and they were both set to “more than 10 ft” (and greyed out).  I turned Trueplay off and they went back to “2 to 10 ft” that I had them set to.  Turned Trueplay on again and they changed back to “more than 10 ft” and their volume increased.

As others mentioned, hopefully it’s just an update bug that overrides the manual setting and automatically changes the surround distance (and volume, accordingly) when Trueplay is on.

No update for this issue?

Still no update with the last firmware 

Is it so difficult to re-add this feature ?