11 ms·

You want ID3 tags [0], there is a composer and many more fields. They are supported by pretty much any media player. The only problem is that, as far as I know,

You want ID3 tags [0], there is a composer and many more fields. They are supported by pretty much any media player. The only problem is that, as far as I know, there is no standard for multiple entries for a field (like artist) and delimiters might be different across software. [0]: https://en.wikipedia.org/wiki/ID3 https://en.wikipedia.org/wiki/ID3

wolverine876 5y ago
I know about the ID3 format, but my understanding is that most fields aren't standardized.
- Semaphor 5y ago
  There is a list of standardized fields, it’s pretty comprehensive [0], or you could look through the spec [1] which has additional comments. [0]: https://en.wikipedia.org/wiki/ID3#ID3v2_frame_specification https://en.wikipedia.org/wiki/ID3#ID3v2_frame_specification [1]: https://id3.org/id3v2.4.0-frames https://id3.org/id3v2.4.0-frames
  - wolverine876 5y ago
    Sorry, that was a poor choice of wording: I know about the spec; I mean that I understood that few fields are supported universally by music software (i.e., as usual, different people implement different parts of the spec).
  - Hamuko 5y ago
    It's been a hot minute but from what I remember about IDv3, the spec is really only like half of the story. Different media players and organisers have pretty different ideas on how the fields should work and which fields are actually relevant, so you really need to just look at how all of these different mainstream programs handle their data if you want to get your own IDv3 implementation working properly. Then there's the frame names. Due to how all of these various ID3v2 implementations do their frames, the names in the spec don't really reflect their real-world names. "TPE2" is specified to be the "Band/Orchestra/Accompaniment" frame in the spec, but in the real world it's actually the "Album artist" frame. And while TIT2 is very much universal, I think TIT1 was much more questionable and different implementations have different ideas on what TIT1 should be.
dangravell 5y ago
I'm not really sure I'd recommend ID3. It's the worst of both worlds: constrained by the limitations of the de facto storage mechanisms and overly prescribed and frankly ignored by a lot of software, bar the main fields.

wolverine876 5y ago

I know about the ID3 format, but my understanding is that most fields aren't standardized.

Semaphor 5y ago
There is a list of standardized fields, it’s pretty comprehensive [0], or you could look through the spec [1] which has additional comments. [0]: https://en.wikipedia.org/wiki/ID3#ID3v2_frame_specification https://en.wikipedia.org/wiki/ID3#ID3v2_frame_specification [1]: https://id3.org/id3v2.4.0-frames https://id3.org/id3v2.4.0-frames
- wolverine876 5y ago
  Sorry, that was a poor choice of wording: I know about the spec; I mean that I understood that few fields are supported universally by music software (i.e., as usual, different people implement different parts of the spec).
- Hamuko 5y ago
  It's been a hot minute but from what I remember about IDv3, the spec is really only like half of the story. Different media players and organisers have pretty different ideas on how the fields should work and which fields are actually relevant, so you really need to just look at how all of these different mainstream programs handle their data if you want to get your own IDv3 implementation working properly. Then there's the frame names. Due to how all of these various ID3v2 implementations do their frames, the names in the spec don't really reflect their real-world names. "TPE2" is specified to be the "Band/Orchestra/Accompaniment" frame in the spec, but in the real world it's actually the "Album artist" frame. And while TIT2 is very much universal, I think TIT1 was much more questionable and different implementations have different ideas on what TIT1 should be.

dangravell 5y ago

I'm not really sure I'd recommend ID3. It's the worst of both worlds: constrained by the limitations of the de facto storage mechanisms and overly prescribed and frankly ignored by a lot of software, bar the main fields.