[Bug 721350] baseparse: push pending events before GAP

[GStreamer (bugzilla.gnome.org)]

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

Thiago Sousa Santos <thiago.sousa.santos> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|1.3.1                       |1.2.3

--- Comment #9 from Thiago Sousa Santos <thiago.sousa.santos at collabora.co.uk> 2014-01-08 17:18:45 UTC ---
commit c8196719e7b0cc8dedc67b9e8cb604c14c91c5a3
Author: Thiago Santos <ts.santos at sisa.samsung.com>
Date:   Thu Jan 2 16:22:37 2014 -0300

    baseparse: remove pending_segment as it was being misused

    It wasn't required, instead baseparse was using it to check the media
    caps to identify if it was handling audio or video.

    The pending_segment was removed and a checked_media boolean
    replaced it for a more accurate naming.

    https://bugzilla.gnome.org/show_bug.cgi?id=721350
Pushed to 1.2 branch


commit 5705e1ec33f753a3b748b8c7e88db05552ee0595
Author: Thiago Santos <ts.santos at sisa.samsung.com>
Date:   Thu Jan 2 13:43:54 2014 -0300

    baseparse: push pending events before GAP event

    A GAP event is handled as an empty buffer by sinks and they expect
    to receive start up events before GAP events (like a segment).

    This is important specially if there is a GAP at the beginning of
    a stream (before any buffers) so that the segment event can be
    pushed downstream before the GAP

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

commit 7513fab9e608d76c0bcb9783da9f86ca8dc14c9a
Author: Thiago Santos <ts.santos at sisa.samsung.com>
Date:   Thu Jan 2 13:41:25 2014 -0300

    baseparse: refactor pending events pushing

    Refactor code repeated 3 times to a common function

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

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