(28-11-2015 07:42)simoncn Wrote: (28-11-2015 00:33)Pastim Wrote: I have a mainly Classical collection, with Works (or parts of large Works) identified with Groups.
I have set a Rating tag on many Movements (tracks) and this is also an Index tag (as are Works and Groups).
If I select Rating 90, I see xyz items (and other indices) that include Movements rated at 90, but also all the other Movements in the Works (Groups) to which those highly rated Movements belong.
Now one might think this is not an issue until one wants to play random Movements rated at 90. One CP (and maybe others) returns Movements from all the Groups listed under Rating 90, even though many of those Movements aren't rated at 90.
So, my question is why do the Groups listed at item level include tracks that don't match the current criteria? Shouldn't they just include those tracks matching the indices used to find them?
Or is there already an option available to do this?
The Group tag is treated differently from other tags. The complete group is treated as an "item" for browsing purposes, whch means you always see the complete contents of the group when browsing. The only way to browse to a track within a group is to browse to the complete group, open the group and then select an individual track.
Bother.
That means I can play 'Random Groups' but have no way to play 'Random Tracks' in a subset such as Rating (or Artist or whatever), since the Control Point can only randomise what it is served up.
I guess I'll have to investigate whether I can have 2 minimservers configured, one with the Group tag aliased to something else so as to avoid Groups completely. Or is there any other solution?