multiqueue + tee problems with gst-launch

[mariannasb]

Hi,

I'm having some issues while trying to use the multiqueue with tees in gst-launch.

This works fine:
gst-launch-1.0 fakesrc ! multiqueue name=q fakesrc ! q. q. ! fakesink q. ! fakesink

This also works fine:
gst-launch-1.0 fakesrc ! tee name=t ! multiqueue name=q ! fakesink

This won't link:
gst-launch-1.0 fakesrc ! tee name=t ! multiqueue name=q t. ! q. q. ! fakesink q. ! fakesink

0:00:00.018359019  2475       0x695d80 ERROR                    tee gsttee.c:368:gst_tee_request_new_pad:<t> pad name src_%u is not unique
0:00:00.018563772  2475       0x695d80 ERROR           GST_PIPELINE grammar.y:617:gst_parse_perform_link: could not link t to q
WARNING: erroneous pipeline: could not link t to q

[Sebastian Dröge-3]

On Mo, 2016-05-02 at 06:38 -0700, mariannasb wrote:

> 
> This won't link:
> gst-launch-1.0 fakesrc ! tee name=t ! multiqueue name=q t. ! q. q. !
> fakesink q. ! fakesink
>
> 0:00:00.018359019  2475       0x695d80 ERROR                    tee
> gsttee.c:368:gst_tee_request_new_pad:<t> pad name src_%u is not
> unique
> 0:00:00.018563772  2475       0x695d80 ERROR           GST_PIPELINE
> grammar.y:617:gst_parse_perform_link: could not link t to q
> WARNING: erroneous pipeline: could not link t to q

This looks like a limitation of gst-launch. Link the pads by their
complete names, e.g. t.src_0 and q.src_0 / q.sink_0. Without that it's
also random which source pad and which sink pad are going together.

In general, at this point of pipeline complexity it is usually better
to write an actual application. gst-launch is only a debugging tool.

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com


_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[mariannasb]

>In general, at this point of pipeline complexity it is usually better
>to write an actual application. gst-launch is only a debugging tool.

I actually have an application, but I'm using gst_parse_launch() because it is quite a large pipeline I'm building (and makes it a lot easier to experiment with some variations of the pipeline).
I guess gst-launch also uses the same.

>This looks like a limitation of gst-launch. Link the pads by their
>complete names, e.g. t.src_0 and q.src_0 / q.sink_0. Without that it's
>also random which source pad and which sink pad are going together.

Anyway, using the pad names resolves the problem:
gst-launch-1.0 fakesrc ! tee name=t ! multiqueue name=q t.src_1 ! q.sink_1 q.src_0 ! fakesink q.src_1 ! fakesink

Thanks