1. 07 Oct, 2017 9 commits
  2. 06 Oct, 2017 5 commits
  3. 05 Oct, 2017 5 commits
  4. 03 Oct, 2017 1 commit
  5. 01 Oct, 2017 1 commit
  6. 28 Sep, 2017 1 commit
    • Sebastian Dröge's avatar
      sbcdepay: Add property to ignore input timestamps · 58f0eabd
      Sebastian Dröge authored
      This then just counts samples and calculates the output timestamps based
      on that and the very first observed timestamp. The timestamps on the
      buffers are continued to be used to detect discontinuities that are too
      big and reset the counter at that point.
      
      When receiving data via Bluetooth, many devices put completely wrong
      values into the RTP timestamp field. For example iOS seems to put a
      timestamp in milliseconds in there, instead of something based on the
      current sample offset (RTP clock-rate == sample rate).
      
      https://bugzilla.gnome.org/show_bug.cgi?id=787297
      58f0eabd
  7. 26 Sep, 2017 1 commit
  8. 22 Sep, 2017 1 commit
  9. 20 Sep, 2017 1 commit
  10. 19 Sep, 2017 2 commits
  11. 17 Sep, 2017 2 commits
  12. 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
  13. 14 Sep, 2017 1 commit
  14. 13 Sep, 2017 5 commits
  15. 11 Sep, 2017 1 commit
  16. 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
  17. 06 Sep, 2017 2 commits