Closed akyag closed 4 years ago
Hmm; that's tricky! It's hard to tell exactly what's going on here… there's a chance it could be a numerical precision thing, in the vein of #3507?
Is there any chance this goes away if you do a beet write
on just those files?
Yup this went away after I did beet write
on all the songs listed. I will keep an eye if this happens again for any new songs I import.
OK, cool. If it does crop up again, maybe the thing to do would be to inspect the tags and database contents directly to see why beets thinks they're out of sync.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Problem
Running this command in verbose (
-vv
) mode: I ran it without -vv because the output was too long. I will post it if its neededLed to this problem:
Above mentioned changes happen at every instance + any songs were actually changed. Is this the normal behavior?
Setup
My configuration (output of
beet config
) is: