AW: rtspsrc - protocols=tcp EOS 8 seconds
mhaines4102
mhaines4102 at gmail.com
Mon Apr 5 16:16:47 UTC 2021
Ping... Sorry guys. Trying to get this looked at again.
gst-launch-1.0 version 1.14.5
New Testing. Changed resolution and FPM as well as i-frames. No change.
Definitely caused by a timeout.
on_timeout_common (GObject * session, GObject * source, GstRTSPStream *
stream)
Which activities would cause an on_timeout when using exclusively TCP in
protocols?
The rtsp server is producing video with sound embedded h264.
Could it be because I am not doing anything with audio? Stream0 is timing
out.
rtspsrc gstrtspsrc.c:3155:on_timeout:<rtspsrc0>
^[[00m source 73fb5375, stream 73fb5375 in session 2 timed outtask
gsttask.c:316:gst_task_func:<rtpjitterbuffer0:src>
Non verbose run. Very typical.
gst-launch-1.0 -e rtspsrc location=rtsp://User:Password@camera0/live2.sdp
protocols=tcp ! fakesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://viewer:Ascent2018@camera0/live2.sdp
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 1
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Progress: (request) Sending PLAY request
Progress: (request) Sending PLAY request
Progress: (request) Sent PLAY request
Got EOS from element "pipeline0".
Execution ended after 0:00:07.763174573
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...
--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
More information about the gstreamer-devel
mailing list