RTSP-Streaming

Thornton, Keith keith.thornton at zeiss.com
Fri Sep 29 11:32:11 UTC 2017


Hi,
when I stream with the following pipelines everything works as expected

Server
test-launch "( videotestsrc do-timestamp=true is-live=true pattern=smpte horizontal-speed=5 ! video/x-raw,width=1920,height=1080,framerate=60000/1001,format=NV12 ! queue name=encode-queue max-size-bytes=124416000 ! x264enc ! video/x-h264,stream-format=byte-stream ! h264parse ! rtph264pay name=pay0 config-interval=10 pt=96 )");

client
gst-launch-1.0 -v -e rtspsrc location=rtsp://192.168.0.5:8554/live ! rtph264depay ! h264parse ! capsfilter caps="video/x-h264,width=1920,height=1080,framerate=(fraction)60000/1001" ! avdec_h264 ! identity silent=false ! fpsdisplaysink sync=true

When I implement the server in my code using the test_appsrc.c as muster
The appsrc part of the pipeline is
"( appsrc name=MyHQSrc min-latency=500000000 format=3  rtph264pay name=pay0 config-interval=10 pt=96 )"

The buffers arrive at the client with different timestamps from those which my encoder sets which are monotonously incrementing DTS and PTS=GST_CLOCK_TIME_NONE.
Can it be that appsink / appsrc re-stamps the buffers with incrementing PTS timestamps.

The consequence is that the demuxer on the client side complains about decreasing timestamps every third or fourth buffer.
Grüße

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20170929/757304ab/attachment.html>


More information about the gstreamer-devel mailing list