Repository navigation
The intro detection fingerprints live on disk under /data/fingerprints, out of the database and its backups - #104
Merged
Merged
Conversation
…erprints, out of the database and its backups
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Chromaprint and pHash fingerprints that intro detection caches per media item made up most of every database backup, while being derived data that is computed again from the media files. They now live in
/data/fingerprints/{audio,phash}/<media_id>.fp, beside the other derived per-media stores.The two tables are left in place, empty. Dropping them belongs to a later release, once the move has run on existing installs.