[gst-devel] Regarding Seek events.

[ved kpl]

Hi,

When PAUSED, the sinks do a preroll and then do a preroll_wait()
(basically wait on a cond). ,which means the streaming threads are
blocked and if there is a queue in between , the thread above the
queue wont stop until the queue is filled up.

Elements other than sinks and src are unaware of this and mostly do
not differentiate between PAUSED/PLAYING.

Ved

On Wed, Dec 10, 2008 at 11:40 PM, Michael Smith <msmith at xiph.org> wrote:
> On Tue, Dec 9, 2008 at 10:41 PM, Sameer Naik
> <sameer.subscriptions at damagehead.com> wrote:
>>
>> Are you implying that though the state of the pipeline is set to PAUSED, the
>> filesrc will continue providing data to its peer. Is this the default
>> behaviour of the plugin? Because if it is, then when a pipeline is in PAUSED
>> state then an application would still be doing quite a lot of processing and
>> also hogging the memory resources.
>
> I was attempting to state that explicitly, not imply it, but yes.
>
> This is how gstreamer is designed; elements other than sinks (and live
> sources) should not treat PAUSED and PLAYING differently at all.
>
> Note that in most pipelines, something will block after a relatively
> short period of time - e.g. a downstream queue will become full, and
> block - so it doesn't consume cpu resources for an unbounded period,
> only for long enough to fill the downstream queues.
>
> Mike
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gstreamer-devel
>