+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: Hide Contents (/showthread.php?tid=1761)
Hide Contents - winxi - 31-08-2014 20:31
Hi, some time ago there has already been quite some discussion about the 'Hide Contents' browsing step which is necessary to avoid duplicated items in the playlist.
The recent version of the BubbleUPnP control point features a 'Remove duplicated items' setting. I think it would be reasonable to omit the Hide Contents step when the control point takes care for duplicated items. Is there still hope for a MinimServer setting to switch off the 'Hide Contents' step?
RE: Hide Contents - simoncn - 31-08-2014 21:17
(31-08-2014 20:31)winxi Wrote: Hi, some time ago there has already been quite some discussion about the 'Hide Contents' browsing step which is necessary to avoid duplicated items in the playlist.
The recent version of the BubbleUPnP control point features a 'Remove duplicated items' setting. I think it would be reasonable to omit the Hide Contents step when the control point takes care for duplicated items. Is there still hope for a MinimServer setting to switch off the 'Hide Contents' step?
I have experimented with this and the results were not successful.
1) ">> Complete Album" can't be removed because this provides additional items, not duplicated items.
2) ">> Tag View" shouldn't be removed because this opens up a complete duplicate hierarchy for every folder (recursively). This would greatly increase the amount of data sent to the control point.
3) It seems that ">> Disc n" could be removed but after many hours of trying different ways to do this I couldn't come up with a new scheme that felt right to me in terms of user experience.
4) This leaves ">> Show All". I think this could be removed but it didn't seem worth trying to do this given that the other three "Hide" menus would still be in place.
RE: Hide Contents - winxi - 31-08-2014 21:51
(31-08-2014 21:17)simoncn Wrote: I have experimented with this and the results were not successful.
1) ">> Complete Album" can't be removed because this provides additional items, not duplicated items.
2) ">> Tag View" shouldn't be removed because this opens up a complete duplicate hierarchy for every folder (recursively). This would greatly increase the amount of data sent to the control point.
3) It seems that ">> Disc n" could be removed but after many hours of trying different ways to do this I couldn't come up with a new scheme that felt right to me in terms of user experience.
4) This leaves ">> Show All". I think this could be removed but it didn't seem worth trying to do this given that the other three "Hide" menus would still be in place.
Thanks for this response, I already thought that it wouldn't be as easy as it may sound. I presume that we are talking about removing just the Hide Contents browsing step for 1) to 4), not about removing the special slecetion choices themselves.
1) This seems to be the an obvious exception when a >> selection choice not only contains duplicated items but also additional items.
2) I can't think of a situation when a user wants to recursively add such a lot items to a playlist that the increased amount of data transferred to the control point becomes problematic.
3) I'm not sure what kind of new scheme you mean, given that it is intended to just remove the intermediate Hide Contents step.
RE: Hide Contents - simoncn - 31-08-2014 22:39
(31-08-2014 21:51)winxi Wrote: 2) I can't think of a situation when a user wants to recursively add such a lot items to a playlist that the increased amount of data transferred to the control point becomes problematic.
The problem is that when the tag view hierarchy is brought in, this exposes all the intelligent browsing paths and this results in a combinatorial explosion of duplicates accessed via different paths.
Quote:3) I'm not sure what kind of new scheme you mean, given that it is intended to just remove the intermediate Hide Contents step.
Yes, that's what I thought before I tried to implement it.
For example, if the disc is sent to the control point as a UPnP musicAlbum container, the control point will show it within the album set as if it were an album named ">> Disc 2" (with album art), which looks completely wrong. If you click on ">> Disc 2", you'll get something that looks like an album (but isn't) and its title will be shown as ">> Disc 2". Also, the tracks within this container will have an XML album value of the top-level album set, which doesn't match their UPnP album container (the disc).
If the disc is sent to the control point as an item list UPnP generic container instead, the tracks within it won't be grouped nicely, won't be sorted correctly and won't be displayed with track numbers.
RE: Hide Contents - winxi - 01-09-2014 08:11
(31-08-2014 22:39)simoncn Wrote: Yes, that's what I thought before I tried to implement it.
For example, if the disc is sent to the control point as a UPnP musicAlbum container, the control point will show it within the album set as if it were an album named ">> Disc 2" (with album art), which looks completely wrong. If you click on ">> Disc 2", you'll get something that looks like an album (but isn't) and its title will be shown as ">> Disc 2". Also, the tracks within this container will have an XML album value of the top-level album set, which doesn't match their UPnP album container (the disc).
If the disc is sent to the control point as an item list UPnP generic container instead, the tracks within it won't be grouped nicely, won't be sorted correctly and won't be displayed with track numbers.
I see, many thanks for the clarification!