Bug 13897 - Playing an album is very complicated in 7.4 (FW7433)
: Playing an album is very complicated in 7.4 (FW7433)
Status: RESOLVED DUPLICATE of bug 13896
Product: SB Controller
Classification: Unclassified
Component: UI
: unspecified
: PC Windows Vista
: -- normal (vote)
: 7.4.0
Assigned To: Squeezebox QA Team email alias
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-07 16:26 UTC by Stefan Hansel
Modified: 2009-09-08 12:19 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Hansel 2009-09-07 16:26:41 UTC
Playing an album is heavily complicated now. 
If a select a single song in an album then press 'forward' I'd expect to skip to the next song of the album (like I'm used from a CD-player). Instead the playlist is restarted (if there are no new items) which always confuses me.

I realize that I can use the 'plus'-button on an album to get a popup where I can select to play the whole album. This is very cumbersome.

I found the 7.3 way much more intuitive (i.e. pressing play on an album just starts it)
Comment 1 Ben Klaas 2009-09-08 08:16:53 UTC
Will look into the confusion you are having, but to be clear-- pressing play on an album still just starts it, same as in 7.3.
Comment 2 James Richardson 2009-09-08 09:51:46 UTC
*** Bug 13898 has been marked as a duplicate of this bug. ***
Comment 3 Ben Klaas 2009-09-08 09:55:16 UTC
This is another one that I think will be fixed by updating SqueezeCenter (now Squeezebox Server).

I do not see this behavior on my setup. Selecting a single song in an album and pressing forward starts the track and pushes to the now playing screen. Pressing forward advances to the next track in the album.

James- on comment#2, don't think bug 13898 has anything to do with this bug...maybe you marked that one dup of the wrong number?
Comment 4 Stefan Hansel 2009-09-08 12:19:18 UTC
If 13869 is fixed, then playing albums on the controller is fine again :)

*** This bug has been marked as a duplicate of bug 13896 ***