Issue with duplicates when creating playlist

[eseb63]

Hello,
I encountered this issue for the Albeniz 2CD album from Ricardo Requejo, tagged like this:

• Suite espagnole Op 47 : 6 tracks with WORK tag
• Iberia suite B. 47 : 12 tracks (4 books of 3 tracks)
  - each Iberia track has a OVERALL_WORK tag "Iberia B.47"
  - each Iberia track has a GROUP tag according to his Book
• Chants d'Espagne op 232 : 5 tracks with WORK tag
  

DiscSubtitle tag (CD1 , CD2) for each track

• Iberia Books I & II on CD1
• Iberia Books III & IV on CD2
  

MinimServer settings:

• itemTags : Overall_Work
• indexTags : Work
• tagValue : Group.Default={Work}, Work.Merge={Overall_Work}
  

Browsing : Composer > Work (on Windows Kinsky)
as expected, i see 3 works:

• Suite espagnole Op 47 (one group)
• Iberia suite B. 47 (4 groups)
• Chants d'Espagne op 232 (one group)
  

When right clicking one of these works and choosing "play later", a playlist is created but this playlist duplicates 7 times (7x6=42 for Suite espagnole, 7x12=84 for Iberia, 7x5=35 for Chants d'Espagne)

I did test with a Carmen album, having the same structure : i get also a playlist with duplication (7 times)
I noticed the same behavior with Windows Kazoo or Linn App.
unlike Kinsky, Kazoo shows groups and detail so it duplicates Book I to IV with 3 tracks for each. Book I and IV have sometimes the 3 tracks duplicated.

It sounds like a bug...


Edit : i ripped 2 other albeniz albums from Alicia de Larrocha, containing the same works : so each work is now referenced in 2 albums.

with same browsing, i get now for the created playlists :

• Suite espagnole Op 47 : 392 (=56x7) items instead of 6 (Requejo) + 8 (Larrocha) = 14
• Iberia suite B. 47 : 672 (=56x12) items instead of 12 (Requejo) + 12 (Larrocha) = 24
• Chants d'Espagne op 232 : 224 (=56x4) items instead of 5 (Requejo) +3 (Larrocha) = 8
  

I join a copy of these albums (with 1 second extracts) and a copy of my profile to help you reproduce the issue.

[simoncn]

This is happening because you are adding the album from the contents of the Work index entry. Kinsky is browsing the subtree under the index entry you have added and is treating each browsing path as a separate file to be played.

For example, for the work "Suite española pour Piano No 1 B. 7 Op. 47 (1886)" these browsing paths are as follows:

2 albums > Albéniz - Iberia [Requejo] > Isaac Albéniz (1860-1909) : Suite española pour Piano No 1 B. 7 Op. 47 (1886)

2 albums > Música Española - Música Para Piano II [Larrocha] > Isaac Albéniz (1860-1909) : Suite española pour Piano No 1 B. 7 Op. 47 (1886)

2 articles > Isaac Albéniz (1860-1909) : Suite española pour Piano No 1 B. 7 Op. 47 (1886)

2 articles > Isaac Albéniz (1860-1909) : Suite española pour Piano No 1 B. 7 Op. 47 (1886)

Artiste > Larrocha, Alicia de [Piano] > Isaac Albéniz (1860-1909) : Suite española pour Piano No 1 B. 7 Op. 47 (1886)

Artiste > Requejo, Ricardo [Piano] > Isaac Albéniz (1860-1909) : Suite española pour Piano No 1 B. 7 Op. 47 (1886)

Pianist > Requejo, Ricardo > Isaac Albéniz (1860-1909) : Suite española pour Piano No 1 B. 7 Op. 47 (1886)

Pianist > [Inconnu] > Isaac Albéniz (1860-1909) : Suite española pour Piano No 1 B. 7 Op. 47 (1886)

Kinsky follows all these browsing paths and and adds all files from all paths to the playlist. Most UPnP control points do the same thing. MinimServer can't do anything to prevent the control point from doing this. Some control points (for example, BubbleUPnP) are able to detect and remove duplicates.

This control point behaviour dates back to the early days of UPnP where each file appeared only once in the browsing hierarchy with a unique browsing path to the file. MinimServer allows a file to be found using multiple browsing paths, which can result in this problem.

The solution is to always use a selection underneath the "n albums" or "n articles" indexes to add files to the playlist. If you do this, there will be no duplicates.

[eseb63]

thanks for this explanation.