chroma: Fingerprint as backup to cheaper metadata matching

This issue was automatically migrated from Google Code.
Original author: dou...@gmail.com (August 25, 2012 18:22:29)
Original issue: google-code-export/beets#431

[puretokyo]

Is there a reason why fingerprinting shouldn't/couldn't be invoked as an optional choice (eg. [F]) on a per-album basis, rather than spanning an entire import? Is integrating the plugin in the future in this way going to be disruptive?

Use-case example: I attempt to import 30 albums, one of which has no tags and 'Track01.flac'-type filenames. When the Musicbrainz-based autotagger inevitably gives bad matches, instead of [S]kipping or [U]sing as is etc, I can [F]ingerprint that album.

[sampsyo]

Great idea—this ticket was originally about automatically doing that when no good matches are found, but manually enabling fingerprinting is an interesting option also.