With mappings from two different source fields to one target field, you're essentially writing the same data back to those two different fields whenever you're performing a change.
With mappings
-
DATEtoYEARand -
TDRCtoYEAR
you're reading the data from the two different source fields, but also writing back any content of the YEAR field to those two mapped source fields.
Until v2.90e, I was dropping identical values for mapped fields, so that only one YEAR field was displayed in Mp3tag. This resulted in the bug report Identical multivalue tag won't be written if mapped
Now with v2.90e, I've made the following change
- FIX: multiple occurrences of a mapped field with identical values were displayed as one. (#11432)
so that on reading mapped fields which have the same value, I'm not dropping duplicates anymore. This also means, that a file with both TDRC and DATE filled with the same value, are now displayed as two YEAR fields. When writing back the change to the file, the two-valued YEAR field gets mapped to both TDRC and DATE which are then also multi-valued and so on.
It's clear that this is not optimal and will probably result in headaches for those affected by this behavior. I'm open for feedback. At the moment it seems to me, that the decision is living either with this issue or the referenced issue.