New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always set year, month, and day tags on MediaFiles in that order #1303
Comments
That's odd! Can you please provide a sample file for testing? The bit about bitrate was recently fixed in 790c41a. |
If it makes any difference, my files already had musicbrainz ids and were imported as-is
then synced
then written
FLAC file here for a limited time: |
Hmm. Oddly, this works fine here:
As you can see, the second |
OK. I did a second 'write' instead of 'write -p' and then a subsequent '-p' only
So that's consistent with what you saw, but the file I gave you before was after my import/mbsync/write. |
OK, here's what I get with that:
So for some reason, all fields take effect on the first Can you please do a little more investigation along these lines? For example, what does the metaflac metadata look like in the first state vs. the intermediate state vs. the final state? Can you recreate the problem with a sequence of |
Initial state:
After import/mbsync/write
After second write:
|
One clue may be that it shows up in the standard output of the first write:
So the code that creates that output knows it should be written. |
Thanks for following up. I was able to track down the problem. The issue is that tags can't represent days without months in this format, and sometimes beets tries to apply the fields in the wrong order. That is, if a file has the year 1998 but no month, then the field contains the string We should probably enforce the order somehow, but I'm not entirely clear how. |
Fix #1303: process `DateItemField` tags in YMD order
Just curious if anyone has reported success with this fix. I'm noticing that many of my files are still trying to write the original day tag on every write attempt. I'm running 1.3.14. It's not all files. |
1.3.10
Immediately after 'write'
I check the FLAC files and see
Issue 1) original_day wasn't written.
IMO, 'write' should think the db and files are in sync immediately after a 'write'.
Issue 2) write thinks the bitrate doesn't match.
I'm not sure what FLAC data to look at in the file...
'update' apparently thinks things are in sync.
So 'update' doesn't care about original_day ??
The text was updated successfully, but these errors were encountered: