Artifact with custom 'track summary' display format [#17355][#17356]

[MayorQwert]

So I'm trying to implement the following format:
$if(<Custom 6>,<Custom 6>: ,)$if(<Custom 1>,<Custom 1> ,<Album> )(<Year>) -$if(<Title>, <Title>, <Filename>)

The custom format I'm using has the following elements for context:
This is for video game soundtracks, Custom 6 is the platform (e.g. "Arcade", "SNES", "PC")
Custom 1 is the Album name, this is because I have a custom formatting for Arcade music that already has the year embedded in the album name, for use in an arcade frontend that plays music but doesn't have the option to customize its preview to add the year in. I entered the album in here without the year and if it is present I use this so that I don't end up having something like "Street Fighter II (1991) (1991)" and instead have just one instance of the year.

It should display content as in these examples:
"Arcade: Dragon Saber (1990) - Jungle (Hidden Stage 4)"
"PC: Red Alert 2 (2000) - Hell March 2"

However it displays as:
"ArcadeZ0: Dragon Saber (1990) - Jungle (Hidden Stage 4)"
"PCZ0: Red Alert 2 (2000) - Hell March 2"

Any idea why the Z0 might be getting added? It's across the board for all cases of where the leading text is added. It doesn't appear if it's omitted.

[gamb2009]

I am experiencing the same thing with data in some custom fields I've added.
"Z0" or "Z1" is added to the data inserted in those fields at the end of the text, or they appear alone, when no data is added.

[Lowlander]

@MayorQwert verify the data is not in the tag?

@Both, which build is causing this issue for you?

[MayorQwert]

No, there's no Z0 in the tags, I've processed probably 7000 files and all have this artifact. I'm personally on 5.0.0.2275.

Another issue, though this may be syntax, is that I am noticing there doesn't seem to be an effective way to enclose items within a function with parenthesis. It will register the first '(' but the function is aborted as soon as it sees a ')', which means that the ending ',)' that would ordinarily be at the function's end is left behind to always be displayed.

Here's an example:
$if(<Custom 2>,(<Custom 2>) ,)$if(<Custom 6>,<Custom 6>: ,)$if(<Custom 1>,<Custom 1> ,<Album> )(<Year>) -$if(<Title>, <Title>, <Filename>)

Custom 2 states whether a track is an arrangement, it's either blank or "Arrangement".

In this case, it's blank so it shouldn't display anything.
Expectation: Arcade: Crime City (1989) - Ending
Reality: ,)ArcadeZ0: Crime City (1989) - Ending

In this case Custom 2 is "Arrangement"
Expectation: (Arrangement) Out Run (1992) - Splash Wave
Reality: (Arrangement ,)Out Run (1992) - Splash Wave


If this is a syntax error, what would be the proper way to declare parenthesis within an expression?

[Lowlander]

Then definitely update and see if this is a problem in the latest release: viewtopic.php?f=30&t=86639&sd=d

I can reproduce: https://www.ventismedia.com/mantis/view.php?id=17355 This may not get fixed before 5.0 is released. You could use [] for now.

[MayorQwert]

Updated and can confirm that it still prints Z0 exactly as before.

[MayorQwert]

I haven't checked all fields but it seems like it's just Custom 6, since Custom 1 and Custom 2 don't have the issue. For now, I'm going to move to using Custom 3 since it doesn't have the same issue.

[Lowlander]

I can reproduce with Track Summary: https://www.ventismedia.com/mantis/view.php?id=17356 It is related to the new custom fields 6-10.