[Bug 721289] pad: using multiple blocking probes doesn't work as expected

[GStreamer (bugzilla.gnome.org)]

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

Sebastian Dröge (slomo) <slomo> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.3.1
            Summary|gstpad: using multiple      |pad: using multiple
                   |blocking probes doesn't     |blocking probes doesn't
                   |work as expected            |work as expected

--- Comment #7 from Sebastian Dröge (slomo) <slomo at coaxion.net> 2014-01-02 12:36:21 UTC ---
Please test if this fixes all your problems

commit 9e125e7bab92259d2d3317c2bf47da081c03ba8a
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Thu Jan 2 13:34:52 2014 +0100

    pad: Add unit test for adding/removing blocking probes while a pad is
blocked

    And make sure that these new probes are actually called if they should
    instead of silently blocking the pad forever.

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

commit 93ce90f83320e845867d28b9cbeea5b596a1ef04
Author: Sebastian Dröge <sebastian at centricular.com>
Date:   Thu Jan 2 13:33:20 2014 +0100

    pad: Check if new probes need to be called when adding/removing some

    This allows blocking a pad, add a new blocking probe, removing
    the first probe and then having the second probe called. Which
    could then decide that data-flow should actually continue
    instead of blocking now.

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

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