Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
using tagFormat to display composer as artist
26-12-2021, 15:27
Post: #1
using tagFormat to display composer as artist
I just updated to minimserver 2.1 and when I activated the new recently added and recently played features, Running with full license. I got this error from minimwatch (using the command line):

>restart
stopping MinimServer[echidna]
MinimServer[echidna] is stopped
MinimServer[echidna]: incorrect tag name 'composer' in option 'Artist.displayFormat' in property 'tagFormat'
MinimServer[echidna] error: now stopped, use 'restart' or 'close'

I have set

tagFormat=Artist.displayFormat={$composer^^: $artist}

so that when a composer is listed I get, the composer and artist listed, but otherwise just the artist. But it appears that I am not allowed to use $composer. I tried setting it to simply {$composer} and get the same error, but if I set it to simply {$artist} then I get no error. (Is composer a nonstandard tag?) I set this up years ago and don't have much classical music. It looks like I tagged classical music so "composer" is the composer and "artist" is set to "conductor / orchestra", as in "Sir Adrian Boult / London Philharmonic Orchestra"

How do I get the result I want, where classical music displays composer, conductor and orchestra and other music just the name of the artist?
Find all posts by this user
Quote this message in a reply
26-12-2021, 20:00
Post: #2
RE: using tagFormat to display composer as artist
You need to have Composer in either indexTags (if you want a Composer index) or itemTags (if you don't want a Composer index). This has always been how displayFormat works.
Find all posts by this user
Quote this message in a reply
26-12-2021, 21:57
Post: #3
RE: using tagFormat to display composer as artist
(26-12-2021 20:00)simoncn Wrote:  You need to have Composer in either indexTags (if you want a Composer index) or itemTags (if you don't want a Composer index). This has always been how displayFormat works.

I had (accidentally) removed composer from indexTags when I was setting up the recently added feature, which then triggered this error. And I didn't realize it was related, so when I fixed indexTags I didn't know I'd also fixed this other problem.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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