Custom GstMeta data dissapearing when received in a new pipeline

[Nicolas Dufresne]

Le lundi 27 juin 2016 à 04:56 -0700, debruyn a écrit :
> I am developing a system that receives a UDP stream from an ARM
> board. I
> need to set my own custom metadata on each buffer that is being sent
> to the
> PC (SIte ID and Camera ID). I already wrote a metadata API
> (implemented as a
> shared library) for this based on this example :
> https://gstreamer.freedesktop.org/data/doc/gstreamer/head/pwg/html/se
> ction-allocation-meta.html
> . The problem is when I set the metadata on the buffer it sets fine,
> but
> when i receive the buffers on the other side the metadata is not
> there. Can
> anybody please help with this problem. Is it even possible to
> implement
> custom metadata like this?
> 
> Here is my code snippets for firstly setting the data and secondly
> reading
> it. (attached is the source file of my Custom metadata)

GstMeta are meant for metadata that are transported inside the
pipeline, if you need metadata over the wire, you need to use features
of your chosen streaming protocol.

As an example, when using RTP, you can add a pad probe after you
payloader, and instead custom data, see
gst_rtp_buffer_set_extension_data() (or the one byte header and two
bytes header variants).

Nicolas