Bug 1195 - update of elapsed time and progress bar somewhat erratic when ffwd'ing through FLAC
: update of elapsed time and progress bar somewhat erratic when ffwd'ing throug...
Status: CLOSED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Audio
: unspecified
: All All
: P5 trivial (vote)
: ---
Assigned To: Vidur Apparao
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-25 12:06 UTC by Kevin Pearsall
Modified: 2008-12-15 11:56 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2005-03-25 12:06:16 UTC
with mp3 it looks pretty consistent, but the bar jumps back and forth
erratically when using flac...
Comment 1 Kevin Pearsall 2005-03-25 12:13:41 UTC
observed with r2722
Comment 2 Kevin Pearsall 2005-03-25 12:19:03 UTC
better in r2723, but there are still some anomalies:
- occasional bounce backwards to the displayed time from when you first started
ffwd'ing
- occasionally shows the time as negative (e.g. 00:-32) when ffwd'ing near the
beginning or end of a track
Comment 3 Kevin Pearsall 2005-03-25 12:20:48 UTC
actually it also seems to sometimes jump back to some random spot in the song
when you press play after you're finished ffwding...  like i was at 3:10 and hit
play, jumped back to 0:11 of a 4:11 duration track, ffwding at 4x.
Comment 4 Vidur Apparao 2005-03-26 09:17:41 UTC
I'm not seeing the erratic time display with 2743. I've fixed a few problems
with time display, so you may want to check it out again.
Comment 5 Kevin Pearsall 2005-03-28 15:54:31 UTC
Ended up doing some testing on this over the weekend, excitedly showing my
roommates the SB2.  And it looks much better now.  Thanks Vidur!
Comment 6 James Richardson 2008-12-15 11:56:47 UTC
This bug has been fixed in the latest release 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.