[gst-devel] Pipeline seek problem
ikirsh at gmail.com
Fri Aug 24 23:08:06 CEST 2007
It is flushing, and I have considered that. I've set both the queues to hold
1 buffer max, and that seem to have made no difference at all.
Is there any other element in that pipeline that can queue a large number of
buffers (rtpmp4vpay maybe? I'm not familiar with its behavior), hence
causing this problem?
On 8/24/07, Andy Wingo <wingo at pobox.com> wrote:
> On Thu 23 Aug 2007 21:02, "Itay Kirshenbaum" <ikirsh at gmail.com> writes:
> > filesrc -> queue -> avidemux -> queue -> rtpmp4pay -> udpsink
> > When I tried adding seek support, I've noticed a strange behavior.
> > After a seek event is performed in the avidemux element, it pushes
> > 5-10 seconds worth of buffers as fast as it can (the 5-10 seconds
> > following the seek position), and will only get to normal playing rate
> > afterwards.
> The seek is probably flushing, which removes all buffers in the queue.
> About 5-10 seconds' worth.
> > From going over basesink logs it seems after
> > flush_start/stop+newsegment the clock is reset, and all buffers
> > received are just sent out, without actually waiting for their time.
> The thing that waits on the time is the sink. Everything else runs until
> the sink is blocked, hence the buildup in the queue until it blocks too
> (when it is full).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gstreamer-devel