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

chroma: Fingerprint as backup to cheaper metadata matching #173

ghost opened this issue Feb 28, 2013 · 2 comments


Copy link

@ghost ghost commented Feb 28, 2013

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


This comment has been minimized.

Copy link

@puretokyo puretokyo commented Oct 17, 2013

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.


This comment has been minimized.

Copy link

@sampsyo sampsyo commented Oct 17, 2013

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.