Please provide complete information as applicable to your setup.
• Hardware Platform (Jetson / GPU):jetson • DeepStream Version:6.3 • JetPack Version (valid for Jetson only):5.1.3 pipelinetest.pdf (36.9 KB)
The uploaded PDF file is my pipeline. I added a probe function after the src pad of the stacker plugin. Its function is to request external devices to obtain the confidence level required for detecting objects after the pipeline is started, and then request that objects with lower confidence levels not be drawn and displayed on the exported video stream. The following is the code for the probe function. After testing and printing, the above code cannot achieve the function I want. Why is this?
Due to practical needs, different scenarios require configuring different categories, and which categories need to be loaded into the pipeline before knowing. I understand the method you mentioned, so the question says’ the pipeline has already been loaded '. Therefore, please reply directly to me with this question
so professional, so professional, The method you mentioned is effective, but there is a new issue. I have found that the confidence level of the obj_sta generated by the nvtracker plugin as NUll or tracking module is less than 0, right? Because I found that when my probe function is added to the src pad of the tracking plugin and the code is as follows, I set the inference interval to 10 frames. Even with tracking, the frames drawn in the streaming video still appear one by one. After investigation, I discovered this problem.So do I need to add my confidence filtering probe function after the src probe in the Nvidian plugin? Because if it is added after the tracker src pad, it will erroneously delete the drawing data of other categories? Is that so?
yes, tracker will add object meta for tracked objects if the objects don’t appear in current frame. you can add the probe on sink of tracker to filter the objects.
Thank you for your reply. The method you mentioned is effective, but I encountered a new issue when I tried to use gst_ element_state (pipeline ->pipeline, GST_STATE_NULL); When the code destroys the pipeline, the processing in the probe function will report a segmentation error. Do I need to remove all probe functions before executing the code, or is there any other good way?
There is no update from you for a period, assuming this is not an issue anymore. Hence we are closing this topic. If need further support, please open a new one. Thanks