<html><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> <style type="text/css">.style1 {font-family: "Times New Roman";}</style></head><body lang="DE" link="blue" vlink="purple"> <div class="WordSection1"> Hi all,<o:p></o:p> <o:p> </o:p> sorry 4 my late response. I had a lot of work during the last two weeks. <o:p></o:p> <o:p> </o:p> I want to thank Nicolas and Victor for fast response and very good input!<o:p></o:p> <o:p> </o:p> I fixed the issue by using a rtpjitterbuffer in combination with the low-latency flag. Without the rtpjitterbuffer the image is getting teared. So I guess it’s necessary in this case.<o:p></o:p> <o:p> </o:p> The following pipeline works quite well in my case:<o:p></o:p> <o:p> </o:p> gst-launch-1.0 udpsrc port=55555 caps="application/x-rtp,media=(string)video,clock-rate=(int)90000, encoding-name=(string)H264, payload=(int)96" ! rtpjitterbuffer latency=10 ! rtph264depay ! vaapih264dec low-latency=true ! vaapipostproc ! kmssink<o:p></o:p> <o:p> </o:p> Timestamping the sink did not improve the misbehavior. <o:p></o:p> <o:p> </o:p> Best regards,<o:p></o:p> Michael<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Von: gstreamer-devel [mailto:gstreamer-devel-bounces@lists.freedesktop.org] Im Auftrag von Nicolas Dufresne Gesendet: Donnerstag, 16. Juli 2020 14:33 An: Discussion of the development of and with GStreamer <gstreamer-devel@lists.freedesktop.org> Betreff: [External] Re: Streaming freezes (vaapi or v4l2src)<o:p></o:p> <o:p> </o:p> <div> <div> <o:p> </o:p> <div> <div> Le jeu. 16 juill. 2020 04 h 00, Timtchenko, Michael <<a href="mailto:Michael.Timtchenko@agcocorp.com">Michael.Timtchenko@agcocorp.com</a>> a écrit :<o:p></o:p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt"> <div> <div> Hello guys,<o:p></o:p> <o:p></o:p> i’ve encountered a very strange behavior while streaming from a v4l2src to a kmssink (or glimagesink) by using vaapi-components for decoding. The problem is, that the streaming starts for 2 seconds, then freezes for 2 seconds and continues again for 2 seconds and so on. This effect is only noticeable when using vaapi-components. If I use a pipeline with simply software decoding, the stream is displayed fluently.<o:p></o:p> </div> </div> </blockquote> </div> </div> <div> Two seconds could be the key frame distance ?<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> <o:p> </o:p> </div> <div> <div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt"> <div> <div> <o:p></o:p> My sending pipeline is constructed as follows:<o:p></o:p> <o:p></o:p> gst-launch-1.0 v4l2src io-mode=dmabuf device=/dev/video$(($1+4)) ! video/x-raw,format=YV12,width=720,height=576 ! v4l2h264enc ! rtph264pay ! udpsink host=${IP} port=55555<o:p></o:p> </div> </div> </blockquote> </div> </div> <div> v4l2h264enc has this extra-controls property that let you genetically change he specific configuration, just an information.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> <o:p> </o:p> </div> <div> <div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt"> <div> <div> <o:p></o:p> Setting pipeline to PAUSED ...<o:p></o:p> Pipeline is live and does not need PREROLL ...<o:p></o:p> Setting pipeline to PLAYING ...<o:p></o:p> New clock: GstSystemClock<o:p></o:p> Redistribute latency...<o:p></o:p> <o:p></o:p> The erroneous reading pipeline looks like this:<o:p></o:p> <o:p></o:p> gst-launch-1.0 udpsrc port=55555 caps="application/x-rtp,media=(string)video,clock-rate=(int)90000, encoding-name=(string)H264, payload=(int)96" ! rtph264depay ! vaapih264dec ! vaapipostproc width=720 height=576 ! glimagesink<o:p></o:p> </div> </div> </blockquote> </div> </div> <div> <o:p> </o:p> </div> <div> One thing to note is the absence of rtpjitterbuffer element, which would allow adding some latency to remove network jitter. So that is one thing to try.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Another possibility is that the issue is cause by vaaph264dec having more latency then avdec_h264. Perhaps give the low-latency property a try ?<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> Let's hope one of these suggestions helps.<o:p></o:p> </div> <div> <o:p> </o:p> </div> <div> <div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-bottom:5.0pt"> <div> <div> <o:p></o:p> Setting pipeline to PAUSED ...<o:p></o:p> Pipeline is live and does not need PREROLL ...<o:p></o:p> Got context from element 'vaapipostproc0': gst.vaapi.Display=context, gst.vaapi.Display=(GstVaapiDisplay)"$GstVaapiDisplayDRM$\ vaapidisplaydrm1";<o:p></o:p> Setting pipeline to PLAYING ...<o:p></o:p> New clock: GstSystemClock<o:p></o:p> Redistribute latency...<o:p></o:p> WARNING: from element /GstPipeline:pipeline0/GstKMSSink:kmssink0: A lot of buffers are being dropped.<o:p></o:p> Additional debug info:<o:p></o:p> ../libs/gst/base/gstbasesink.c(3005): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstKMSSink:kmssink0:<o:p></o:p> There may be a timestamping problem, or this computer is too slow.<o:p></o:p> WARNING: from element /GstPipeline:pipeline0/GstKMSSink:kmssink0: A lot of buffers are being dropped.<o:p></o:p> Additional debug info:<o:p></o:p> ../libs/gst/base/gstbasesink.c(3005): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstKMSSink:kmssink0:<o:p></o:p> There may be a timestamping problem, or this computer is too slow.<o:p></o:p> <o:p></o:p> If I run the following pipeline on the same system, the stream is presented fluently without any problems:<o:p></o:p> <o:p></o:p> gst-launch-1. 0 udpsrc port=55555 caps=\"application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264, payload=(int)96\" ! rtph264depay ! avdec_h264 ! decodebin ! videoconvert ! kmssink<o:p></o:p> <o:p></o:p> I’m not sure what exactly the problem is. Maybe the timestamping mechanism in vaapi has a different behavior then in the avdec_h264 as the log message says? I’ve also changed log levels but I couldn’t find anything helpful. <o:p></o:p> <o:p></o:p> Any help for further diagnostics is highly appreciated. <o:p></o:p> <o:p></o:p> Kind regards<o:p></o:p> Michael<o:p></o:p> <o:p></o:p> <o:p></o:p> <o:p></o:p> </div> <o:p> </o:p> <div> Bitte beachten / Please note!<o:p></o:p> <div> ******************************************************************************* <o:p> </o:p> AGCO GmbH Sitz der AGCO GmbH: Johann-Georg-Fendt-Str.4, 87616 Marktoberdorf, Germany Registergericht Amtsgericht Kempten HRB 10327 Geschäftsführer: Christoph Groeblinghoff, Ingrid Bussjaeger-Martin, Dr. Heribert Reiter, Ekkehart Glaeser Vorsitzender des Aufsichtsrates: Torsten Dehner<o:p></o:p> ******************************************************************************* <o:p></o:p> Diese E-Mail ist nur für den Empfänger bestimmt, an den es gerichtet ist und kann vertrauliches bzw. unter das Berufsgeheimnis fallendes Material enthalten. Jegliche darin enthaltene Ansicht oder Meinungsäußerung ist die des Autors und stellt nicht notwendigerweise die Ansicht oder Meinung von AGCO dar. Sind Sie nicht der Empfänger, so haben Sie diese E-Mail irrtümlich erhalten und jegliche Verwendung, Veröffentlichung, Weiterleitung, Abschrift oder jeglicher Druck dieser E-Mail ist strengstens untersagt. Weder AGCO noch der Absender übernehmen die Haftung für Viren; es obliegt Ihrer Verantwortung, die E-Mail und deren angehängte Dateien (sofern vorhanden) auf Viren zu überprüfen.<o:p></o:p> ******************************************************************************* <o:p></o:p> This email is intended solely for the use of the individual to whom it is addressed and may contain confidential and/or privileged material. Any views or opinions presented are solely those of the author and do not necessarily represent those of AGCO. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Neither AGCO nor the sender accepts any responsibility for viruses and it is your responsibility to scan and virus check the email and its attachment(s) (if any).<o:p></o:p> ******************************************************************************* <o:p></o:p> </div> </div> </div> _______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.freedesktop.org" target="_blank">gstreamer-devel@lists.freedesktop.org</a> <a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><o:p></o:p> </blockquote> </div> </div> </div> </div> This email is intended solely for the use of the individual to whom it is addressed and may contain confidential and/or privileged material. Any views or opinions presented are solely those of the author and do not necessarily represent those of AGCO. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Neither AGCO nor the sender accepts any responsibility for viruses and it is your responsibility to scan and virus check the e-mail and its attachment(s) (if any). This email is intended solely for the use of the individual to whom it is addressed and may contain confidential and/or privileged material. Any views or opinions presented are solely those of the author and do not necessarily represent those of AGCO. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing or copying of this email is strictly prohibited. Neither AGCO nor the sender accepts any responsibility for viruses and it is your responsibility to scan and virus check the e-mail and its attachment(s) (if any). . . , . . . </body></html>