<div dir="ltr">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?<br></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">On Tue, May 7, 2013 at 11:07 AM, Tim-Philipp Müller-2 [via GStreamer-devel] <span dir="ltr"><<a href="/user/SendEmail.jtp?type=node&node=4659823&i=0" target="_top" rel="nofollow" link="external">[hidden email]</a>></span> wrote:<br>
<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 07:09 -0700, johnwesting wrote:
<br><br></div><div class="im">> I'm not sure where I got this from but I thought with GStreamer
<br>> versions 0.8 is less than 0.10, does that mean the threading feature
<br>> was removed from newer versions? Why?
<br>> 
<br>> 
<br>> If I don't have the option of creating threads using the {} brackets
<br>> then how can I spawn additional threads using gst-launch? I tried
<br>> placing queues everywhere I could in the pipeline but this still did
<br>> not solve the problem.
<br><br></div><div class="im">In 0.10 and 1.0 you can force the creation of a new streaming thread by
<br>inserting a queue (or multiqueue) element into the pipeline.
<br><br>In 0.8 scheduling (when data would flow between which pads) worked
<br>completely differently, there were dedicated schedulers which would try
<br>to figure out which pads needed attention etc. In 0.10/1.0 we leave this
<br>kind of scheduling mostly to the kernel.
<br><br> Cheers
<br>  -Tim
<br></div><div><br>> 
<br><div class="im">> On Tue, May 7, 2013 at 6:18 AM, Tim-Philipp Müller-2 [via
<br></div><div><div class="h5">> GStreamer-devel] <[hidden email]> wrote:
<div class='shrinkable-quote'><br>>         On Tue, 2013-05-07 at 08:50 +0100, David Röthlisberger wrote:
<br>>         
<br>>         > On 6 May 2013, at 21:50, John Westing wrote: 
<br>>         > > 
<br>>         > > I read the article and understand that the problem is
<br>>         likely an issue with threading, hence the reason for the {}
<br>>         brackets described in my first post: {} brackets in a
<br>>         gst-launch pipeline spawn an additional thread for the
<br>>         elements surrounded in the brackets. However, in my case when
<br>>         I use the {} brackets I get the GStreamer warning "Error
<br>>         during parsing: syntax error, unexpected $undefined" as
<br>>         described in my first post. 
<br>>         > 
<br>>         > Interesting, I didn't know that! Where is this documented? A
<br>>         Google 
<br>>         > search for "gst-launch brackets thread" returns this man
<br>>         page: 
<br>>         > <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><br>>         > 
<br>>         > which says: 
<br>>         > 
<br>>         >     A group of elements surrounded by curly braces {, } will
<br>>         be executed 
<br>>         >     in a separate thread. 
<br>>         > 
<br>>         > However, it isn't clear what version of GStreamer the above
<br>>         corresponds 
<br>>         > to. On my Ubuntu 12.10 system, neither the man page for
<br>>         gst-launch-0.10 
<br>>         > nor gst-launch-1.0 contain this text (nor any mention of
<br>>         "{").
<br>>         That { } syntax for a new thread is GStreamer 0.8 syntax. It
<br>>         doesn't do 
<br>>         anything in 0.10.x or 1.x. It's probably best to ignore every
<br>>         document 
<br>>         where you find these in a gst-launch context. 
<br>>         
<br>>         Cheers 
<br>>          -Tim 
<br>>         
<br>>         _______________________________________________ 
<br>>         gstreamer-devel mailing list 
<br>>         
<br>>         [hidden email] 
<br>>         <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><br>>         
<br>>         
<br>>         
</div></div></div>>         ______________________________________________________________
<br><div class="im">>         If you reply to this email, your message will be added to the
<br>>         discussion below:
<br>>         <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> 
<br>>         To unsubscribe from Multiple Source Pipeline Hangs, click
<br>>         here.
<br>>         NAML 
<br>> 
<br>> 
<br>> 
<br>> 
<br></div>> ______________________________________________________________________
<br><div class="im">> View this message in context: Re: Multiple Source Pipeline Hangs
<br></div><div class="im">> Sent from the GStreamer-devel mailing list archive at Nabble.com.
<br></div><div class="im">> _______________________________________________
<br>> gstreamer-devel mailing list
<br>> <a href="http://user/SendEmail.jtp?type=node&node=4659821&i=0" rel="nofollow" link="external" target="_blank">[hidden email]</a>
<br>> <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">
<br><br>_______________________________________________
<br>gstreamer-devel mailing list
<br><a href="http://user/SendEmail.jtp?type=node&node=4659821&i=1" rel="nofollow" link="external" target="_blank">[hidden email]</a>
<br><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><br>

        
        
        
        <br>
        <br>
        <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-tp4659808p4659821.html" target="_blank" rel="nofollow" link="external">http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659821.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>.<br>

                <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><br></div>


        
        
        
<br/><hr align="left" width="300" />
View this message in context: <a href="http://gstreamer-devel.966125.n4.nabble.com/Multiple-Source-Pipeline-Hangs-tp4659808p4659823.html">Re: Multiple Source Pipeline Hangs</a><br/>
Sent from the <a href="http://gstreamer-devel.966125.n4.nabble.com/">GStreamer-devel mailing list archive</a> at Nabble.com.<br/>