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

    Avid Contributor I
    September 16, 2016
    Ryan S:

    Do you even comprehend why long time users are upset with a FUNDAMENTAL change in the operation of Sonos? I have been a Sonos user since 2007. Some updates have been frustrating, but this one is downright infuriating. I hove not been around the forums since you castrated the old Sonos forum, but for years on the old forum we would tout the superiority of the Sonos queue over other systems. Now, after many years of loyalty and promotion of Sonos you go ahead and make a change that goes against everything we have been promoting for you.

    The worst thing is that I did not have a choice in this update. I just brought a Sonos unit out of storage and was forced to update the app before I could update the player.

    Please add the ability to disable the touch to play feature.
    Avid Contributor I
    September 16, 2016
    I just discovered that my non-updated iPad app still works with the system. I only was forced to update on my iPhone when I added the old component.

    I wonder how long before I am forced to update the app? No way I am updating otherwise...
    September 16, 2016
    Ryan S:
    The worst thing is that I did not have a choice in this update. I just brought a Sonos unit out of storage and was forced to update the app before I could update the player.


    A good example of why the "if you don't like it just don't upgrade" argument is not practical.
    Local music library with carefully constructed playlists - no shuffling!, Integration with Homeseer Automation, No touch screen devices, No streaming services, No Apple products ever
    soveryfaraway
    Enthusiast II
    September 16, 2016
    If you're on Twitter... it's #SONOS #6.4, tweet your disdain. They *are* listening; give them an ear full.
    Quocunque Jeceris Stabit
    chicks
    September 16, 2016
    I wonder if the change was necessary in order to accommodate the upcoming Spotify Connect and third party apps? Maybe the streaming providers demanded the change so that their apps wouldn't need to be changed. There has to be a reason we aren't aware of.
    jgatie
    September 16, 2016
    I wonder if the change was necessary in order to accommodate the upcoming Spotify Connect and third party apps? Maybe the streaming providers demanded the change so that their apps wouldn't need to be changed. There has to be a reason we aren't aware of.

    Maybe not necessary, but I can see them pushing for a similar look and feel. It still does nothing to separate the single user with headphones vs. multi-room communal sharing experience of Sonos.
    soveryfaraway
    Enthusiast II
    September 16, 2016
    If that is the case, IMHO, it would have been better to create separate apps for that functionality rather than blowing the rest of us to kingdom come.
    Quocunque Jeceris Stabit
    jgatie
    September 16, 2016
    Well it is no secret that the queue has been a thorn in the side of a very vocal, if not very large contingent of Sonos users. It started with diehard iTunes users, who were used to the "select a song and play from here" function of the first iPod, and continuing with the apps that mimicked the iPod interface because it was ubiquitous, as much as it was limited. I personally felt liberated when I first used a Sonos queue. Still having an iPod for use in the car, I would curse at the dashboard because I couldn't insert a song I wanted to hear into a playlist without deleting the current playlist and playing the rest of the album that song was on. I've said it before, going to the Sonos queue after using an iPod was like driving with my feet on the steering wheel for years and then learning you could steer with your hands. This update defaults to my feet on the steering wheel again, and I hate it.
    soveryfaraway
    Enthusiast II
    September 16, 2016
    It is rather like they traded a flexible and fairly powerful database system for an iPod. It's clear that someone (or several, as it might be) didn't appreciate what they had and trashed it for the simpletons who also could not appreciate it.
    Quocunque Jeceris Stabit
    nicka99
    Local Superstar
    September 16, 2016
    be aware that sonos havent trashed anything (aside from the strange insert at track 2). The functions that existed before still exist.

    However, it is the way this changed is forced on all users I take issue with.

    Its clear there is one camp who are happy with the new changes as enables them to more easily play albums and playlists in their entirety and not even be aware of the queue. The other prefer to work with a more 'sticky' queue that can be easily manipulated and added to as in 6.3 and everything before it.
    Moving the 'album and playlist' play functions centre stage comes at the expense of the previous 'jukebox' style queueing options being buried deeper.

    This is really a case for a configuration option to have the new way or the old and, since this entirely controller based, I can see no reason why it cant be done.