Tracking the demuxer responsible for SEGMENT_DONE message

[Nicolas Dufresne]

Le lundi 20 février 2017 à 02:52 -0800, Baby Octopus a écrit :
> Hi Tim,
> 
> Thanks for the response
> 
> SEGMENT_DONE message seems to be posted by the GstPipeline itself. So
> GST_ELEMENT_NAME(GST_MESSAGE_SRC(message)) is giving name of the
> pipeline
> and not the demuxer
> 

GstBin (your pipeline), will watch for all GST_MESSAGE_SEGMENT_START
and will forward to the application a single message when the same
number of GST_MESSAGE_SEGMENT_DONE has been received.

So technically, this message is from all the elements driving (handling
seeks) your pipeline (demuxers, parsers or sources). It is sent once to
the application so you should not have to care.

You can of course implement GstBin::handle_message() in one of your own
bin, and handle those messages yourself for a subset of your pipeline.

Nicolas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20170220/74dc0e82/attachment.sig>