Movement rather than Track Title

[audio_elf]

Is this possible...

I want to display the Movement (a tag field I populate in my classical music) in preference to the Track title on my control point and the Naim front panel.

I tried adding
Title.replace={Movement}
to tagValue but this resulted in the control point showing
Title; Movement
(e.g.) Divertimento: i. Allegro ma non troppo; i. Allegro ma non troppo

Is what I'm wanting to do possible?

[DavidHB]

I guess that it is somewhat dependent on the behaviour of your preferred control point and renderer, but with my Linn player, BubbleDS and Kazoo, I have successfully used displayFormat rather than replace to control the track title display. The relevant section of the User Guide is here, but you've probably been through that already.

Using my setting (which I know works) as an example, I typically put work and movement, but not composer, information in the track title However, I like to display the track title with the composer's name shown. My tagFormat property therefore includes

Title.displayFormat={$composer$title^^^: }

Both control points and the player display show the composer name, then a colon and space, and then the actual track title. Using this logic, you might try

Title.displayFormat={$movement^^^}

though I have not tried it myself, because I prefer not to mess with settings that work for me. Obviously, 'movement' (or whatever the tag is called) will need to be in indexTags or itemTags for this to work.

Just as a matter of curiosity, what do you typically include in and omit from the track titles of classical albums; or, put another way, why do you need a separate movement tag?

David

[simoncn]

(26-08-2015 10:35)audio_elf Wrote:  Is this possible...

I want to display the Movement (a tag field I populate in my classical music) in preference to the Track title on my control point and the Naim front panel.

I tried adding
Title.replace={Movement}
to tagValue but this resulted in the control point showing
Title; Movement
(e.g.) Divertimento: i. Allegro ma non troppo; i. Allegro ma non troppo

Is what I'm wanting to do possible?

Thanks for letting me know about this. It is a bug affecting replacement of the Title tag and probably a few other tags for which MinimServer is doing special processing. Instead of the initial tag value being replaced, the bug causes the replacement value to be added as an additional value.

I will investigate how to fix this for the next update. For now, you should be able to do what you need by using the approach that DavidHB has described.

[audio_elf]

Thanks David (and Simon) ... that works perfectly.

[simoncn]

(26-08-2015 22:11)simoncn Wrote:  I will investigate how to fix this for the next update.

Unfortunately, it isn't possible to fix this without causing other problems or adding significant overhead to tag processing, so the next update will prohibit using the "replace" option to replace the following tags: TRACKNUMBER, DISCNUMBER, ALBUM, GROUP, TITLE, ALBUMARTIST, DISCSUBTITLE and DATE. If this is a problem for anyone, please let me know.

[DavidHB]

(30-08-2015 18:18)simoncn Wrote:  ... the next update will prohibit using the "replace" option to replace the following tags: TRACKNUMBER, DISCNUMBER, ALBUM, GROUP, TITLE, ALBUMARTIST, DISCSUBTITLE and DATE. If this is a problem for anyone, please let me know.

Given that the displayFormat option can be used as previously described, it is difficult to see how this could be a major limitation. In the circumstances, it seems a sensible change to make.

David

[audio_elf]

No, not a problem especially as the workaround works brilliantly.

[simoncn]

(30-08-2015 18:18)simoncn Wrote:  Unfortunately, it isn't possible to fix this without causing other problems or adding significant overhead to tag processing, so the next update will prohibit using the "replace" option to replace the following tags: TRACKNUMBER, DISCNUMBER, ALBUM, GROUP, TITLE, ALBUMARTIST, DISCSUBTITLE and DATE. If this is a problem for anyone, please let me know.

I have now found a way to support this without any significant overhead and this support will be available in the next update. See the last paragraph of this section for details of how the new support works.