Multiple composition tags

[DavidHB]

(14-01-2014 08:56)simoncn Wrote:  Thanks for this more detailed explanation. This is happening because MinimServer treats the entire group as a single item when browsing and searching, and all the tags for all the group's contents are merged together and applied to the group as a whole.

Yes. I twigged that ... eventually.

Quote:To do what you want, it would be necessary to refine the concept of grouping by exposing the individual items with all their tags for browsing and searching operations ... This is an interesting idea, but it would be quite a large amount of work to implement it and it probably wouldn't perform as efficiently as the current mechanism. Given that the case you're describing is rare and only requires one extra click to navigate into the group, I'm inclined to add this to the "interesting ideas to think about" list for now.

This is as much as it is reasonable to hope for. I quite agree that sacrificing performance to implement a change of this kind makes no sense at all.

I have been thinking about the 'rarity' factor, and it seems to me that the case typically arises when the 'contained' track is better known in its own right than the 'container' work. Another example would be the Villa-Lobos "Little Train of the Caipira" from Bachianas Brasileiras No. 2. As such cases are not all that numerous, it might be better to make a separate copy of the 'contained' track with different metadata and no grouping, rather than use multiple composition tags in the original. That would solve the containment problem, such as it is.

David