[Bug 700806] gstbasesrc: retry pushing STREAM_START event if needed

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=700806
  GStreamer | gstreamer (core) | git

--- Comment #6 from Sebastian Dröge <slomo at circular-chaos.org> 2013-05-22 09:40:11 UTC ---
I think that's possible now after this commit:
commit e0f59d22eb414175c2471458c598681210a210cb
Author: Sebastian Dröge <sebastian.droege at collabora.co.uk>
Date:   Thu May 9 10:29:11 2013 +0200

    pad: If we push sticky events because of another sticky event, only push
those that come before the new event

    https://bugzilla.gnome.org/show_bug.cgi?id=699937

Before that it was possible that the old segment event was sent downstream
after a flush when GstPad was sending sticky events downstream (e.g. because it
got a new stream-start event). However we *require* a segment event to arrive
after a flush before any data, if we don't remove the old one we could end up
using the old segment without getting any warnings or anything. So maybe the
old segment should just be "invalidated" instead of being removed, to work as a
placeholder there for a new segment event.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.