Post Reply 
Streamlining the browsing tree & multiple configs
17-09-2013, 12:42 (This post was last modified: 17-09-2013 14:50 by haggis999.)
Post: #3
RE: Streamlining the browsing tree & multiple configs
(17-09-2013 10:44)simoncn Wrote:  At present, Genre is just an index tag and has no other special significance. I would be reluctant to add special treatment for this specific index tag. It might be possible to extend browsing paths to do what you want by adding the ability to define a browsing path for 'Genre=Classical/Composer/Work' or something along these lines. Can you say more about the differences you have in mind?

To use your terminology, I only see the requirement for two 'browsing paths' to meet my needs, one for classical music and one for non-classical. Since the distinction between classical and non-classical logically belongs in the Genre tag, that would seem to be the appropriate trigger for automatically selecting the correct browsing path.

When I want to play classical music, I want to make my selection as follows:

Composer > Work > Artist (but only if multiple recordings exist) > Full track listing of work

When I want to play non-classical music, my preferred selection process would be:

Artist > Album > Full track listing of album

David
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Streamlining the browsing tree & multiple configs - haggis999 - 17-09-2013 12:42

Forum Jump:


User(s) browsing this thread: 1 Guest(s)