The latency measurement method used in python is just native bindings. latency measurement is implemented in C language.
Okay. I have also created the bindings for NvDsMetaCompLatency by following the steps in BINDINGSGUIDE.md and created a probe similar to the one mentioned here. I am able to access the components thru pyds. NvDsMetaCompLatency and print their latencies thru Python. These latencies match the component latency values which were printed when creating the bindings via cffi. However, my frame number is still 0 for both “bindings approaches” across batches. Please advise why this might be happening. It seems that in the underlying C-library might not be setting the frame number correctly?
Since I am using a single source currently, I could also extract the frame number value from NvDsBatchMeta.frame_meta_list.frame_num and use that instead of NvDsMetaCompLatency.frame_num. However, this will create an issue when I add more sources…