It could be possible to uncheck the 'Store in file tag' box in the definition of each fields (Options/Starup Settings) like Replay gain, BPM, etc.. but unfortunately this is not possible for default fields.
In any case those 4 values stored in the tags are totally harmless. They don't modify the musical data in any way.
Could not find the "store in file tag' box
i also wanted to be able to do this for ratings as well, as well as most of the other fields , bios, comments etc.
My ideas to prevent MC from tagging files range from.
- making the directories/files read only so the files are untouched. IS it true if MC cant save to the files it saves to teh library itself. Would this work at all ?
- Tools->Plugin manager->Input->MP3 plugin->Configure
there are 2 items there for iD3v1 & ID3v2,
Dont save ( ignore existing).....what does this mean, will it leave the orginal as is ...itsnot very clear to me somehow ?
The idea of not saving anything to the files it self , is to use MC as an abstraction layer over the files. I wanted to see to what extent usability of MC depends on writing to files.
i wanted to play around with this, so when i recommended MC to others, it did not modify anything at all in their collection, and saved everythgin to the library.
once people got more comfortable with MC, they could use the library to populate the files. Though i wonder wheter that is even necesaary at all. Is it possible to use just the library, making all tagging changes in the library leaving the files untouched.
What benefits are there to tagging the files, instead of relying on the library to use MC leaving the files as is ?