1. 13 Nov, 2018 1 commit
    • Linus Svensson's avatar
      rtpsession: Implement reset · 8fc8b7ee
      Linus Svensson authored
      Reset RTPSession when rtpsession changes state from PAUSED to READY.
      Without this change, a stored last_rtptime in RTPSource could interfere
      with RTP timestamp generation in RTCP Sender Report.
      
      Fixes #510
      8fc8b7ee
  2. 12 Nov, 2018 1 commit
  3. 07 Nov, 2018 1 commit
  4. 28 Oct, 2018 1 commit
  5. 15 Oct, 2018 2 commits
  6. 10 Oct, 2018 4 commits
  7. 12 Jul, 2018 1 commit
  8. 23 Jun, 2018 1 commit
  9. 23 May, 2018 1 commit
  10. 15 May, 2018 3 commits
  11. 13 May, 2018 4 commits
  12. 25 Apr, 2018 1 commit
  13. 06 Apr, 2018 2 commits
  14. 12 Mar, 2018 1 commit
  15. 26 Feb, 2018 2 commits
  16. 21 Feb, 2018 4 commits
  17. 15 Feb, 2018 1 commit
  18. 18 Jan, 2018 1 commit
    • Mathieu Duponchelle's avatar
      rtpbin: fix leak of elements requested by signals · 03dc2295
      Mathieu Duponchelle authored
      When the signal returns a floating reference, as its return type
      is transfer full, we need to sink it ourselves before passing
      it to gst_bin_add (which is transfer floating).
      
      This allows us to unref it in bin_remove_element later on, and
      thus to also release the reference we now own if the signal
      returns a non-floating reference as well.
      
      As we now still hold a reference to the element when removing it,
      we also need to lock its state and setting it to NULL before
      unreffing it
      
      Also update the request_aux_sender test.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=792543
      03dc2295
  19. 02 Dec, 2017 1 commit
  20. 01 Nov, 2017 1 commit
  21. 07 Oct, 2017 2 commits
  22. 17 Sep, 2017 1 commit
  23. 15 Sep, 2017 1 commit
    • Patrick Radizi's avatar
      rtpbin: add option for sanity checking timestamp offset · 3de02445
      Patrick Radizi authored
      Timestamp offsets needs to be checked to detect unrealistic values
      caused for example by NTP clocks not in sync. The new parameter
      max-ts-offset lets the user decide an upper offset limit. There
      are two different cases for checking the offset based on if
      ntp-sync is used or not:
      1) ntp-sync enabled
         Only negative offsest are allowed since a positive offset would
         mean that the sender and receiver clocks are not in sync.
         Default vaule of max-ts-offset = 0 (disabled)
      2) ntp-sync disabled
         Both positive and negative offsets are allowed.
         Default vaule of max-ts-offset = 3000000000
      The reason for different default values is to be backwards
      compatible.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=785733
      3de02445
  24. 14 Sep, 2017 1 commit
  25. 07 Sep, 2017 1 commit
    • George Kiagiadakis's avatar
      rtprtx{send,receive}: improve the debug messages · 286e1e62
      George Kiagiadakis authored
      * use INFO/DEBUG/LOG/TRACE equaly and meaningfully;
        previously rtprtxsend:LOG and rtprtxreceive:LOG would generate
        a totally different amount of log traffic and sometimes it was
        impossible to see the information you wanted without useless
        spam being printed around
      * improve the wording, give a reasonable and self-explanatory
        amount of information
      * print SSRCs in hex
      * avoid G_FOO_FORMAT for readability (we are just printing integers)
      286e1e62