3 ms·
Classical 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 performe
by kube-system 5y ago
Classical 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.