Re: [SlimDevices: Plugins] TrackStat adding duplicate tracks on every rescan

2012-04-29 Thread haschmich
erland wrote: However, if you feel you are interested to help, you can try to run it and see if it generates any incorrect duplicates in your library. In case you do, you should probably look at the end of the thread as it evolved a bit during the testing I did back then, so the most

Re: [SlimDevices: Plugins] TrackStat adding duplicate tracks on every rescan

2012-04-27 Thread haschmich
Thanks erland, this worked exactly as you described. No duplicate tracks after import, and after one re-scan, it looks like this now, which is as expected: Code: $ grep musicbrainzId /media/stubenas/usb1/trackstat/trackstat_scheduled_backup_20120427b-manual-nohist.xml

Re: [SlimDevices: Plugins] TrackStat adding duplicate tracks on every rescan

2012-04-27 Thread erland
haschmich wrote: Anyway, I've always thought of the MusicBrainzId thing as kind of a kludge, as it is inherent that it cannot provide ids for every track, think of e.g. personal recordings which aren't even published. The ideal for me would be TrackStat generating its own IDs

[SlimDevices: Plugins] TrackStat adding duplicate tracks on every rescan

2012-04-26 Thread haschmich
I'm experiencing duplicate track records in TrackStat for songs which have identical musicbrainzids. Symptoms are that I can't browse certain albums with trackstat any longer, giving me an error like in the attached server log. The number of duplicate TrackStat entries increases with every

Re: [SlimDevices: Plugins] TrackStat adding duplicate tracks on every rescan

2012-04-26 Thread prabbit
I'm seeing similar behavior with my rescans, too. prabbit's Profile: http://forums.slimdevices.com/member.php?userid=11142 View this thread: http://forums.slimdevices.com/showthread.php?t=94950

Re: [SlimDevices: Plugins] TrackStat adding duplicate tracks on every rescan

2012-04-26 Thread erland
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