[gstreamer-bugs] [Bug 582056] [asfdemux] forcing an EOS on the pipeline doesn't work with wmv files

[GStreamer (bugzilla.gnome.org)]

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=582056

  GStreamer | gst-plugins-ugly | Ver: git

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|critical                    |minor
             Status|UNCONFIRMED                 |RESOLVED
          Component|gst-plugins-bad             |gst-plugins-ugly
         Resolution|                            |FIXED
            Summary|gst_event_new_eos don't work|[asfdemux] forcing an EOS on
                   |in wmv files                |the pipeline doesn't work
                   |                            |with wmv files
   Target Milestone|HEAD                        |0.10.12
            Version|0.10.22                     |git




------- Comment #7 from Tim-Philipp Müller  2009-05-30 12:13 UTC -------
I haven't tested it, but this should fix it:

 commit 7c40c992388d8eaca9a8999dd281c24ccc69c99e
 Author: Tim-Philipp Müller <tim.muller at collabora.co.uk>
 Date:   Fri May 29 20:07:14 2009 +0100

    asfdemux: fix bogus flow return handling in eos handler

    Don't overwrite the origin flow return by whatever flow we get
    when trying to push the remaining internally queued payloads.
    We want to do our eos logic, ie. send an EOS event or segment-done
    message in any case. Makes things EOS properly when an EOS event
    is forced upon the pipeline so that the source returns
    FLOW_UNEXPECTED to a pulling asfdemux. Should fix #582056.

I'm not entirely sure why you do what you do though - forcing an eos event on a
playing pipeline is a slightly unusual thing to do. You might want to have a
look at "gnonlin".


-- 
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=582056.