haschmich wrote: > > However there's not much I can do for the cases under 2), and the > duplicates TrackStat entries keep increasing with every re-scan. > > This behaviour seems to have been introduced with my updating from 7.5.1 > to 7.7.1 a few weeks ago, which correlates to about 75 re-scans since > then. > There are three different cases where this could happen (which I'm aware of): 1. When track have incorrectly been tags with same musicbrainz id even if they should be different, these cases I strongly recommend to fix the tagging for. 2. When you are using cue sheets and are affected by this bug: http://bugs.slimdevices.com/show_bug.cgi?id=17894 (this has nothing to do with musicbrainz id's but it's causing similar issues) 3. When you have correct the tracks with musicbrainz id correctly but are affected by the change Musicbrainz did in May 2010 when they changed the behavior so compilation tracks started to get the same identity as the same song on the main normal album. They changed principles which caused the musicbrainz identifiers to not be unique anymore, they now represent a recording and not a track and a recording can exist on multiple CD's.
All these causes problems for TrackStat which is built based on the old musicbrainz principle where each track got a unique identity. It's point 3 which is caused by a "bug" in TrackStat. The reason I haven't fixed this yet is that I haven't figured out a good solution, the easy solution would be to just make it possible to disable the musicbrainz handling completely, but this would result in that you no longer can rename/move tracks and keep the TrackStat statistics. Still I think this is the solution I'm going to select at least on short term because I've started to realize that this cause issues for more and more people. If you have a lot of duplicate, a trick to get rid of them is to: 1. Make sure you have taken a backup of the database files in the cache directory (after shutting down SBS/LMS), so you can get back if it doesn't work. 2. Perform a TrackStat backup (and make sure the backup file contain proper data, look at it with a text editor or similar) 3. Use the "Remove all data" button in TrackStat setting page backup section 4. Restore the backup from point 2. In point 4 TrackStat is going to use the musicbrainz identifiers and based on this it will ensure that no duplicates is generated. Of course, this doesn't solve the problem, because you will still get duplicates the next time you perform a rescan, I'm just saying that it's a way to get rid of some of them if it's starting to get very bad. If you do this operation, make sure to keep the backup from point 1 so you have a way back if something goes wrong. I'll try to get some time during the next weeks or so and implement the simple solution where it's possible to disable the musicbrainz related logic through a settings page. ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=94950 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
