GNOME Bugzilla – Bug 760949
decodebin: Correctly expose pads from elements that have directly exposable pads
Last modified: 2016-01-25 12:52:06 UTC
See commit message. This is a regression caused by 44871680f02f5eae970c3d4f87b4e168ec412a25, i.e. https://bugzilla.gnome.org/show_bug.cgi?id=742924
Created attachment 319513 [details] [review] decodebin: Correctly expose pads from elements that have directly exposable pads analyze_new_pad() can return a new decode chain, which might have a new GstDecodePad in the end. We should use those two for expose_pad() and not the original ones that were passed to analyze_new_pad(). This fails when having a demuxer element that has raw pads immediately or if a decoder with raw caps is after an adaptive demuxer.
Attachment 319513 [details] pushed as acd08a8 - decodebin: Correctly expose pads from elements that have directly exposable pads