You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found a bug within the chroma plugin which can cause the recordings returned by an acoustid lookup to be suggested with an incorrect distance when those recording have been merged.
However, when importing the music file using beets, the recording 79d185cc-8453-4020-85f3-0c53d4a2ebd1 might not be the best candidate. This is because of the variable recording_ids in the track_distance function of the chroma plugin does not contain the id 79d185cc-8453-4020-85f3-0c53d4a2ebd1.
deftrack_distance(self, item, info):
dist=hooks.Distance()
ifitem.pathnotin_matchesornotinfo.track_id:
# Match failed or no track ID.returndistrecording_ids, _=_matches[item.path]
dist.add_expr("track_id", info.track_idnotinrecording_ids)
returndist
$ beet import -s song.mp3
/media/.../song.mp3
Match (95.8%):
Phantom Planet - California (Tchad Blake mix)
≠ title
MusicBrainz, Index None, Track None,
https://musicbrainz.org/recording/79d185cc-8453-4020-85f3-0c53d4a2ebd1
* Artist: Phantom Planet
≠ Title: California -> California (Tchad Blake mix)
➜ [A]pply, More candidates, Skip, Use as-is, Enter search, enter Id, aBort
Setup
OS: Ubuntu 24.04.1 LTS
Python version: 3.12.3
beets version: 2.2.0
Turning off other plugins made problem go away (yes/no): no
Problem
I've found a bug within the chroma plugin which can cause the recordings returned by an acoustid lookup to be suggested with an incorrect distance when those recording have been merged.
For example, the fingerprint AQADtJmYJYsSKQry5... of this music file results in an acoustid response:
Both recordings have been merged into the recording with the id 79d185cc-8453-4020-85f3-0c53d4a2ebd1.
However, when importing the music file using beets, the recording 79d185cc-8453-4020-85f3-0c53d4a2ebd1 might not be the best candidate. This is because of the variable
recording_ids
in thetrack_distance
function of the chroma plugin does not contain the id79d185cc-8453-4020-85f3-0c53d4a2ebd1
.Step to reproduce
The import of the music file from above with the chroma plugin enabled does not confidently suggest the recording 79d185cc-8453-4020-85f3-0c53d4a2ebd1.
Proposed solution
This commit seems to fix the issue.
Setup
My configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: