FS#7244 - Follow playlist results in selection of next track

Attached to Project: Rockbox
Opened by Steve Bavin (pondlife) - Friday, 01 June 2007, 10:31 GMT
Last edited by Steve Bavin (pondlife) - Friday, 06 July 2007, 20:53 GMT
Task Type Bugs
Category User Interface
Status Closed
Assigned To No-one
Operating System All players
Severity Low
Priority Normal
Reported Version Daily build (which?)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


1) Enable Follow Playlist.
2) Play a track in the File Browser (not the last track in a directory though).
3) Press SELECT to go from the WPS back to the browser.

Expected result:
The currently playing track is highlighted.

Actual result:
The next track is highlighted. Testing with shuffle enabled I can see this is the next track to be played, not the next track in the directory. You may need to repeat the process a few times (i.e. pressing SELECT from WPS)...

I can repro this from cleared settings, just enabling Follow Playlist.
This only occurs on my H340, but not on the H340 simulator.
This task depends upon

Closed by  Steve Bavin (pondlife)
Friday, 06 July 2007, 20:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  Committed the patch, seems to work fine.
Comment by Hexagonal (Hexagonal) - Friday, 01 June 2007, 14:27 GMT
maybe it is the same bug as mine:
Comment by JerryLange (psycho_maniac) - Wednesday, 13 June 2007, 04:04 GMT
I can reproduce this bug with my 80gig ipod video
Comment by Robert Kukla (roolku) - Thursday, 14 June 2007, 11:50 GMT
I can confirm the bug (F60). Another symptom is that the wps-tag %fn (filename) shows the next filename and not the current one for the described scenario.

It appears that (mp3entry).path is somehow set incorrectly, as it also effects plugins that make use of that information.
Comment by Steve Bavin (pondlife) - Monday, 18 June 2007, 11:14 GMT
roolku - FYI, your symptom is logged as  FS#7248 .
Comment by Steve Bavin (pondlife) - Friday, 06 July 2007, 17:39 GMT
OK, the attached one-line patch resolves this... the question is does it break anything else?? Please give it a spin: