[Bug 679545] [0.11] adder: not-negotiated errors

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=679545
  GStreamer | gst-plugins-base | 0.11.x

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |0.11.x

--- Comment #4 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2012-08-04 23:51:55 UTC ---
At least the most basic stuff should work now hopefully; sorry it took so long
to get this fixed.

commit 24478261a26a464ecf827787b94cc04061c2a88f
Author: Tim-Philipp Müller <tim at centricular.net>
Date:   Sun Aug 5 00:41:10 2012 +0100

    adder: send CAPS event downstream fixing not-negotiated errors

    Make sure to send a CAPS event downstream when we get our
    first input caps. This fixes not-negotiated errors and
    adder use with downstream elements other than fakesink.

    Even gst-launch-1.0 audiotestsrc ! adder ! pulsesink works now.

    Also, flag the other sink pads as FIXED_CAPS when we receive
    the first CAPS event on one of the sink pads (in addition to
    setting those caps on the the sink pads), so that a caps query
    will just return the fixed caps from now on.

    There's still a race between other upstreams checking if
    caps are accepted and sending a first buffer with possibly
    different caps than the first caps we receive on some other
    pad, but such is life.

    Also need to take into account optional fields better/properly.

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

commit ec13933aaaa15cc7c0b83fd13abf8ccd12e47b9b
Author: Tim-Philipp Müller <tim at centricular.net>
Date:   Sat Aug 4 22:25:08 2012 +0100

    tests: add adder test to check that caps are sent downstream

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