[Bug 755469] asfdemux: Non-flushing seeks don't work, broken segment seek handling and other seeking related issues

[GStreamer (GNOME Bugzilla)]

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

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
   Target Milestone|git master                  |1.7.1

--- Comment #11 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
commit 738e48ef49d2d77f539e1d1f4a4cdc15e1b81949
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Wed Sep 23 20:45:34 2015 +0200

    asfdemux: Don't push any data on pads after the segment.stop

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

commit 155c8fc6a6af05c6f08cde5133cff79350be8243
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Wed Sep 23 20:30:21 2015 +0200

    asfdemux: Only change segment start to a keyframe for KEYUNIT seeks

    Not for accurate seeks, which should accurately start at the requested
    position.

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

commit f501188191c63bc531437d6311f46a9a7d535f6b
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Wed Sep 23 20:23:40 2015 +0200

    asfdemux: Update segment.position when pushing buffers

    Without this, non-flushing seeks are not going to work well.

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

commit c526153ec9341183eef05da6918e7e94bcd2db29
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Wed Sep 23 19:37:43 2015 +0200

    asfdemux: Only push EOS event if we're not doing a segment seek

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

commit 42d7aec41224a240f6b9646c834edad123a1b186
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Wed Sep 23 16:31:28 2015 +0200

    asfdemux: If pushing buffers returned EOS, go into the EOS and not failure
code path

    We don't want to unconditionally send an EOS event downstream, but might
want
    to send a SEGMENT_DONE message/event instead if a segment seek was done
    before.

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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.