Issue with Converting ONNX Model with different dimensions to TensorRT Engine for DeepStream

[junshengy]

@hema.ganaparthi

I observe a latency between the OSD display and the processing. Specifically, after processing four frames,

This is usually not related to OSD, but is usually caused by RTSP camera. You also need to check the timing of nvinfer and the GPU load.

You can use local file to measure latency. Refer to this FAQ

DeepStream SDK FAQ

7. [DS 5.0GA_All_App] Enable Latency measurement for deepstream sample apps If you are using deepstream-app, to check the component latency directly, you need to set the env export NVDS_ENABLE_COMPONENT_LATENCY_MEASUREMENT=1 export NVDS_ENABLE_LATENCY_MEASUREMENT=1 If you are using other deepstream sample apps such as deepstream-test3, you need to apply the following patch and set the env export NVDS_ENABLE_COMPONENT_LATENCY_MEASUREMENT=1 export NVDS_ENABLE_LATENCY_MEASUREMENT=1 …

@hema.ganaparthi

Because, it is not acceptable to detect the object after a 1-2 seconds delay while it is standing in front of the camera.

The latency of rtsp camera is usually 1-2s. Lower latency requires smaller I frame intervals and UDP transmission, which requires high network quality, otherwise it will cause packet loss, screen distortion and other problems.

In addition, if you only use gst-play-1.0 to play the rtsp stream, what is the latency?

Try setting the value of the live-source property of nvstreammux to true.

We have discussed too many topics in this topic. Please open a new topic for other questions.