Orchestra Tag

[simoncn]

(26-06-2012 18:37)bbrip Wrote:  while it would of course be possible to tag ensembles other than orchestra in the Artist tag this would create some other inconsistancies. Let me take the example of an opera. Here you have a number of soloists, which in our Minim definition we would tag under "Artist", we would have one (or more) chorus(es), which I would prefer not to also submit to the "Artist" tag but put under "Ensemble", we have an Orchestra and a Conductor, which both go into the equally-named tags.

So I would agree with Wammer here, that really the *perfect* option would be what you described under option 2, ie that Minim supports both, Orchestra and Esemble tags and than feeds a string containing the following info to the Artist field if the control point:

"Artist(1), Artist(2), Artist(3), Artist(4), Ensemble(1), Ensemble(2), Orchestra, Conductor"

That isn't what I described under option 2. I think it's too confusing to have two tags with such similar meanings. Option 2 is for MinimServer to support the Orchestra tag and allow the user to map it to Ensemble (or anything else) for display in the control point browse tree.

For the situation you described, you could use Artist for the choruses, although I realise this isn't your first preference. Alternatively, you could use some other tag such as "Ensemble", "Choir" or "Chorus", which would be displayed in the control point browse tree but wouldn't be added to the control point artist information.

Given the current lack of widely accepted standards or conventions for how this tagging of multiple performers should be done, I'd prefer to leave the MinimServer support for building the control point artist information as it is for now. This means that the control point artist information will be built from the Artist, Orchestra and Conductor tags, all of which have a reasonable amount of user adoption.