GNOME Bugzilla – Bug 700213
rtpgstpay: sticky events are not forwarded to to the src pad
Last modified: 2013-05-13 11:45:10 UTC
After this commit 9532b04947baf701585a8643c90b1e1c48498be3: rtpgstpay: fix invalid memory access in event handler First process event in payloader, then hand it to the base class which takes ownership of the event. https://bugzilla.gnome.org/show_bug.cgi?id=699637 the sticky events are not properly forwarded to the src pad.
Do you have a testcase to reproduce this? This shows stream-start, caps, event, multiple buffers, and eos arriving just fine on the fakesink: gst-launch-1.0 videotestsrc num-buffers=2 ! rtpgstpay ! fakesink silent=false -v
I can reproduce it by applying the gst-rtsp-server patch (see https://bugzilla.gnome.org/show_bug.cgi?id=699220) and running the following unit test: GST_CHECKS=test_client_sdp make -C tests/check gst/client.check With the commit 9532b in gst-plugins-good, the test client in gst-rtsp-server fails. The reason of this failure is that the max-bitrate tag is not forwarded to the src pad of the rtpgst payloader and no bandwidth line is generated by the server.
commit f28ab45f3e31f1bd7f3709d99b88709747e726ef Author: Sebastian Dröge <sebastian.droege@collabora.co.uk> Date: Mon May 13 10:43:32 2013 +0200 rtpgstpay: First let baseclass handle events, then put them into the stream Fixes handling of sticky events. https://bugzilla.gnome.org/show_bug.cgi?id=700213