Bugzilla – Bug 2334
Now playing index off by one after unsyncing players
Last modified: 2008-09-15 14:39:24 UTC
On Slimserver 6.2b1 (build 4687 on Windows XP Pro), running 2 players (one SB2 wireless and one SoftSqueeze on local machine). Synced players for a while and then unsynced. After unsync, the Now Playing was off by one song (showed the song just played, not the active song. This showed on the web interface and on the SB2 player interface. To add to the mix, I was also in Song shuffle mode. I have not tried to reproduce this; tonight was first occurence (I have only had the SB2 for 3 days ;-) )
kdf - any thoughts here?
Additional data; I have seen this happen without the synchronization; if you jump around in a playlist then the server *sometimes* ends up one song off (it shows the song just played, not the song actually playing). This happened twice today, I will see if I can narrow it down more to id the guilty sequence
no ideas here. I've never noticed it on my setup. I don't sync, however. code clearly jumps to the current song if showing 'now playing' info, so variables would be how could the detection of showing 'now playing' be tripped up, or how could the curent song index get confused. another user reported a fix after rescanning, indicating a track ID->database problem, but I'm not sure that what it reported here matches up with that.
I've also seen this but not recently. All SlimServer functions returned the correct song (as seen from output of iTunesUpdate & SlimScrobbler) just the playlist/now playing display was wrong. I'd guess some sort of problem with a track considered invalid in some way removed from the play "list" and hence the track index pointing to wrong track? (BTW I never user syncronised players so that is unlikely to be the cause)
I'll leave this open, but need a reproducible case.
(In reply to comment #5) > I'll leave this open, but need a reproducible case. > I will see what I can do to get you a case.
it has been very reproducible for me! But I see a lot of bugs that look similar (incorrect track displayed) have been fixed recently... I will download the latest 6.2 and see if it happens again. Is there any debug output that would be useful?
Yees, the --d_source debug output would be helpful. Also specific details (each key press and what you see) to help reproduce here.
I've had it on random all morning, which normally triggers the problem quite quickly, and no problems so far...
Created attachment 1033 [details] d_source log It's doing it again. 3 tracks off this time! Log attached - I let a couple of tracks play and moved up and down the playlist with the remote. Is it something to do with this 'song queue' mentioned at the end?
this looks the same or similar to bug 2510 btw.
ok, lets group this with 2510 *** This bug has been marked as a duplicate of 2510 ***