Matroska music scanner ignores the PART_NUMBER/track metadata.

[voronind-com]

atldotnet is used by Jellyfin, and I was forwarded here.

This is the original issue: jellyfin/jellyfin#13484

Basically it seems so that PART_NUMBER/track metadata is not being parsed by atldotnet.

As per Matroska spec, quote:

PART_NUMBER UTF-8 Number of the current part of the current level. (e.g., if TargetType is TRACK, the track number of an audio CD)

Please tell if there's not enough info from this message and Jellyfin issue.

[Zeugma440]

Hi and thanks for your feedback~

All I can say for now is that ATL does support that field. Something is telling me we're facing some sort of an edge case.

Create an example mka audio file with album metadata using ffmpeg with something like -metadata "part_number=10".

Could you please be more explicit in the repro steps I should use? I can't work with "put something like xxx". Thanks for your understanding 😉

[voronind-com]

@Zeugma440 Sadly, I've never touched c# in my life, so I can't really test it myself. Is there a cli tool to repl this library? I was told that Jellyfin uses this library to extract metadata. I can share an example file: https://share.voronind.com/112_440_Hz.mka
ffprobe shows DATE and track correctly, but JF shows no such metadata for it. Sorry for inconvinience and thanks for the help.

[Zeugma440]

Got it, thanks for the file.

The problem has nothing to do with metadata; the file you submitted has a tiny defect (first Cluster Element starts at Timestamp 7 instead of starting at Timestamp 0), which put ATL off the rails.

I've fixed that for next release

[voronind-com]

That's odd, the file was created completely with ffmpeg. Glad it's fixed now, thank you very much! <3

[Zeugma440]

Fix is available on today's v6.16. Please close the issue if it works on your side~

[voronind-com]

Fix is available on today's v6.16. Please close the issue if it works on your side~

I'll have to wait for the Jellyfin team to release with it.
To simplify things, I'll just close it now and reopen if this happens again. Thanks!