From c969239c7c6b5ed9895e11e9a3e433f591a1496f Mon Sep 17 00:00:00 2001 From: Mathieu Duponchelle Date: Thu, 12 Nov 2020 22:27:08 +0100 Subject: [PATCH] h264parse: try harder to update timecode NumClockTS is the maximum number of timecodes the pic_timing SEI can carry, but it is perfectly OK for it to carry fewer, and have one of the clock_timestamp_flags set to 0. Part-of: --- gst/videoparsers/gsth264parse.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gst/videoparsers/gsth264parse.c b/gst/videoparsers/gsth264parse.c index 9dc235c90c..d5f2816e59 100644 --- a/gst/videoparsers/gsth264parse.c +++ b/gst/videoparsers/gsth264parse.c @@ -2841,16 +2841,16 @@ gst_h264_parse_create_pic_timing_sei (GstH264Parse * h264parse, num_clock_ts = num_clock_ts_table[h264parse->sei_pic_struct]; - if (num_meta != num_clock_ts) { + if (num_meta > num_clock_ts) { GST_LOG_OBJECT (h264parse, - "The number of timecode meta %d is not equal to required %d", + "The number of timecode meta %d is superior to required %d", num_meta, num_clock_ts); return NULL; } GST_LOG_OBJECT (h264parse, - "The number of timecode meta %d is equal", num_meta); + "The number of timecode meta %d is compatible", num_meta); memset (&sei, 0, sizeof (GstH264SEIMessage)); sei.payloadType = GST_H264_SEI_PIC_TIMING;