Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quality-based Trumping during import #341

Open
GoogleCodeExporter opened this issue Mar 12, 2015 · 5 comments
Open

Quality-based Trumping during import #341

GoogleCodeExporter opened this issue Mar 12, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants