Skip to content
Discussion options

You must be logged in to vote

There's no way to add custom fields without using the concrete formats like Id3v2Tag. ItemKey::Unknown was kind of a nuisance since it required Lofty to do extra validation when merging tags. With it gone, every ItemKey is now guaranteed to have well defined mappings.

It also pushes users away from resorting to custom fields unless absolutely necessary.

What I recommend instead is to make PRs for any ItemKeys that you may need. For example, release country is already a well defined field, it just doesn't have an ItemKey mapping yet: https://picard-docs.musicbrainz.org/en/appendices/tag_mapping.html#id30

As for TAGS, that'd probably be better suited for an ItemKey::Keywords (which also doe…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by UnknownSuperficialNight
Comment options

You must be logged in to vote
1 reply
@Serial-ATA
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants