05-16-2022, 08:42 PM
@schliden
Welcome to the weird and wonderful world of music metadata, where there is no industry-wide agreement on what information elements should be captured, how they should be identified, and how they should be encoded.
Yes, the FLAC specification says metadata shall (only) be contained in a VORBIS_COMMENT block where each entry is in the form of FieldName=Data. In general, the case-insensitive FieldNames can be user-defined, although the VORBIS specification includes a proposed minimal list of FieldNames and their intended usage which includes "performer" so there has been general acceptance of the use of this name.
OTOH, the MP3 specification did not include a method of including metadata. The de facto ID3 specification(s) came later. In the ID3v2.3 approach, each entry is contained in a frame with a 4-character frame title/identifier. The spec includes a list of predefined 4-character identifiers and their intended usage; it also includes the catchall TXXX (user-defined) frame.
As you've discovered, there isn't universal agreement on how the predefined frames should be used. In the case of the concept of performer, I've seen the use of various TPEx frames, IPLS ("Involved People List") frame, and TXXX frame with Performer/Value pair. (Note that TIPL is an ID3v2.4 frame identifier and ID3v2.4 is not commonly used.)
I just checked the source code for MPD's decoding of tags and found that it maps the content of a TPE4 frame into performer in its library database.
Regards,
Kent
Welcome to the weird and wonderful world of music metadata, where there is no industry-wide agreement on what information elements should be captured, how they should be identified, and how they should be encoded.
Yes, the FLAC specification says metadata shall (only) be contained in a VORBIS_COMMENT block where each entry is in the form of FieldName=Data. In general, the case-insensitive FieldNames can be user-defined, although the VORBIS specification includes a proposed minimal list of FieldNames and their intended usage which includes "performer" so there has been general acceptance of the use of this name.
OTOH, the MP3 specification did not include a method of including metadata. The de facto ID3 specification(s) came later. In the ID3v2.3 approach, each entry is contained in a frame with a 4-character frame title/identifier. The spec includes a list of predefined 4-character identifiers and their intended usage; it also includes the catchall TXXX (user-defined) frame.
As you've discovered, there isn't universal agreement on how the predefined frames should be used. In the case of the concept of performer, I've seen the use of various TPEx frames, IPLS ("Involved People List") frame, and TXXX frame with Performer/Value pair. (Note that TIPL is an ID3v2.4 frame identifier and ID3v2.4 is not commonly used.)
I just checked the source code for MPD's decoding of tags and found that it maps the content of a TPE4 frame into performer in its library database.
Regards,
Kent
