Question

Rubbish new update, what do others think ?

  • 10 September 2016
  • 82 replies
  • 4436 views


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.

82 replies

Userlevel 6
Badge +7
Hopefully we are not just voices blowing in the wind!
Userlevel 7
Badge +22
I agree but there are aweful lot of threads. Shouldn't Sonos combine these into one thread.
Sonos - this is a really awful and unpopular update. Please un-screw this for your many loyal subscribers.
p.s. That last post was for @seob, and the other thread I referred to was actually this one! Thanks @soveryfaraway for the suggestion. I had several pages open and forgot to refresh. Doh!
Someone on another thread wondered if the update had changed the default wireless channel. It might be worth checking if the Sonosnet wifi is separate from your home wifi. Using channels 1 and 11 is the best setup. Channels 1 and 6 or 6 and 11 is also OK but not quite as separate.
Userlevel 4
Badge +1
A note to everyone here that is serious about getting the UI back to where it works for you (as it probably did not so long ago) - post tasteful but sincere reviews on 6.4 to everywhere you've made purchases of Sonos gear. Here, on the community site (controlled by Sonos) we are only howling dogs. On the retailers websites, we are bombs. Without this market influence, we are just a lot of noise.

Cheers!
Userlevel 4
Badge +1
I'd be curious if the update defaulted the network channel on some installs. It happens sometimes. My Sonos can't use the default (6 I think), it conflicts with the WiFi. Had to set Sonos to 11, but I haven't had such a problem with the update so I don't think it was an issue here. I have 3 access points and two extenders on one and no network issues at all. Only stinky UI so far.
Userlevel 2
Badge +2
@seob: did you try a full network reboot?

@The LHC: if all IP addresses have been preassigned, what are the potential network issues remaining that could cause this?


Yes I did a full network reboot. Still having a few dropouts. It may be network issues due to the update, but I think there was something different about this one. Never had these dropouts before after an update, and I've been using Sonos for several years as well. So even if it is "just network issue" they were caused by the Sonos update.
Userlevel 7
Badge +22
Queue Destruction! Don't update your Sonos! Select a track and get ready for the entire artist catalog of 200 songs to kill your meticulously built queue. Hopefully the skilled employees of Sonos are listening- pun intended!!! Help!!!!

What do you want help on? Writing puns?
Queue Destruction! Don't update your Sonos! Select a track and get ready for the entire artist catalog of 200 songs to kill your meticulously built queue. Hopefully the skilled employees of Sonos are listening- pun intended!!! Help!!!!
Userlevel 5
Badge +10
Chucked a few albums onto the Sonos today. I understand why "play now" might now default to "insert into queue" when you're playing music (use case: "play this song then go back to what you were playing"), but the desktop app's implementation for playing when the music is stopped is weird - it inserts into queue, not at the start (somewhat logical) or end (previous behaviour), plays what you asked it to, then continues to play something you were listening to minutes/hours/days ago. And given the insert position of likely track 2 of a playlist/album... I can't replicate this on the iPad, because the "play all" button only seems to do a queue-replace-and-play-now. So for a system where a key selling point is "it just works on all your devices", this kind of inconsistency over something as simple as "playing music" does not bode well...
Userlevel 6
Badge +7
Did you even test this pathetic backward step before destroying the user experience for your customers?

.


User695950 you can be assured that this update was tested and previewed in Beta testing. I participated in it myself and when I experienced it I communicated my strong feelings against this update through the official Beta channels. I had communicated that for the 1st time a Sonos change had seemed completely unintuitive and has actually materially deteriorated my user experience.

There has been a thread among community users that discuss it at length. What you would find there are many for and many against. But my perspective is that the ones who like it were not necessarily grossly unhappy with the previous queuing concept. However, those against it are strongly against and also for the 1st time I am actually seeing a few making dire comments about how it ultimately altered their feeling for the product and that they will have trouble recommending. I am certainly not in that space. I still think the products are great and I can work around it. But I remain unhappy with the change. I think for myself and many others the previous system worked perfectly. There are a few changes that allow quicker actions eg play all and shuffle- I like those.

See the thread discussing the Beta below.

https://en.community.sonos.com/announcements-228985/sonos-version-64-now-public-beta-6738453
Userlevel 4
Badge
Sonos what the actual hell have you done? You've totally ruined the control app with this nonsense. Did you even test this pathetic backward step before destroying the user experience for your customers?

Every time you click on a song to play it, it deletes your entire queue (that I did want and spent ages building full of my favourite tracks) and replacing it with the entire album or playlist (which I don't want!). There was the Play All function for occasions when you wanted to add a whole album to your queue. Wanting to play one song does not equate to wanting to play the whole album and delete every bloody song from your queue without warning.

This is worse than annoying. It is unfit for purpose and in this one move, you have annihilated all the enjoyment from your products. I've been using Sonos for several years, I have loved it. I've spent over a grand on your kit, and encouraged many friends to join the Sonos community because your products worked, were intuitive and flexible. I currently regret that. No one in their right mind would want to buy a product that behaves like this current shower of sh@t.

THERE WAS NOTHING WRONG WITH HOW IT WAS. PLEASE ALLOW ME TO PUT IT BACK IMMEDIATELY.

You've taken the best feature of Sonos, which worked perfectly, thing which made me invest a lot of money in several Sonos units for around my home and utterly ruined it. It is currently unusable.

If you want to avoid this experience destroying farce people, do not whatever you do, install the upgrade to version 6.4. Stick with 6.3.2 where everything worked as it should.

PLEASE CAN SOMEONE FROM SONOS REPLY TO THIS URGENTLY AND HELP ME PUT THIS BACK TO HOW IT USED TO BE WHEN IT WORKED AND RESTORE THE FUNCTIONALITY THAT I PAID FOR...
Userlevel 4
Badge
Not only is the new update for "play now" functionality a step back, but it's inconsistent. Losing the queue history and overwriting every time you start playing is a change we can probably deal with, but the actual behaviour when you play an album is:
1. On iOS, overwrite entire queue with new album
2. On Windows desktop, insert album into queue (typically at position 2) so your queue looks like "last album played track one, new album added, last album played tracks 2-9"
3. On old Sonos CR200 controller, add new album to end of queue (as before)

Oh, and there's the scary error messages... did anyone actually design or test this?

The queue "just worked" and was great. If you're going to de-emphasise or outright kill it, at least make up your mind, Sonos.
Userlevel 5
Badge +10
Not only is the new update for "play now" functionality a step back, but it's inconsistent. Losing the queue history and overwriting every time you start playing is a change we can probably deal with, but the actual behaviour when you play an album is:
1. On iOS, overwrite entire queue with new album
2. On Windows desktop, insert album into queue (typically at position 2) so your queue looks like "last album played track one, new album added, last album played tracks 2-9"
3. On old Sonos CR200 controller, add new album to end of queue (as before)

Oh, and there's the scary error messages... did anyone actually design or test this?

The queue "just worked" and was great. If you're going to de-emphasise or outright kill it, at least make up your mind, Sonos.
@seob: did you try a full network reboot?

@The LHC: if all IP addresses have been preassigned, what are the potential network issues remaining that could cause this?
There are also some bugs as well. Getting a lot of queue 1002 errors when trying to use the new functionality.

That's just network issues that are often exposed by the full reboots the update process requires. You need to do a full network restart.


You may be right, but every sonos device and all other devices on my network have preassigned ip addresses.


So? It's still a network issue and not a bug.


And you know this how? Several others reporting the same issue after 6.4. Only thing that has changed on my system. Been rock solid for a few years. I'm betting there's bugs in 6.4 causing this.


I know this because we get the same bug reports after every update release and it's ALWAYS network issues uncovered by the reboots but hey what do I know, I've only been here for 8 years or more...
Userlevel 4
Badge +1
The silly thing about it all is that in OOP the app would not have grown much in size to provide for both pathways. If they had a proper perspective, they could have had it all for both sorts of potential clients. Apparently, they were lacking somewhere. My reviews forward are negative, since Sonos took a useful product I had purchased at a substantial cost in good faith and diminished the value of the product to me in a substantial way.
Userlevel 4
Badge +1
Thanks to all, will update reviews on all my purchase sites. 🙂
Userlevel 2
Badge +2
There are also some bugs as well. Getting a lot of queue 1002 errors when trying to use the new functionality.

That's just network issues that are often exposed by the full reboots the update process requires. You need to do a full network restart.


You may be right, but every sonos device and all other devices on my network have preassigned ip addresses.


So? It's still a network issue and not a bug.


And you know this how? Several others reporting the same issue after 6.4. Only thing that has changed on my system. Been rock solid for a few years. I'm betting there's bugs in 6.4 causing this.
Userlevel 4
Badge +1
All - terribly sorry, but if this is Sonos today, I am out. 3 Play 1's, 2 Connects and a Boost - modest, but over 5000 tunes in the library. I can't work with it as it is. It just blows my mind. I can't build a playlist anymore without excruciating efforts. Sonos - you have stabbed your faithful in the back with your "update". Was all this to get new business? Sounds like marketing got the upper hand of R&D.
There are also some bugs as well. Getting a lot of queue 1002 errors when trying to use the new functionality.

That's just network issues that are often exposed by the full reboots the update process requires. You need to do a full network restart.


You may be right, but every sonos device and all other devices on my network have preassigned ip addresses.


So? It's still a network issue and not a bug.
Userlevel 4
Badge +1
I think they should have preserved the existing UI and added a mode switch to enter a parallel UI that performs instant "Play Now" gratification. Wouldn't have been that difficult and wouldn't have needed to affect any playlist.
Userlevel 2
Badge +2
There are also some bugs as well. Getting a lot of queue 1002 errors when trying to use the new functionality.

That's just network issues that are often exposed by the full reboots the update process requires. You need to do a full network restart.


You may be right, but every sonos device and all other devices on my network have preassigned ip addresses.
There are also some bugs as well. Getting a lot of queue 1002 errors when trying to use the new functionality.

That's just network issues that are often exposed by the full reboots the update process requires. You need to do a full network restart.