FS#1377 - Negative time shown in WPS on resume of long files

Attached to Project: Rockbox
Opened by Anonymous Submitter - Tuesday, 20 May 2003, 14:14 GMT
Last edited by Daniel Stenberg (bagder) - Friday, 05 December 2003, 09:42 GMT
Task Type Bugs
Category Music playback
Status Closed
Assigned To No-one
Operating System
Severity Low
Priority Normal
Reported Version Release 2.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


When resuming on a long file (~60 minutes or more),
when your last position was fairly far into the file
(~20 minutes or more), the WPS will show a negative
value for the current time. The actual position it is
playing from will be correct, but the display
information will continue to be wrong.
I have never noticed the negative time when resuming
smaller files. It happens frequently for large files.

Currently using the release version 2.0. It also
happened with daily builds before 2.0.

Jukebox 20 GB recorder: JBR20101
This task depends upon

Closed by  Daniel Stenberg (bagder)
Friday, 05 December 2003, 09:42 GMT
Reason for closing:  Fixed
Comment by Ritchie Lau (bdbx18) - Wednesday, 02 July 2003, 16:27 GMT

Anyone working on this? I have the same problem.
The WPS shows a negative number on resume but the
moment you fast forward, it plays back from a much earlier
point. So now I spent a lot of time fastforwarding back and
searching for the resume point.

To alleviate the amount of fastforwarding, I do my radio
recordings at 30 mins timesplit each.

Comment by Linus Nielsen Feltzing (linusnielsen) - Friday, 04 July 2003, 07:51 GMT

Have you tried the latest daily build?
Comment by Harold Toler (herg) - Friday, 01 August 2003, 14:32 GMT

I can confirm that this still happens with the CVS-030801
daily build.
Comment by Harold Toler (herg) - Friday, 01 August 2003, 15:51 GMT

A little more info:

Playback resumes at the correct position, only the elapsed
time is incorrect.
I could not repeat the problem with a CBR file.
Comment by Harold Toler (herg) - Monday, 04 August 2003, 20:37 GMT

I have submitted a patch to fix this.
Comment by Björn Stenberg (zagor) - Friday, 17 October 2003, 15:13 GMT

This is fixed in CVS.