[Bug 705108] rtpgstpay: Add a config-interval property

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=705108
  GStreamer | gst-plugins-good | git

--- Comment #2 from Youness Alaoui <youness.alaoui at collabora.co.uk> 2013-07-30 21:31:08 UTC ---
There aren't any other events that rtpgstpay sends.. it only sends the
GST_EVENT_TAG, GST_EVENT_CUSTOM_DOWNSTREAM and GST_EVENT_CUSTOM_BOTH, and I
don't think the custom events should be resent. That's why I'm only resending
the tags and caps events.

Good point about dropping everything in the depayloader from stream-start to
caps, but the depayloader doesn't receive a caps event, it only receives rtp
packets with the header containing the caps index to use.. so the first packet
will contain the caps already.. and if it doesn't, then the depayloader will
drop the packets anyways since it doesn't know what caps they have.

Anyways, I was told that the stream-start can be sent as an 'update' without
the need for a new-segment or caps event, and it doesn't seem to affect the
sink either since it receives the stream-start without new-segment/caps, and it
works fine.

(FYI: the header contains a 3 bit field containing the caps index, each packet
will have this field telling what the caps of the data is, if the caps are new,
the index is incremented and the next data packet will contain inlined-caps (as
a string) preceding the data and a 1 bit flag will be enabled in the header to
say that this packet contains inlined flags. The depayloader will drop any
packets that has a caps index which it has not already cached.)

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.