1. 15 Jun, 2017 3 commits
  2. 13 Jun, 2017 1 commit
  3. 29 May, 2017 3 commits
  4. 08 May, 2017 8 commits
  5. 12 Apr, 2017 1 commit
  6. 24 Mar, 2017 1 commit
  7. 22 Mar, 2017 1 commit
  8. 17 Mar, 2017 2 commits
  9. 16 Mar, 2017 2 commits
  10. 15 Mar, 2017 3 commits
  11. 10 Mar, 2017 1 commit
  12. 27 Feb, 2017 1 commit
    • Andrew S's avatar
      rtpjitterbuffer: Don't always reset PTS to 0 after a gap · ec1769b0
      Andrew S authored
      In function rtp_jitter_buffer_calculate_pts: If gap in incoming RTP
      timestamps is more than (3 * jbuf->clock_rate) we call
      rtp_jitter_buffer_reset_skew which resets pts to 0. So components down
      the pipeline (playes, mixers) just skip frames/samples until pts becomes
      equal to pts before gap.
      
      In version 1.10.2 and before this checking was bypassed for packets with
      "estimated dts", and gaps were handled correctly.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=778341
      ec1769b0
  13. 23 Feb, 2017 4 commits
  14. 22 Feb, 2017 2 commits
  15. 21 Feb, 2017 6 commits
  16. 20 Feb, 2017 1 commit