More flexibility for extra slection choices

[winxi]

(11-09-2013 12:48)simoncn Wrote:  I don't think this is correct.

If the top-level container is a multidisc album and the recursive Browse request is marked as 2), MinimServer would return the complete list of tracks for the album because these are direct children of the top-level container. There is no need to return the disc containers as well, because these contain the same tracks as the top-level container.

If the top-level container is a single disc of a multidisc album, this means the container for the single disc was returned by a previous Browse request marked as 1) for the album. If the recursive Browse request for the single disc is marked as 2), MinimServer would return the complete list of tracks for the single disc because these are direct children of the disc container.

So in both these cases it is correct to mark the top-level recursive Browse request as 2).

I mainly use BubbleUPnP as the control point. With BubbleUPnP, it is possible to play/enqueue a whole container using its context menu. I consider such a selected container as the top-level container of a recursive search, but maybe it's the wrong terminology.

Let me give an example: when the current view is a whole multidisc album, there are all tracks visible and also '>> Disc n' containers. When now selecting one of the '>> Disc n' containers to be played via the context menu (long tap in BubbleUPnP), this '>> Disc n' container should be marked as 1), because otherwise MinimServer would return it empty.

So, my comment from before should be: When a single container is selected to be played recursively, it should be marked by the control point as 1) and all its sub-containers should be marked as 2).