For your case, you may add “obj-cnt-win-in-ms” cfg to make nvanalytics use the point closer to center coordinate (x_left + width/2, y_top + height). please refer to this cfg.config_nvdsanalytics.txt (206 Bytes)
Hi, thanks for the suggestion! I have a couple of follow‑up questions to better understand:
What exactly does the obj-cnt-win-in-ms parameter control in nvdsanalytics?
You mentioned “make nvanalytics use the point closer to center coordinate (x_left + width/2, y_top + height)”. From my understanding, the analytics plugin already uses the bottom‑center of the bounding box (x_left + width/2, y_top + height). Could you clarify how obj-cnt-win-in-ms changes that behavior?
In my video, the bottom center is within the ROI, so why isn’t it working?
Could you also share a small example of how to configure this parameter in config_nvdsanalytics.txt (and the effect of different values)?
1&&2. nvdsanalytcs uses the bboxes of the same object in the consecutive frames. “obj-cnt-win-in-ms” is a window for object count. The smaller the value, the fewer frames are used.
3. from my test, if using “obj-cnt-win-in-ms=1”, when the bottom center is within the ROI, the count will increase.
4. please refer to my last comment.