The plugin uses attributes to find duplicates. However, you can configure it to use any field you like; see the keys option: http://docs.beets.io/en/v1.4.3/plugins/duplicates.html
For example, if you've already run fingerprinting on your music and have added the resulting MBIDs to your files, you can use those to identify duplicates. For what it's worth, that's the general workflow for finding out using acoustid whether two songs are the same: you generate an acoustic fingerprint for each; you ask the acoustid server for the MBID for each fingerprint; and then you check whether the MBIDs match. Comparing fingerprints directly is considerably more complicated—that's a task best relegated to the acoustid server. Adrian > On Mar 2, 2017, at 12:53 PM, Daniele Giglio <[email protected]> wrote: > > According to the manual 'beet dup' should find duplicates present in my > library, it's not clear if it only use tags or acoustic id too. By the way I > cannot make it work, I've imported a collection of file which contains at > least two duplicates (I've checked using Picard's fingerprint feature) but > beets doesn't returns anything. > > Any clue? > Thanks in advance. > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "beets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
