|
MinimServer 0.70 - Working with the new tagFormat property
|
|
10-04-2013, 15:46
Post: #29
|
|||
|
|||
RE: MinimServer 0.70 - Working with the new tagFormat property
(10-04-2013 14:19)bbrip Wrote: Sorry that was a typo of mine. I have Soloist.multiTag set but still only get the first soloist passed on.... Sorry, that was a typo of mine: it should be Soloist.display.multiTag. I've tried this, and I get multiple soloists as separate <artist role="Soloist"> XML tags. Are you sure the file contains multiple Soloist tags? Quote: I want composer information send, but I want it send to the Composer field not the Artist field, ie of that empty bracket expression 'kills' the composer from being passed on, I better leave it as the default. The XML data sent to the control point doesn't have a composer field. The XML tag used to send composer information is either <artist role="Composer"> or <author role="Composer">. If you want to send composer information, you need to specify either Composer.displayRoles={artist} or Composer.displayRoles={author} to tell MinimServer which of these to use. Quote:well, what you describe in the last paragraph is pretty much what I want: I'd like to see all "artists" in the wider sense, ie mainly Soloists and conductors to appear as individual entries in the "Artist" tag so I can search or browse on them. (for now not Orchestras or Ensembles, thats just getting too mingled-up for my taste). This is possible with MinimServer 0.70, but it seems inconsistent. Are you expecting the control point to use the <artist role="xxx"> data for searching/browsing purposes only, and to use the <artist> data for display purposes only? I would hope that a control point that accepts multiple <artist role="xxx"> tags would also accept multiple <artist> tags, and would be smart enough to combine the information in all these tags to produce a suitable artist display string. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



