Bugzilla – Bug 605
Incorrect song numbers when using MoodLogic
Last modified: 2008-12-18 11:51:58 UTC
When using MoodLogic, the number of the first song is always listed with a 0, and put at the bottom of the list--the second song is listed as 1, 3rd as 2, etc. I chose "don't use moodlogic", did a rescan, and it was fixed. I chose "use moodlogic" again, and the problem reappeared.
I wasn't specific--i'm talking about album track listings here. so, for example, on Wilco's YHF, i am trying to break your heart shows up as 0, and kamera 1, etc.
is this the case for every album in your collection? I'm unable to reproduce this on my setup. What does moodlogic say is the track number for these songs? Are you looking at the songinfo page of the web interface , which skin are you using? do you have a music folder setting at the same time, or do you have it blank and use moodlogic only?
Upon further investigation, this issue appears to be caused by ML. All of the tracks in the ML mdb are numbered from 0 to X for each album. I tried incrementing all of the track numbers by 1 in the ML db, and that didn't help. All of the ID3 tags still have the proper track numbers listed. Any way to default the slimserver web interface to display 0 as the first track instead of 1?
The track numbers displayed by SlimServer are taken from the ID3 tags or the Moodlogic DB. if you change those, you will have to wipe the cache to get slimserver to fully index the changes. Server settings, performance, wipe cache. If you are talking about the track numbering for the playlist in the Fisbhone skin, the skin starts the playlist at 1. There are no settings to change this.
Okay--I made a backup of the moodlogic mdb then incremented all of the track numbers by 1. Then, i started slimserver, wiped the cache, and everything is now okay. Although this is obviously a moodlogic bug, it's worth noting that the ML gui doesn't appear to read directly from the mdb at startup, but rather a file called Mlsdbv4 in the ml directory. So, although i added 1 to all of the song numbers earlier, the ml gui still had the outdated info cached. Anyhow, the problem, as it was passed to slimserver wasn't limited to just the web interface--it was also present in the squeezebox interface. so, when you choose an album with the remote, and play all tracks, it always put the first song at the bottom of the playlist. Looks like slimserver software assumes that track numbers will always be a subset of natural numbers. It's a workaround, but it works for me. I tried to research the problem on the ml forums, but it's full of 14 year olds, and it looks like the organization as a whole is underfunded and understaffed. thanks for the help.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.