Hello everybody,
First of all, please read this small topic for information : http://www.hydrogenaudio.org/forums/index....showtopic=61383
This being said, here are my thoughts :
STYLE
Basics:- the main "genre" should go into the GENRE-tagfield
- the tag-fieldname used for storing secondary music-styles is "STYLE"
- the tagfield may contain any kind of "keywords" do describe "what" the track sounds like.
- it should NOT contain info about the "mood" of a track("how" it sounds like)
- the styles should be seperated with a comma and space, like "post-rock, noise, electronica"
- If the file does not use ID3v2 tags, then you may also use multiple tagfields with identical name instead.
- this tagfield is trackspecific
Reasons for agreeing on this scheme:- simple
- allows backwards-compatibility while not ruling out multivalue-field capabilities of modern tagsystems
- easily readable
- easy to remember and type in manually
- name is consistent with other tagfields(ARTIST, ALBUM, GENRE, STYLE)
Code snippets:
// To display the styles of a track,
// simple put the following somewhere...
%style%
Adoption-Status: early-adoption stage- Already supported in some playlist-displays
- Adoption should be simple because of how easy it is to switch to it(low effort)
It seems the adoption of that proposed %style% standard hasn't been that simple, because since mar. 1, 2006, that adoption hasn't really gone a long way from the start (there isn't any official standard yet).
I don't know what the definitive standard will be, and I certainly am no one to decide on such a standard. However, if I had to propose or vote for something for that subgenre standard, it would certainly be %subgenre%
Advantages : all those of %style%, especially this one :
- name is consistent with other tagfields (ARTIST, ALBUM, GENRE, SUBGENRE)
(it is even more logical than style : after all, what could be more natural than genre / subgenre ?)
Disadvantages : none to my knowledge
Hope it helps, who knows.