mpegts latency

Michael Gruner michael.gruner at ridgerun.com
Thu Aug 1 13:13:21 UTC 2019


You are likely losing your H264 reference frame and the encoder is not generating another one. Try setting the encoders “key-int-max=30” (or some prudential value) to force periodical generation.

Michael
www.ridgerun.com

> On Aug 1, 2019, at 1:27 AM, TheGiamig <thegiamig at gmail.com> wrote:
> 
> Thanks for your responses, I removed the unwanted latency putting
> autovideosink sync=false.
> At the moment is a good workaround for me, I'm just trying to understand how
> all the thing works..
> 
> So now I can capture a portion of desktop, encode in h264 and put out a
> mpegts stream.
> Next step is the streaming over network.
> I just pushed the stream in a udpsink and on the other side got it by
> udpsrc:
> 
> sender:
> gst-launch-1.0.exe dx9screencapsrc x=0 y=0 width=800 height=600 !
> videoconvert  ! queue ! x264enc tune=zerolatency speed-preset=ultrafast
> byte-stream=true ! mpegtsmux alignment=7 ! queue ! udpsink host=127.0.0.1
> port=5000
> 
> receiver:
> gst-launch-1.0 udpsrc address=127.0.0.1 port=5000 ! tsdemux ! queue !
> decodebin ! videoconvert ! autovideosink sync=false
> 
> This way the video is corrupted, when the image changes fastly I got strange
> pixels, green or grey areas and so on. It seems some data will be lost. It
> can be normal on internet, but on 127.0.0.1..
> 
> I got the same result using RTP instead of mpegts.
> 
> So I replaced udpink and udpsrc with tcpclientsink and tcpserversrc and the
> problem goes away.
> 
> What do you think about?
> 
> Thanks
> 
> 
> 
> 
> 
> 
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel


More information about the gstreamer-devel mailing list