gstreamer/gst-libs/gst/rtp
Stian Selnes 1586981b1b rtcpbuffer: Fix validation of packets with padding
The padding (if any) is included in the length of the last packet, see
RFC 3550.

Section 6.4.1:
   padding (P): 1 bit
      If the padding bit is set, this individual RTCP packet contains
      some additional padding octets at the end which are not part of
      the control information but are included in the length field. The
      last octet of the padding is a count of how many padding octets
      should be ignored, including itself (it will be a multiple of
      four).

Section A.2:
   *  The padding bit (P) should be zero for the first packet of a
      compound RTCP packet because padding should only be applied, if it
      is needed, to the last packet.

   *  The length fields of the individual RTCP packets must add up to
      the overall length of the compound RTCP packet as received.

https://bugzilla.gnome.org/show_bug.cgi?id=751883
2015-07-06 12:06:47 +03:00
..
gstrtcpbuffer.c rtcpbuffer: Fix validation of packets with padding 2015-07-06 12:06:47 +03:00
gstrtcpbuffer.h rtcpbuffer: Update package validation to support reduced size rtcp packets 2015-06-05 10:18:21 +02:00
gstrtpbaseaudiopayload.c rtpbaseaudiopayload: Don't copy memory if not needed, just append payload to the RTP buffer 2015-06-30 10:39:01 +02:00
gstrtpbaseaudiopayload.h Fix FSF address 2012-11-03 23:05:09 +00:00
gstrtpbasedepayload.c rtpbasedepayload: provide chain_list function on sink pad 2015-06-01 19:00:55 +01:00
gstrtpbasedepayload.h rtpbasedepayload: provide chain_list function on sink pad 2015-06-01 19:00:55 +01:00
gstrtpbasepayload.c rtpbasepayload: Always prefer downstream's ssrc suggestion if any 2015-06-05 16:44:08 +02:00
gstrtpbasepayload.h Fix FSF address 2012-11-03 23:05:09 +00:00
gstrtpbuffer.c rtpbuffer: optimise payload mapping for buffers with one memory 2015-06-01 19:01:23 +01:00
gstrtpbuffer.h rtpbuffer: add gst_rtp_buffer_get_payload_bytes 2013-06-18 11:23:40 +02:00
gstrtpdefs.h rtp: Add GstRTPProfile enum 2015-05-20 15:41:06 +03:00
gstrtphdrext.c doc: Fix gsttrtphdrext section name 2015-06-18 21:03:15 -04:00
gstrtphdrext.h rtp: add helpers for header extensions 2012-11-06 09:18:54 +01:00
gstrtppayloads.c docs: remove outdated and pointless 'Last reviewed' lines from docs 2014-04-26 23:28:57 +01:00
gstrtppayloads.h Fix FSF address 2012-11-03 23:05:09 +00:00
Makefile.am gi: Use INTROSPECTION_INIT for --add-init-section 2015-06-16 18:04:57 -04:00
README rtp: Add support for multiple memory blocks in RTP 2012-07-17 16:41:36 +02:00
rtp.h rtp: Add GstRTPProfile enum 2015-05-20 15:41:06 +03:00

The RTP libraries
---------------------

  RTP Buffers
  -----------
  The real time protocol as described in RFC 3550 requires the use of special
  packets containing an additional RTP header of at least 12 bytes. GStreamer
  provides some helper functions for creating and parsing these RTP headers.
  The result is a normal #GstBuffer with an additional RTP header.
 
  RTP buffers are usually created with gst_rtp_buffer_new_allocate() or
  gst_rtp_buffer_new_allocate_len(). These functions create buffers with a
  preallocated space of memory. It will also ensure that enough memory
  is allocated for the RTP header. The first function is used when the payload
  size is known. gst_rtp_buffer_new_allocate_len() should be used when the size
  of the whole RTP buffer (RTP header + payload) is known.
 
  When receiving RTP buffers from a network, gst_rtp_buffer_new_take_data()
  should be used when the user would like to parse that RTP packet. (TODO Ask
  Wim what the real purpose of this function is as it seems to simply create a
  duplicate GstBuffer with the same data as the previous one). The
  function will create a new RTP buffer with the given data as the whole RTP
  packet. Alternatively, gst_rtp_buffer_new_copy_data() can be used if the user
  wishes to make a copy of the data before using it in the new RTP buffer.
 
  It is now possible to use all the gst_rtp_buffer_get_*() or
  gst_rtp_buffer_set_*() functions to read or write the different parts of the
  RTP header such as the payload type, the sequence number or the RTP
  timestamp. The use can also retreive a pointer to the actual RTP payload data
  using the gst_rtp_buffer_get_payload() function.

  RTP Base Payloader Class (GstBaseRTPPayload)
  --------------------------------------------

  All RTP payloader elements (audio or video) should derive from this class.

  RTP Base Audio Payloader Class (GstBaseRTPAudioPayload)
  -------------------------------------------------------

  This base class can be tested through it's children classes. Here is an
  example using the iLBC payloader (frame based).

  For 20ms mode :

  GST_DEBUG="basertpaudiopayload:5" gst-launch-0.10 fakesrc sizetype=2
  sizemax=114 datarate=1900 ! audio/x-iLBC, mode=20 !  rtpilbcpay
  max-ptime="40000000" ! fakesink

  For 30ms mode :

  GST_DEBUG="basertpaudiopayload:5" gst-launch-0.10 fakesrc sizetype=2
  sizemax=150 datarate=1662 ! audio/x-iLBC, mode=30 !  rtpilbcpay
  max-ptime="60000000" ! fakesink

  Here is an example using the uLaw payloader (sample based).

  GST_DEBUG="basertpaudiopayload:5" gst-launch-0.10 fakesrc sizetype=2
  sizemax=150 datarate=8000 ! audio/x-mulaw ! rtppcmupay max-ptime="6000000" !
  fakesink

  RTP Base Depayloader Class (GstBaseRTPDepayload)
  ------------------------------------------------

  All RTP depayloader elements (audio or video) should derive from this class.