I was surprised to find that moving a saved configuration to a fresh install of mp3tag does not configure EVERYTHING in the new installation as it was in the source installation. One feature we never use (and don't like) are the default settings for tag mapping. We always try to make sure we delete those for the kind of work we do. The last thing I want to encounter is a problem caused by tags whose field names have been altered unexpectedly. We want WYSIWYG fieldname/value displays across the entire program.
A new installation of 2.70 received a configuration update from a "master" setup that doesn't include any mapping. Not knowing that I had to check the entire range of customized features lead us to almost apply an action item to nearly 70,000 files. Fortunately I tested it on several dozen files first and found the problem after some searching. Still, it was too close for comfort.
There are other specially configured settings as well that we wish to carry across touto a new installation intended to exactly match the master. Clearly this is not possible with extra and special attention.
So, the question is this: Which features are included in a saved configuration file and which ones are not? Is there an easy way to identify was ISN'T included in the cnfiguration file so that we can create a checklist to manually finish the installaiton of mp3tag.exe on a new machine or at another site?