Bug 6064 – Elapsed time is inaccurate in 'Now Playing' screensaver

Bug 6064 - Elapsed time is inaccurate in 'Now Playing' screensaver

Summary:

Elapsed time is inaccurate in 'Now Playing' screensaver

Status:	CLOSED FIXED

Product:	SB Controller
Classification:	Unclassified
Component:	Screensavers
Version:	unspecified
Platform:	All All

Importance:	P2 normal (vote)
Target Milestone:	7.1
Assigned To:	Richard Titmuss

URL:
Keywords:

Depends on:	6950
Blocks:
	Show dependency tree / graph

Reported:	2007-11-06 10:19 UTC by Dan Evans
Modified:	2008-12-15 12:38 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dan Evans 2007-11-06 10:19:20 UTC

When the 'Now Playing' screensaver kicks in its Elapsed time is wrong.  It advances at about 5x speed.

Also, if I press the LEFT button it jumps the Elapsed time back to some mid-point where it then freezes briefly.  Then after a moment it advances at 5x speed again.

Pressing LEFT should also interrupt the screensaver.  It doesn't.

Comment 1 Richard Titmuss 2007-11-15 04:18:13 UTC

I have already fixed the now playing elapsed time advancing too rapidly. I still need to look at why the now playing does not exit correctly, this is a common screensaver problem.

Comment 2 Richard Titmuss 2007-11-16 14:21:51 UTC

Pressing left to exit the screensaver is fixed in r917.

Comment 3 Chris Owens 2008-07-30 15:32:29 UTC

This bug has now been fixed in the 7.1 release version of SqueezeCenter!  Please download the new version from http://www.slimdevices.com if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.

Comment 4 James Richardson 2008-12-15 12:38:00 UTC

This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.