Multiple Source Pipeline Hangs

[johnwesting]

I'm not sure where I got this from but I thought with GStreamer versions
0.8 is less than 0.10, does that mean the threading feature was removed
from newer versions? Why?

If I don't have the option of creating threads using the {} brackets then
how can I spawn additional threads using gst-launch? I tried placing queues
everywhere I could in the pipeline but this still did not solve the problem.

Thanks,
John



On Tue, May 7, 2013 at 6:18 AM, Tim-Philipp Müller-2 [via GStreamer-devel] <
ml-node+s966125n4659814h91 at n4.nabble.com> wrote:

> On Tue, 2013-05-07 at 08:50 +0100, David Röthlisberger wrote:
>
> > On 6 May 2013, at 21:50, John Westing wrote:
> > >
> > > I read the article and understand that the problem is likely an issue
> with threading, hence the reason for the {} brackets described in my first
> post: {} brackets in a gst-launch pipeline spawn an additional thread for
> the elements surrounded in the brackets. However, in my case when I use the
> {} brackets I get the GStreamer warning "Error during parsing: syntax
> error, unexpected $undefined" as described in my first post.
> >
> > Interesting, I didn't know that! Where is this documented? A Google
> > search for "gst-launch brackets thread" returns this man page:
> > http://linux.about.com/library/cmd/blcmdl1_gst-launch.htm
> >
> > which says:
> >
> >     A group of elements surrounded by curly braces {, } will be executed
> >     in a separate thread.
> >
> > However, it isn't clear what version of GStreamer the above corresponds
> > to. On my Ubuntu 12.10 system, neither the man page for gst-launch-0.10
> > nor gst-launch-1.0 contain this text (nor any mention of "{").
>
> That { } syntax for a new thread is GStreamer 0.8 syntax. It doesn't do
> anything in 0.10.x or 1.x. It's probably best to ignore every document
> where you find these in a gst-launch context.
>
> Cheers
>  -Tim
>
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email] <http://user/SendEmail.jtp?type=node&node=4659814&i=0>
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659814.html
>  To unsubscribe from Multiple Source Pipeline Hangs, click here<http://gstreamer-devel.966125.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4659808&code=am9obi5ibGFuay53ZXN0aW5nQGdtYWlsLmNvbXw0NjU5ODA4fDU0MDE1MDQyMQ==>
> .
> NAML<http://gstreamer-devel.966125.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659819.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20130507/d0816715/attachment-0001.html>