Andreas

There are some other tags that would be nice (especially some for audio books, which I'm highly interested in). [Here](https://docs.mp3tag.de/mapping/) is a huge list of the MP3Tag's mapping tables, which...

> First things first, don't forget these fields can already be written by the library, using Track.AdditionalFields I know, ATL is very flexible. I'm promoting your library everywhere I can...

> PS : Don't hesitate to use GitHub Discussions threads to ask about the code. I'll happily answer! Ok, here is a huge Post for discussion ;) #133

> Knowing that field is represented by an integer in the MP4 format, how would you handle having "2.1" as the input ? Turning it into 21 ? Truncating to...

> I chose for the MP4 writer to ignore non-integer values while logging a warning. I'm fine with that. > As you may expect, I don't intend to create non-standard...

> Available in today's v4.12 Awesome, thank you. > Any specific feature / pattern in mind ? No, I just have to remove the properties that are now in the...

> I guess I can manage to ignore what is inside AdditionalFields whenever the standard equivalent has a value. How about that ? So maybe I'll give you an example...

Cool to see that is regarded now. Maybe it would be nice to keep a possibility to force a save under specific circumstances. `mp4v2` has a tool `mp4tag` with a...

Thank you for taking a look. > Is there any spec or description about that ? Yes, [here](https://github.com/enzo1982/mp4v2/blob/cc17ffe84c08f26011e4a2867f6196e62c4258ee/doc/texi/tool/mp4file.texi). @enzo1982 took a huge effort create a documentation, see https://mp4v2.org ``` @item...

> => As far as retrocompatibilty goes, I'd rather make "force save" enabled by default and let people disable it when they want to focus on performance. Would you be...