Ah ... you are right, the issue is caused by duplicate MusicBrainz IDs.
This reveals the culprits:
Code:
--------------------
SELECT url,musicbrainz_id FROM tracks WHERE musicbrainz_id IN
(SELECT musicbrainz_id FROM tracks where musicbrainz_id IS NOT NULL
GROUP BY musicbrainz_id HAVING COUNT(*) > 1)
--------------------
However, while most of the duplicates in fact originate from the
semantics change in MusicBrainz NG (which was a bad idea IMHO, but
that's a different story), this is not the only reason where these
might come from. Some were simply mistagged (oops...) and should go
away now with the next scan, some originate from a single long track
being split into individual parts, each of which inherits the original
MBID, and some are legit duplicates, for example when there are
instances of the same track with different bit rates.
I tried adding a suffix to the MBID (like
"02252562-35b6-42c8-b61c-c504ed438761+1",
"02252562-35b6-42c8-b61c-c504ed438761+2"), but in this case SBS does
not even store the ID in the database at all, even though the column is
40 characters wide. So I take it that there is currently no solution,
other than removing the MusicBrainz IDs from the offending files?
--
usch
------------------------------------------------------------------------
usch's Profile: http://forums.slimdevices.com/member.php?userid=33389
View this thread: http://forums.slimdevices.com/showthread.php?t=58916
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
