Problems with decoding RTSP sources in deepstream

[claudio.campuzano.b]

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU): GPU
• DeepStream Version: 5.1
• NVIDIA GPU Driver Version: 470.82.01
• Issue Type: bugs
• How to reproduce the issue ?: When I run the deepstream test applications (deepstream-app or deepstream-test-5), and from sources I assign multiple RTSP signals to it
• Requirement details:

What happens is that when processing the RTSP signals, in the deepstream output there are “blurs” (both in rtsp-sink and file-sink)(attached image). We believe that Ds is decoding the rtsp signals wrongly and that due to these “blurs” we make bad detections and classifications, in addition to obtaining a bad output image. Is there any way to correct this? As additional information, when the original RTSP signals are reproduced by means of vlc or ffmpeg, these “blurs” are not shown.
Stream detail:
Stream #0:0: Video: h264 (Main), yuv420p(progressive), 640x480, 30 fps, 30 tbr, 90k tbn, 60 tbc

[gharbv]

rtsp cam maybe has bit rate parameter, the value need larger.

[Fiona.Chen]

What is the original resolution of your camera? Can you dump ES stream and provide it for us to analysis?

[Fiona.Chen]

@claudio.campuzano.b

in the deepstream output there are “blurs” (both in rtsp-sink and file-sink)

Can you config larger [nvstreammux] resolution with deepstream-app config file? It is better to be the same as the original resolution of your camera. DeepStream Reference Application - deepstream-app — DeepStream 6.3 Release documentation. Please set proper “width” and “height” for nvstreammux.