scrub: Remove beets-supported tags as specified by user

[GoogleCodeExporter]

The users should be able to specify certain tags, that are to be spared from 
scrubbing. Maybe this could be specified in the configuration file:

[scrub]
keep: lyrics comment encodersettings
removeall: yes

where the "keep" values override the "removeall" option. In this example the 
file would be stripped of everything except the values defined in "keep:". If 
no keep values are defined, and "removeall" is set to yes, the new ID3v2 tag 
will contain no leftovers. If no options are set at all, the internal beets 
standard is going to be used.

Original issue reported on code.google.com by amselfelder on 25 Aug 2012 at 9:41

[GoogleCodeExporter]

Thanks! This is related to #189, in which a subset of MusicBrainz tags can be 
selected.

Original comment by adrian.sampson on 25 Aug 2012 at 4:33

• Changed title: scrub: Remove beets-supported tags as specified by user
• Changed state: Accepted
• Added labels: Type-Enhancement, Priority-Medium, Component-Plugins

[GoogleCodeExporter]

I believe the "zero" plugin accomplishes this use case. Let me know if this 
feature would still be useful in light of that.

Original comment by adrian.sampson on 21 Dec 2012 at 6:28

• Changed state: WontFix

[GoogleCodeExporter]

Can the "zero" plugin be configured in a way to keep certain fields instead of 
removing them?

Something to keep the encoder settings and remove or nullify everything else.

Original comment by amselfelder on 21 Dec 2012 at 8:20

[GoogleCodeExporter]

At the moment, the best solution is to type "beet fields", copy the list of 
field names, paste it into your config file under zero.fields, and remove those 
fields you want to keep. (We could also, of course, provide the inverse option 
to do this automatically.)

Original comment by adrian.sampson on 21 Dec 2012 at 9:02