Nvurisrcbin Occasional Malfunction

[zyann]

• Hardware Platform (Jetson / GPU) Jetson orin nx 8g
• DeepStream Version 7.0
• JetPack Version (valid for Jetson only) 6.0 L4T 36.3.0
• Issue Type( questions, new requirements, bugs) bugs
I have never encountered issues when using nvurisrcbin to read RTSP streams from a camera. However, I have noticed that this plugin occasionally malfunctions when reading RTSP streams forwarded by a GStreamer RTSP server. Specifically, it repeatedly triggers reconnection attempts but fails to connect, even though the RTSP stream can be successfully opened with VLC, PotPlayer, or FFplay.

Unfortunately, this issue does not occur consistently; it only happens intermittently, so I’m not sure if you will be able to reproduce it.

I have constructed two simple pipelines to test this bug. The first pipeline uses nvurisrcbin to loop-read a file and forward it via nvrtspoutsinkbin:

sudo gst-launch-1.0 nvurisrcbin uri=file:///home/nvidia/tunnel.mp4 file-loop=1 ! nvrtspoutsinkbin rtsp-port=10000

The second pipeline is:

sudo gst-launch-1.0 nvurisrcbin uri=rtsp://localhost:10000/ds-test rtsp-reconnect-interval=5 ! nvrtspoutsinkbin

Test Video:

tunnel.zip (11.3 MB)

Output Log:

logs.txt (43.4 KB)

[fanzh]

I am checking.

[zyann]

My testing method involves keeping the first pipeline constant while continuously stopping and rerunning the second pipeline with Ctrl+C to simulate a stream reconnection scenario. This intermittently results in the issue described above.

I am currently developing with DeepStream 6.2. In this version, when the second pipeline reconnects, there is a chance that nvurisrcbin gets blocked, displaying a “No data from source” error. The plugin’s reconnection mechanism does not get triggered.

Therefore, I tested with the latest version of DeepStream. While the reconnection works normally compared to version 6.2, the problem does not seem to be completely resolved.

[fanzh]

5 second is too short. you can use rtsp-reconnect-interval=15.

[zyann]

Thank you, I tried increasing the latency parameter of nvurisrcbin, and after raising it to a certain value, this problem no longer occurred.