There maybe a timestamping problem or this computer is too slow

Does anyone get this output with gstreamer?

I am trying out gstreamer with rtp from my latptop to nvidia xavier

My sender pipeline is as such

gst-launch-1.0 v4l2src ! videoconvert ! 'video/x-raw,format=(string)I420' ! x264enc ! rtph264pay ! udpsink host=127.0.0.1 port=1234

My client pipeline is as such

gst-launch-1.0 -vvv udpsrc port=1234 ! application/x-rtp,payload=96 ! rtph264depay ! avdec_h264 ! xvimagesink

I am getting the following output and my stream is slow and laggy too.

WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot of buffers are being dropped.
Additional debug info:
gstbasesink.c(2902): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot of buffers are being dropped.
Additional debug info:
gstbasesink.c(2902): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.
WARNING: from element /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0: A lot of buffers are being dropped.
Additional debug info:
gstbasesink.c(2902): gst_base_sink_is_too_late (): /GstPipeline:pipeline0/GstXvImageSink:xvimagesink0:
There may be a timestamping problem, or this computer is too slow.

Any help would be appreciated. Thank you!

Solution

How is the CPU usage at these occasions? I have no experience with this platform - may its intention be to run most things on the GPU (like video decoding and display).

Try sync=false for the video sink. It may still be laggy but no frames will be thrown away. So maybe some more info can be gained by observing this pipeline.

What about using autovideoconvert ! autovideosink as a sink instead of using xvimagesink?

Consider using the rtpbin element instead of manually doing the RTP part. The bin does a lot of smart buffering etc that may help here.

And of course double check that the problem does not happen on the laptop encoder side..