Bug 9864 - Pressing PLAY on a song in the context of an album does not immediately play that song when shuffle is on
: Pressing PLAY on a song in the context of an album does not immediately play ...
Status: RESOLVED DUPLICATE of bug 14662
Product: SqueezePlay
Classification: Unclassified
Component: Browser
: unspecified
: PC Other
: P3 normal with 5 votes (vote)
: 7.5.x
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-10-31 17:46 UTC by Blackketter Dean
Modified: 2011-04-08 04:59 UTC (History)
5 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blackketter Dean 2008-10-31 17:46:56 UTC
If you press PLAY on a song in the context of an album, the whole album should be played starting with the selected song, even if shuffle is on.

This is the behavior on the classic UI and should be consistent.
Comment 1 Ben Klaas 2008-11-03 08:58:59 UTC
mine to fix. 7.3.1
Comment 2 James Richardson 2008-12-19 08:03:53 UTC
Changing target to next release
Comment 3 Ben Klaas 2009-08-26 07:54:05 UTC
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Comment 4 Chris Owens 2010-03-09 18:00:39 UTC
the 7.4.x target is in the past
Comment 5 Raph 2011-02-23 03:41:00 UTC
Noooo, why WONTFIX ?

I mean it looks like a basic feature of the controller : click on a song to listen to it, whatever the options or mode you selected. Never seen that on any music player, even the most stupid one :(

To be honest, I am completely new to the Squeezebox world (spent less than an hour playing with mine) and I do not know how the "Shuffle mode" has been designed. It looks like in this case, the "current playlist" is built from the user view (album/artist/anything) and then randomized (else, if it is about moving randomly in the current playlist, why bother randomizing the album when building the current playlist ?). The index used to say "play the 
[index] track of the current playlist" is the index of the song selected by the user in the album view. And because of randomization, they do not match...

Instead of using an index related to the current playlist, could a Track Id be used ? In fact, my question is "Is that a lot of work ? Isn't it already half done ? (i mean using an Track Id with the current playlist in another context)".

Well, I use the "Shuffle mode" a lot, and it's very annoying...
Comment 6 Jim McAtee 2011-02-23 05:44:11 UTC
I'd like to suggest that this bug be reopened.  This is something that should be looked at in the onebrowser development.  Some behavior has to be chosen - either the old behavior of the ip3k ui, or the (broken?) behavior of SqueezePlay.

A quick test of onebrowser shows that it may be partially fixed in that branch.  As an example: If you have an SP player in 'shuffle songs' mode and play track 4 from an album, it adds all tracks from the album and it does begin playback with track 4.  However, track 4 will also be the fourth item in the current playlist, which means that three (random) tracks from the album will placed in the playlist before the selected track and won't be played.

The correct behavior would be add the selected track as the first item and shuffle the remaining tracks to follow.
Comment 7 Ben Klaas 2011-02-23 15:22:45 UTC
apologies, marking this WONTFIX was a clerical error on my part. A different bug was intended for that resolution.
Comment 8 Alan Young 2011-04-08 04:59:07 UTC
*** This bug has been marked as a duplicate of bug 14662 ***