Skip to main content
Contributor I
September 12, 2016

SONOS are you reading this? Please put the controller queue function back how it was!

  • September 12, 2016
  • 351 replies
  • 16930 views
I've downloaded version 6.4 of the app. What a mistake. To anyone who is about to do it, DON'T DO IT IF YOU LIKE YOUR QUEUE.

Sonos please put it back how it was. This new app is so awful I am considering selling my entire Sonos rig (6 pieces!) and walking away from you, after what was until this week, many happy years.

Touching on a track because I want to play it, or add it to the queue (the queue that I DID WANT), does not mean I want to delete the whole queue and replace it with the entire album (which I DON'T WANT) which the newly added track comes from.

If I wanted to delete my queue, I would delete it. If I wanted to add the whole album, I would add it using the play all function.

You've just taken something intuitive and user friendly which worked so well and turned it into a worse than hateful mess.

PLEASE UNDO THIS AWFUL, HORRIBLE CHANGE.
    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.

    351 replies

    Ryan S
    Retired Sonos Staff
    September 12, 2016
    Thanks for all the feedback everyone. We've been reading all your comments and are passing them on to the team, so thanks again for sharing.

    We know there are some huge changes here and will continue to be listening for the future. There aren't any plans I can give you a sneak peak into but we are always looking to improve Sonos for everyone.
    Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
    Chris
    Lead Maestro
    September 12, 2016
    Answer isn't roll back it is Sonos having next update cater to improvements to protect queue for queue users. Current release focused on individual user. Next update need some love for multi user multiroom (you know that thing that has made Sonos so successful in the past).
    Respect the Queue (2)Move (3)Beam (1) Era100 (2)ARC (1)SonosOne (1)Playbar (4)Play5 (4)Play1 (3)Play3 (1)Port (2)Connect (1) Roam (2) Ace (1)Connect:Amp (4)Sonos Amp (1)Sub + (9) Echo + Smartthings; (2)Play)
    BarryM
    September 13, 2016
    Thanks for all the feedback everyone. We've been reading all your comments and are passing them on to the team, so thanks again for sharing.

    We know there are some huge changes here and will continue to be listening for the future.

    One glaring "huge" change is that you appear to have rushed a beta release into production knowing that it broke things for existing customers.

    ie. abrupt termination of currently playing tracks, due non-intuitive tap exposures
    and unwanted queue destruction due to the UI making incorrect guesses about what I want
    and the replaying of the old queue, when I just asked to play something new

    It is seems to be generously assumed here that you will complete your new options, which I am sure have been welcomed by many, by restoring normalcy for existing queue users. ... But these shortcomings, and incomplete behaviour modifications, were well discussed in the public beta, and probably prior to that also.

    So why piss everybody off by rushing the job? ... that's a bit of a "huge change" isn't it? ... and an unwelcome one too IMO.
    Renowned Enthusiast II
    September 13, 2016
    Sometimes you just need to leave well enough alone!!! The thread discussing the changes while in Beta I thought would have made that pretty clear.
    (1) Play 1, (1) Play 3, (2) Play 5s Gen 1, (1) Play 5 Gen 2, (1) Connect Amp powering a pair of Wharfedale Diamond 10.1, (2) Echo Dots.
    September 13, 2016
    Sometimes you just need to leave well enough alone!!! The thread discussing the changes while in Beta I thought would have made that pretty clear.

    I think you are misunderstanding the purpose of the beta and of this release. It is important to the Sonos vision for users to migrate to the newly announced voice control strategy as soon as it is available. A good way to motivate people to make the switch is to make the current controller less familiar and intuitive so there won't be any reluctance to move on to voice control. The only purpose of the beta was to gauge that the feedback was sufficiently negative to ensure they had accomplished their goal.

    It is also important for Sonos to drive as many new sales as possible to the Amazon Echo before Google Home is released even if it means cannibalizing Play1 sales by making the Sonos app too complicated for new users to operate. In the long run the lost customers will be recovered when they are ready to step up to a multi-room Sonos system that can be voice controlled by their existing Echo but if they are lost to Google Home they wouldn't need Sonos to build a voice controlled multi-room system and would be gone forever.

    So you see, everything is proceeding exactly according to plan.
    Local music library with carefully constructed playlists - no shuffling!, Integration with Homeseer Automation, No touch screen devices, No streaming services, No Apple products ever
    chicks
    September 13, 2016
    Yeah, Right! :rolleyes:
    Enthusiast II
    September 13, 2016
    Voice control is the new '3D television'!
    Prodigy II
    September 13, 2016
    The key issue I have with the new queue changes is that the "play now" button seems both inconsistent across apps when you want it to be, and then does the wrong thing in an attempt to be consistent. Firstly, the default behaviour of "play now" seems to fluctuate between "replace queue and play" and "insert into queue and play". Given the differences between iOS and desktop apps you now need to learn what the button does. Far worse though is the annoying consistency of the "play now and insert" feature eg. for playing an album:
    1. When you're playing music then fine, play now plays the new album, inserts those songs into queue, then continues with whatever was in the queue.
    2. When the music is stopped (eg. queue holds yesterday's listening session), hitting "play now" inserts the new album into the queue (after current stopped song at position 2), then continues with whatever's left. This is quite literally the "play this album followed by tracks 2-10 of what you were listening to yesterday" button.

    Am I missing something? Is this really how anyone would want something as basic as the "play" button to work?

    Losing the queue is not a big deal (you can always save it), and I can work around this by always replacing the queue until this is hopefully fixed in a few months, but really Sonos - what were you thinking?
    Renowned Enthusiast II
    September 13, 2016
    Sometimes you just need to leave well enough alone!!! The thread discussing the changes while in Beta I thought would have made that pretty clear.

    I think you are misunderstanding the purpose of the beta and of this release. It is important to the Sonos vision for users to migrate to the newly announced voice control strategy as soon as it is available. A good way to motivate people to make the switch is to make the current controller less familiar and intuitive so there won't be any reluctance to move on to voice control. The only purpose of the beta was to gauge that the feedback was sufficiently negative to ensure they had accomplished their goal.

    It is also important for Sonos to drive as many new sales as possible to the Amazon Echo before Google Home is released even if it means cannibalizing Play1 sales by making the Sonos app too complicated for new users to operate. In the long run the lost customers will be recovered when they are ready to step up to a multi-room Sonos system that can be voice controlled by their existing Echo but if they are lost to Google Home they wouldn't need Sonos to build a voice controlled multi-room system and would be gone forever.

    So you see, everything is proceeding exactly according to plan.


    Reading that was actually equal parts amusing and thought provoking. Thought provoking because I did stop to consider that this change might in fact be part of a larger strategy with voice control featuring in there. Amusing because seeing it written in this way is quite funny.

    Ryan can you confirm on behalf of Sonos??? Are you guys trying to annoy the hell of us for "strategic reasons"???
    (1) Play 1, (1) Play 3, (2) Play 5s Gen 1, (1) Play 5 Gen 2, (1) Connect Amp powering a pair of Wharfedale Diamond 10.1, (2) Echo Dots.
    Chris
    Lead Maestro
    September 13, 2016
    There is a strategy I believe and that's marketing. Theynfor some reason felt making Sonos more familiar in its operation to the. Stice apps would rive sales and make the Sonos app more familiar to new users. And they probably have some new developers who are used to that method and don't particularly understand what made Sonos great in the first place.

    Downside - that method is not particularly well suited in a multi room multi user environment
    Respect the Queue (2)Move (3)Beam (1) Era100 (2)ARC (1)SonosOne (1)Playbar (4)Play5 (4)Play1 (3)Play3 (1)Port (2)Connect (1) Roam (2) Ace (1)Connect:Amp (4)Sonos Amp (1)Sub + (9) Echo + Smartthings; (2)Play)