[SOLVED] tagValue Artist.merge does not work with certain tagUpdate file?

[simoncn]

The order of tag processing is as follows:

1) Tags are read from the audio file
2) Special tags (with names starting #) are added if present in either indexTags or itemTags
3) For each tag in turn, tagUpdate processing (if any) is applied to the tag, followed by aliasTags processing (if any)
4) For each new tag added by tagUpdate processing, tagUpdate processing (if any) is applied to the tag, followed by aliasTags processing (if any)
5) Any actions specified in tagOptions are applied in the order they appear in the tagOptions string
6) Any actions specified in tagValue are applied in the order they appear in the tagValue string
7) Any indexFormat actions in tagFormat are applied in the order they appear in the tagFormat string

This completes tag processing. Any displayFormat actions in tagFormat do not change tag values. They are applied to metadata sent to the control point when this metadata is requested.

[zym1010]

Thanks! However, I wonder how this explains my original problem?

Given the order of tag processing given here, it seems that, after step 4), my original problematic file should have the following tags, assuming this file physically has FIVE tags (one Artist tag with 4 artists' names concatenated together and four ArtistIndividual tags), and the tagUpdate adds one conductor.

Code:

file1.m4a
+ARTIST=A1
+ARTIST=A2
+ARTIST=A3
+ARTIST=A4
+CONDUCTOR=C1

Then step 6) should be able to merge conductor C1 into the existing four artists. No?

(07-11-2022 22:49)simoncn Wrote:  The order of tag processing is as follows:

1) Tags are read from the audio file
2) Special tags (with names starting #) are added if present in either indexTags or itemTags
3) For each tag in turn, tagUpdate processing (if any) is applied to the tag, followed by aliasTags processing (if any)
4) For each new tag added by tagUpdate processing, tagUpdate processing (if any) is applied to the tag, followed by aliasTags processing (if any)
5) Any actions specified in tagOptions are applied in the order they appear in the tagOptions string
6) Any actions specified in tagValue are applied in the order they appear in the tagValue string
7) Any indexFormat actions in tagFormat are applied in the order they appear in the tagFormat string

This completes tag processing. Any displayFormat actions in tagFormat do not change tag values. They are applied to metadata sent to the control point when this metadata is requested.

[simoncn]

(07-11-2022 23:14)zym1010 Wrote:  Then step 6) should be able to merge conductor C1 into the existing four artists. No?

I have looked at the code again and I have found something that causes the code that removes any ARTIST tags added in step 4 to also (incorrectly) remove any ARTIST tags added in step 6.

This bug will be fixed in the next MinimServer update. Thanks very much for your help and persistence with identifying this issue.

[zym1010]

Thank you very much for looking into this issue and replying to me in detail!!!

(08-11-2022 11:16)simoncn Wrote:  

(07-11-2022 23:14)zym1010 Wrote:  Then step 6) should be able to merge conductor C1 into the existing four artists. No?

I have looked at the code again and I have found something that causes the code that removes any ARTIST tags added in step 4 to also (incorrectly) remove any ARTIST tags added in step 6.

This bug will be fixed in the next MinimServer update. Thanks very much for your help and persistence with identifying this issue.

[simoncn]

This bug is now fixed in MinimServer update 219.

At present, update 219 can be installed manually from the About dialog (Show updates) or from the Packages tab of the Properties dialog.

[zym1010]

(07-12-2022 12:43)simoncn Wrote:  This bug is now fixed in MinimServer update 219.

At present, update 219 can be installed manually from the About dialog (Show updates) or from the Packages tab of the Properties dialog.

Thank you very much!!! I will test it when i get a chance.