1. 14 Mar, 2017 7 commits
  2. 12 Mar, 2017 1 commit
  3. 10 Mar, 2017 2 commits
  4. 09 Mar, 2017 3 commits
  5. 08 Mar, 2017 2 commits
  6. 03 Mar, 2017 3 commits
    • Jan Schmidt's avatar
      splitmux: Add unit test for reverse playback · 4335c4c1
      Jan Schmidt authored
      Ensure that reverse playback works and generates the range
      of timestamps (0-3s) we expect, in monotonically descending order.
      4335c4c1
    • Jan Schmidt's avatar
      splitmuxsrc: Fix reverse playback · 7c0a9cb5
      Jan Schmidt authored
      Fix the check for whether the start time of the segment has
      been reached when playing in reverse. Otherwise, playback
      stops after reaching the start of any file part, instead of
      continuing until all parts within the segment have played
      7c0a9cb5
    • Jan Schmidt's avatar
      qtdemux: Don't lose crypto info on a new moof · c82ced18
      Jan Schmidt authored
      We parse the next moof in advance of having pushed
      all samples from the previous one in some cases, and
      we'll still need the crypto info from the previous
      fragment so keep around any unused crypto info entries
      when adding new ones
      c82ced18
  7. 02 Mar, 2017 2 commits
  8. 01 Mar, 2017 1 commit
  9. 28 Feb, 2017 5 commits
  10. 27 Feb, 2017 9 commits
  11. 26 Feb, 2017 1 commit
    • Andrew's avatar
      rtpjitterbuffer: Don't always reset PTS to 0 after a gap · 76792a5c
      Andrew 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
      76792a5c
  12. 24 Feb, 2017 4 commits