I run this pipeline on multiple RTSP cameras, Right after the pipeline starts, some cameras throw EOS.
What else I have done so far, I run the pipeline with gst-launch uridecodebin ! fakesink, I dont get any EOS signal, not sure if this is even a right and/or complete test that concludes anything.
I am trying to understand what can be happening and what exactly is causing this issue ?
Please check every camera with “gst-launch uridecodebin ! fakesink”.
please check if the simplified pipeline "gst-launch uridecodebin ! nvstreammux ! fakesink " is fine with one camera. please refer to this faq for how to set nvstreammux parameters.
if fine in the step 2, You can continue to add more cameras. If still can’t work, please share a running log.
what is the complete gst-launch cmd? do you mean “gst-launch uridecodebin ! fakesink” works well for each camera?
Did the application stop at the beginning or after a while? From the log “RROR from source: Could not read from resource.”, it is because receiving RTSP stream failed.
To narrow down the issue, could you share the three logs of running app with only source 7, running app with only source 1, and running app with source 7&&1? Thanks!
what I understand now is that, it is not only related to a certain streams. Any out of 8 streams can get into this problem.
here are the logs.
user@user-Default-string:~/hawkEdge$ gst-launch-1.0 uridecodebin uri="rtsp://root:pass@ip:port/live.sdp" ! fakesink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Pipeline is PREROLLED ...
Prerolled, waiting for progress to finish...
Progress: (connect) Connecting to rtsp://root:pass@ip:port/live.sdp
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 1
Progress: (request) SETUP stream 2
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Progress: (request) Sending PLAY request
Redistribute latency...
Redistribute latency...
Redistribute latency...
Redistribute latency...
Progress: (request) Sending PLAY request
Redistribute latency...
Redistribute latency...
Progress: (request) Sent PLAY request
Redistribute latency...
Redistribute latency...
Redistribute latency...
Redistribute latency...
Redistribute latency...
Redistribute latency...
WARNING: from element /GstPipeline:pipeline0/GstURIDecodeBin:uridecodebin0/GstRTSPSrc:source: Could not read from resource.
Additional debug info:
../gst/rtsp/gstrtspsrc.c(5819): gst_rtspsrc_loop_udp (): /GstPipeline:pipeline0/GstURIDecodeBin:uridecodebin0/GstRTSPSrc:source:
The server closed the connection.
I am using uridecodebin in the pipeline as the source element.
From the logs.txt, there is “timeout on UDP port” printing and there is not rtpjitterbuffer receiving printing. hence please rule out the RTSP receiving issue first. Please share the log 1.log after running the following cmd.
gst-launch-1.0 --gst-debug-level=5 rtspsrc location=“rtsp://root:pass@ip:port/live.sdp” ! fakesink >1.log 2>1.log
If it still run into the same issue, Please fix the RTSP receiving stream issue first. For example, please make sure the camera supports the standard RTSP protocol and the network supports RTP transmitting.
From the log 1.log, the app run into the same issue “The server closed the connection” after about one minute. Since there is no DeepStream plugin in the receiving stream pipeline(rtspsrc-> fakesink), this receiving issue would be outside of DeepStream. You may ask the camera vendoer how to get a stable stream. Thanks!