Bug 15684 - Song progress when SBS stopped
: Song progress when SBS stopped
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: Now Playing
: 7.5.0
: PC Windows XP
: P3 normal (vote)
: 7.5.x
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-11 04:51 UTC by Philip Meyer
Modified: 2010-09-13 11:57 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments
never have elapsed time exceed track duration, nor remaining time go less than zero (788 bytes, patch)
2010-06-04 10:43 UTC, Ben Klaas
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2010-02-11 04:51:20 UTC
I've noticed that if I'm playing a song locally from SBS, and I stop SBS, the song continues to play (as it is buffered in the Touch memory). But when it gets to the end of the song, the track time continues to count up, and the track time remaining shows strange info (like -32:00).

What should happen? I was expecting that when the buffer was empty (e.g. the end of song reached), the Now Playing screen would show music stopped/paused, and then the idle screensaver fire up after <n> seconds.
Comment 1 Chris Owens 2010-03-08 11:30:32 UTC
Moving lower-priority bugs to next target
Comment 2 Ben Klaas 2010-06-04 10:43:18 UTC
Created attachment 6879 [details]
never have elapsed time exceed track duration, nor remaining time go less than zero

at a bare minimum we shouldn't have the NowPlaying applet updating the progress elapsed/remain times past the duration of the track. This patch addresses that.

To consider for the future-- if audio is not streaming and server is disconnected, update NP screen to show Stopped
Comment 3 SVN Bot 2010-06-15 09:04:43 UTC
 == Auto-comment from SVN commit #8855 to the jive repo by bklaas ==
 == http://svn.slimdevices.com/jive?view=revision&revision=8855 ==

Fixed Bug: 15684
Description: never have elapsed time exceed track duration, nor remaining time go less than zero
Comment 4 Chris Owens 2010-09-13 11:57:38 UTC
This bug has now been fixed in a released version of the Squeezeplay firmware (SB Touch, SB Radio, and SB Controller).  If you are still seeing this bug, please make certain you are running firmware 9009 or higher, and re-open it.

Thanks!