Find location of not-linked/-negotiated errors

Eslam Ahmed eslam.ahmed at
Mon Jan 17 08:33:27 UTC 2022

Hi there,

You can obtain a lot of information by dumping the graph of your pipeline.

If you are using gst-launch, then try to set the environment variable
GST_DEBUG_DUMP_DOT_DIR to a directory where the .dot graph is dumped before
running your pipeline.

If you are building an application, set the same environment variable and
call GST_DEBUG_BIN_TO_DOT_FILE manually for your pipeline.

You can then use any .dot viewer on your platform to view the dot/graph

You can also convert .dot files to .svg images by running $ dot -Tsvg

Best Regards,
Eslam Ahmed

On Sun, Jan 16, 2022 at 10:00 PM Florian Echtler via gstreamer-devel <
gstreamer-devel at> wrote:

> Hello again,
> this also sounds like a very simple thing, but if my pipeline fails to
> start with one of these errors, how do I figure out which elements were
> involved, i.e. failed to link/negotiate? I assume there is a suitable
> GST_DEBUG config, but I haven't found it yet.
> Best, Florian
> --
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list