1. 14 Aug, 2015 2 commits
  2. 10 Aug, 2015 2 commits
  3. 06 Jul, 2015 1 commit
    • Stian Selnes's avatar
      rtcpbuffer: Fix validation of packets with padding · 1586981b
      Stian Selnes authored
      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
      1586981b
  4. 22 Jun, 2015 2 commits
  5. 11 Jun, 2015 2 commits
  6. 05 Jun, 2015 1 commit
  7. 02 Jun, 2015 1 commit
  8. 29 May, 2015 1 commit
  9. 23 May, 2015 1 commit
  10. 19 May, 2015 1 commit
  11. 18 May, 2015 1 commit
  12. 26 Apr, 2015 2 commits
  13. 23 Apr, 2015 2 commits
  14. 17 Apr, 2015 1 commit
  15. 08 Apr, 2015 1 commit
  16. 05 Apr, 2015 2 commits
    • Tim-Philipp Müller's avatar
      tests: appsrc: clean up block_deadlock test and make it work in valgrind · 0aa0b89a
      Tim-Philipp Müller authored
      Remove all the bus watch and main loop code from the block_deadlock
      test, it's not needed: neither pipeline will ever post an EOS or ERROR
      message on the bus, and we're the only ones posting an error, from a
      timeout. Might just as well just sleep for a bit and then do whatever
      we want to do.
      
      Don't gratuitiously set tcase timeout, just use whatever is the
      default (or set via the environment).
      
      Make individual pipeline runs shorter.
      
      Check for valgrind and only do a handful iterations when running
      in valgrind, not 100 (each iteration takes about 4s on a core i7).
      
      Make videotestsrc output smaller buffers than the default resolution,
      we don't care about the buffer contents here anyway.
      
      Fixes test timeouts when run in valgrind.
      0aa0b89a
    • Tim-Philipp Müller's avatar
      tests: multisocketsink: fix flaky unit test · 46aa4744
      Tim-Philipp Müller authored
      On slower systems, or under high system load (e.g. check-valgrind),
      the sending_buffers_with_9_gstmemories test would sometimes fail,
      because the read call only returns 32 bytes instead of the full
      36 bytes expected. This is because multisocketsink might end up
      doing a partial write of 32 bytes first, and then write the
      missing 4 bytes later, but since we don't wait for all of data
      to be written, there's a short window where our read call in the
      unit test might then only receive the 32 bytes written so far,
      which makes it deeply unhappy.
      
      Instead, make sure we loop to read all bytes.
      46aa4744
  17. 04 Apr, 2015 1 commit
    • Tim-Philipp Müller's avatar
      tests: basetime: fix timeouts when running under valgrind · 73278948
      Tim-Philipp Müller authored
      This test sets a rather short timeout, increase this when
      we run under valgrind. Also add a short sleep to the
      fakesrc ! fakesink pipeline to avoid thrashing the CPU,
      which would often not stop the main loop when it should.
      
      Also fix wrong (0.10) return value from pad probe callback.
      73278948
  18. 03 Apr, 2015 1 commit
  19. 02 Apr, 2015 1 commit
  20. 27 Mar, 2015 1 commit
  21. 26 Mar, 2015 1 commit
  22. 16 Mar, 2015 1 commit
  23. 15 Mar, 2015 1 commit
  24. 14 Mar, 2015 1 commit
  25. 13 Mar, 2015 3 commits
    • William Manley's avatar
      socketsrc: Add `connection-closed-by-peer` signal · a297b054
      William Manley authored
      This provides notification that the socket in use was closed by the peer
      and gives an opportunity to replace it with a new one which is not
      closed, allowing reading from many sockets in order.
      
      I use this in pulsevideo to implement reconnection logic to handle the
      pulsevideo service dieing, such that is can be restarted without
      disrupting downstream.
      
      Fixes https://bugzilla.gnome.org/show_bug.cgi?id=739546
      a297b054
    • William Manley's avatar
      tcp: Add element socketsrc · 7c10499e
      William Manley authored
      `socketsrc` can be considered a source counterpart to `multisocketsink`.
      It can be considered a generalization of `tcpclientsrc` and
      `tcpserversrc`:  it contains all the logic required to communicate over
      the socket but none of the logic for creating the sockets/establishing
      the connection in the first place, allowing the user to accomplish this
      externally in whatever manner they wish making it applicable to other
      types of sockets besides TCP.
      
      This commit essentially copies the implementation directly from
      tcpserversrc.  Later patches will tidy the implementation up and
      re-implement `tcpclientsrc` and `tcpserversrc` in terms of `socketsrc`.
      
      See https://bugzilla.gnome.org/show_bug.cgi?id=739546
      7c10499e
    • William Manley's avatar
      multisocketsink: Map `GstMemory`s individually when sending · b8232a74
      William Manley authored
      If a buffer is made up of non-contiguous `GstMemory`s `gst_buffer_map`
      has to copy all the data into a new `GstMemory` which is contiguous.  By
      mapping all the `GstMemory`s individually and then using scatter-gather
      IO we avoid this situation.
      
      This is a preparatory step for adding support to multisocketsink for
      sending file descriptors, where a GstBuffer may be made up of several
      `GstMemory`s, some of which are backed by a memfd or file, but I think this
      patch is valid and useful on its own.
      
      Fixes https://bugzilla.gnome.org/show_bug.cgi?id=746150
      b8232a74
  26. 11 Mar, 2015 1 commit
  27. 10 Mar, 2015 1 commit
  28. 04 Mar, 2015 2 commits
  29. 27 Feb, 2015 2 commits