Answered

Sonos S2



Show first post
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.

180 replies

Userlevel 5
Badge +4

The new S2 app no longer persistently shows the elapsed and remaining time for the track being played. It does show the progress bar but the times appear when the track starts and then disappear after a couple of seconds. Same thing if you touch the screen while a track is playing - times re-appear, then quickly fade.

I really dislike this - I like to be be able to see at least the time remaining without having to continuously be tapping the screen. Very annoying. A step backwards by Sonos here.

I have dBpoweramp Music Converter for windows. I think it is the same, but i dont know how to set it up to convert from 24/96 to 24/48. Can you help me?

 

Use the dBpoweramp Music Converter, set to convert from FLAC to FLAC, then add the Resample DSP Effect and set the frequency to 48 KHz.  

Thanks jgatie 

Userlevel 7
Badge +15

Note that it looks like it's not just splitting your system and having them function as before but as two separate systems.

The ones that stay on S1 actually get reset and you lose access to all playlists etc. you may have created over the years.

Is the second part the reason for stating the first part? Any other way that splitting is more than just splitting, leaving the S1 playing as it has all these years?

And the second part can’t be nice - though I assume that this applies to local NAS playlists and not, for example, those made in Apple Music?

Hi Kumar, the first part is just an observation that the split isn't just a ‘Split your systems and carry on as before - but with them unable to link to each other.’ decision.

Effectively you start with all speakers running S1 (11.2) and then tell it which speakers you want to keep as part of S1.  Instead of splitting them off as a separate system with a separate App with its settings intact, it resets them all - but still ends up running the same software it did before the reset. A way of carrying on as before would have been good - especially if you have more than one speaker staying  on S1 (factory resets always a last resort but never really an issue if you had more than one speaker as the reset one had the setting reapplied when it was added again).

I haven't done the split as I have no reason to yet and the loss of the persistent time bar function is another form over function decision I could do without.

Also, my ‘in' to Sonosnet is my Connect and that is only S1 compliant.  I don't know how the change process would handle that - would I then lose connection to all speakers and then be asked to put a cable into another one (not easy atm) or ask me to resort to a WiFi setup.

And yes, it's local Sonos Playlists (the ones we have no proper way of backing up) that are lost.

Cheers.

Userlevel 3
Badge +1

So we are 24 hours or so, into the brave new Sonos world what are we thinking ? I feel a little disappointed if I am honest . I was expecting/hoping that Sonos would have given us a shiny new jewel of an app, something that looked good on the screen something to want to play and explore music with but mmmm! The colour of the new S2 app is awful It should be the gateway to exploring music it's not ! Once past the colour you get to step back into the 90s because that's what it feels like almost a retro app ,  it's all a bit to basic . The S1 app I can only think that the colour and writing on it is designed to make you feel embarrassed to use it in front of people, it looks like it was designed and built on a windows Vista computer found in a cupboard ! in all honesty Sonos this should have been a feast of new gifts to us but in reality it feels like you just slapped a coat of paint over it .

Userlevel 5
Badge +4

So we are 24 hours or so, into the brave new Sonos world what are we thinking ? I feel a little disappointed if I am honest . I was expecting/hoping that Sonos would have given us a shiny new jewel of an app, something that looked good on the screen something to want to play and explore music with but mmmm! The colour of the new S2 app is awful It should be the gateway to exploring music it's not ! Once past the colour you get to step back into the 90s because that's what it feels like almost a retro app ,  it's all a bit to basic . The S1 app I can only think that the colour and writing on it is designed to make you feel embarrassed to use it in front of people, it looks like it was designed and built on a windows Vista computer found in a cupboard ! in all honesty Sonos this should have been a feast of new gifts to us but in reality it feels like you just slapped a coat of paint over it .

Yes - well put. S2 is really disappointing and underwhelming.

Userlevel 2
Badge +1

Hi. I’m just wondering if I can update 2 of my S2 compatible speakers (Play 1’s) to S2 for use in a bedroom and keep my 2 Play 3’s on S1 to group with with my 2 gen 1 Play 5’s in a bigger room?

 Although it’s moot because I’m not going to do it, I don’t think I successfully communicated my point of concern, which was that the product removal tool only provides the option to remove incompatible products to be reserved for S1, with the remaining 4 compatible speakers going to S2. What I was considering was keeping  2 of the compatible speakers in S1 with the Gen 1 Play 5’s, and moving the other 2 to S2.   But there doesn’t seem to be a way to do that.

Or am I missing something?                                                         

Userlevel 1
Badge +1

It does indeed seem as if the main change has been an interface designed by the brand police of the marketing department.

 

And yes, it's local Sonos Playlists (the ones we have no proper way of backing up) that are lost.

 

For various reasons my mixed system will remain in unified S1 mode forever, but if I did want to split, the above issue would be another deterrent, given my extensive Sonos playlists curated over the years. It would have been simpler to be able to move compatible speakers to S2, without affecting what remains behind as S1, for sure.

PS: and do people get warned of this, or does it pop up after the event as a nasty surprise? And does this occur even if the entire system is compatible with S2 and is being moved there?

Hi. I’m just wondering if I can update 2 of my S2 compatible speakers (Play 1’s) to S2 for use in a bedroom and keep my 2 Play 3’s on S1 to group with with my 2 gen 1 Play 5’s in a bigger room?

 Although it’s moot because I’m not going to do it, I don’t think I successfully communicated my point of concern, which was that the product removal tool only provides the option to remove incompatible products to be reserved for S1, with the remaining 4 compatible speakers going to S2. What I was considering was keeping  2 of the compatible speakers in S1 with the Gen 1 Play 5’s, and moving the other 2 to S2.   But there doesn’t seem to be a way to do that.

Or am I missing something?                                                         

The removal tools just resets the legacy players to factory settings. There’s nothing to stop you doing a manual factory reset on some S2-compatible players in addition. Do this before updating them to S2.

You can then set them all up together as a separate S1 system.

Userlevel 7
Badge +15

 

And yes, it's local Sonos Playlists (the ones we have no proper way of backing up) that are lost.

 

… It would have been simpler to be able to move compatible speakers to S2, without affecting what remains behind as S1, for sure.

PS: and do people get warned of this, or does it pop up after the event as a nasty surprise? And does this occur even if the entire system is compatible with S2 and is being moved there?

I'm pretty sure that what what most were reasonable expecting.  Because it was all so secretive and Sonos didn't release the process until yesterday we didn't know how it was going to work.  In the many pages on the site there is mention of settings being lost - I'm not sure of how the warnings are worded when doing the process as I have not done it as I want to keep using my S1 speaker as I did beforehand.

It just seems bizarre to me that it needs a reset when it is already running the new S1 software and it couldn't have been split properly and kept ruining as it is now (new App/household, whatever..)

It just seems bizarre to me that it needs a reset when it is already running the new S1 software and it couldn't have been split properly and kept ruining as it is now (new App/household, whatever..)

The assumption is that users will want to move forward with S2, but they can if they want split off any S1-only units and set up a fresh system for those.

There’s nothing to stop a user doing it the other way round: manually factory reset a few S2-compatible units, make a new system of those, and update it to S2. 

Either way, a clean new system gets created, empty of playlists, service accounts, etc. It’s a question of which system is more important in terms of the retention of playlists etc.

Userlevel 7
Badge +15

But both are just as important.  Just because I can no longer group the speakers post-S1, it seems reasonable to assume I'd still want to listen to the same things I used to when in the room the speaker is in.

But both are just as important.  Just because I can no longer group the speakers post-S1, it seems reasonable to assume I'd still want to listen to the same things I used to when in the room the speaker is in.

I agree; one system needing a rebuilding of local playlists is a downer and it does not make sense to users to have to choose between systems for this information to be retained. And even if this is some strategy to discourage split systems, there should be clear warning of this tripwire before it explodes.

Other setting losses are probably not of great consequence - but many of my Sonos playlists have over 2000 tracks in them and I would not happy if I had to rebuild these. I would be even less happy if I discovered this after a wipe out.

Userlevel 1

Reading about the issues with playlists, I have to admit I am confused. All mine were retained.

Yesterday I updated my system ( Playbar, Sub (2nd Gen), Connect:AMP (2nd Gen) ) to S2 before my Arc and Gen 3 Sub arrive this week.

I didn’t uninstall the existing Sonos apps, but downloaded and installed the new S2 app on my Windows PC, Android Phones, MacBook and iPad.

In the S2 app, all the Preferences, Sonos Playlists and Sonos Favorites remain as before.

NOTHING has changed - it was a flawless upgrade.

 

 

Userlevel 7
Badge +15

Yes, it sounds like you have done a simple upgrade from S1 to S2?

The issue is that if you need to split your system because some of your devices are not compatible with S2, you first of all update everything to the new S1 software, then decide which ones are not going to be a part of S2 and they are then all removed and Factory reset - losing all of their settings, Playlists etc.  You are not left with quite the split system with them behaving as before but not able to be linked - you need to make a decision on which is more important and reset the other.

My Play 5 Gen 1 is in a room where Grouping is not that important anymore - but listening to all the music  and Sonos Playlists, Favourites etc, that I currently do still is.

Split S1 - S2.

Did anyone try to upgrade part of the speakers while keeping the ones to be retained in S1 unplugged from power?

Maybe in that case after upgrade powering them up again allows them to keep the settings and playlists….

Split S1 - S2.

Did anyone try to upgrade part of the speakers while keeping the ones to be retained in S1 unplugged from power?

Maybe in that case after upgrade powering them up again allows them to keep the settings and playlists….

This doesn’t work. You end up with an S1 controller that complains that the S2 units are “incompatible”, and an S2 controller that complains that the S1 units “need update”.

Userlevel 7
Badge +15

@ratty, you know more about this than many/all.  I do think most who were aware of the forthcoming split (but maybe not part of a beta where it may have been known) were expecting to be left with a set of speakers on S1 and a set on S2, both controlled by a separate App but behaving as they previously did - but no longer able to be grouped.

How could Sonos have achieved this?

 

How could Sonos have achieved this?

I expect the Sonos response to be that 95 percent of the user base does not use NAS anymore, and of the diminishing by the day percentage of those that do, a very small number will be interested in split systems. Of which an even smaller number will have large playlists. And are therefore not worth the trouble.

Userlevel 7
Badge +15

 

How could Sonos have achieved this?

I expect the Sonos response to be that 95 percent of the user base does not use NAS anymore, and of the diminishing by the day percentage of those that do, a very small number will be interested in split systems. Of which an even smaller number will have large playlists. And are therefore not worth the trouble.


What ‘trouble’ though?  It’s extra work for the users to attempt to get their system back where it was.  I’m trying to understand if it’s ‘technical’ or just a decision they’ve made.  Sonos playlists can have content from sources from more than just a NAS - mine include tracks from other sources, including Spotify, too.

@ratty, you know more about this than many/all.  I do think most who were aware of the forthcoming split (but maybe not part of a beta where it may have been known) were expecting to be left with a set of speakers on S1 and a set on S2, both controlled by a separate App but behaving as they previously did - but no longer able to be grouped.

How could Sonos have achieved this?

You know what they say: a little knowledge is a dangerous thing.

One can conceive of a way a system (household) could be divided in two whilst leaving such things as playlists intact. It’s just software after all.

Putting it into practice in a supportable fashion is of course a different matter, with policy and resource implications.

FWIW I’d also hoped Sonos would have provided a household splitting tool.

 Sonos playlists can have content from sources from more than just a NAS - mine include tracks from other sources, including Spotify, too.

I gave up on mixed source playlists when the lack of volume normalisation across sources came in the way. But yes, in that case, I suppose these too would need rebuilding. 

Trouble in this context just means costs, I suppose, to answer that question you raised. Sonos has to have felt that these were not justified by how many users need this facility, also with S2 being the chosen path forward for the company. Or, perhaps this requirement simply did not come to their mind, seeing the present focus of the company.

 

Userlevel 2
Badge +1

Hi. I’m happy and content staying with S1 so that I can use my 2 legacy 5’s with my 2 Play 3’s  and 2 play 1’s. When the 5’s become incompatible I’m ready to buy 2 Gen 3 Fives and move the whole thing up to S2. My only concern is that at that time everybody else with legacy 5’s will be doing the same thing, which may cause a run on new Fives and a waiting period to get them. For that reason it has crossed my mind to buy the new Fives now and beat the rush.

Any of you smart guys think that’s a legitimate concern or am I crazy?

The latter. Your 5 units will suffer hardware failure that will stop them from working. All the units out there will suffer this at different times.

And there will be some like me that will buy other alternatives to Sonos when legacy S1 kit dies, so there is that factor as well.

I agree with @Kumar that a run on Fives at some future point is not worth worrying about.

The only thing i would add is that, IMO, the gen 2 Play:5 was/is a vast improvement on the gen 1 (and by all accounts the Five is similar acoustically to the gen 2).  If the budget is there, i would consider getting them now and enjoying them.  If you order from Sonos and don’t share my view on the difference in audio quality, you could return them.