[Bug 747829] New: rtpsession: Forward stream-start events to send_rtcp srcpad

[GStreamer (GNOME Bugzilla)]

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

            Bug ID: 747829
           Summary: rtpsession: Forward stream-start events to send_rtcp
                    srcpad
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: dv at pseudoterminal.org
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Created attachment 301514
  --> https://bugzilla.gnome.org/attachment.cgi?id=301514&action=edit
Patch to forward stream-start events to send_rtcp srcpad

Currently, if the send_rtp sinkpad receives a stream-start event, it is only
forwarded to the send_rtp srcpad, not the send_rtcp one. Any sink linked to the
send_rtcp srcpad will not ever receive stream-start events. But sinks need to
receive these events so they can post stream-start messages, and in GStreamer,
the pipeline will not dispatch stream-start messages until *all* sinks have
posted this message. As a result, the application's bus watch / bus sync
handler will never see stream-start events.

This patch corrects that by simply sending stream-start & caps & segment events
to the send_rtcp srcpad when the stream-start event is received. With it,
application bus watch/sync handler callbacks receive stream-start messages
again.

I am not sure if this could be done in an easier way, probably by using sticky
events. But the relevant events  are sticky on the send_rtp sinkpad, not on the
send_rtcp srcpad.

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