[gstreamer-bugs] [Bug 476514] [queue] Doesn't forward EOS event in all cases

[GStreamer (bugzilla.gnome.org) <bug...@bu...>]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=476514

  GStreamer | gstreamer (core) | Ver: HEAD CVS




------- Comment #18 from Wim Taymans  2007-09-14 17:20 UTC -------
UNEXPECTED means that it does not want anymore buffers. It's fine to push an
EOS, FLUSH or NEWSEGMENT. Queue should probably get rid of all buffers up to a
queued NEWSEGMENT or EOS, and not shut down the push thread.

I'm thinking about the case where you have httpsrc -> queue -> mad and you
requested a SEGMENT seek in time from 0 to 3 seconds, mad does not know the
byte end position so asks to seek from byte 0 to the end. When it has pushed up
to 3 seconds it can return UNEXPECTED, which should make httpsrc perform the
EOS logic (post SEGMENT_DONE), at which point the app can do another SEGMENT
seek.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=476514.