Bug Description
In beets v2.6.0 and v2.6.1, when importing albums detected as Various Artists, the MusicBrainz plugin is never invoked, resulting in immediate "No matching release found" with zero candidates evaluated.
Environment
- beets version: 2.6.1 (also affects 2.6.0)
- Working version: 2.5.1
- Python version: 3.12
- Installation method: Docker (linuxserver/beets:nightly)
Steps to Reproduce
-
Import an album that triggers Various Artists detection:
beet import "/downloads/new/Summer Walker/Over It (Complete Set Video Version)/"
-
Observe the output:
Album might be VA: True
chroma: acoustid album candidates: 0
Evaluating 0 candidates. (immediate, no MusicBrainz search)
No matching release found for 19 tracks.
Expected vs Actual Behavior
v2.5.1 (Working):
Album might be VA: True
chroma: acoustid album candidates: 0
musicbrainz: Searching for MusicBrainz releases with: {'release': 'over it...', 'alias': 'over it...', 'tracks': '19', 'arid': '89ad4ac3-...'}
musicbrainz: Requesting MusicBrainz release e6076fa2-...
Evaluating 2 candidates.
v2.6.1 (Broken):
Album might be VA: True
chroma: acoustid album candidates: 0
Evaluating 0 candidates.
No matching release found for 19 tracks.
Critical difference: No musicbrainz: log lines appear - the plugin is never invoked.
Regression Range
- Working: v2.5.1
- Broken: v2.6.0 and v2.6.1
Likely Cause
The refactoring of the MusicBrainz plugin in v2.6.0 (replacing python-musicbrainzngs with custom MusicBrainzAPI class) appears to have broken the plugin invocation path when va_likely=True.
Workaround
Stay on v2.5.1 or manually search using MusicBrainz ID (option I during import).
Bug Description
In beets v2.6.0 and v2.6.1, when importing albums detected as Various Artists, the MusicBrainz plugin is never invoked, resulting in immediate "No matching release found" with zero candidates evaluated.
Environment
Steps to Reproduce
Import an album that triggers Various Artists detection:
beet import "/downloads/new/Summer Walker/Over It (Complete Set Video Version)/"Observe the output:
Album might be VA: Truechroma: acoustid album candidates: 0Evaluating 0 candidates.(immediate, no MusicBrainz search)No matching release found for 19 tracks.Expected vs Actual Behavior
v2.5.1 (Working):
v2.6.1 (Broken):
Critical difference: No
musicbrainz:log lines appear - the plugin is never invoked.Regression Range
Likely Cause
The refactoring of the MusicBrainz plugin in v2.6.0 (replacing python-musicbrainzngs with custom MusicBrainzAPI class) appears to have broken the plugin invocation path when va_likely=True.
Workaround
Stay on v2.5.1 or manually search using MusicBrainz ID (option I during import).