Deepstream frame latency: frame number still stuck at zero (DS6, JP4.6)

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU) Xavier AGX
• DeepStream Version 6.0
• JetPack Version (valid for Jetson only) 4.6
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only)
• Issue Type( questions, new requirements, bugs)
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)


Please see attached screenshot for latencies. The frame number is stuck at zero and no sensible frame latencies are reports.


Im using a USB camera and no changes to deepstream-app/config apart from the source part of the config (for USB camera).

Maybe you can try it in-house with a USB camera, its simple to try… I’m using a logitech 1080p fps 30. The only changes from a clean install is in the deepstream_app_config_yoloV3.txt:

[source 0]



The issue you mentioned reproed, we are investigating if it’s expected or a bug. and feedback if any progress.

Latency instrumentation for DS is not in open source. You can insert a probe on source pad of v4l2 source, start the timer, insert another probe at sink pad of sink component. Time difference between the two will give the latency of the buffer.

1 Like

Can’t we write the python bindings for nvds_measure_buffer_latency() api??

You can insert a probe on source pad of v4l2 source, start the timer, insert another probe at sink pad of sink component.

Python binding open sourced, you can write python binidings for nvds_measure_buffer_latency

but I could not find the C code for nvds_measure_buffer_latency() api in deepstream 5.1.
Can I get some tips on writing the binding…??

As for this, there one bug for frame latency for camera source input. that’s why suggested as this. we have bug tracking internally.

For the file input will it work?

It’s mainly for rtsp source, but for file source also working, only v4l2decoder component get a more larger latency.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.