The #GstMeta structure should be included as the first member of a #GstBuffer
metadata structure. The structure defines the API of the metadata and should
be accessible to all elements using the metadata.
A metadata API is registered with gst.meta.Meta.apiTypeRegister which takes a
name for the metadata API and some tags associated with the metadata.
With gst.meta.Meta.apiTypeHasTag one can check if a certain metadata API
contains a given tag.
Multiple implementations of a metadata API can be registered.
To implement a metadata API, gst.meta.Meta.register should be used. This
function takes all parameters needed to create, free and transform metadata
along with the size of the metadata. The function returns a #GstMetaInfo
structure that contains the information for the implementation of the API.
The #GstMeta structure should be included as the first member of a #GstBuffer metadata structure. The structure defines the API of the metadata and should be accessible to all elements using the metadata.
A metadata API is registered with gst.meta.Meta.apiTypeRegister which takes a name for the metadata API and some tags associated with the metadata. With gst.meta.Meta.apiTypeHasTag one can check if a certain metadata API contains a given tag.
Multiple implementations of a metadata API can be registered. To implement a metadata API, gst.meta.Meta.register should be used. This function takes all parameters needed to create, free and transform metadata along with the size of the metadata. The function returns a #GstMetaInfo structure that contains the information for the implementation of the API.
A specific implementation can be retrieved by name with gst.meta.Meta.getInfo.
See #GstBuffer for how the metadata can be added, retrieved and removed from buffers.