4 ms·
I'd like music metadata that is universally compatible across systems and across time (e.g., 50 years from now). Is there any such standard? Apple's Style Guide
by wolverine876 5y ago
I'd like music metadata that is universally compatible across systems and across time (e.g., 50 years from now). Is there any such standard? Apple's Style Guide is the most complete I've seen, which makes it useful - how closely does it match my needs?
In limited experience, just about the only standard metadata was album, track title, and artist (I forget the names of the exact fields). Not only do I want more, that works terribly for classical music where the artist could be the composer Wagner, the Chicago Symphony, conductor Solti, various soloists, etc.
- Semaphor 5y agoYou 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 agoI know about the ID3 format, but my understanding is that most fields aren't standardized.
- Semaphor 5y agoThere 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 agoSorry, 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 agoIt'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 agoI'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.
- kube-system 5y agoClassical isn’t really different. It’s just that we only listen to cover bands. :) Modern works are also often composed by someone different than the performers. The style guide listed describes fields for a separate composer(s) as well.
- wolverine876 5y agoIf the Chicago Symphony directed by George Solti plays Wagner, with Thomas Hampson as a soloist, who do you list in the artist field? How do I search for everything by one of those performers? > The style guide listed describes fields for a separate composer(s) as well. My impression is that only the artist or performer field (I forget the exact name) is reliably supported across music software; composer is not.
- kube-system 5y ago> who do you list in the artist field? All of them, according to section 11 of Apple's style guide. But yeah, most music library software sucks and was developed by people with a non-professional understanding of music, and thus is missing important information they don't know/care about, and/or contains bad assumptions about the cardinality of the data. ID3 was a hobby project that somehow became a defacto standard.
- dangravell 5y agoI don't agree with it all, but this is an interesting thought piece I recently came across: https://absolutelybaching.com/music-articles/the-axioms-of-classical-music-tagging/ https://absolutelybaching.com/music-articles/the-axioms-of-c...
- kube-system 5y ago[deleted]
- dangravell 5y agoAgree about different uses of metadata. But I don't really understand your point about butchering data and KV stores. It just seems to me the author is opinionated about (what they see as) the most important entity types to organise the library around.
- gerjomarty 5y agoThis is why I submitted today actually, I was looking around for a decent spec on how to tag my music collection and stumbled across this. If this could be adapted to ID3 or Vorbis comments, and also widely accepted by other players, it would be a dream.
- comprev 5y agoThere is such a thing - a digital metadata standard called DDEX [0]. I worked in streaming classical music for a while (engineering/ops) and we had 100,000s of large XML files to parse. They arrived with digital audio files and contained useful checksum data inside. All of the information regarding licensing, streaming rights, composer, movement, and almost every piece of data regarding a song/work was included. [0] https://ddex.net/ https://ddex.net/
- wolverine876 5y agoAwesome! Thank you! EDIT: Is there an established way to embed the metadata in the music file, rather than in a separate XML file?
- comprev 5y agoUnfortunately not that I'm aware of however the XML format has certainly helped normalise the metadata between distributors - alternative artist spelling is a good example. Numerous ways to spell Tchaikovsky!
- wolverine876 5y agoDo you know if the metadata is available via a free, open resource? For others, here are some very interesting looking links I just found: * https://kb.ddex.net/display/HBK/Technical+Description+of+RIN https://kb.ddex.net/display/HBK/Technical+Description+of+RIN Recording Information Notification (RIN) standard, used by DDEX. See the samples at the bottom for a good sense of it. * https://jaxsta.com/ https://jaxsta.com/ Jaxsta is said to aggregate DDEX metadata, but I'm not sure what exactly that means or if it's publicly available. * https://www.sound.credit/ https://www.sound.credit/ Sound Credit calls itself "The Next Generation of Credits, Liner Notes, and Album Art" and seems marketed toward industry, but uses the RIN standard (and DDEX metadata?). Someplace said the metadata was freely available, but I don't see it in a brief look.
- comprev 5y ago
- dangravell 5y agoOne thing to consider is what you really mean when you say music metadata, because you didn't mention where you want to use or store this metadata. Are you talking about released music, or simply information about the work? Publishing info? And so on. You might find the MusicBrainz style guidelines useful: https://musicbrainz.org/doc/Style https://musicbrainz.org/doc/Style WRT classical: https://musicbrainz.org/doc/Style/Classical https://musicbrainz.org/doc/Style/Classical
- wolverine876 5y agoThanks for the style guides. I want to store the metadata in the files; otherwise, over the years, it will become separated and lost. The data I want is about the music: performers, composer, etc. I would love to have the equivalent of liner notes, with details about producer, engineer, each musician, etc., but I fear that's not realistic (I have less info on my computer versions of the music than with the old analog versions.) My use: Playing the music, discovering new music, etc. E.g., 'who produced this song? What else in my collection have they produced?'