tsdemux: missing new-segment after seeking in push mode

Submitted by Holger Kaelberer

Link to original bug (#780186)

Description

Created attachment 348161
GST_DEBUG=play:5,tsdemux:5,mpegts:5,mpegtspacketizer:5,mpegtsbase:5,GST_DEBUG=vaapi*:5,codecparsers*:5

With some content playback stops after seeking in push mode (http). Does not happen with the same content transmuxed to an mp4 container, therefore probably tsdemux related. Not yet sure about the root cause. Happens with git master (from last week), 1.10 and 1.8.3. Following output is generated from git master.

vaapidecode complains about parsing errors after seeking:

0:00:03.648211853 14196 0x7f95f014b000 WARN codecparsers_h264 gsth264parser.c:976:gst_h264_parser_parse_pic_timing: didn't get the associated sequence param
ater set for the current access unit
0:00:03.648227337 14196 0x7f95f014b000 WARN codecparsers_h264 gsth264parser.c:1021:gst_h264_parser_parse_pic_timing: error parsing "Picture timing"
0:00:03.648245709 14196 0x7f95f014b000 ERROR vaapidecode gstvaapidecode.c:1118:gst_vaapidecode_parse_frame: parse error 8

Not sure if this this is related to the following:

(gst-play-1.0:14236): GStreamer-WARNING **: gstpad.c:4429:gst_pad_push_data:h264parse0:src Got data flow before segment event

(gst-play-1.0:14236): GStreamer-WARNING **: gstpad.c:4176:gst_pad_chain_data_unchecked:capsfilter0:sink Got data flow before segment event

(gst-play-1.0:14236): GStreamer-WARNING **: gstpad.c:4429:gst_pad_push_data:capsfilter0:src Got data flow before segment event

(gst-play-1.0:14236): GStreamer-WARNING **: gstpad.c:4176:gst_pad_chain_data_unchecked:vaapidecodebin0:sink Got data flow before segment event

(gst-play-1.0:14236): GStreamer-WARNING **: gstpad.c:4429:gst_pad_push_data:sink:proxypad3 Got data flow before segment event

(gst-play-1.0:14236): GStreamer-WARNING **: gstpad.c:4176:gst_pad_chain_data_unchecked:vaapidecode0:sink Got data flow before segment event

Tested with gst-play, seems to happen both with GST_SEEK_FLAG_KEY_UNIT and GST_SEEK_FLAG_ACCURATE.

Unfortunately, I'm not allowed to provide test-content publicly. Could provide a snippet in private communication if needed and ok for you.

Attachment 348161, "GST_DEBUG=play:5,tsdemux:5,mpegts:5,mpegtspacketizer:5,mpegtsbase:5,GST_DEBUG=vaapi*:5,codecparsers*:5":
debug.txt.gz