Classical music best practices with v17 and futur v18
#5
I "bit the bullet" and adopted Musicbrainz style for classical.  The drawbacks I've seen are

1.  A certain amount of redundancy
2.  Long "song" titles which are difficult to display in skins
3.  Difficulty in providing a grouping / sorting by "work".

Some more minor difficulty in dealing with alias names.

I find "performer" tag better than eg ensemble, as it allows a more descriptive role.  But it would be nice if there were an ability to group roles in a hierarchy -- I have performers with role of soprano, soprano I, soprano II which I would like to be able to group together.  I also have a problem where a performer role is portraying a person (eg in opera).

scott s.
.
maintainer of skin  Aeon MQ5 mods for post-Gotham Kodi releases:
Matrix see: Aeon MQ5 Mod Martix release thread
Leia see: Aeon MQ5 Mod Leia release thread
Reply


Messages In This Thread
RE: Classical music best practices with v17 and futur v18 - by scott967 - 2018-08-22, 00:07


Logout Mark Read Team Forum Stats Members Help
Classical music best practices with v17 and futur v181
This forum uses Lukasz Tkacz MyBB addons.