1. 21 Jan, 2014 1 commit
    • George Kiagiadakis's avatar
      rtprtxsend: run a new GstTask on the src pad · 133913a1
      George Kiagiadakis authored
      The reason behind this is to minimize the retransmission delay.
      Previously, when a NACK was received, rtprtxsend would put a
      retransmission packet in a queue and it would send it from chain(),
      i.e. only after a new buffer would arrive.
      
      This unfortunately was causing big delays, in the order of 60-100 ms,
      which can be critical for the receiver side.
      
      By having a separate GstTask for pushing buffers out of rtxsend,
      we can push buffers out right after receiving the event, without
      waiting for chain() to get called.
      133913a1
  2. 15 Jan, 2014 2 commits
  3. 03 Jan, 2014 5 commits
    • Wim Taymans's avatar
      rtprtxsend: Allow SSRC-multiplexing and multiple payload types in the original stream · 130ad1b1
      Wim Taymans authored
      Conflicts:
      	tests/examples/rtp/server-rtpaux.c
      130ad1b1
    • George Kiagiadakis's avatar
      rtprtxsend: use a GSequence to implement the buffer queue · 51edc071
      George Kiagiadakis authored
      This has the advantage that searching the queue to find the
      buffer with the requested seqnum is done with binary search.
      51edc071
    • George Kiagiadakis's avatar
    • George Kiagiadakis's avatar
      rtprtxsend: Handle the max_size_time property · 7d530ab5
      George Kiagiadakis authored
      This property allows you to specify the amount of buffers
      to keep in the retransmission queue expressed as time (ms)
      instead of buffer count (which is the max_size_buffers property).
      7d530ab5
    • Julien Isorce's avatar
      rtpmanager: add new rtprtxsend / rtprtxreceive elements · 5a1aa759
      Julien Isorce authored
      The purpose of the sender RTX object is to keep a history
      of RTP packets up to a configurable limit (in time). It will
      listen for custom retransmission events from downstream. When
      it receives a request for retransmission, it will look up the
      requested seqnum in its list of stored packets. If the packet
      is available, it will create a RTX packet according to RFC 4588
      and send this as an auxiliary stream.
      
      The receiver will listen to the custom retransmission events
      from the downstream jitterbuffer and will remember the SSRC1
      of the stream and seqnum that was requested. When it sees a
      packet with one of the stored seqnum, it associates the SSRC2
      of the stream with the SSRC1 of the master stream. From then
      on it knows that SSRC2 is the retransmission stream of SSRC1.
      This algorithm is stated in RFC 4588. For this algorithm to
      work, RFC4588 also states that no two pending retransmission
      requests can exist for the same seqnum and different SSRCs or
      else it would be impossible to associate the retransmission with
      the original requester SSRC.
      When the RTX receiver has associated the retransmission packets,
      it can depayload and forward them to the source pad of the element.
      
      RTX is SSRC-multiplexed
      
      Fixes https://bugzilla.gnome.org/show_bug.cgi?id=711084
      5a1aa759