anomie_[m] uploaded an image: (113KiB) < https://matrix.chatbrainz.org/_matrix/media/v3/download/chatbrainz.org/GdRBAUUVCywmHfSdgSxpuawN/Screenshot_20250527_074312_Edge.jpg >
2025-05-27 14724, 2025
anomie_[m]
Wut… there's no way that the publisher gave streaming services the same barcode that's used for their physical release that has an extra bonus CD, right? That would be so annoying. I guess I need to see if the barcode on the physical release is correct
2025-05-27 14743, 2025
anomie_[m]
There are definitely people selling a CD with that barcode, 4570192936709
2025-05-27 14700, 2025
anomie_[m]
I am so annoyed, I only expected this kind of carelessness with ISRCs
A straight search from titles extracted from filenames won't work well. So there are only two approaches:
2025-05-27 14709, 2025
outsidecontext[m
- Fingerprint lookup aka Scan. Should work, but will probably pull in some other compilations
2025-05-27 14709, 2025
outsidecontext[m
- Search for the release on MB, load it into Picard and drag the files over. Hopefully at least the track number gives some hint for helping match files automatically to the proper track. But your comment indicates it doesn't and needs to be matched one by one.
2025-05-27 14716, 2025
moviuro
can confirm #2 (import release, match one-by-one)
2025-05-27 14701, 2025
outsidecontext[m
Mmmh, yes, aliases actually would make sense to set. But won't help with Picard. Picard doesn't store the aliases in the loaded metadata and hence also doesn't make use of them when matching files to tracks.
2025-05-27 14744, 2025
outsidecontext[m
If you have the files in proper order on the left you can actually select them all and drop them on the first track of the release. Picard will in this case distribute the files to the tracks in order.
2025-05-27 14748, 2025
outsidecontext[m
As opposed to dropping on the release, which will make Picard try to guess the proper track based on metadata similarity
2025-05-27 14735, 2025
thuna` joined the channel
2025-05-27 14743, 2025
moviuro
I didn't find any way to just match on the duration (which is unique across the release)
2025-05-27 14755, 2025
outsidecontext[m
It does use the length also. But title similarity is weighted the highest. And if this is a total mismatch like here it fails. The fastest approach is likely the drag and drop of all files on the first track.
2025-05-27 14715, 2025
Appellate has quit
2025-05-27 14710, 2025
texke has quit
2025-05-27 14727, 2025
Appellate joined the channel
2025-05-27 14754, 2025
otisolsen70 has quit
2025-05-27 14727, 2025
anomie_[m]
Since this probably isn't the first time this has happened, Harmony ought to query only digital releases from MB in my opinion
2025-05-27 14757, 2025
anomie_[m]
Though that would have the consequences of excluding any "I don't know" mediums
2025-05-27 14709, 2025
anonn joined the channel
2025-05-27 14708, 2025
aerozol[m] has quit
2025-05-27 14715, 2025
thuna` has quit
2025-05-27 14738, 2025
tagomago has quit
2025-05-27 14755, 2025
aerozol[m] joined the channel
2025-05-27 14755, 2025
aerozol[m]
I think it's good that Harmony prompted you to double check the physical release. Then you can uncheck "MusicBrainz" at the top of Harmony and submit the release, to proceed
2025-05-27 14729, 2025
anonn has quit
2025-05-27 14721, 2025
prout has quit
2025-05-27 14730, 2025
prout joined the channel
2025-05-27 14703, 2025
anomie_[m]
True, but it's still annoying that it breaks other functionality
