I'm not sure how many other people have multiple file types in their music libraries. I have both Flac and mp3 files and increasingly, ogg vorbis as well. I'm finding the task of creating actions to tag the various files in the same way becoming more and more difficult as the number of file types and the number of my action groups increases.
This was an earlier discussion, with a failed attempt at addressing the problem:
While looking at the C:\Program Files\Mp3tag\help\main_tags.html help page for the current Mp3tag mappings, it occurred to me: Why have these mappings fixed and inflexible? What if users could define their own mappings?
- Keep Mp3tag's current tag mappings in a user-readable and modifiable text file. Load this file when Mp3tag starts up.
- Permit users to also have a custom tag mapping file (so that the default Mp3tag file doesn't have to be edited, just for safety sake). Load this file after the default mappings each time Mp3tag starts up. This way the default mappings may be overridden or new ones defined.
Tag mappings would be defined by tag type (id3v1, id3v2.3 etc) and/or by file extension.
- When an action, field or column references a defined tag, map it to the tag name defined. If an action references a tag that is not defined, don't translate it, just use it as-is wherever possible.
[.flac,.ogg] ALBUMSORT=Album Sort MYTAG=Some Tag [id3v2.4] ALBUMSORT=TSOA MYTAG=TXYZ
A file extension begins with a dot (.), while a tag type does not. The tag types would have to be predefined and limited to those recognized by Mp3tag. Recognition of both file extensions and tag names would be case-insensitive, but the tag written would maintain the capitization as listed in the definition.
This way, the actions themselves don't have to deal with all the intracies of dealing with different file types according to file extension or whatever. It makes it very simple for Mp3tag to add new tags, without having to hard-code them, plus users can add their own without needing to wait for a new release of Mp3tag.