Bugzilla – Bug 3928
remove dead data when doing on the fly scanning of updated tracks
Last modified: 2009-10-22 11:23:21 UTC
When tracks in an album are updated via common browsing, SlimServer picks up tag changes to artists but it doesn't drop previously referenced contributors that now (should) have no tracks or albums. Fix a typo in an artist name and you'll then have two similarly spelled artists, both in the library's artist list and in the credits for the album/track. In the artist list (browse Artists) the mispelled contributor will have an album, but it will contain 0 tracks.
Small correction: The two artists are listed under browse artist, and they're both listed wherever the album is listed, but they're not both listed in the track details.
Jim - can you run with --d_import - the cleanup method should be called when a rescan is run. Is this via BMF or rescan?
What I meant by 'common browsing' is just normal browsing via New Music, Albums, Artists, etc. This activity seems to be enough to cause tracks to be rescanned and changes written to the database. I don't recall how deep I had to browse - perhaps all the way to the track detail level to get it to completely update the info. Is that the intended behavior?
Dan says that is actually the intended behavior.
Ok, that's fine. I've changed this to an enhancement request. I'd suggest running some sort of limited cleanup for these cases. Go through the metadata of album, date, contributors and genres associated with any track being changed or deleted from the database, and delete any that no longer exist.
will reassess post 6.5
This appears to be largely fixed in recent releases.
This bug has been marked as fixed in the 7.4.1 release version of SqueezeBox Server! Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.