Distinguish NV_DS_SOURCE_RTSP and NV_DS_SOURCE_URI

[nguyencongthuyen]

Hi all,
I’m running an application to detect objects from 8 rtsp streams.
If i configure source type as NV_DS_SOURCE_RTSP, there is some broken image when i dump and save to Minio

If i change source type to NV_DS_SOURCE_URI, this phenomenon has gone but there is big delay of processing image.

Anyone can help me to explain the different between NV_DS_SOURCE_RTSP and NV_DS_SOURCE_URI.
and how to fix broken image problem?

It is my detail setup:

• Hardware Platform (Jetson / GPU) : Jetson Xavier
• DeepStream Version 6.0
• JetPack Version 4.6

[DaneLLL]

Hi,
The implementation is open source. Please check

/opt/nvidia/deepstream/deepstream-6.0/sources/apps/apps-common/src/deepstream_source_bin.c

Main difference is that NV_DS_SOURCE_URI uses uridecodebin and NV_DS_SOURCE_RTSP uses rtspsrc. From the scene it seems like the h264 stream is incomplete and cannot be well decoded. We suggest set and adjust latency for try. The properties are listed in
DeepStream Reference Application - deepstream-app — DeepStream 6.1.1 Release documentation

[nguyencongthuyen]

Thank you!
btw, should I change to h265 stream for less latency?

[DaneLLL]

Hi,
There should be no much difference in latency between h264 and h265, but you may give it a try.