Closed fortysix2ahead closed 2 years ago
Can you please include your configuration (as indicated in the issue template)?
The problem is most likely that the track in question is actually a video (on the disk, presumably the audio track was extracted when ripping?), see e.g. https://musicbrainz.org/release/127836f5-11dc-45d9-82b4-7f98c9c35f1e
Good catch! This seems to be issue! It's not a ripping thing, but the entry in MB is probably wrong. The 3CD release I have does not contain a video track. It's audio, but in MB it's marked as video. The same holds true for this: https://musicbrainz.org/release/141fa8ae-f345-4d99-97c0-84ae27b6138f Track #18 on CD 2 is the one that gives the problem an it is marked as video. Don't know if it's technically possible for a CD to have a video track in between audio tracks.
Good catch! This seems to be issue! It's not a ripping thing, but the entry in MB is probably wrong. The 3CD release I have does not contain a video track. It's audio, but in MB it's marked as video. The same holds true for this: https://musicbrainz.org/release/141fa8ae-f345-4d99-97c0-84ae27b6138f Track #18 on CD 2 is the one that gives the problem an it is marked as video. Don't know if it's technically possible for a CD to have a video track in between audio tracks.
I think multi-session (is that the correct term?) CDs are a thing, i.e. you can have both an audio session and a data session (with the video) on the same disc. I don't remember which one it was, but I've had (still have?) a CD like this. So maybe the MB entry is not even wrong, but it does not correspond to the one you own?
I'm going to close this, since it does not seem to be an issue with beets.
Over the last weeks it happened from time to time that single tracks or albums are not matched by the importer. The album is complete, all is fine on MB side, the importer detects the correct album, but does match one single track of the album, although it's there. Today it happened again and out of the blue I noticed when it happens. It happened to me only, when the album consists of (at least??) 3 CDs. Is that really a coincidence?
Debug output is below, but it does not contain any pointers to a possible bug.
Problem
Running this command in verbose (
-vv
) mode:The problem happened at least with these releases: https://musicbrainz.org/release/127836f5-11dc-45d9-82b4-7f98c9c35f1e https://musicbrainz.org/release/141fa8ae-f345-4d99-97c0-84ae27b6138f https://musicbrainz.org/release/d43fa3e1-ec7c-416c-91f5-c6728307cf1a
Setup