I was using the save & load configuration feature a while back & I remember having some discrepancies with newly added custom values to fields.
Ex:
Configuration 1
title
genre
sub genre
Configuration 2
title
genre
style
Mood
I felt like if I added any custom values to genre while in configuration 1 & theswitched d to configuration 2 those custom values I added were not available in configuration 2 even though the field is the same. For that reason i think i just jept one large configuration instead of swapping back & forth.
Can anyone confirm this behavior? It may very well be an issue only on my end or i'm mistaken (this was months ago now) its very possible that I am in error
It looks to me like comparing apples and pears:
Configuration 1 has 3 fields
Configuration 2 has 4 fields
only 2 of the 5 are the same.
Also, it is not clear to me whether the names of the columns are the headings or the field names and which fields are referenced.
So right now I don't know what I should do to reproduce an alleged problem.
So configuration 1 & two are the save files & the bulleted items are fields. The title & genre fields in this example should be the same field as there is only one title & genre field for me
To make a new configuration i iust unchecked / checked certain fields so that more or less of them would appear in my tag pannel at any given time.
I usually add new values to fields using the shift + enter keyboard shortcut
Are we talking about the tag panel (which has no columns) or the file list (which has columns)
For further analysis, screenshots of the respective element definition would be nice.
Also, as you say that this happend a couple of months ago, it would help if you could check in your environment whether the problem is still there.
So what I did before was select the fields I wanted to see using the check box.
Then I'd save that selection as a new configuration.
I'd alter the selection & save another configuration.
In the event that both configurations included the same Field If I add custom values to that field they are only available on one configuration & not the other even though the field is the same.
I wasn't sure if I was misunderstanding how configurations worked so I just opted not to use them at the time
EDIT**
I've just tried this and it seems MP3TAG "normalizes" everything so switching to another configuration removes the recently added custom fields & if you switch back they are also removed from the original configuration you started with