Please provide complete information as applicable to your setup.
• Hardware Platform (Jetson / GPU) Jetson
• DeepStream Version 6.0.1
• JetPack Version (valid for Jetson only) 4.6.2
• TensorRT Version 8.2.1.8
• NVIDIA GPU Driver Version (valid for GPU only)
• Issue Type( questions, new requirements, bugs) Questions
• 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) NvTracker
Hello, I’m using DeepStream with YoloV4 as a detector and NvDCF tracker to generate the bounding boxes for a real-time detection applicaiton. The detector works well however my target scenario is sometimes difficult, meaning that objects can be detected in one frame and then detected again only 10 or so frames after, by which time the object has moved. NvTracker is working in the background keeping a track of the object as it moves, however I get flickering of the bounding boxes.
I know that NvTracker is working because it keeps the same ID on each object after they have moved (say between a period of 10 frames) but it does not report any bounding box metadata in realtime. If I enable the reporting of past-frame data, I can see that NvTracker has stored the information of each tracklet however this method does not work in realtime.
Is it possible to access internal information about bboxes in shadow/tentative mode in realtime so I can display this on the OSD? Using the past-frame data is not useful for a realtime application as by this time the object has moved .
I think this thread describes the same issue - I do not think it has been fixed in Deepstream 6.0.1?
Thanks