FastFoward and FastRewind Issue with Gstreamer

Elmy Elias Elmy.Elias at
Wed Jul 27 22:05:06 PDT 2011

Thanks Tim.. 

Elmy Elias

Block B, 3rd Floor, Salarpuria Hallmark, Kadubeesanahalli, Marathahalli-Sarjapur Outer Ring Road, Bangalore 560037, India
Phone: +919880134224, Fax: +918066532001
Elmy.Elias at

Follow what's going on at Teleca's blog on

The information contained in this message is confidential and is intended for the addressee(s) only. If you have received this message in error please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly prohibited.

-----Original Message-----
From: at [ at] On Behalf Of Tim-Philipp Müller
Sent: Tuesday, July 26, 2011 2:07 PM
To: gstreamer-devel at
Subject: RE: FastFoward and FastRewind Issue with Gstreamer

On Tue, 2011-07-26 at 09:08 +0200, Elmy Elias wrote:

> Can I know the exact reason for getting an error  GStreamer-CRITICAL **: gst_segment_set_seek: assertion
> `start <= stop' failed  when I do a reverse seek .

That would be a bug somewhere. You can set the G_DEBUG=fatal_warnings
environment variable and then run your application in a debugger such as
gdb, which will then abort at the warning, and then you can see from the
stack trace where it comes from.

How well trick modes and especially backwards playback will work depends
a lot on the exact circumstances: what is the exact playback pipeline,
which demuxer or parser is used, what decoders are used, etc.

Don't think the SKIP flag is implemented widely yet.

You probably always want to do a FLUSHing seek in a player application.
If your seek is not flushing, there may be a longer delay, because there
may still be data in queues and elsewhere that needs to be processed. If
a FLUSHing seek doesn't work in some circumstances, that needs to be


gstreamer-devel mailing list
gstreamer-devel at

More information about the gstreamer-devel mailing list