beets 1.2.1
This release introduces a major internal change in the way that similarity scores are handled. It means that the importer interface can now show you exactly why a match is assigned its score and that the autotagger gained a few new options that let you customize how matches are prioritized and recommended.
The refactoring work is due to the continued efforts of Tai Lee. The changes you'll notice while using the autotagger are:
- The top 3 distance penalties are now displayed on the release listing, and all album and track penalties are now displayed on the track changes list. This should make it clear exactly which metadata is contributing to a low similarity score.
- When displaying differences, the colorization has been made more consistent and helpful: red for an actual difference, yellow to indicate that a distance penalty is being applied, and light gray for no penalty (e.g., case changes) or disambiguation data.
There are also three new (or overhauled) configuration options that let you customize the way that matches are selected:
- The
ignored
setting lets you instruct the importer not to show you matches that have a certain penalty applied. - The
preferred
collection of settings specifies a sorted list of preferred countries and media types, or prioritizes releases closest to the original year for an album. - The
max_rec
settings can now be used for any distance penalty component. The recommendation will be downgraded if a non-zero penalty is being applied to the specified field.
And some little enhancements and bug fixes:
- Multi-disc directory names can now contain "disk" (in addition to "disc"). Thanks to John Hawthorn.
web
: Item and album counts are now exposed through the API for use with the Tomahawk resolver. Thanks to Uwe L. Korn.- Python 2.6 compatibility for the
beatport
plugin,missing
, andduplicates
. Thanks to Wesley Bitter and Pedro Silva. - Don't move the config file during a null migration. Thanks to Theofilos Intzoglou.
- Fix an occasional crash in the
beatport
when a length field was missing from the API response. Thanks to Timothy Appnel. scrub
: Handle and log I/O errors.lyrics
: The Google backend should now turn up more results. Thanks to Fabrice Laporte.random
: Fix compatibility with Python 2.6. Thanks to Matthias Drochner.