Display of MKV PART_NUMBER tags without target level

[RobMacNeil]

Hi Xanashi,

I've noticed that tags for mkv files created by MKVToolNix mkvpropedit don't get set up with specific target detail if input tag has a target type value of 50.
In other words, if you use mkvextract on a file that's been tagged using mkvpropedit this way, then extracted output xml file will show <Targets /> rather than <Targets><TargetTypeValue>50</TargetTypeValue></Targets>, even though the target type value 50 was explicit in mkvpropedit input tag xml file.
I might join MKVToolNix community forum to find out more about this.
Up to now I've mostly been using Mp3tag to interactively tag my mkv files.
Mp3tag doesn't exhibit this odd behaviour of not setting target type value if it's equal to 50.
But I'm potentially interested in using mkvpropedit within PowerShell scripts to do some automated batch file tag editing.

Anyway, the point is, for the PART_NUMBER tag in particular, this loss of target level information means Episode number does not display in Windows when Icaros is activated.

The display of Episode number was addressed in issue #157 where the following mapping was requested:

PART_NUMBER TargetTypeValue=50 (*System.Media.EpisodeNumber)

However, it looks like Windows natively displays Episode number even when there's no specific target value set (as well as when it's set to value 50), as if Windows somehow assumes 50 is the default target level for MKV.

So, in such cases, Icaros activation has the effect of making Episode number disappear from view in Windows File Explorer.

And, as I say, without Icaros, for MKV files, Windows natively displays a PART_NUMBER tag with an unspecified target type value as Episode number (System.Media.EpisodeNumber).

[RobMacNeil]

Hi Xanashi,

You've been quiet lately.
I hope all's well.

I just wanted to let you know that I joined MKVToolNix community forum to ask about MKV tags with target type value 50.

It was confirmed there that the value "50" is the default value for the element TargetTypeValue.
This information is in Matroska's element specification table rather than in Matroska's tagging section.

Scroll down to fairly near the bottom of the elements specification table for the relevant entry, or simply find (Ctrl+F) for the text: TargetTypeValue

Anyway, it means where you don't find a specific TargetTypeValue for a simple named tag, then the value of "50" should be assumed.

As mentioned above, it looks like Windows natively handles this default behaviour, and Icaros properties activation breaks it, so I think this should really be treated as a bug.

[Xanashi]

Hi RobMacNeil,

All is well, I've just had a lot of real life things going on.
Thank you for reporting and looking into this. I would consider this a bug as well.
I'll make sure it's fixed in the next release of Icaros. 👍