Deepstream Tracker FAQ

Tracker FAQ

This topic is a conclusion for Tracker related problems, following problems is a summary from DS 4.0 to latest DS version(5.0.1).

Standalone tracker sample:

We don’t have an official standalone sample, refer forum topic KLT NvMOT usage

DCF tracker:

We suggest to use latest DS version since we had fixed many tracker related issues to make the tracker more stable and robustness on latest DS version.

  1. Show 64-bit long Unique ID

    1. Set useUniqueID: 1 in tracker config
  2. Make tracker ID continues and reset ID

    1. Currently we don’t support the feature and user can do it by installing a probe and implementing it
    2. Related topic Track id not continuous
  3. Assign tracker ID per stream

    1. Disable batch processing mode
    2. Related topic Dcf tracker use same tracker to increase objectID in mutil stream
  4. Shadow tracking

    1. a per-object tracker is in inactive mode is called the shadow tracking, refer tracker plugin manual for more details
    2. Related topics Tracking info
  5. Track per class ID

    1. Use the per-class configuration in PGIE config and set threshold to be an infeasible high number like 100
    2. Related topics Track on the specified class-id
  6. Frequent ID switch w/o nearby objects

    1. Refer DCF tuning Doc for more details
    2. Related topics NVDCF Tracking Parameters Detailed Info
  7. Ghost bbox

    1. Refer DCF tuning Doc for more details
    2. How to smooth the bbox detections with the DCF tracking in DS5.0 GA?
  8. Tracker update frequency(related to motion dynamic)

    1. Try to tune the Moving-Average Estimator or Kalman Filter (based on the value of stateEstimatorType in your config)
    2. Related topics NvDCF tracker update frequency