Bugzilla – Bug 2559
Use of genric tags confuses DB build (I think)
Last modified: 2008-09-15 14:39:24 UTC
I believe I've proven to myself that SlimServer messes up when creating the slimserversql.db file from stratch *IF* there is an album with the following tags: album = album artist = artist I use those generic tags when ripping sometimes and then go to FreeDB or where ever later to do the proper tagging. If I use the tags above the resulting album (named "album" of course based on the tag) does not point to the right tracks, but to the tracks of some other album. I tested this by deleting and re-creating the entire slimserversql.db file several times with the same result. I then changed the tags (using Tag&Rename) to be: album = album1 artist = artist1 and recreated slimserversql.db file one more time, and voila the album (now named "album1") is correct. I've had this happen more than once. It seems that using the tags: album = album artist = artist is confusing slimserver when it builds the database.
can you attach a (small?) file that exhibits this problem? I'll add it to my music library and see if I can duplicate the problem.
I have marked this "bug" as INVALID.....sorry for the false alarm. As I went looking for a suitable file to post here as requested, I noticed that I had inadvertently left a 2nd album in a state where its album and artist tags were also "album" and "artist" respectively. I had not noticed before because this 2nd album was part of a mult-disc set and in adirectory with completely different name than the 1st album. But of course SlimServer groups tracks based on album name as stated in the tags not on directory names. So SlimServer was actually putting all these tracks together as one album since I have the group multi-disc option set. Therefore, once I changed the tags of one of these 2 albums to "Album1" and Artist1", the tracks separated again making me think what I expressed above in the original report.