Multiple entries in playlist

[simoncn]

(24-03-2014 19:08)DavidHB Wrote:  I'm posting this as a general query, because I don't know whether or not it relates to expected behaviour, or whether the behaviour is a function of MinimServer or the control point (Bubble DS in my case).

The specific case is as follows. In my collection, I have two recordings of the Mendelssohn Third Symphony. If I browse through Genre, Composer, Composition to right-click on the entry for the symphony, and then select Play, I get a playlist in which each symphony appears multiple times. Ideally, of course, I want a playlist that references each recording only once.

Thanks to the useful feature in Bubble DS whereby the number of entries within a particular item is shown once that item has been accessed and the entries counted, it is easy to see what is going on. Below the entry for the symphony within Composition that are entries shown as 2 Albums, 2 items (the works are grouped), Artist, AlbumArtist, Date, All Artists, Conductor and Orchestra. If the playlist is created at the Composition level, playlist entries will be created for all these items, duplicating the entries (in this case) a total of sixteen times.

The problem can of course be avoided by refining the selection within the composition entry, but it would be nice not to have to drill down to the nth degree when all that its wanted is to play the available recording(s) of a particular work. Is it possible for MinimServer to refine the playlist selection sent to Bubble DS so that it does not contain duplicates? Or is this something I should expect the control point to do? If the entries are drawn from a list cached by the control point, there is clearly nothing that MinimServer can do to help.

Thanks in advance for any advice.

David

I have tried this and it seems that BubbleDS is doing an aggregated recursive UPnP Browse operation of the selection's complete subtree by sending a series of Browse requests and combining the results, without eliminating results that have duplicate resource information.

There is nothing that MinimServer can do to eliminate these duplicates, because there are no duplicates in the results that MinimServer sends for any individual Browse request. The duplicates arise because of the aggregated series of Browse requests issued by the control point.

There are two possible solutions:

1) The control point could do an aggregated recursive series of UPnP Browse requests and remove items with duplicate resource information from the aggregated list.

2) The control point could issue a single UPnP Search request instead of an aggregated recursive series of UPnP Browse requests. This would give MinimServer the opportunity to identify and eliminate duplicates in the result set. (I'm currently working on a change to MinimServer to ensure duplicates are removed from Search results.)