NvDsObjectMeta.parent set to None After Passing Through Gst-nvvideoconvert

Accelerated Computing Intelligent Video Analytics DeepStream SDK
1

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU)
GPU
• DeepStream Version
7.0
• JetPack Version (valid for Jetson only)
• TensorRT Version
8.6
• NVIDIA GPU Driver Version (valid for GPU only)
550.107.02
• Issue Type( questions, new requirements, bugs)
bugs
• 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)

Previously, I mentioned that the parent variable in the NvDsObjectMeta class was being set to None when adding a non-NVIDIA GStreamer component, as referenced in this post:

However, after running some tests, I noticed that the component actually responsible for setting NvDsObjectMeta.parent to None is Gst-nvvideoconvert.

What’s interesting is that all other metadata remains intact, but specifically, NvDsObjectMeta.parent is set to None after the metadata passes through Gst-nvvideoconvert.

Could someone explain why only the parent field is affected and whether there’s a workaround for this behavior?

3

This problem is because when metadata is processed between different elements, it may be copied.

When metadata is copied, NvDsObjectMeta.parent may be set to None. This is not a bug, but may be a limitation of the element.

In addition, the nvvideoconvert you mentioned above also causes this problem because gst-buffer is copied.

We do not recommend adding a probe function to the src/sink pad of the downstream element to obtain metadata. It is best practice to obtain it when needed

1 Like
5

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