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
  • 16933 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

    Prodigy II
    December 11, 2016
    Then you get two polarised sets of users IMO.
    A big complaint is about when people throw parties. Some guests are likely to have Sonos. Which version will they try to use - back to babysitting, as some have called it, your guests.

    The current system needs more work on it to iron out some of the wrinkles. Why not seek to improve the current experience rather than being firmly stuck in the, controversial in its own right, past and be positive about direction.

    Wouldn't, say, an undo button (for just one movement forward, be of more benefit than toggles.


    I honestly don't understand this talk about "polarized groups". That casts an unnecessary negative cloud on a request to customize. I have no issue using the queue in my preferred way and you doing the same. For me to understand your point you need to present the argument for the downside in allowing different use cases. I personally see no concern. SonoPad presented 4 queue management options - I picked one and scarcely think about what the persons may be doing. This would be to create a problem where none really exists. But again please explain what is the real issue with the customization you are seeing.


    Please use "different" instead of polarised. That is my point for the downside. You will have two users not understanding what the other is saying because one is old way and the other isn't. Take the party as an oft used example, some of the users will be the old way and some new. Is that confusing? Or will the dreaded babysitting be required for those new users. Toggles require future changes to be compliant with those toggles but at some point they will not be viable, and I can't see Sonos, or any other company, willing to spend a lot of money maintaining toggles for an exceedingly small number of users.

    New customers will know no different. Those users arriving in a discussion which is using old terms serves only to confuse, and maybe that would be a polarising force and maybe dilute the help process on this forum.

    Sonopad is a paid for third party app that will bend, sway and do pirouettes to keep the money coming in. That the app provides the required control the case for toggles in Sonos is defeated by the existence of an excellent app that will do what you want. And with absolutely no confusion between users - possibly between Sonopad users...
    Chris
    Lead Maestro
    December 11, 2016
    Sonospad provides options but no universal search and frankly I'm not a fan of the interface in general. Talk about being different for people coming to your house. Instead of their normal controller you ask them to use another controller so they don't override your music. A controller they would have to pay for to put on their phone. Yea that doesn't make sense ... vs a toggle to protect the queue. Sure new users may not know the difference in the way it used to work ... they also may not show the loyalty previous users did.
    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)
    Prodigy II
    December 11, 2016
    @Alan. Where things are inserted into the queue needs more work. To my mind, this a move forward change that needs supporting.

    Exactly. I think I understand what Sonos are trying to do, and I'm generally in favour. Incorporating a queue adds complications over an old-fashioned CD/iTunes-style UI, but Sonos were doing pretty well up to version 6.3 with the context-aware relationship between the play button and the queue. It should be super-easy to just find stuff and play it with the minimum number of button presses and have the queue work in an intuitive manner. But Sonos aren't there yet, and don't seem to be prioritising fixing bugs / UI / UX issues with the core product, which is a multi-room all-your-sources albums/playlists/tracks/whatever music player that "just works".
    Renowned Enthusiast II
    December 11, 2016
    Chris I agree the the loss of universal search is not ideal and the design of the interface is not as slick as Sonos but for me I feel that these limitations are tolerable compare to to how strongly I dislike the new play functionality. The likelihood of unlikely outcomes is significantly reduced. To each his own.
    (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
    December 11, 2016
    The new play methodology is a mess
    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)
    Renowned Enthusiast II
    December 12, 2016
    Has anyone stopped to consider how Amazon Alexa integration will impact the new play functionality. I assume asking Alexa for a song will erase the queue. If queue is edited she will prompt you with a warning? I can only assume.
    (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
    December 12, 2016
    Yes
    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)
    Chris
    Lead Maestro
    December 12, 2016
    I believe I mentioned months ago
    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)
    Lyricist I
    December 14, 2016
    I "upgraded" from version 4 to the new version 7.

    What an error!

    The new versions user interface is close to unuseable.

    There should be an option to go back to the old and perfectly usable version 4.
    BCM
    December 14, 2016
    Welcome to three years ago. Take a few minutes and work with it... you'll get used to it. It's quite enjoyable.