prabbit wrote: > > 4. I ran Database Query to look at how "healthy" my LMS/TrackStat > environment is. Frankly, according to the queries, it's not very > healthy. There are a lot of duplicates with musicbrainz IDs (919), there > are numerous TrackStat inconsistencies, and a couple of Custom Scan > inconsistencies, too. > > Erland, it's #4 that concerns me the most. Should I start a separate > thread for those? I can post the query results. I would need some > guidance on addressing the potential issues. It may be that some of them > are benign, but you'd have to be the judge of that. > It's probably a good idea to start a new thread if we need to discuss this further.
But for the duplicate musicbrainz ID's the reason is likely the changed principle Musicbrainz did 2010 when they started to use the same musicbrainz id on a track on a normal album and the same track on a compilation album. Unfortunately this breaks the possibility for TrackStat to uniquely identify music files with musicbrainz id, the only solution to get rid of the problem is to deactivate the musicbrainz support in TrackStat through the "Enable musicbrainz tags" option in TrackStat settings. If you have duplicate musicbrainz id's the number of duplicates are going to increase every time TrackStat does a refresh, this happens at startup and after rescan unless you have disabled the refresh functionality. If you disbable musicbrainz tag functionality it means that if you rename/move files TrackStat won't be able to keep the statistics for them. To get rid of the existing duplicates, unfortunately the only solution is to: 1. Take a backup of TrackStat data through TrackStat settings page 2. As an extra safety, you can also shutdown SBS/LMS and take a copy of the persist.db file in the SBS/LMS Cache directory 3. In TrackStat settings page select to "Remove all data" and then specify the full path to the backup file taken in point 1 and use the "Restore from File" functionality. The restore operation will make sure to only import one instance with the same musicbrainz id, so this will get rid of the duplicates. Remember that the import runs in backgroud so you need to look in the server.log file to see when it's completely finished. The "Find alternative files" option generally makes the restore process a lot slower, so unless you need the restore to try to relocate files which you have moved previously which didn't have musicbrainz tags I would suggest disabling "Find alternative files" option. Please note that in a large library with "Find alternative files" the restore can easily take many hours. In my own library with about 4000 tracks it just takes few minutes and is significantly faster than that if I disable "Find alternative files" option. If you get warning about "Unused " entries, this is typically statistics pointing to files that either have been removed or moved/renamed and didn't have musicbrainz tags. If you just want to remove these there is a "Delete unused statistics" button in TrackStat settings page. I have not tried this in a large library but I suspect it could take some time to execute and while doing so I think the server will be locked, so you probably don't want to do this when you are about to listen to some music. Generally the unused entries doesn't cause any problem unless you have a lot of them so it makes the database a lot larger than it needs to be. Feel free to reply in this thread if you just have a quick question, but please use a separate thread if you feel that you have a lot of questions. ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=96124 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
