Open dabrain34 opened 2 years ago
I took a look into this stream. It's characteristics are,
Geometry :
Coded Width : 1920
Displayed Width : 1920
Coded Height : 1080
Displayed Height : 1080
Codec : decode h.265
VideoChromaFormat : 420
VideoFormat : PAL
ColorPrimaries : BT470BG
TransferCharacteristics : BT470BG
MatrixCoefficients : BT470BG
The rendering with GstVkParser has no relevant detail in the resultant pictures. The problem is that the parser is not correctly handling the scaling lists. I get correct rendering if I fudge them to the right values. I will investigate the root cause of the scaling matrix parsing next.
I'm attaching API dumps of Gst vs Nvidia for future reference. There are several interesting differences,
codedExtent
's height in vkCmdDecodeVideo
is 1080 for Gst, but 1088 for nv. Apparently not a problem, but weird!sar_width
and sar_height
are 0 for gst, 1 for nv. Ditto for 2.pShortTermRefPicSet
, there is a FIXME in the parser about handling this properly. Ditto for 2.JSON API dumps between nvidia are gst gst.txt nvidia.txt
The foot.zip is not correctly displayed by vk_video_decoder using GstVkVideoParser