<div>I am assuming this is what you want</div><div><br></div><div> When output selector switches from one pad to another, the one that got inactive.. downstream the pipeline should continue till the end. i.e. the buffers it had till that point should still flow instead of that segment becoming inactive</div>
<div><br></div><div>I'm no expert and am not sure 100% of the following, but see if it makes sense.. someone else may be able to shed better light</div><div><br></div><div>The inactive pads will no longer get buffers from upstream. So in a push scenario, no calls will be made to "push the buffers" further down. Maybe a queue after the output selector might help here so that the rest of the downstream pipeline can "pull" the data or push it independent of the output selector?</div>
<div>It might depend on what you have downstream though...</div><div><br></div><div>On second thoughts, shouldn't the output selector wait for it's push to return before making the active pad inactive? If so, then all data is already pushed by it downstream and then it becomes inactive. I need to look at the output selector, so I am not sure here. Perhaps what you desire is already happening.. </div>
<div>I am not sure thought what happens if the data is being pulled from it, rather than push or whether making the pad inactive causes an event which drops all buffers downstream completely.</div><div><br></div><div>Perhaps someone else may be able to shed better light.. and even let me know if my understanding of the output selector is right?</div>
<div><br></div><div><br></div><div><div><br><div class="gmail_quote">On Fri, Dec 23, 2011 at 1:30 AM, <span dir="ltr"><<a href="mailto:gstreamer-devel-request@lists.freedesktop.org">gstreamer-devel-request@lists.freedesktop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send gstreamer-devel mailing list submissions to<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:gstreamer-devel-request@lists.freedesktop.org">gstreamer-devel-request@lists.freedesktop.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:gstreamer-devel-owner@lists.freedesktop.org">gstreamer-devel-owner@lists.freedesktop.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of gstreamer-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. How to empty pipeline stages linked to an inactive<br>
output-selector source pad? (Fabrizio Dini)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 22 Dec 2011 18:36:08 +0100<br>
From: Fabrizio Dini <<a href="mailto:dini.fabrizio@gmail.com">dini.fabrizio@gmail.com</a>><br>
Subject: How to empty pipeline stages linked to an inactive<br>
output-selector source pad?<br>
To: <a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br>
Message-ID:<br>
<<a href="mailto:CAAmXsFDSRs9EhcKXYpUkN2anpm0BudjqjQcUfy6uHvTa6ENa0Q@mail.gmail.com">CAAmXsFDSRs9EhcKXYpUkN2anpm0BudjqjQcUfy6uHvTa6ENa0Q@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hello everybody!<br>
<br>
This is my first post on this mailing list, so please forgive me for any<br>
misuse of this list or netiquette violation I might commit: sorry in<br>
advance.<br>
<br>
That said, the subject says it all, I think.<br>
<br>
I have a video pipeline that includes an output-selector. Downstream the<br>
selector, I have two branches of pipeline linked to two src pad of the<br>
selector. They are equal: a muxer and a file sink.<br>
<br>
What I would like to do is, when I change the active pad on the<br>
output-selector, have the stages downstream the inactive pad to push their<br>
buffers to the next stage, instead of dropping it. Here, I am calling<br>
"inactive pad" the one which become inactive as a consequence of changing<br>
the the "active-pad" property in the selector, or put differently, the pad<br>
that was _previously_ active.<br>
<br>
I tried sending a different events to the active pad before changing it,<br>
but without success.<br>
<br>
Any hint?<br>
<br>
Thank you in advance.<br>
<br>
Fabrizio<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20111222/baf12df8/attachment.htm" target="_blank">http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20111222/baf12df8/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
<br>
<br>
End of gstreamer-devel Digest, Vol 11, Issue 53<br>
***********************************************<br>
</blockquote></div><br></div></div>