Alex

Your files have ID3v1 tags, and `audiotags` assumes ID3v2. `id3` has [`v1v2::read_from_path`](https://docs.rs/id3/latest/id3/v1v2/fn.read_from_path.html) to handle both if you'd like to refactor `audiotags` to use that.

> Was or Is there a reason why somebody would want to read only v2 tag and not v1v2 behind abstraction `v1v2` is a relatively new module IIRC. Definitely wasn't...

> Is there possibility to lose any information in the conversion from v1 to v2 tags e.g. were any of the fields dropped and are there any incompatibility concerns otherwise...

I'd say privatize these [methods on `FlacTag`](https://docs.rs/audiotags/latest/audiotags/components/struct.FlacTag.html#impl-FlacTag-1) first and foremost. It is a little strange to only allow Vorbis Comments to get a custom key/value store. Goals: * Provide access...

No longer blocked, new MSRV is 1.85

Are you saying after parsing a tag you end up with both `©gen` and `gnre` atoms? That shouldn't happen, all `gnre` atoms should be upgraded. I do agree that the...

> But you can't tell the `©gen` tags apart if there are multiple of them I'm not sure what you mean, the atoms contain no additional metadata to separate them...

Ah, yeah that's a confusing situation. We can't really signal *which* genres have been converted. I've already added `ParseOptions::implicit_conversions` locally. I guess if a `©gen` is present, we can also...

I added Pl3xmap support a couple years ago. It ended up being removed somewhat recently cause they couldn't decide on an addon system and kept changing things, leaving it completely...

@milesegan I'll put out 0.21.0 today and pick this back up for 0.22.0. It is something I'd like to start working on again.