HDR flag check

MediaInfoLib - v19.09

That version on other (non youtube) files shows

Video
ID                                       : 257 (0x101)
Menu ID                                  : 1 (0x1)
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5.1@High
HDR format                               : SMPTE ST 2086, HDR10 compatible
Codec ID                                 : 36
Duration                                 : 1 min 38 s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 60.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 10 bits
Writing library                          : ATEME Titan KFE 3.7.3 (4.7.3.1003)
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : PQ
Matrix coefficients                      : BT.2020 non-constant
Mastering display color primaries        : Display P3
Mastering display luminance              : min: 0.0040 cd/m2, max: 1100 cd/m2

Blatant necro-post :slightly_smiling_face: regarding the long-standing issue of the Vero 4K not correctly triggering HDR on the TV when playing an HDR VP9 (or VP9.2) video.

I’ve recently acquired an Amazon Fire Stick 4K, and I was interested to see that it has the same problem: if I play an HDR VP9 file in Kodi on the AFS4K, it doesn’t signal the TV to switch to HDR mode.

I found that interesting because it uses a different chipset from the Vero, and it runs Amazon’s hacked version of Android rather than Linux; but also because HDR VP9 works fine in both the official YouTube app, and in an open source third party YouTube player app like SmartTubeNext. (See GitHub - yuliskov/SmartTubeNext: Ad free app for watching tube videos on Android TV boxes ).

Is it possible this should be raised as a general Kodi issue rather than as an OSMC problem?

And does the way that SmartTubeNext works (or the way that it differs from Kodi under Android TV, anyway) offer any possible solution?

Isn’t the Amazon Firestick also AMLogic based?

I don’t see why – as Kodi has no HDR implementation for this hardware at all.

No, Mediatek. MTK8695+MT7668, according to Amazon.

Fair enough. When I see Kodi exhibiting the same problem on two different platforms, while a different piece of open source software on one of those platforms isn’t affected, it seems reasonable to ask if it’s a Kodi software issue. But if it isn’t, it isn’t.

I don’t think it is a Kodi issue.

It can’t be for us – because AMLogic support is added by us and isn’t part of Kodi (at least not anymore).

Kodi will use a generic MediaCodec approach for Android, which is a universal interface for accelerating hardware decode.