by New new wave » Sat Apr 22, 2017 9:35 pm
The feature I wish MM actually had is being able to define dependencies between specific genres like in MB.
The two most important relations between genres are being derivatives and influences.
The "derivative" relation indicates the parent/origin of a genre, while an "influence" refers to secondary influences and fusions from other musical styles that are not necessarily related to its stylistic origin.
The reason I think it is important to let the user define these relations between genres is because it helps to organize a library, query auto-playlists, and results in a more consistent and clean tagging for the genre field.
The actual utility of this feature is that it lets you render songs with a very specific genre in other queries that look for their actual stylistic origins and broader genres instead of their exact specific genre.
It helps a lot when you have like 250 different genres as a result of carefully tagging each song in your library accurately for the exact micro-sub-genre it really belongs to at the deepest level.
Typical examples include: "Rock → punk → new wave → dark wave → ethereal wave"
Say I have a playlist that looks up for "new wave" songs, and since "ethereal wave" is a derivative of a derivative of "new wave", it should look up for that song as well, although the genre "new wave" was not mentioned in its "genre" field and nor "dark wave", but only "ethereal wave".
In this case, the value "ethereal wave" should be equivalent to "Rock; punk; new wave; dark wave; ethereal wave" when looking up for genres. It leaves the genre field way shorter, clearer and maintainable.
And it becomes even more useful when it relates influences and fusions, there are fusions almost between every two major genres, and especially in electronic and rock genres. For example, the results of "crossover thrash" should be relevant equally for both "thrash metal" and "hardcore punk", Although thrash would rather be derived from something else like NWOBHM in the chronological sense of hierarchical dependency and origin, and having to mention both of them in every actual "crossover" song would just make the "crossover" label completely redundant to specify the fusion.
Why is having to describe every time repetitively like 5-6 stylistic origins in each song, is more elegant than just binding the relations between those genres once and for all? It would be way more consistent, every "symphonic black metal" entry is also a "rock" entry at the end of the day, but mentioning both in each entry feels wrong to me, just think of it... and put on a note that MusicBee actually already offers this exact feature, why is MM still behind with that?
The feature I wish MM actually had is being able to define dependencies between specific genres like in MB.
The two most important relations between genres are being derivatives and influences.
The "derivative" relation indicates the parent/origin of a genre, while an "influence" refers to secondary influences and fusions from other musical styles that are not necessarily related to its stylistic origin.
The reason I think it is important to let the user define these relations between genres is because it helps to organize a library, query auto-playlists, and results in a more consistent and clean tagging for the genre field.
The actual utility of this feature is that it lets you render songs with a very specific genre in other queries that look for their actual stylistic origins and broader genres instead of their exact specific genre.
It helps a lot when you have like 250 different genres as a result of carefully tagging each song in your library accurately for the exact micro-sub-genre it really belongs to at the deepest level.
Typical examples include: "Rock → punk → new wave → dark wave → ethereal wave"
Say I have a playlist that looks up for "new wave" songs, and since "ethereal wave" is a derivative of a derivative of "new wave", it should look up for that song as well, although the genre "new wave" was not mentioned in its "genre" field and nor "dark wave", but only "ethereal wave".
In this case, the value "[i]ethereal wave[/i]" should be equivalent to "[i]Rock; punk; new wave; dark wave; ethereal wave[/i]" when looking up for genres. [b]It leaves the genre field way shorter, clearer and maintainable.[/b]
And it becomes even more useful when it relates influences and fusions, there are fusions almost between every two major genres, and especially in electronic and rock genres. For example, the results of "crossover thrash" should be relevant equally for both "thrash metal" and "hardcore punk", Although thrash would rather be derived from something else like NWOBHM in the chronological sense of hierarchical dependency and origin, and having to mention both of them in every actual "crossover" song would just make the "crossover" label completely redundant to specify the fusion.
Why is having to describe every time repetitively like 5-6 stylistic origins in each song, is more elegant than just binding the relations between those genres once and for all? It would be way more consistent, every "symphonic black metal" entry is also a "rock" entry at the end of the day, but mentioning both in each entry feels wrong to me, just think of it... and put on a note that MusicBee actually already offers this exact feature, why is MM still behind with that?
