You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a duplicate (i.e. same musicbrainz id) release is detected during an
import, break ties based on the quality of the two candidates. Losers should
either be marked as trumped or deleted per a configuration setting.
. Track-complete releases should trump incomplete releases.
. Releases whose tracks all use the same codec should trump those whose are
mixed.
. Releases of a matching codec but a higher bit rate should trump those of a
lower bit rate.
. Releases in a lossless format should trump lossy ones.
. Releases with a cue file should trump those without.
. Releases with a log file should trump those without.
Cue files, log files, and any checksum files or other rip-specific files should
be trumped when their associated audio files are trumped.
Image files from the two releases should be compared to each other and
lower-resolution duplicates should be marked as trumped or deleted per a
configuration setting.
All non-duplicate images and other files should be retained in case a
poorer-quality release has more and/or better images.
n.b. http://aatiis.me/2010/08/12/fast-image-comparison-with-python.html
Original issue reported on code.google.com by [email protected] on 16 Feb 2012 at 1:16
Original issue reported on code.google.com by
[email protected]
on 16 Feb 2012 at 1:16The text was updated successfully, but these errors were encountered: