[Bug 669509] h264parse/aacparse: caps renegotiation fails due to baseparse calling gst_pad_use_fixed_caps

[GStreamer (GNOME Bugzilla)]

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

--- Comment #5 from Aleksander Wabik <awabik at opera.com> ---
It might be a historical thing, from GStreamer 0.10.32:

Author: Mark Nauwelaerts <mark.nauwelaerts at collabora.co.uk>  2009-10-28
12:00:08
Committer: Tim-Philipp Müller <tim.muller at collabora.co.uk>  2011-04-08 16:44:47
Parent: 9f5bb92e74fde1d8f0218c6019de15e6f175af5c (aacparse: Fix compilation
warnings)
Child:  899a6de75b00ed6f9bf65338f2f66787133f0f60 (baseparse: documentation
fixes)
Branches: 1.4.5-with-backports, master, remotes/origin/1.4.5-with-backports,
remotes/origin/CES-2013-BCM, remotes/origin/RELEASE-0.10.35-bison-fix,
remotes/origin/SDK-4.3-bison-fix, remotes/origin/master,
remotes/origin/upstream-0.10
Follows: RELEASE-0.10.32
Precedes: RELEASE-0.10.33

    baseparse: use_fixed_caps for src pad

    After all, stream is as-is, and there is little molding to downstream's
    taste that can be done.  If subclass can and wants to do so, it can
    still override as such.

Then, that line that sets fixed caps was propagated when baseparse was
separated from aacparse, then when it was moved from audioparsers to baseparse,
then into GStreamer 1.x.

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