Bug 11628 - Now Playing mode lagging by one track
: Now Playing mode lagging by one track
Status: RESOLVED WORKSFORME
Product: SqueezePlay
Classification: Unclassified
Component: Now Playing
: unspecified
: PC Other
: P1 normal (vote)
: 7.4.0
Assigned To: Ben Klaas
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-03 04:49 UTC by Michael Herger
Modified: 2009-09-08 09:31 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 Michael Herger 2009-04-03 04:49:19 UTC
When listening to eg. Last.FM it pretty often happens that the screensaver is lagging by one track. I'm seeing artwork and track information from the previous track.

Probably related to bug 11627. Trying to reproduce right now, but I think it happens after I've loved/banned a track.

SC Version: 7.4 - 25762 @ Wed Apr 1 01:38:14 PDT 2009
SP 7.4 r4824 (Jive), 7.4 r5096 (fab4)
Comment 1 Chris Owens 2009-04-13 09:12:58 UTC
Ben notes that there is a 30-second update which should make sure the screen does eventually get updated correctly.  Does that not happen, Michael?
Comment 2 Michael Herger 2009-04-14 05:11:20 UTC
I'd say it was lagging even after several tracks
Comment 3 Blackketter Dean 2009-07-22 09:02:12 UTC
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code.  Feel free to move it back if it's specific to the original product.
Comment 4 Michael Herger 2009-07-24 03:38:40 UTC
Ahem... still happening.
Comment 5 Richard Titmuss 2009-08-24 12:08:59 UTC
i've seen this too, when SP can't play an AAC file. then the NP track is reported incorrectly. I think it was wrong on both SP and the web interface when I saw this.

Michael do you see this just on SP, or the web interface too.
Comment 6 Michael Herger 2009-08-25 05:03:37 UTC
I'm unable to reproduce this right now. Been playing with Last.FM, thumbs up and down. Seems fine now...
Comment 7 Ben Klaas 2009-08-25 06:57:43 UTC
I'm fairly certain this will be an SC issue where playerstatus is not sending correct information, but I haven't seen it in a long time now. I'm moving this to WORKSFORME