Bugzilla – Bug 4435
Miscellaneous playlist display errors in new version
Last modified: 2006-11-08 11:07:48 UTC
I downloaded a new version of SlimServer (6.5.1 - 10479). There are several errors in the display of the playlist. 1) If a track is displayed in the Playlist as, for example, ("TrackNumber" "Track" from "Album" by "Artist"), the "Now Playing" line in the playlist display says only (from "Album") - no Tracknumber, Track or Artist. This is a new behavior from my previous version (6.5.1 - 10337). 2) When a track becomes the now playing track, its display in the Playlist changes to ("TrackNumber" "Track" from "Album") - the Artist is removed. This then continues to be the display when the playlist moves to the following track. This sometimes happened with the previous version but now seems to be consistent. 3) Occasionally tracks lose the Artist when they are entered into the Playlist. This behavior is erratic, and typically only happens to a few tracks in an album. This also occasionally happened with earlier versions of SlimServer. I tried to reproduce it then, but it did not seem to be a function of a particular track or album - it just occurs randomly.
One further observation. Errors 1) and 2) do NOT occur for the first track of each album - the "Now playing" display has all of the information, and the Artist remains in the playlist entry. All other tracks behave as described.
After I performed a "Clear Library and Rescan Everything" operation, these display errors went away. It is possible that these errors are related to the problem of Bug 4434, since I did change the article ignoring before these errors occurred. However, note that items 2) and 3) did occur occasionally with earlier versions.
Clearing the library and rescanning everything is a decent workaround, but it sounds like there is a bug here with the 'Scan for new and changed music' function. Ross could you make sure this is reproducible?
I have tried to reproduce this problem, by deleting and reinstalling SlimServer and then changing the articles to ignore, but I have not been able to make it happen again. There must have been some specific sequence of things I did to cause it, and I have not yet done exactly that sequence again. I will keep a lookout for it to reoccur.
Steve, In that case would you mind if I set this bug to works for me for now, then when you have run into this again and determine steps to reproduce we'll reopen the bug and take another look at it?