processing order issue between tagValue and tagFormat

[eseb63]

(28-03-2025 13:15)simoncn Wrote:  When you specify a multivalued tag in tagFormat, the values are combined with a default separator ", ". This is what you are seeing. The separator can be changed or removed.

I thought they would be treated sequentially rather than combined : which kind of use case for this combination feature ?

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.

(28-03-2025 13:15)simoncn Wrote:  If you browse by Work instead of Composer-Work (so that tagFormat is not applied), you should see the two WORK tag values shown separately.

Indeed, but the composer prefix is usefull when browsing from other entities than composer.


I made another test, and again, i don't understand the result :

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 ?