Sonos Version 6.4 Now in Public Beta



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.

290 replies

Userlevel 7
Badge +22
I'm done
Ken - did you follow the steps I posted above and see now issue? So you have no issue if you search for a song and if you click on it that it does Play Now when it doesn't do that if you pick a song other places.

Chris,

I'm not seeing this issue... Forget the folders issue just for one moment... Think of everything in simple terms as a playlist.

If you do a Sonos search and select a track from your songs tab it will treat it as a playlist (with just one song) and it will replace the UNEDITED queue with that song and begin playing it. It is meant to work that way.

If you do a Sonos search and select an album cover (play button on cover) it will replace your queue with the whole album and start playing its first track... The other tracks will play in order afterwards if you don't use the shuffle feature. It is meant to work that way.

If you do a Sonos search and select any album or playlist cover (not the play button on the cover) it will reveal the individual tracks on that album or playlist .. If you choose one track,it will replace your UNEDITED queue with the entire album or playlist and start playing the track you selected... The other tracks will play in order afterwards, if you don't use the shuffle feature. It is meant to work that way.

If you go to any playlist (even Sonos Favorites) or elsewhere the same thing happens. There is no difference.

The only occasion where it doesn't work in this way is the previously discussed folder issue... Which is under investigation by Sonos and probably for later release.

The only time the queue is not instantly replaced, is if the queue has been altered or edited in some way by you, the user.

Does that help make sense? Otherwise I'm not exactly sure what the problem is that you are seeing?

It is how I expect the Sonos search results etc to work, but I do appreciate there is a problem with folders and tracks within them not behaving like playlists, but that should be sorted in the near future.
Userlevel 7
Badge +22
So it should default to play now and if clicked stop your music. I think I'm a pretty expert user and playing music yesterday at least 3-4 times I accidentally did the horrible thing of clicking on a song and this what in as listening to stopped.

I give up.
But what else should the default action be? You're dealing with a single track in a list of search results, disembodied from the album of which it's a part. It would be illogical to 'Play from here' in that context. That's appropriate for selecting a track directly from the body of an album or playlist, which -- because it replaces the queue -- triggers the 'edited' popup as appropriate.
Userlevel 7
Badge +22
Ken, I'll explain it one last time and give up.

If you have an edited queue.

If you browse for a song in library or service or choose a song in a playlist... and you click on it you will get pop up that you have an edited queue. To play now you hit ... and chose play now.

If you search for a song with the search function and you click on the song it performs play now immediately and stops current song from playing.

As simple as that - complete opposite way of working by finding song in 2 different methods. The play now being default when searching song is incorrect.
Just one point: the queue is always in use. 'Play from here' front-ends the manipulation of the queue with a somewhat different UI, that's all.
Userlevel 7
Badge +22
Ken - did you follow the steps I posted above and see no issue? So you have no issue if you search for a song and if you click on it that it does Play Now when it doesn't do that if you pick a song other places.

2) same issue if search by Song - clicking on song does Play Now instead of Play All (interrupting music if using queue)


Can you elaborate the issue with this.

If I search a song and click it, it plays immediately, inserting itself into the queues current position. I believe this is how it should behave and makes perfect sense to me.

What do you think it should do?


gtrance,

Yes, I'm with you on this, I can't see an issue either, but I'm not sure if I am misunderstanding the point that Chris is raising here. I think it works how I would expect it to work too.

Simply everything selected by a user is treated as a 'playlist', even if that is just one song, or many songs ...and the chosen playlist will always replace an UNEDITED queue without any warning.

The user can load an entire playlist to the queue, even by selecting one track 'within' a playlist... It just starts playing from the selected track.

The only time the 'replace-warning-box' appears to the end-user, is if the existing queue has been EDITED by the user.
Userlevel 7
Badge +22
I agree ratty - Play now selected from context menu shouldn't give a pop-up.

It is the default action being play now when clicking a song that is the issue. The default action clicking a song when queue is in use should not be Play Now. In all other circumstances in controller (except folders and song search) is that clicking a song is Play From Here (which gives you a pop up are you sure as it clears the queue). The default action is incorrect in these circumstances. Folders issue has been acknowledged. Song search newly found.
The default click/tap action is one thing (which may or may not need correcting in some contexts), but Play Now is non-destructive so, no, I certainly wouldn't expect an 'Are you sure?' every time. Since each Play Now would in itself constitute a queue modification such popups could easily infuriate a user.
Userlevel 7
Badge +22
Ratty - if you search for a song and accidentally click on it would you expect it to stop the current song playing and play it now? Has never been that way in the past. It is way to easy to click on a song on a mobile device.

I understand it will behave this way when not using queue. But when using queue the default in other views has been that if you click on song with edited queue you would get the pop up dialog not Play Now.
Userlevel 7
Badge +22
Playlists work properly with Sonos new method. If I click on a song in playlists (with edited queue) I get the pop up dialog that is expected saying queue has been edited.

It is just folders and Song Search that appear to behave incorrectly. Folders I can live with as I'm only one uses. Song search - that is a big issue.
it will Play Now (expected action would be that you would get Queue has been edited dialog)
No, because Play Now is non-destructive on the queue.
Userlevel 7
Badge +22
It is not just issue in folders - when you search a song it behaves just like with folders and it defaults to Play Now. The song search behaves incorrectly just as Folders does as I have stated above. Does not work properly in Folders or Song search (I haven't tried from saved playlist).

- Edit Queue
- Search for Song
- when song results show accidentally tap on the song
- it will Play Now (expected action would be that you would get Queue has been edited dialog)
Chris/MikeV

MikeV, you are correct...

I think these things are doing what the Sonos programmers intended. The only issue I can see, is the previously-reported 'folders' issue, which Sonos staff have recently acknowledged, but said they will fix in a later version.

Here is how I see it...

Starting with an empty queue.. If you click a normal playlist-cover (play button) or album-cover (play button) (not a folder, obviously) it will load the playlist or album into queue and start playing ... Even if there is only one song in the playlist.

If a queue exists already and it is NOT edited, the playlist or album chosen, will replace the existing queue without any warning.

If an EDITED queue exists however, the playlist or album chosen, will not replace the queue immediately, but the warning box appears giving the user a chance to replace their edited queue, or cancel.

In the Sonos Search results everything returned in the tabs (Artists, Albums etc.) is treated like a playlist when you click on it... Including things under the 'songs' tab.

If the queue has been EDITED - you will get the usual warning box... If it has NOT been altered, then anything chosen will simply replace the queue.

One other thing to mention... If you decide to go into any playlist (anywhere) and view the separate individual tracks and tap on a track, it will still load the entire playlist to the queue, but begin playing the queue with the track you have chosen. Again if the original queue was unedited it will simply replace what was there. If not you get the replace-warning box.

So as I see it, apart from the issues surrounding folders... everything else seems to be working as intended, or at least how I expect it to work.

Note: A user can alter the default 'tap' actions mentioned above, either by selecting the (...) ellipsis, or long-pressing an album cover (not its play button), or long-pressing on an individual-track and choosing the actions of one of the many context menu options instead ... Such as adding the selected item to the end of queue etc.

I believe that some users here have mentioned they would like to see the default 'tap' selections on a track/playlist/album etc. as capable of being changed or customised to become one of the options that's on the context menu instead... Again that's probably something easier said than done and maybe something for the future rather than this v6.4 software release.

The only variation to the default action I have found so far, is the one Chris raised earlier and that is the 'acknowledged' folder issue, which has been reported to Sonos earlier.

As far as I can see the Sonos search results seem to be working okay for me so far. Unless I am misunderstanding the issue that is being raised here by Chris.
Userlevel 7
Badge +22
I'm not choosing the option - its not option its default when click on song with queue in use.

I'm not saying there needs to be a notification but it shouldn't be the default happening. If I chose Play Now in menu no it shouldn't warn.

Clicking on stops music and plays Now which has never been the function when using queue.
Userlevel 7
Badge +21
Normally if you are using queue and click on song you get pop up that queue is in use. Here it stops music playing and plays immediately. It should never stop the music when using queue unless specifically told to.
Only if it's clearing the queue, and the queue has been modified from the playlist/album that had been loaded into it originally, should it be notifying you.

If it's just adding to the queue, even if playing immediately, then there should be no notification. The notification isn't that what you're playing is being changed... it's giving you the opportunity to back out of an action that is irreversible (clearing an unsaved queue that you won't get back if not saved).

If you tell it to play an individual song immediately, the fact that you've chosen that option should be confirmation enough to say that you want what is currently playing to be switched to what you have selected.
Userlevel 7
Badge +22
Normally if you are using queue and click on song you get pop up that queue is in use. Here it stops music playing and plays immediately. It should never stop the music when using queue unless specifically told to.
Userlevel 3
Badge +4

2) same issue if search by Song - clicking on song does Play Now instead of Play All (interrupting music if using queue)


Can you elaborate the issue with this.

If I search a song and click it, it plays immediately, inserting itself into the queues current position. I believe this is how it should behave and makes perfect sense to me.

What do you think it should do?
Userlevel 7
Badge +22
I wouldn't be so sure that voice control etc. may be in the background just not turned on or seen by beta testers. The way they seem to be hastily making changes in this beta through makes me think that they are required to have it ready for release on 8/30 for the announcement (unfortunately). I wouldn't be surprised they release a version with known issues to meet the deadline.
Play Now may need to push out to next release when they have more time to do it correctly (unless that is just me hoping they either pull it or make these corrections).
I would hope that they fix these issues to get it right. The changes are in-your-face central to the user experience, and they need to be intuitive and reliable with regard to the users' intention. ... The current situation is anything but that IMO.

I wouldn't suppose that there was any particular rush to get these changes out there. It is not as if they were addressing any of the hot issues du jour, such as voice control, or disappointing cut-down facilities when using streamed services, ... or no android trueplay, or poor playbar connectivity.

I would think think that the headlines that will be hoping for would be along the lines "Sonos now easier to use", and they wouldn't want that to be spoiled by the kind of dissent which occurred when they upset users' satisfaction, by tinkered with the pause button in a way that didn't take into account all use cases.
Userlevel 7
Badge +22
No mention regarding audible
is there support for audible in this build?
Userlevel 7
Badge +17
I don't know about #1 as no longer use a local library.
#2 has been like that from the start of beta 6.4 - the behaviour clicking a searched song is different from choosing the same song from an album or playlist.
Userlevel 7
Badge +22
Barry M is correct. If queue is exhausted and hit play now it should add to end of queue and play now (not go back and put in random 2nd slot).

Other Play Now issues:
1) Folder View clicking on Song invokes Play Now even if using queue (thus interrupting music) . . should be Play All (and if using queue give pop up warning).
2) same issue if search by Song - clicking on song does Play Now instead of Play All (interrupting music if using queue)

Both are issues as well with Play Now function. I believe they rushed out the Play Now function because of popular demand and it has caused some unforeseen issues. Goes to show you how people are always saying .... add this its a no brainer (well there are lots of things that can happen - there are no NO Brainers). Play Now may need to push out to next release when they have more time to do it correctly (unless that is just me hoping they either pull it or make these corrections).