Post Reply 
Streamlining the browsing tree & multiple configs
17-09-2013, 17:15 (This post was last modified: 17-09-2013 17:16 by simoncn.)
Post: #4
RE: Streamlining the browsing tree & multiple configs
(17-09-2013 12:42)haggis999 Wrote:  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

I'm not sure whether it will be possible to open the full track listing automatically. This is because of issues with how to do this within the constraints of the UPnP browsing protocol. I'll look into this if and when I implement browsing paths. At the moment, I can't give any time estimate for when this might happen.
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 - simoncn - 17-09-2013 17:15

Forum Jump:


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