<div dir="ltr">It's not only before, source 2 will not even start to negotiate its caps until source 1 is completely finished negotiating. </div><div class="gmail_extra"> <div class="gmail_quote">On Tue, May 7, 2013 at 12:34 PM, Tim-Philipp Müller-2 [via GStreamer-devel] <<a href="/user/SendEmail.jtp?type=node&node=4659826&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>> wrote: <blockquote style='border-left:2px solid #CCCCCC;padding:0 1em' class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"> On Tue, 2013-05-07 at 08:58 -0700, johnwesting wrote: > I placed queues, queue2s, and multiqueues in every place the pipeline > would allow. I guess there's no hope for starting both sources in > parallel using gst-launch? </div><div class="im">I assume both sources operate in push mode, in which case a streaming thread will be started for each. They will run independent of each other by default already. If you observe that caps for source1 are negotiated before source2 starts up, that's most likely a coincidence, or something timing-related on your specific machine. </div> Cheers -Tim <div><div class="im"> > On Tue, May 7, 2013 at 11:07 AM, Tim-Philipp Müller-2 [via </div><div><div class="h5">> GStreamer-devel] <[hidden email]> wrote: <div class='shrinkable-quote'> > On Tue, 2013-05-07 at 07:09 -0700, johnwesting wrote: > > > > 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. > > > In 0.10 and 1.0 you can force the creation of a new streaming > thread by > inserting a queue (or multiqueue) element into the pipeline. > > In 0.8 scheduling (when data would flow between which pads) > worked > completely differently, there were dedicated schedulers which > would try > to figure out which pads needed attention etc. In 0.10/1.0 we > leave this > kind of scheduling mostly to the kernel. > > Cheers > -Tim > > > > > > On Tue, May 7, 2013 at 6:18 AM, Tim-Philipp Müller-2 [via > > > GStreamer-devel] <[hidden email]> 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: > > > > <a href="http://linux.about.com/library/cmd/blcmdl1_gst-launch.htm" rel="nofollow" link="external" target="_blank">http://linux.about.com/library/cmd/blcmdl1_gst-launch.htm</a> > > > > > > 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] > > > <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="nofollow" link="external" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> > > > > > > > > > ______________________________________________________________ > > If you reply to this email, your message will be > added to the > > discussion below: > > > <a href="http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659814.html" rel="nofollow" link="external" target="_blank">http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659814.html</a> > > To unsubscribe from Multiple Source Pipeline Hangs, > click > > here. > > NAML > > > > > > > > > > > > ______________________________________________________________________ > > View this message in context: Re: Multiple Source Pipeline > Hangs > > > Sent from the GStreamer-devel mailing list archive at > Nabble.com. > > > _______________________________________________ > > gstreamer-devel mailing list > > [hidden email] > > > <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="nofollow" link="external" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> > > > _______________________________________________ > gstreamer-devel mailing list > [hidden email] > <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="nofollow" link="external" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> > > > > ______________________________________________________________ > If you reply to this email, your message will be added to the > discussion below: </div></div></div><div class="im">> <a href="http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659821.html" rel="nofollow" link="external" target="_blank">http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659821.html</a> <div class='shrinkable-quote'> > To unsubscribe from Multiple Source Pipeline Hangs, click > here. > NAML > > > > > ______________________________________________________________________ > View this message in context: Re: Multiple Source Pipeline Hangs > Sent from the GStreamer-devel mailing list archive at Nabble.com. > _______________________________________________ > gstreamer-devel mailing list > <a href="http://user/SendEmail.jtp?type=node&node=4659824&i=0" rel="nofollow" link="external" target="_blank">[hidden email]</a> > <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="nofollow" link="external" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a></div></div><div class="im"> </div> _______________________________________________ gstreamer-devel mailing list <a href="http://user/SendEmail.jtp?type=node&node=4659824&i=1" rel="nofollow" link="external" target="_blank">[hidden email]</a> <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="nofollow" link="external" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> <hr color="#cccccc" noshade size="1"> </div><div style="color:#444;font:12px tahoma,geneva,helvetica,arial,sans-serif"><div class="im"> <div style="font-weight:bold">If you reply to this email, your message will be added to the discussion below:</div> </div><a href="http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659824.html" target="_blank" rel="nofollow" link="external">http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659824.html</a> </div><div class="HOEnZb"><div class="h5"> <div style="color:#666;font:11px tahoma,geneva,helvetica,arial,sans-serif;margin-top:.4em;line-height:1.5em"> To unsubscribe from Multiple Source Pipeline Hangs, <a href="" target="_blank" rel="nofollow" link="external">click here</a>. <a href="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" rel="nofollow" style="font:9px serif" target="_blank" link="external">NAML</a> </div></div></div></blockquote></div> </div> <hr align="left" width="300" /> View this message in context: <a href="http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659826.html">Re: Multiple Source Pipeline Hangs</a> Sent from the <a href="http://gstreamer-devel.966125.n4.nabble.com/">GStreamer-devel mailing list archive</a> at Nabble.com.