processing order issue between tagValue and tagFormat

[simoncn]

(28-03-2025 16:31)eseb63 Wrote:  I thought they would be treated sequentially rather than combined : which kind of use case for this combination feature ?

The original purpose of tag formatting was to pass a displayFormat tag value to the control point for display when viewing or playing a track or album. For this, a single value is needed.

The indexFormat option was added later and uses the same formatting implementation as displayFormat. Because it uses the same implementation, it produces a single value.

Quote:If i create a GROUP tag for the 4 ballades tracks, i get when browsing by Composer-Work a single entry with the concatenation of the 4 ballades, i suppose it's the same mechanism.

If you are using indexFormat, you will always get a single contatenated value.

Quote:I tried tagValue : Composer-Work.Merge={Work_Set}
this time, when browsing Composer-Work i get only the "4 ballades" entry and not the individual ballades ?

This is because you are merging Work_Set, which contains the single value "4 ballades". If you want to add the individual ballades, you need this:

Composer-Work.merge={Work_Set, Work}

or this:

Work.merge={Work_Set}, Composer-Work.merge={Work}