Gst-nvdsmetamux
The Gst-nvdsmetamux plugin is a NvDsBatchMeta utils plugin which forms new NvDsBatchMeta from multiple input branches. When connecting a branch to nvdsmetamux, a new pad must be requested from the muxer using gst_element_get_request_pad and the pad template sink_%u.
Application needs select one active sink pad which gstbuffer will be passed to src pad. The default active sink pad is the sink pad 0. nvdsmetamux will find the nearest video frame meta based on the active sink pad video frame PTS and merge the meta data into output buffer NvDsBatchMeta. Application can set the PTS tolerance threshold, if the difference of frame PTS for the same source id is bigger than the threshold, The meta data merge will be skipped. The default of the PTS match threshold is 60 ms.
Input buffer will be return if all video frame PTS are less than current selected PTS for all source id in the batch. Application can filter meta data based on source id and model unique id.

Inputs and Outputs
-
Inputs
- Gst Buffer (batched)
- NvDsBatchMeta
-
Control parameters
- active-pad
- pts-tolerance
- config-file
-
Output
- Gst Buffer (batched)
- NvDsBatchMeta merged NvDsBatchMeta from all sink pads
Features
The following table summarizes the features of the plugin.
Gst-nvsmetamux features
Gst-nvdsmetamux File Configuration Specifications
The Gst-nvdsmetamux configuration file uses a “Key File” format.
The [property] group configures the general behavior of the plugin. It is the only mandatory group.
The following table describe the keys supported for [property] groups.
Gst-nvdsmetamux Property Group Supported Keys
Gst Properties
The following table describes the Gst properties of the Gst-nvdsmetamux plugin.
Gst-nvsmetamux gst properties
Sample pipelines
Given below are some sample pipelines to demonstrate metamux plugin’s usage, please set the appropriate configuration file and library paths.
Merging metadata from two inputs: