Like the topic title says, Just putting it out there. Hope option for Front speakers happen soon.
New CEO really seems to finally care about customers wishes and wants. Hopefully this is one first things that comes out very soon.
After this happens, love see DTS;X finally arrive.
It’s already possible with Sonosequencr.
It’s already possible with Sonosequencr.
Very true. But I not have iPhone and much rather have it native thru the Sonos app instead having jump thru hoops.
Yes, hard to believe someone wants to deal with Sonos app. Stranger things have happened though.
It’s certainly been a request since 2013, when the PLAYBAR was released.
It’s certainly been a request since 2013, when the PLAYBAR was released.
New CEO seemed to lightly hint it is being highly considered or maybe in process. Wish more was shared. Maybe CEO unsure himself on timetable.
But I’d love have it like yesterday. Plus Sonos sell more speakers too.
Interesting, I missed that ‘hint’, could you share where that was posted? I’d be delighted if that turns out to be happening, I’d prefer three separates for my front speakers, rather than my current soundbar.
Interesting, I missed that ‘hint’, could you share where that was posted? I’d be delighted if that turns out to be happening, I’d prefer three separates for my front speakers, rather than my current soundbar.
From the above reddit link:
We’ve actually done a fair bit of work on this over the years, including an external beta where we let people try out a front L/R setup using speakers like the Ones. The bones of that effort are still buried in the software, which is how tools like SonoSequencr can recreate the configuration today. But what we learned in the process gave us some humility. It turned out that pushing discrete front channels over wireless, especially that close to the soundbar in some homes could cause a lot of packet drop and bandwidth issues. That created dropouts right in the front soundstage. That kind of thing is unforgiving. It’s super noticeable and totally undermines the experience.
Gee, packet drop and bandwidth issues due to pushing discrete front channels over wireless causing dropouts. Who’da thunk it? 😉
I think it is related to the space between radios issues like I was having here. Three feet is about the minimum that works well for me, closer and I get drops.
In different rooms/Rooms a pair of Play 3s and a gen 1 Beam at one foot (through a wall) didn't work.
Two Play 1s in a verktical stack really didn't work well at all.
Making the 3 front speaker option available, but warning of the spacing needs, would likely cause more grief than the additional sales would support.
Now a new Atmos Amp with l/r/c and two height channels that also supported two Subs, that I'd be tempted by. Maybe Bond two for a Somos powered room full of other-brand speakers and you'd be tempting folks to replace their AVR with an Amp.
From the above reddit link:
We’ve actually done a fair bit of work on this over the years, including an external beta where we let people try out a front L/R setup using speakers like the Ones. The bones of that effort are still buried in the software, which is how tools like SonoSequencr can recreate the configuration today. But what we learned in the process gave us some humility. It turned out that pushing discrete front channels over wireless, especially that close to the soundbar in some homes could cause a lot of packet drop and bandwidth issues. That created dropouts right in the front soundstage. That kind of thing is unforgiving. It’s super noticeable and totally undermines the experience.
Gee, packet drop and bandwidth issues due to pushing discrete front channels over wireless causing dropouts. Who’da thunk it? 😉
Yet I’ve never heard anyone who has used Sonosequencr to add fronts make such complaints…
Yet I’ve never heard anyone who has used Sonosequencr to add fronts make such complaints…
I’m sure the problems are edge cases. But Sonos has to consider edge cases. We only have to look at the app disaster to see what happens when they don’t.
Yet I’ve never heard anyone who has used Sonosequencr to add fronts make such complaints…
I’m sure the problems are edge cases. But Sonos has to consider edge cases. We only have to look at the app disaster to see what happens when they don’t.
Having the optional ability to add fronts in the app is completely different to releasing an unfinished app.
Having the optional ability to add fronts in the app is completely different to releasing an unfinished app.
Not as I see it. If the option to add fronts caused dropouts in 1% of the installations, that would mean 10’s of thousands of systems were affected. Would it be any more acceptable for 10’s of thousands of people to be coming here with problems with a new feature than the number having problems with the new app? Of course not.
Having the optional ability to add fronts in the app is completely different to releasing an unfinished app.
Not as I see it. If the option to add fronts caused dropouts in 1% of the installations, that would mean 10’s of thousands of systems were affected. Would it be any more acceptable for 10’s of thousands of people to be coming here with problems with a new feature than the number having problems with the new app? Of course not.
As if tens of thousands of people ever visit this community. Of course not.
As if tens of thousands of people ever visit this community. Of course not.
That’s sort of my point. There weren’t 10’s of thousands here about the new app, but there was certainly an uproar. I can’t say for sure the percentage of those who were affected, but I don’t think calling them edge 1% cases (such as would be seen with allowing wireless front speakers) is far from the truth..
As if tens of thousands of people ever visit this community. Of course not.
That’s sort of my point. There weren’t 10’s of thousands here about the new app, but there was certainly an uproar. I can’t say for sure the percentage of those who were affected, but I don’t think calling them edge 1% cases (such as would be seen with allowing wireless front speakers) is far from the truth..
The half-baked app was not due to edge cases. Anyone using the app on release knew it wasn’t fit for purpose.
As I said previously, I’ve yet to see a user complaining about packet drop and bandwidth issues.
Even if a user did have an issue using front surrounds, they can easily just remove them from the equation and go back to the “approved” setup.
The half-baked app was not due to edge cases. Anyone using the app on release knew it wasn’t fit for purpose.
As I said previously, I’ve yet to see a user complaining about packet drop and bandwidth issues.
Even if a user did have an issue using front surrounds, they can easily just remove them from the equation and go back to the “approved” setup.
Agree to disagree. Both the new app and the option to add L/R speakers to a soundbar should have been held back if even edge case scenarios caused problems. And the anecdotal evidence of an a few people using a relatively obscure app not seeing any problems is not proof the problems did not exist.
The half-baked app was not due to edge cases. Anyone using the app on release knew it wasn’t fit for purpose.
As I said previously, I’ve yet to see a user complaining about packet drop and bandwidth issues.
Even if a user did have an issue using front surrounds, they can easily just remove them from the equation and go back to the “approved” setup.
Agree to disagree. Both the new app and the option to add L/R speakers to a soundbar should have been held back if even edge case scenarios caused problems. And the anecdotal evidence of an a few people using a relatively obscure app not seeing any problems is not proof the problems did not exist.
I never said problems couldn’t exist. What I did say was “If a user did have an issue using front surrounds…” which accepts some users may have an issue, probably no more so than the current users that have issues with their Sonos setup.
Whether you agree or disagree is immaterial. If a user wants to use front surrounds then they can.
I never said problems couldn’t exist. What I did say was “If a user did have an issue using front surrounds…” which accepts some users may have an issue, probably no more so than the current users that have issues with their Sonos setup.
Whether you agree or disagree is immaterial. If a user wants to use front surrounds then they can.
Actually, if they have problems with the front surrounds, they can’t use them if they want to, which is my point. Sonos shouldn’t release new functionality until even edge cases are working. Be that an option for L/R front speakers, or an app rewrite. It’s a philosophy Sonos has adhered to for 20 years, the only exception being the app rewrite which almost spelled their downfall.
If the SonoSequencr frontspeaker bonding fails, then the developer is unable to help, and the Sonos Support won’t help. Pay r/SonoSequencr a visit.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.