Nvmultiurisrcbin can not open rtsp

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU) GPU RTX3090
• DeepStream Version 7.1 DOCKER

use command start gst-launch-1.0 nvmultiurisrcbin port=9999 ip-address=localhost batched-push-timeout=33333 max-batch-size=10 drop-pipeline-eos=1 live-source=1 width=2560 height=1440 ! nvmultistreamtiler ! nveglglessink

when add a stream start with file://, the pipeline can run normally.

when add a stream start with rtsp, example rtsp://xxxxxxxxx:8558/card/4

root@ps:/tmp/data/api# gst-launch-1.0 nvmultiurisrcbin port=9999 ip-address=localhost batched-push-timeout=33333 max-batch-size=10 drop-pipeline-eos=1 live-source=1 width=2560 height=1440 ! nvmultistreamtiler ! nveglglessink
Setting pipeline to PAUSED ...
Civetweb version: v1.16
Server running at port: 9999
Pipeline is PREROLLING ...
Got context from element 'eglglessink0': gst.egl.EGLDisplay=context, display=(GstEGLDisplay)NULL;
uri:/api/v1/stream/add
method:POST
uri:/api/v1/stream/add
method:POST
Progress: (open) Opening Stream
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://xxxxxxx:8558/card/4
Progress: (connect) Connecting to rtsp://xxxxxx:8558/card/4
Progress: (open) Retrieving server options
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 1
Progress: (request) SETUP stream 1
Progress: (open) Opened Stream
Progress: (open) Opened Stream

the rtsp stream can use VLC or ffplay open

why?

I think this is a bug, I can reproduce.
1.There is a workaround. When starting the pipeline, set uri-list=file://xxxx property to nvmultiurisrcbin.
Then add rtsp stream and it will work fine

2.It’s opensource, you can debug it.
/opt/nvidia/deepstream/deepstream/sources/gst-plugins/gst-nvmultiurisrcbin and /opt/nvidia/deepstream/deepstream/sources/gst-plugins/gst-nvurisrcbin.

I think this issue is caused by the different processing flow of nvurisrcbin for file/rtsp uri

i will test first

The second method Looking forward to the official announcement.

This is a very serious bug, is there a way to fix it quickly? The first solution is not very ideal.

This problem is related to gst-launch-1.0, but deepstream-test5 works fine, you can refer to it.

Comment the uri list

 [source-list]
 num-source-bins=2
-list=file:///opt/nvidia/deepstream/deepstream/samples/streams/sample_1080p_h264.mp4;file:///opt/nvidia/deepstream/deepstream/samples/streams/sample_1080p_h265.mp4
+#list=file:///opt/nvidia/deepstream/deepstream/samples/streams/sample_1080p_h264.mp4;file:///opt/nvidia/deepstream/deepstream/samples/streams/sample_1080p_h265.mp4
 use-nvmultiurisrcbin=1
 #To display stream name in FPS log, set stream-name-display=1
 stream-name-display=0
@@ -46,7 +46,7 @@ http-port=9000

Run deepstream-test5-app

./deepstream-test5-app -c configs/test5_config_file_nvmultiurisrcbin_src_list_attr_all.txt -p 1

i use python build pipeline, found when start loop, add rtsp stream, do not start process

Therefore, I used gst-launch-1.0 for verification.

service maker python no such bug.