Replies: 1 comment
-
|
It appears this specific issue was fixed in 2.3.0!
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Beets write does not persist MusicBrainz tags (mb_albumartistid, mb_artistid, albumtype) despite success logs
Environment
/Volumes/data/media/music/music_library/....flac/Volumes/data/media/music/music_library/main_library/Zedd/Clarity (Deluxe)/03 Spectrum.flacProblem
Running
beet writereports metadata changes (e.g.,mb_albumartistid) are being written, but the changes do not persist in the file.Picard confirms this, as the
mb_albumartistidtag is still missing.This happens repeatedly, even when invoking
writemultiple times on the same file.Logs from back-to-back
writeoperationsFile Timestamps
Screenshot from Picard
Attached below is a screenshot showing
mb_albumartistidis not present forSpectrum.flacdespite repeated writes:Config
Questions
beet writeactually writemb_albumartistidto FLACs?Any help debugging this is appreciated!
Further Confirmation with Another Album
Tried again with another album (
AFI - Decemberunderground) using the following command:(base) ➜ music_incoming beet -vv write | tee output_write.logThis was executed after prior
writeattempts on the same files. Output shows repeated writes of the same tags, indicating they are not sticking:Observation: These logs mirror the earlier behavior seen with
Zedd - Clarity (Deluxe)— multiple confirmedwriteoperations, withmb_albumartistidstill not showing up in tools like Picard after the fact.Permissions Verified
(base) ➜ music ls -lah '/Volumes/data/media/music/music_library/main_library/Zedd/Clarity (Deluxe)/' ... -rwx------@ 1 jessehorne staff 31M Aug 3 19:59 03 Spectrum.flacAll files are writable by the current user (
jessehorne) and have no permissions preventing writing. File timestamps also confirm they were touched, but expected tags are still not written.Summary of Behavior
This appears to be a general issue with certain MusicBrainz tags (e.g.
mb_albumartistid,mb_artistid) not being committed to disk, despite:beet writeclaiming successMultiple Tags Are Affected
This issue affects more than one tag. In both albums tested, several tags were reported as changed and written, but did not persist.
Tags Affected per Album
mb_albumartistidmb_artistid,mb_albumartistid,albumtypeDespite write events and updated file timestamps, these tags do not appear in tools like Picard and are flagged again on every subsequent
beet write.Final Summary
The issue appears to be systemic:
mb_albumartistid,mb_artistid,albumtype)Looking for help confirming whether:
Thanks again!
Beta Was this translation helpful? Give feedback.
All reactions