1. 01 Nov, 2018 10 commits
  2. 31 Oct, 2018 1 commit
  3. 30 Oct, 2018 11 commits
  4. 29 Oct, 2018 1 commit
  5. 28 Oct, 2018 4 commits
  6. 27 Oct, 2018 1 commit
    • Edward Hervey's avatar
      tests: Solidify tcp connection check · 33e92afd
      Edward Hervey authored
      The previous failure was a timeout which was due to the sending pipeline
      pushing test buffer *before* the remote client was accepted. We would
      therefore never get the buffer on the other side.
      
      While the client socket would indeed appear as "connected", this doesn't
      mean that the remote server side did "accept" it (which is where we then
      add it to the list of remote parties to which data will be sent).
      
      The problem isn't with the element implementation, but to the nature of
      TCP 3-way handshake.
      
      In order to make the test reliable, wait for the sink to have accepted
      the remote client (by checking the number of handles) before sending out
      test buffers.
      33e92afd
  7. 18 Oct, 2018 1 commit
  8. 17 Oct, 2018 2 commits
  9. 15 Oct, 2018 1 commit
  10. 11 Oct, 2018 1 commit
  11. 10 Oct, 2018 1 commit
    • Stian Selnes's avatar
      rtpbasepayload: rtpbasedepayload: Add source-info property · f766b85b
      Stian Selnes authored
      Add a source-info property that will read/write meta to the buffers
      about RTP source information. The GstRTPSourceMeta can be used to
      transport information about the origin of a buffer, e.g. the sources
      that is included in a mixed audio buffer.
      
      A new function gst_rtp_base_payload_allocate_output_buffer() is added
      for payloaders to use to allocate the output RTP buffer with the correct
      number of CSRCs according to the meta and fill it.
      
      RTPSourceMeta does not make sense on RTP buffers since the information
      is in the RTP header. So the payloader will strip the meta from the
      output buffer.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=761947
      f766b85b
  12. 08 Oct, 2018 1 commit
  13. 07 Oct, 2018 1 commit
  14. 05 Oct, 2018 2 commits
  15. 04 Oct, 2018 2 commits