Bugzilla – Bug 4278
Blank album names after rescan new/changed music
Last modified: 2008-12-18 11:12:53 UTC
1. I have an album that contains several tracks. 2. I change one of the track so the ALBUM tag is removed 3. I perform a rescan of new/changed music The result is that the album information is cleared, its also cleared for all tracks on the album not just the track where the ALBUM tag was removed. The correct behaviour would be to connect the track with no ALBUM tag to the virtual album "No Album". If I browse albums the album with shown with just a blank entry without any text at all. I have only verified that this is the case with MP3v2 tags. The problem is solved if I perform a full rescan, then it correctly results in album information for all the tracks with ALBUM tags and "No Album" is showed on the track with no ALBUM tag.
I am seeing something, but it doesn't quite appear to be the same bug. May I ask what directory these tracks are in? I think the directory name may have something to do with the problem.
They are in: /mnt/mp3music_small/Cajsa Stina �kerstr�m - Kl�dd f�r att g�/
I can't reproduce this, but I'm willing to keep looking at it. If any other users see this, they can add info. The workaround is straightforward: do a clear and rescan everything. I'm setting the target for 7.0 so that it doesn't prevent release of 6.5.1 in a few days.
I too have recently seen something like this, but as I hadn't scanned for a while and I was picking up a fair number of changes to tags, I can't really say much that would help identify the bug. I did a full rescan to recover. After a scan for new and changed files, I ended up with a blank album name containing "No Album" tracks. I also had a "No Album" album name, which only contained a few entries.
Please open a new bug if there is related behavior.
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.