FS#9819 - Rapid skipping causes next track info to stop updating

Attached to Project: Rockbox
Opened by Jonas Häggqvist (rasher) - Thursday, 22 January 2009, 21:46 GMT
Last edited by Jonathan Gordon (jdgordon) - Wednesday, 16 December 2009, 08:56 GMT
Task Type Bugs
Category Music playback
Status Closed
Assigned To No-one
Operating System All players
Severity Low
Priority Normal
Reported Version Version 3.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


The summary pretty much says it all: My usual listening pattern is to add most or all songs on my player, and skip songs I'm not in the mood for. This occasionally results in a lot of skipping (past say, 5-10 tracks), and while I do this the next track info will stay the same, so if I have a playlist of Track1-Track20, and am listening to Track1, and start skipping, the next track will continue to be Track2. I *think* that the next track info is only updated once I stop skipping and a complete rebuffering to the new location has been done, though this is just speculation.

I'm not 100% sure this happens everytime, but I see it often with my usage pattern.
This task depends upon

Closed by  Jonathan Gordon (jdgordon)
Wednesday, 16 December 2009, 08:56 GMT
Reason for closing:  Out of Date
Additional comments about closing:  rasher, reopen if its still happening... no repro 6 months ago is long enough
Comment by Jonathan Gordon (jdgordon) - Thursday, 22 January 2009, 22:20 GMT
this isnt really a bug that im is worth worrying about... the problem is the CPU/hdd just isnt fast enough to keep up. Untill the buffering is done there is no way to get the next tracks id3 info...
when a track i buffered it happens in this order:
1) id3 info
2) AA if enabled
3) audio

this happens untill it runs out of room on the buffer, then the first track off the buffer has its id3 info loaded to make sure it can be displayed.... what you are doing though is trashing the buffered info too quickly so nothing is buffered at all, and you are still skipping so you keep trashing the buffer... nothing can be done about this.
Comment by Thomas Martitz (kugel.) - Friday, 23 January 2009, 16:52 GMT
As long as the next track info (or all track infos) is fine again once you stopped rapid skipping I wouldn't call this a bug.

"Fixing this" would maybe mean to disallow fast skipping, and I wouldn't want that.
Comment by Jonas Häggqvist (rasher) - Friday, 23 January 2009, 17:06 GMT
I disagree. At the very least, as soon as the Next track info is no longer valid (after the first track skip) it shouldn't be showed, I understand that there might not be any infor ready to display, but displaying a song I skipped past many tracks ago as the next track, for 10-15 seconds is just wrong.
Comment by Johannes Linke (Jaykay) - Friday, 23 January 2009, 20:27 GMT
i agree with rasher, the wrong information should be immediately deleted when its no longer valid. i think a empty "next song" is better then a wrong "next song".
Comment by Thomas Martitz (kugel.) - Monday, 06 April 2009, 04:04 GMT
Is this still happening?
Comment by Thomas Martitz (kugel.) - Wednesday, 10 June 2009, 07:19 GMT
I can't reproduce it.