Bugzilla – Bug 15835
Progress bar doesn't move and then catches up; Elapsed time not displayed until bar catches up
Last modified: 2012-02-27 17:33:08 UTC
Running continuous Touch/TinySC testing using firmware r8622 playing flac album from USB hard drive. Has been running for about 24 hours. Not sure when it started, but it wasn't like this earlier in the 24 hour period. At the beginning of each track, the track progress bar for the default Now Playing screen doesn't move until perhaps 2/3s of the track has played. When it does move, it just jumps to that point. The elapsed time/time remaining values on either side of the bar aren't displayed at the beginning of playing this track. When the bar jumps, suddenly the values are displayed too. Attaching two photos: No progress bar movement, and another immediately after the progress bar corrected itself. Hopefully the elapsed and remaining time values are a clue to what is going on.
Created attachment 6598 [details] Now Playing with progress bar incorrect
Created attachment 6599 [details] Now Playing immediately after progress bar corrected itself
Also should note that this happens for all successive tracks.
Steven could you see how hard it is to reproduce this?
I've reviewed the code in the NowPlaying applet and there's no obvious reason why those labels would disappear like that. Would love to see a clear means of reproducing this so I can investigate further.
Could this be a consequence of the fix for Bug 15814?
In NowPlaying, _updatePosition() is called every second. if the player object returns false from isWaitingToPlay(), it will not update anything. -- Bug 15814: do not update position if track isn't actually playing if self.player:isWaitingToPlay() then log:debug('track is waiting to play, do not update progress bar') return end to figure out if this is the problem, Logging for applet.NowPlaying should be set to debug, the problem reproduced, and the log attached to this bug. I think there's a good chance playerstatus is not being sent after waitingToPlay is removed or that the playerstatus message is actually wrong. Sanity checking the Player.lua code for this doesn't make me think the issue is SP side
Mickey have you seen this recently? I have not seen it lately myself.
Mickey and Steven agree they don't see this any more.
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.