Streamlining the browsing tree & multiple configs

[simoncn]

(23-09-2013 22:38)DavidHB Wrote:  What I was trying to say (perhaps ineptly) was that the data in Group might just be the work name, or it might be a lower-level summary of the contents of the grouped tracks. An example with perhaps more general applicability than your fascinating Biber case (didn't Biber like to make things complicated!) would be an opera, where the work might be 'Porgy and Bess' and the Group names would be 'Porgy and Bess, Act I' etc. This makes a lot of sense if the whole opera is treated as a single album, which is what I like to do.

Groups could be used for the acts of an opera. This is similar to the Biber example that I gave (which I don't think is a case of Biber making things over-complicated, but choosing a structure that properly reflects the specific religious context for which this work was composed).

Quote:I note what you say about Group sometimes replacing Album in the displayed data. I assume that this would not be the case in selection lists, as I had taken the statement in the User Guide

"When you display the contents of an album that contains grouped tracks, the group will appear as a single item instead of appearing as separate tracks."

to mean that, more normally, Groups would replace track data in the lists.

Yes, that's correct for item (track) lists within albums and for the <n> items list. In MinimServer, an item is either a track or a group. You should be able to play a group item in the same way as you play a track item, as long as you're not using foobar2000 as your control point.