[Bug 778298] [REGRESSION]: decodebin2: Wrong stream-topology reported for some streams

[GStreamer (GNOME Bugzilla)]

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

--- Comment #4 from Thibault Saunier <tsaunier at gnome.org> ---
> Yes that makes sense. There's probably other things that should also be removed though.
> I remember doing similar things in encodebin, maybe also check there?

I checked and the only thing that seems to be filter there is the streamheader,
I do not think it should be filter in our case as we should have the same one
(or none which is also fine) before and after the parser.

> Do you still get different caps and two streams here if the input has e.g. no profile but h264parse adds one?

I do not have this case handy, any idea where I could find that?

I guess I would but then it is not a problem if fields are added as
intersection would work afaiu.

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