27.07.2022, 16:23
I think there's a misunderstanding here. I am not claiming that Hybrid incorrectly maps the color profiles to the appropriate mkvmerge index. The issue is that if you set "--colour-matrix-coefficients 0:6" (6=SMPTE 170M, BT.601 NTSC), either via "MKV advanced signaling" or via "customMkvmergeAddition", the output MKV file will have the matrix set to BT.470BG, which is "--colour-matrix-coefficients 0:5" (BT.601 PAL). Therefore, it is currently impossible to produce a final MKV file using UTVideo that will have the matrix set to BT.601 NTSC (SMPTE 170M).
If I run mkvmerge myself from Hybrid's directory like: "mkvmerge.exe -o fixed.mkv --colour-matrix-coefficients 0:6 bad.mkv", this time it actually works - the output MKV file has matrix set to BT.601 NTSC (SMPTE 170M). So the problem is not in mkvmerge or ffprobe/MediaInfo.
Random note: apparently mkvmerge uses "color" or "colour" based on your computer's regional settings, and since mine are set to UK... crazy
If I run mkvmerge myself from Hybrid's directory like: "mkvmerge.exe -o fixed.mkv --colour-matrix-coefficients 0:6 bad.mkv", this time it actually works - the output MKV file has matrix set to BT.601 NTSC (SMPTE 170M). So the problem is not in mkvmerge or ffprobe/MediaInfo.
Random note: apparently mkvmerge uses "color" or "colour" based on your computer's regional settings, and since mine are set to UK... crazy