GStreamer-devel

Pipeline fails after exactly 2.5 hours

Classic

List

Threaded

10 messages Options

Henk Schurink

Pipeline fails after exactly 2.5 hours

Hello gstreamers,

The following pipeline fails after exactly 2.5 hours every time:

sudo gst-launch-1.0 -e rtspsrc
location=rtsp://HT1:%24hypothermicCamera1%23%23@192.168.0.30:88/videoMain !
rtpjitterbuffer ! rtph264depay ! decodebin ! videoconvert ! x264enc !
h264parse ! splitmuxsink location="/c1/record%07d.mp4"
max-size-bytes=100000000 max-files=6000

After that time it has only recorded about 1.8GB of footage and my disk has
2.7TB free, so space should not be a problem.

Here's the error:

ERROR: from element
/GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could
not multiplex stream.
Additional debug info:
gstqtmux.c(4561): gst_qt_mux_add_buffer ():
/GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
Buffer has no PTS.
EOS on shutdown enabled -- waiting for EOS after Error
Waiting for EOS...
Redistribute latency...

Any help would be appreciated!

Best regards,
Henk Schurink

--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

Nicolas Dufresne-5

Re: Pipeline fails after exactly 2.5 hours

Le vendredi 15 novembre 2019 à 03:52 -0600, Henk Schurink a écrit :

> Hello gstreamers,
>
> The following pipeline fails after exactly 2.5 hours every time:
>
> sudo gst-launch-1.0 -e rtspsrc
> location=rtsp://HT1:%24hypothermicCamera1%23%23@192.168.0.30:88/videoMain !
> rtpjitterbuffer ! rtph264depay ! decodebin ! videoconvert ! x264enc !
> h264parse ! splitmuxsink location="/c1/record%07d.mp4"
> max-size-bytes=100000000 max-files=6000
>
> After that time it has only recorded about 1.8GB of footage and my disk has
> 2.7TB free, so space should not be a problem.
>
> Here's the error:
>
> ERROR: from element
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could
> not multiplex stream.

You might be hitting similar issues, but with x264enc as what some
people have hit, and lead to write this patch:

https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/merge_requests/768

Investigation required. I don't recall x264enc ever not producing both
PTS and DTS, so it really looks like yet another parser bug. You should
also enable more traces and try to find the condition that triggers
this.

> Additional debug info:
> gstqtmux.c(4561): gst_qt_mux_add_buffer ():
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
> Buffer has no PTS.
> EOS on shutdown enabled -- waiting for EOS after Error
> Waiting for EOS...
> Redistribute latency...
>
> Any help would be appreciated!
>
> Best regards,
> Henk Schurink
>
>
>
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

signature.asc (201 bytes) Download Attachment

Henk Schurink

Re: Pipeline fails after exactly 2.5 hours

Hi Nicolas, I appreciate your answer.

Last night I upgraded to 1.16.1. The pipeline crashes even earlier and the
produced files are between 20-70MB each, never reaching the 100MB limit
assigned to splitmuxsink.

This is the error message when the current file stops and the next file
starts (it does recover after this error but it prematurely starts recording
to the next file for some reason.):

0:02:08.755626858 [336m 3899[00m 0x55b20b68b630 [33;01mWARN [00m [00m
qtmux gstqtmux.c:5118:gst_qt_mux_can_renegotiate:<muxer>[00m pad video_0
refused renegotiation to video/x-h264,
codec_data=(buffer)0164001fffe1001c6764001facd9405005bb016a02020280000003008000001e478c18cb01000568ebecb22c,
stream-format=(string)avc, alignment=(string)au, level=(string)3.1,
profile=(string)high, width=(int)1280, height=(int)720,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1,
interlace-mode=(string)progressive, colorimetry=(string)bt709,
chroma-site=(string)mpeg2, multiview-mode=(string)mono,
multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono,
chroma-format=(string)4:2:0, bit-depth-luma=(uint)8,
bit-depth-chroma=(uint)8, parsed=(boolean)true
0:02:12.798088977 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
libav gstavviddec.c:880:gst_ffmpegviddec_get_buffer2:<avdec_h264-0>[00m
Couldn't get codec frame !
0:02:12.798202672 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
libav :0::[00m get_buffer() failed
0:02:12.798210177 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
libav :0::[00m thread_get_buffer() failed
0:02:12.798217659 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
libav :0::[00m decode_slice_header error
0:02:12.798224304 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
libav :0::[00m no frame!
0:02:12.798235775 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
libav gstavviddec.c:1864:gst_ffmpegviddec_handle_frame:<avdec_h264-0>[00m
Failed to send data for decoding
0:02:20.327723513 [336m 3899[00m 0x55b20b68b630 [32;01mFIXME [00m [00m
basesink gstbasesink.c:3246:gst_base_sink_default_event:<sink>[00m
stream-start event without group-id. Consider implementing group-id handling
in the upstream elements
0:02:20.327834709 [336m 3899[00m 0x55b20b68b630 [33;01mWARN [00m [00m
qtmux gstqtmux.c:2981:gst_qt_mux_start_file:<muxer>[00m Robust muxing
requires reserved-moov-update-period to be set
0:02:22.864544424 [336m 3899[00m 0x7fe534050400 [33;01mWARN [00m [00m
rtpjitterbuffer rtpjitterbuffer.c:572:calculate_skew:[00m delta - skew:
0:00:01.028883909 too big, reset skew
0:02:22.864603568 [336m 3899[00m 0x7fe510002d40 [33;01mWARN [00m [00m
rtpjitterbuffer rtpjitterbuffer.c:572:calculate_skew:[00m delta - skew:
0:00:01.028883909 too big, reset skew

And after ~30 minutes the pipeline crashes with the following error:

0:24:12.513906078 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
libav gstavviddec.c:880:gst_ffmpegviddec_get_buffer2:<avdec_h264-0>[00m
Couldn't get codec frame !
0:24:12.514386268 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
libav :0::[00m get_buffer() failed
0:24:12.514395743 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
libav :0::[00m thread_get_buffer() failed
0:24:12.514404721 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
libav :0::[00m decode_slice_header error
0:24:12.514412069 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
libav :0::[00m no frame!
0:24:12.514424554 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
libav gstavviddec.c:1864:gst_ffmpegviddec_handle_frame:<avdec_h264-0>[00m
Failed to send data for decoding
0:24:26.024407851 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
videodecoder
gstvideodecoder.c:2759:gst_video_decoder_prepare_finish_frame:<avdec_h264-0>[00m
decreasing timestamp (0:24:21.883374288 < 0:24:21.904006671)
0:24:29.514983177 [336m 3899[00m 0x55b20b68b630 [33;01mWARN [00m [00m
qtmux gstqtmux.c:4832:gst_qt_mux_add_buffer:<muxer>[00m error: Buffer has
no PTS.
ERROR: from element
/GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could
not multiplex stream.
Additional debug info:
gstqtmux.c(4832): gst_qt_mux_add_buffer ():
/GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
Buffer has no PTS.
EOS on shutdown enabled -- waiting for EOS after Error
Waiting for EOS...

Any idea what might cause this behaviour?

--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

Nicolas Dufresne-5

Re: Pipeline fails after exactly 2.5 hours

Le dimanche 17 novembre 2019 à 10:43 -0600, Henk Schurink a écrit :

> Hi Nicolas, I appreciate your answer.
>
> Last night I upgraded to 1.16.1. The pipeline crashes even earlier and the
> produced files are between 20-70MB each, never reaching the 100MB limit
> assigned to splitmuxsink.
>
> This is the error message when the current file stops and the next file
> starts (it does recover after this error but it prematurely starts recording
> to the next file for some reason.):
>
> 0:02:08.755626858 [336m 3899[00m 0x55b20b68b630 [33;01mWARN [00m [00m
> qtmux gstqtmux.c:5118:gst_qt_mux_can_renegotiate:<muxer>[00m pad video_0
> refused renegotiation to video/x-h264,
> codec_data=(buffer)0164001fffe1001c6764001facd9405005bb016a02020280000003008000001e478c18cb01000568ebecb22c,
> stream-format=(string)avc, alignment=(string)au, level=(string)3.1,
> profile=(string)high, width=(int)1280, height=(int)720,
> pixel-aspect-ratio=(fraction)1/1, framerate=(fraction)30/1,
> interlace-mode=(string)progressive, colorimetry=(string)bt709,
> chroma-site=(string)mpeg2, multiview-mode=(string)mono,
> multiview-flags=(GstVideoMultiviewFlagsSet)0:ffffffff:/right-view-first/left-flipped/left-flopped/right-flipped/right-flopped/half-aspect/mixed-mono,
> chroma-format=(string)4:2:0, bit-depth-luma=(uint)8,
> bit-depth-chroma=(uint)8, parsed=(boolean)true
> 0:02:12.798088977 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
> libav gstavviddec.c:880:gst_ffmpegviddec_get_buffer2:<avdec_h264-0>[00m
> Couldn't get codec frame !
> 0:02:12.798202672 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
> libav :0::[00m get_buffer() failed
> 0:02:12.798210177 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
> libav :0::[00m thread_get_buffer() failed
> 0:02:12.798217659 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
> libav :0::[00m decode_slice_header error
> 0:02:12.798224304 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
> libav :0::[00m no frame!
> 0:02:12.798235775 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
> libav gstavviddec.c:1864:gst_ffmpegviddec_handle_frame:<avdec_h264-0>[00m
> Failed to send data for decoding
> 0:02:20.327723513 [336m 3899[00m 0x55b20b68b630 [32;01mFIXME [00m [00m
> basesink gstbasesink.c:3246:gst_base_sink_default_event:<sink>[00m
> stream-start event without group-id. Consider implementing group-id handling
> in the upstream elements
> 0:02:20.327834709 [336m 3899[00m 0x55b20b68b630 [33;01mWARN [00m [00m
> qtmux gstqtmux.c:2981:gst_qt_mux_start_file:<muxer>[00m Robust muxing
> requires reserved-moov-update-period to be set
> 0:02:22.864544424 [336m 3899[00m 0x7fe534050400 [33;01mWARN [00m [00m
> rtpjitterbuffer rtpjitterbuffer.c:572:calculate_skew:[00m delta - skew:
> 0:00:01.028883909 too big, reset skew
> 0:02:22.864603568 [336m 3899[00m 0x7fe510002d40 [33;01mWARN [00m [00m
> rtpjitterbuffer rtpjitterbuffer.c:572:calculate_skew:[00m delta - skew:
> 0:00:01.028883909 too big, reset skew
>
> And after ~30 minutes the pipeline crashes with the following error:
>
> 0:24:12.513906078 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
> libav gstavviddec.c:880:gst_ffmpegviddec_get_buffer2:<avdec_h264-0>[00m
> Couldn't get codec frame !
> 0:24:12.514386268 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
> libav :0::[00m get_buffer() failed
> 0:24:12.514395743 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
> libav :0::[00m thread_get_buffer() failed
> 0:24:12.514404721 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
> libav :0::[00m decode_slice_header error
> 0:24:12.514412069 [336m 3899[00m 0x55b20b68b400 [31;01mERROR [00m [00m
> libav :0::[00m no frame!
> 0:24:12.514424554 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
> libav gstavviddec.c:1864:gst_ffmpegviddec_handle_frame:<avdec_h264-0>[00m
> Failed to send data for decoding
> 0:24:26.024407851 [336m 3899[00m 0x55b20b68b400 [33;01mWARN [00m [00m
> videodecoder
> gstvideodecoder.c:2759:gst_video_decoder_prepare_finish_frame:<avdec_h264-0>[00m
> decreasing timestamp (0:24:21.883374288 < 0:24:21.904006671)
> 0:24:29.514983177 [336m 3899[00m 0x55b20b68b630 [33;01mWARN [00m [00m
> qtmux gstqtmux.c:4832:gst_qt_mux_add_buffer:<muxer>[00m error: Buffer has
> no PTS.
> ERROR: from element
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could
> not multiplex stream.
> Additional debug info:
> gstqtmux.c(4832): gst_qt_mux_add_buffer ():
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
> Buffer has no PTS.
> EOS on shutdown enabled -- waiting for EOS after Error
> Waiting for EOS...
>
> Any idea what might cause this behaviour?

First degree answer is "Buffer has no PTS.". But that seems like a side
effect of the stream being corrupted. You have to analyse your
bitstream and find out why it gets corrupted before it reaches the
decoder.

>
>
>
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

Thornton, Keith

AW: Pipeline fails after exactly 2.5 hours

In reply to this post by Henk Schurink

Hi,
we have a similar problem caused by two frames with the same timestamp being sent down the pipeline. The h264parse plugin changes the timestamp of the second frame to CLOCK_TIME_NONE and the qtmux in splitmuxsink thows the buffer_has_no_PTS error
You could try adding a pad_probe which detects this situation to confirm that you are suffering from the same problem.

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel <[hidden email]> Im Auftrag von Henk Schurink
Gesendet: Freitag, 15. November 2019 10:52
An: [hidden email]
Betreff: Pipeline fails after exactly 2.5 hours

Hello gstreamers,

The following pipeline fails after exactly 2.5 hours every time:

sudo gst-launch-1.0 -e rtspsrc
location=rtsp://HT1:%24hypothermicCamera1%23%23@192.168.0.30:88/videoMain !
rtpjitterbuffer ! rtph264depay ! decodebin ! videoconvert ! x264enc !
h264parse ! splitmuxsink location="/c1/record%07d.mp4"
max-size-bytes=100000000 max-files=6000

After that time it has only recorded about 1.8GB of footage and my disk has 2.7TB free, so space should not be a problem.

Here's the error:

ERROR: from element
/GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could not multiplex stream.
Additional debug info:
gstqtmux.c(4561): gst_qt_mux_add_buffer ():
/GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
Buffer has no PTS.
EOS on shutdown enabled -- waiting for EOS after Error Waiting for EOS...
Redistribute latency...

Any help would be appreciated!

Best regards,
Henk Schurink

--
Sent from: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgstreamer-devel.966125.n4.nabble.com%2F&data=02%7C01%7C%7C5a7973958cb64a60671f08d769b20fe1%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C637094085794607841&sdata=m05n8UdM6PcqAMPfAVfNmTnbWOIHCt8fKtzpspgnbD8%3D&reserved=0
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7C01%7C%7C5a7973958cb64a60671f08d769b20fe1%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C637094085794607841&sdata=%2Bvffrquk5RdXajpXwh62J4eEG42iP6UVZoARTnFCFIk%3D&reserved=0
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

Nicolas Dufresne-5

Re: AW: Pipeline fails after exactly 2.5 hours

Le lundi 18 novembre 2019 à 09:28 +0000, Thornton, Keith a écrit :
> Hi,
> we have a similar problem caused by two frames with the same timestamp being sent down the pipeline. The h264parse plugin changes the timestamp of the second frame to CLOCK_TIME_NONE and the qtmux in splitmuxsink thows the buffer_has_no_PTS error
> You could try adding a pad_probe which detects this situation to confirm that you are suffering from the same problem.

h264parse should not do that, seems like a bad idea. Did you file an
issue ? Also, was this interlaced content ?

>
> -----Ursprüngliche Nachricht-----
> Von: gstreamer-devel <[hidden email]> Im Auftrag von Henk Schurink
> Gesendet: Freitag, 15. November 2019 10:52
> An: [hidden email]
> Betreff: Pipeline fails after exactly 2.5 hours
>
> Hello gstreamers,
>
> The following pipeline fails after exactly 2.5 hours every time:
>
> sudo gst-launch-1.0 -e rtspsrc
> location=rtsp://HT1:%24hypothermicCamera1%23%23@192.168.0.30:88/videoMain !
> rtpjitterbuffer ! rtph264depay ! decodebin ! videoconvert ! x264enc !
> h264parse ! splitmuxsink location="/c1/record%07d.mp4"
> max-size-bytes=100000000 max-files=6000
>
> After that time it has only recorded about 1.8GB of footage and my disk has 2.7TB free, so space should not be a problem.
>
> Here's the error:
>
> ERROR: from element
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could not multiplex stream.
> Additional debug info:
> gstqtmux.c(4561): gst_qt_mux_add_buffer ():
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
> Buffer has no PTS.
> EOS on shutdown enabled -- waiting for EOS after Error Waiting for EOS...
> Redistribute latency...
>
> Any help would be appreciated!
>
> Best regards,
> Henk Schurink
>
>
>
> --
> Sent from: https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgstreamer-devel.966125.n4.nabble.com%2F&data=02%7C01%7C%7C5a7973958cb64a60671f08d769b20fe1%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C637094085794607841&sdata=m05n8UdM6PcqAMPfAVfNmTnbWOIHCt8fKtzpspgnbD8%3D&reserved=0
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7C01%7C%7C5a7973958cb64a60671f08d769b20fe1%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C637094085794607841&sdata=%2Bvffrquk5RdXajpXwh62J4eEG42iP6UVZoARTnFCFIk%3D&reserved=0
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

Henk Schurink

Re: AW: Pipeline fails after exactly 2.5 hours

In reply to this post by Thornton, Keith

Thornton, Keith wrote
> Hi,
> we have a similar problem caused by two frames with the same timestamp
> being sent down the pipeline. The h264parse plugin changes the timestamp
> of the second frame to CLOCK_TIME_NONE and the qtmux in splitmuxsink thows
> the buffer_has_no_PTS error
> You could try adding a pad_probe which detects this situation to confirm
> that you are suffering from the same problem.

Hello,

I've removed the h264parse element from my pipeline and now it's been
running steadily for the last 10 hours. I couldn't thank you enough! Best
regards.

--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

Thornton, Keith

AW: AW: Pipeline fails after exactly 2.5 hours

In reply to this post by Nicolas Dufresne-5

Hi,
we have a patch from Jan for our own use-case but he says it is generally difficult because the code is in BaseParser and this could have a detrimental effect for other parsers.
Gruesse

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel <[hidden email]> Im Auftrag von Nicolas Dufresne
Gesendet: Montag, 18. November 2019 19:32
An: Discussion of the development of and with GStreamer <[hidden email]>
Betreff: Re: AW: Pipeline fails after exactly 2.5 hours

Le lundi 18 novembre 2019 à 09:28 +0000, Thornton, Keith a écrit :
> Hi,
> we have a similar problem caused by two frames with the same timestamp
> being sent down the pipeline. The h264parse plugin changes the timestamp of the second frame to CLOCK_TIME_NONE and the qtmux in splitmuxsink thows the buffer_has_no_PTS error You could try adding a pad_probe which detects this situation to confirm that you are suffering from the same problem.

h264parse should not do that, seems like a bad idea. Did you file an issue ? Also, was this interlaced content ?

>
> -----Ursprüngliche Nachricht-----
> Von: gstreamer-devel <[hidden email]>
> Im Auftrag von Henk Schurink
> Gesendet: Freitag, 15. November 2019 10:52
> An: [hidden email]
> Betreff: Pipeline fails after exactly 2.5 hours
>
> Hello gstreamers,
>
> The following pipeline fails after exactly 2.5 hours every time:
>
> sudo gst-launch-1.0 -e rtspsrc
> location=rtsp://HT1:%24hypothermicCamera1%23%23@192.168.0.30:88/videoMain !
> rtpjitterbuffer ! rtph264depay ! decodebin ! videoconvert ! x264enc !
> h264parse ! splitmuxsink location="/c1/record%07d.mp4"
> max-size-bytes=100000000 max-files=6000
>
> After that time it has only recorded about 1.8GB of footage and my disk has 2.7TB free, so space should not be a problem.
>
> Here's the error:
>
> ERROR: from element
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could not multiplex stream.
> Additional debug info:
> gstqtmux.c(4561): gst_qt_mux_add_buffer ():
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
> Buffer has no PTS.
> EOS on shutdown enabled -- waiting for EOS after Error Waiting for EOS...
> Redistribute latency...
>
> Any help would be appreciated!
>
> Best regards,
> Henk Schurink
>
>
>
> --
> Sent from:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgstre
> amer-devel.966125.n4.nabble.com%2F&data=02%7C01%7C%7Ce3ffb26337734
> eb18fe508d76c56da14%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C63709
> 6992586929449&sdata=97Ihu0USqnchrDLxHffdiHx3%2BCOPF3begTEbkqWLkE4%
> 3D&reserved=0 _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist
> s.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7
> C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa
> 3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5G
> u9bu06vIssP2WWxTzfI%3D&reserved=0
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist
> s.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7
> C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa
> 3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5G
> u9bu06vIssP2WWxTzfI%3D&reserved=0

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5Gu9bu06vIssP2WWxTzfI%3D&reserved=0
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

David Ing

Re: AW: Pipeline fails after exactly 2.5 hours

Keith -- I would like to see that patch if you have a diff.

I have also observed some problems which may be attributable to this parsing error.

On Mon, Nov 18, 2019 at 11:01 PM Thornton, Keith <[hidden email]> wrote:

Hi,
we have a patch from Jan for our own use-case but he says it is generally difficult because the code is in BaseParser and this could have a detrimental effect for other parsers.
Gruesse

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel <[hidden email]> Im Auftrag von Nicolas Dufresne
Gesendet: Montag, 18. November 2019 19:32
An: Discussion of the development of and with GStreamer <[hidden email]>
Betreff: Re: AW: Pipeline fails after exactly 2.5 hours

Le lundi 18 novembre 2019 à 09:28 +0000, Thornton, Keith a écrit :
> Hi,
> we have a similar problem caused by two frames with the same timestamp
> being sent down the pipeline. The h264parse plugin changes the timestamp of the second frame to CLOCK_TIME_NONE and the qtmux in splitmuxsink thows the buffer_has_no_PTS error You could try adding a pad_probe which detects this situation to confirm that you are suffering from the same problem.

h264parse should not do that, seems like a bad idea. Did you file an issue ? Also, was this interlaced content ?

>
> -----Ursprüngliche Nachricht-----
> Von: gstreamer-devel <[hidden email]>
> Im Auftrag von Henk Schurink
> Gesendet: Freitag, 15. November 2019 10:52
> An: [hidden email]
> Betreff: Pipeline fails after exactly 2.5 hours
>
> Hello gstreamers,
>
> The following pipeline fails after exactly 2.5 hours every time:
>
> sudo gst-launch-1.0 -e rtspsrc
> location=rtsp://HT1:%24hypothermicCamera1%23%23@192.168.0.30:88/videoMain !
> rtpjitterbuffer ! rtph264depay ! decodebin ! videoconvert ! x264enc !
> h264parse ! splitmuxsink location="/c1/record%07d.mp4"
> max-size-bytes=100000000 max-files=6000
>
> After that time it has only recorded about 1.8GB of footage and my disk has 2.7TB free, so space should not be a problem.
>
> Here's the error:
>
> ERROR: from element
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could not multiplex stream.
> Additional debug info:
> gstqtmux.c(4561): gst_qt_mux_add_buffer ():
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
> Buffer has no PTS.
> EOS on shutdown enabled -- waiting for EOS after Error Waiting for EOS...
> Redistribute latency...
>
> Any help would be appreciated!
>
> Best regards,
> Henk Schurink
>
>
>
> --
> Sent from:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgstre
> amer-devel.966125.n4.nabble.com%2F&data=02%7C01%7C%7Ce3ffb26337734
> eb18fe508d76c56da14%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C63709
> 6992586929449&sdata=97Ihu0USqnchrDLxHffdiHx3%2BCOPF3begTEbkqWLkE4%
> 3D&reserved=0 _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist
> s.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7
> C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa
> 3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5G
> u9bu06vIssP2WWxTzfI%3D&reserved=0
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist
> s.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7
> C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa
> 3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5G
> u9bu06vIssP2WWxTzfI%3D&reserved=0

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5Gu9bu06vIssP2WWxTzfI%3D&reserved=0
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

Thornton, Keith

AW: AW: Pipeline fails after exactly 2.5 hours

Von: gstreamer-devel <[hidden email]> Im Auftrag von David Ing
Gesendet: Dienstag, 19. November 2019 18:21
An: Discussion of the development of and with GStreamer <[hidden email]>
Betreff: Re: AW: Pipeline fails after exactly 2.5 hours

Keith -- I would like to see that patch if you have a diff.

I have also observed some problems which may be attributable to this parsing error.

On Mon, Nov 18, 2019 at 11:01 PM Thornton, Keith <[hidden email]> wrote:

Hi,
we have a patch from Jan for our own use-case but he says it is generally difficult because the code is in BaseParser and this could have a detrimental effect for other parsers.
Gruesse

-----Ursprüngliche Nachricht-----
Von: gstreamer-devel <[hidden email]> Im Auftrag von Nicolas Dufresne
Gesendet: Montag, 18. November 2019 19:32
An: Discussion of the development of and with GStreamer <[hidden email]>
Betreff: Re: AW: Pipeline fails after exactly 2.5 hours

Le lundi 18 novembre 2019 à 09:28 +0000, Thornton, Keith a écrit :
> Hi,
> we have a similar problem caused by two frames with the same timestamp
> being sent down the pipeline. The h264parse plugin changes the timestamp of the second frame to CLOCK_TIME_NONE and the qtmux in splitmuxsink thows the buffer_has_no_PTS error You could try adding a pad_probe which detects this situation to confirm that you are suffering from the same problem.

h264parse should not do that, seems like a bad idea. Did you file an issue ? Also, was this interlaced content ?

>
> -----Ursprüngliche Nachricht-----
> Von: gstreamer-devel <[hidden email]>
> Im Auftrag von Henk Schurink
> Gesendet: Freitag, 15. November 2019 10:52
> An: [hidden email]
> Betreff: Pipeline fails after exactly 2.5 hours
>
> Hello gstreamers,
>
> The following pipeline fails after exactly 2.5 hours every time:
>
> sudo gst-launch-1.0 -e rtspsrc
> location=rtsp://HT1:%24hypothermicCamera1%23%23@192.168.0.30:88/videoMain !
> rtpjitterbuffer ! rtph264depay ! decodebin ! videoconvert ! x264enc !
> h264parse ! splitmuxsink location="/c1/record%07d.mp4"
> max-size-bytes=100000000 max-files=6000
>
> After that time it has only recorded about 1.8GB of footage and my disk has 2.7TB free, so space should not be a problem.
>
> Here's the error:
>
> ERROR: from element
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer: Could not multiplex stream.
> Additional debug info:
> gstqtmux.c(4561): gst_qt_mux_add_buffer ():
> /GstPipeline:pipeline0/GstSplitMuxSink:splitmuxsink0/GstMP4Mux:muxer:
> Buffer has no PTS.
> EOS on shutdown enabled -- waiting for EOS after Error Waiting for EOS...
> Redistribute latency...
>
> Any help would be appreciated!
>
> Best regards,
> Henk Schurink
>
>
>
> --
> Sent from:
> https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgstre
> amer-devel.966125.n4.nabble.com%2F&data=02%7C01%7C%7Ce3ffb26337734
> eb18fe508d76c56da14%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C63709
> 6992586929449&sdata=97Ihu0USqnchrDLxHffdiHx3%2BCOPF3begTEbkqWLkE4%
> 3D&reserved=0 _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist
> s.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7
> C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa
> 3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5G
> u9bu06vIssP2WWxTzfI%3D&reserved=0
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist
> s.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7
> C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa
> 3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5G
> u9bu06vIssP2WWxTzfI%3D&reserved=0

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freedesktop.org%2Fmailman%2Flistinfo%2Fgstreamer-devel&data=02%7C01%7C%7Ce3ffb26337734eb18fe508d76c56da14%7C28042244bb514cd680347776fa3703e8%7C1%7C0%7C637096992586939402&sdata=7ahSby4oxVraqY08dqHSlw5Gu9bu06vIssP2WWxTzfI%3D&reserved=0
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

0001-baseparse-Don-t-ignore-repeated-incoming-PTS.patch (4K) Download Attachment