FS#4787 - Skipping songs in playlist when using high bitrate ogg vorbis files

Attached to Project: Rockbox
Opened by Tim Crist (ts-x) - Monday, 06 March 2006, 01:55 GMT
Last edited by Christi Scarborough (christi-s) - Sunday, 19 March 2006, 15:22 GMT
Task Type Bugs
Category Music playback
Status Closed
Assigned To No-one
Operating System Iriver H300 series
Severity Medium
Priority Immediate
Reported Version
Due in Version Version 3.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


When playing certain albums encoded as q9 ogg vorbis, songs are being skipped. The songs being skipped play fine if you play them directly. They also play fine if you skip directly to them. What's strange is that the songs are actually shown in the playlist, they just don't get played. Depending on the album, different song positions are skipped. In the two examples I've identified so far, it's the fifth and seventh songs respectively that are skipped.

Through some experimentation with one of the albums I was able to gain a little more insight into this. For that particular album the fifth song was always being skipped. I noticed that while the second song was playing (and subsequently buffering the fifth song) the boost percentage was 90%+. Hard drive activity also seemed to be a bit eratic - the wps indicator was flashing and seemed to be on for longer than normal. As an experiment I re-encoded the second song to q8 (which would require less boost) - and it fixed the problem. So based on that, I'm thinking this has something to do with a buffering problem when high boosting is required.

This issue is maybe three or fours weeks old, before that the same albums played fine. I *believe* it might have been introduced around the time of the eq / pcm buffer changes, but I'm not positive.
This task depends upon

Closed by  Daniel Stenberg (bagder)
Friday, 21 April 2006, 18:07 GMT
Reason for closing:  Fixed
Comment by Tim Crist (ts-x) - Wednesday, 19 April 2006, 23:13 GMT
The recent playback system changes seemed to have fixed this. I just updated my build for the first time since the changes began (mid to late Mar-06) and have not been able to trigger this behavior. As always, great work!