Please provide complete information as applicable to your setup.
• Hardware Platform (Jetson / GPU)
GPU
• DeepStream Version
6.0
• JetPack Version (valid for Jetson only)
• TensorRT Version
8.0.1.6
• NVIDIA GPU Driver Version (valid for GPU only)
470.86
• Issue Type( questions, new requirements, bugs)
Question/Bug?
• 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)
- Use the DeepStream reference application.
- Configure a pipeline to use two sources and also makes use of the MSG_CONV_BROKER sink, being sure to set a debug directory for the resulting converted messages. Also configure the sink to use the DEEPSTREAM_MINIMAL schema. Also make use of a primary inference engine and a tracker (in my case, the tracker is NvDCF and makes use of the libnvds_nvmultiobjectracker lib, with batch processing enabled along with past frame).
- Note that, at seemingly random intervals, a tracked object’s bounding box seems to have its (x, y) coordinates (i.e. “left” and “top”) doubled (unless the proper value is actually the doubled one in which case it’s halved).
I’ve checked and confirmed that the “scaleW” and “scaleH” values used in creating the DEEPSTREAM_MINIMAL payloads are both 1.0.
I don’t have this issue when using only a single source, so given that the difference is a factor of 2, I’m inclined to believe that something about the number of sources is doing something funny.
Perhaps I’ve configured something incorrectly, but I can’t figure out what since the bounding box jumps at random.
Any help would be greatly appreciated.
Thank you.