Bug 14760 - Playing a music-service already-playing item should not restart it (go to Now Playing instead)
: Playing a music-service already-playing item should not restart it (go to Now...
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Player UI
: 7.4.0
: PC Other
: P2 enhancement with 1 vote (vote)
: 7.5.0
Assigned To: Alan Young
:
Depends on: 14423
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-13 16:24 UTC by Weldon Matt
Modified: 2010-04-08 17:26 UTC (History)
4 users (show)

See Also:
Category: Feature


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Weldon Matt 2009-10-13 16:24:00 UTC
This was a design oversight of mine for "press-to-play" behavior that was brought up by Pandora (since it causes specific side effects for them).

If an item is currently playing in "Now Playing," selecting it again from a menu should not stop and re-start playback.  Instead, the UI should just push into the Now Playing screen.  This is how ipods and many other devices work, and it's done to avoid accidentally restarting playback.

Not a huge deal, maybe, with a song in "My Music," but when you get into things like interactive radio, podcasts/long-form content etc. it can cause user frustration.

Also, in Pandora's case, if the item is a station, re-selecting it adds to the skip limit of the station in question.
Comment 1 James Richardson 2009-10-13 16:25:28 UTC
Ben: please re-target as needed.
Comment 2 Andy Grundman 2009-10-13 16:33:29 UTC
For now we should just do the simple thing of intercepting 'playlist play' if the URL matches the currently playing URL, and then push to Now Playing, on both ip3k and SP UIs.
Comment 3 James Richardson 2009-10-13 19:26:15 UTC
*** Bug 14754 has been marked as a duplicate of this bug. ***
Comment 4 Alan Young 2009-10-13 23:40:43 UTC
Hmm, This is a distinct change in behaviour. I'm not sure that all users would be happy with it.
Comment 5 Weldon Matt 2009-10-14 10:09:47 UTC
(In reply to comment #4)
> Hmm, This is a distinct change in behaviour. I'm not sure that all users would
> be happy with it.

When was the last time "all users" were happy with anything (seriously)?  That's, um, a pretty high bar for success. Point taken though :-).

Press-to-play was already a pretty major change in behavior in 7.4.  In this type of playback model, the current "re-play if already playing" has irreversible consequences in some cases.  For example, accidentally pressing the name of a Pandora station while listening to it already will skip past the current song, and the user has no way to get back to that song.  This is one of the reasons why other press-to-play devices, such as the ipod, just take the user to the now playing screen if the track/station is already playing(where he/she can still pause, skip, etc if desired).

This is also how Pandora apps work (anywhere you encounter them).  And in fact they've asked us to make this change in order to pass their certification process...
Comment 6 SVN Bot 2009-11-17 06:59:49 UTC
 == Auto-comment from SVN commit #29295 to the slim repo by ayoung ==
 == https://svn.slimdevices.com/slim?view=revision&revision=29295 ==

bug 14760: Pressing an already-playing item should not restart it (go to Now Playing instead) 
This is implemented in the case that the playlist consists of a single item with the same URL as the one that is about to be played. Works with Pandora.
Works from SP but not on ip3k using IR because of bug 14423.
Comment 7 Alan Young 2009-11-17 09:38:07 UTC
Update hours, etc.
Comment 8 Alan Young 2009-12-05 06:10:25 UTC
Bug 14423 is now fixed
Comment 9 SVN Bot 2009-12-05 06:11:02 UTC
 == Auto-comment from SVN commit #29551 to the slim repo by ayoung ==
 == https://svn.slimdevices.com/slim?view=revision&revision=29551 ==

bug 14760: Playing a music-service already-playing item should not restart it (go to Now Playing instead)
Comment 10 Chris Owens 2010-04-08 17:26:52 UTC
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!