Post Reply 
MinimServer 0.70 - Working with the new tagFormat property
10-04-2013, 13:34
Post: #27
RE: MinimServer 0.70 - Working with the new tagFormat property
(10-04-2013 13:01)bbrip Wrote:  
(09-04-2013 14:23)simoncn Wrote:  You should be able to send multiple <artist> XML tags by using Artist.multiTag. This would work with Artist file tags or with Soloist file tags aliased to Artist.

Other variations are possible. You could leave the Soloist tag unaliased and use the Soloist.displayRoles={artist} setting to send it to the control point as the XML tag

<artist role="Soloist">My Soloist</artist>

You can combine this with Soloist.multiTag to send multiple soloist values as separate XML tags.

Back on trying to get multiple artist strings passed as XML tags. I tried the method you describe above, Aliasing Soloist as artist and then setting the MultiTag property for Artist. However, it only picks up one soloist (the first one).

As I said prevously (see above), you need to use Soloist.multiTag, not Artist.multiTag.

Quote:I tought it might be related to the fact that the "Composer.displayRoles={artist}" was still set (therefore a duplicate assignment of artist to yet another field??) and took that off. However when restarting Minim, I found that Minim just parses that string back in...

If you have Composer in indexTags or itemTags, MinimServer will add 'Composer.displayRoles={artist}' by default. If you don't want to send any composer information to the control point, you need to set 'Composer.displayRoles={}'.

Quote:The other limitation of the above method is, that I can no longer use the tagFormat property to set the display format for Artist to "soloist, orchestra, conductor"... etc...

This should work OK if you use Soloist.multiTag instead of Artist.multiTag.

Quote:I then tried around with the "index.format" property but that only throw error messages at me.. I thought that was the differentiation that you could set a display value for a given tag and one for indexing purposes ?? I could'nt get that to work so I need to scratch my head a bit more how to best achieve this Confused

bbrip

What would you like to have in the XML data that MinimServer sends to the control point for display? If you want:

<artist role="Soloist">soloist1</artist>
<artist role="Soloist">soloist2</artist>
<artist>soloist1, soloist2, orchestra, conductor</artist>

you can do this by setting a combination of

Soloist.displayRoles
Soloist.multiTag
Artist.displayFormat

This is a slightly strange combination of separate XML tags (for soloist) and merged information in a single XML tag (for artist). I was expecting people who prefer the multiple tag approach to be sending

<artist role="Soloist">soloist1</artist>
<artist role="Soloist">soloist2</artist>
<artist role="Orchestra">orchestra</artist>
<artist role="Conductor">conductor</artist>

so that the control point can do the appropriate combining of these values for display. If you can explain what you'd like to achieve, I can probably suggest how to do it.
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
RE: MinimServer 0.70 - Working with the new tagFormat property - simoncn - 10-04-2013 13:34

Forum Jump:


User(s) browsing this thread: 1 Guest(s)