<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> And/or on a h265parse element behind the encoder. In fact, you'll probably need both Nicolas' and Nick's suggestions: the receiver needs both a key frame and the information the config-interval inserts into the stream (<a moz-do-not-send="true" href="https://www.quora.com/What-are-SPS-and-PPS-in-video-codecs">SPS and PPS</a>) to start decoding. I don't know why it would work with h264; I'd expect the same issue. Kind regards, Michiel <div class="moz-cite-prefix">On 18-01-2021 08:33, Marc Leeman wrote: </div> <blockquote type="cite" cite="mid:CAH+fs=9Y1yO145bUFngvb+Y=oxQ7+0XfOLBc169cYZDRo3LG1w@mail.gmail.com"> <pre class="moz-quote-pre" wrap="">use config-interfal with the payloader. On Thu, 14 Jan 2021 at 14:00, mp <a class="moz-txt-link-rfc2396E" href="mailto:tevzpoberznik@gmail.com"><tevzpoberznik@gmail.com></a> wrote: </pre> <blockquote type="cite"> <pre class="moz-quote-pre" wrap=""> Hello! I have a problem with streaming H.265 video on UDP as it works only when the receiver starts listening BEFORE the sender starts streaming. It is the same for MPEG-TS and RTP protocol. With H.264 there is no such problem. Exemplary sender pipeline: gst-launch-1.0 v4l2src device=/dev/video0 ! decodebin ! videoconvert ! "video/x-raw, format=(string)I420" ! x265enc name=encoder ! 'video/x-h265, stream-format=(string)byte-stream, alignment=(string)au' ! rtph265pay mtu=1400 ! udpsink host=127.0.0.1 port=1234 Exemplary receiver pipeline: gst-launch-1.0 -v udpsrc port=1234 do-timestamp=true ! application/x-rtp,encoding-name=H265,payload=96 ! rtph265depay ! h265parse ! queue ! avdec_h265 ! xvimagesink Does anyone have any idea how to solve this problem? Thanks, best regards, Matevz </pre> </blockquote> </blockquote> </body> </html>