saymonz

Had the same issue. Solved it by setting the LANGUAGE var instead of LANG. `LANGUAGE=C yay` I tried setting LC_ALL first, as it should override every other settings [according to...

I can confirm 2.5.0 still won't match albums even when I just tagged them using Picard with a perfect match. Beets computes a match score around 93% and won't autotag....

Adding ``` match: distance_weights: data_source: 0.0 # Disable data source matching ``` To the config indeed makes the match 100% in the case I tested (an album already matched against...

I don't think it's really the issue, as it's seemingly triggering the penalty even with albums that were previously matched by beets or Picard, so they should match the data...

Heres the example I tried, without disabling the data_source mismatch penalty: ``` $ beet info -a album:="Jam Session" -i data_source,path /srv/sync/Audio/Musique/La Jam/1999 - Jam Session [ep] data_source: MusicBrainz $ beet...

Yeah, mistakenly thought beets was detecting already in-library items as it does some magic about that according to https://beets.readthedocs.io/en/stable/reference/cli.html#reimporting Doing ``beet import -L album:="Jam Session"`` indeed matched the album correctly,...

My guess is that this penalty should be discarded entirely on importing new items, makes no sense to mismatch void, and trigger only on re-import when data_source is indeed mismatching.

@talski I think you could get above the autotag threshold by disabling the data source mismatch penalty too, using the config snippet in https://github.com/beetbox/beets/issues/6096#issuecomment-3405913337

The ideal solution might be a "preferred data source" setting which would take a list of data sources in order of preference like the others "preferred" options (https://beets.readthedocs.io/en/stable/reference/config.html#preferred). Then, on...