Multi pipeline logging identification

Dwight Kulkarni dwight at
Thu Dec 9 20:22:08 UTC 2021

Hi Vinod,

You can try registering for the Bus messages with: *gst_bus_add_watch(..)*

The GstMessage object returned can be queried for it's source object name.

On Thu, Dec 9, 2021 at 11:54 AM vinod kesti via gstreamer-devel <
gstreamer-devel at> wrote:

> Hi all,
> I am running multiple Gstreamer pipelines in single linux process. All
> the pipelines are similar and only udp input and output ports are chanig.
> Log function is Registered using gst_debug_add_log_function(),  after the
> gst_init(). I am not able to identify the which pipeline dumping the error.
> One way I found is if GObject is an GstElement/GstPad I am able to find
> the parent pipeline and dump the pipeline name. But I have facing problem
> when GObject in the callback is null. Is there any way to differentiate
> from which Pipeline we are getting warning.
> Sent from Yahoo Mail. Get the app <>


Dwight Kulkarni
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list