Add tracker in deepstream-test3, error reported ,WHY?

  • deepstream-app version 6.0.1
  • DeepStreamSDK 6.0.1
  • CUDA Driver Version: 10.2
  • CUDA Runtime Version: 10.2
  • TensorRT Version: 8.2
  • cuDNN Version: 8.2
  • libNVWarp360 Version: 2.0.1d3

Add tracker in deepstream-test3, error reported ,WHY?
I added the tracker component to the code of deepstream-test3 and make a link, and run it and reported an error. If I do not add this tracker ,everything runs fine.

0:00:04.093635385 16016   0x55996bb8c0 INFO                 nvinfer gstnvinfer_impl.cpp:313:notifyLoadModelStatus:<primary-nvinference-engine> [UID 1]: Load new model:config_infer_primary.txt sucessfully
Decodebin child added: source
Decodebin child added: decodebin0
Running...
Decodebin child added: qtdemux0
Decodebin child added: multiqueue0
Decodebin child added: h264parse0
Decodebin child added: capsfilter0
Decodebin child added: aacparse0
Decodebin child added: faad0
Decodebin child added: nvv4l2decoder0
Opening in BLOCKING MODE 
NvMMLiteOpen : Block : BlockType = 261 
NVMEDIA: Reading vendor.tegra.display-size : status: 6 
NvMMLiteBlockCreate : Block : BlockType = 261 
In cb_newpad
In cb_newpad
Frame Number = 0 Number of objects = 7 Vehicle Count = 4 Person Count = 3
0:00:04.511904727 16016   0x55992e0800 WARN                 nvinfer gstnvinfer.cpp:2288:gst_nvinfer_output_loop:<primary-nvinference-engine> error: Internal data stream error.
0:00:04.511953878 16016   0x55992e0800 WARN                 nvinfer gstnvinfer.cpp:2288:gst_nvinfer_output_loop:<primary-nvinference-engine> error: streaming stopped, reason not-linked (-1)
ERROR from element primary-nvinference-engine: Internal data stream error.
Error details: /dvs/git/dirty/git-master_linux/deepstream/sdk/src/gst-plugins/gst-nvinfer/gstnvinfer.cpp(2288): gst_nvinfer_output_loop (): /GstPipeline:dstest3-pipeline/GstNvInfer:primary-nvinference-engine:
streaming stopped, reason not-linked (-1)
Frame Number = 1 Number of objects = 6 Vehicle Count = 3 Person Count = 3
Returned, stopping playback
Deleting pipeline

Process finished with exit code 0

Can you share your idea why do you add a tracker for test3? Test3 is a demo for using multiple sources and tracker is not needed for this case, you can refer test2 for tracker usage.

Thanks for your answer, I solved the problem because I didn’t initialize the tracker.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.