1. 20 Oct, 2018 1 commit
  2. 19 Oct, 2018 5 commits
  3. 17 Oct, 2018 1 commit
  4. 25 Sep, 2018 1 commit
  5. 24 Sep, 2018 1 commit
  6. 03 Sep, 2018 1 commit
  7. 02 Aug, 2018 1 commit
  8. 31 Jul, 2018 1 commit
  9. 26 Jul, 2018 2 commits
  10. 06 Jul, 2018 1 commit
  11. 29 Jun, 2018 2 commits
    • Alicia Boya García's avatar
      qtdemux: rework segment event pushing, again · 025a430d
      Alicia Boya García authored
      This patch aims at fixing the recent regressions in the adaptive test
      suite.
      
      All segment pushing in push mode is now done with
      gst_qtdemux_check_send_pending_segment(), which is idempotent and
      handles both edit lists cases and cases where the upstream TIME segments
      have to be sent directly.
      
      Fragmented files that start with a non-zero tfdt are also taken into
      account, but their handling has been vastly simplified: now they are
      handled as implicit default seeks so there is no need to extend the
      GstSegment formulas as was being done before.
      
      qtdemux->segment.duration is no longer modified when
      upstream_format_is_time, respecting in this way the durations provided
      by dashdemux and fixing bugs in reverse playback tests where mangled
      durations appeared in the emitted segments.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=752603
      025a430d
    • Alicia Boya García's avatar
      qtdemux: Don't send EOS during upstream reverse playback · 2c394304
      Alicia Boya García authored
      Upstream driving elements such as dashdemux often do reverse playback by
      feeding qtdemux with the fragments containing the requested playback
      range in reverse order.
      
      But the requested playback range stop may be somewhere in the
      middle of a fragment. In that case, a naive pts >= segment.stop
      condition may declare end of segment prematurely when demuxing this
      first fragment.
      
      This used not to happen because there were places in moov parsing where
      segment.stop was overwritten to GST_CLOCK_TIME_NONE even if
      upstream_format_is_time -- resulting in this case in a segment with rate
      < 0 and stop == -1 and hence not triggering the EOS check, but that was
      likely an accident.
      
      This patch modifies the EOS check to take this case into account, not
      sending EOS when upstream_format_is_time if rate < 0.
      
      This fixes adaptive.dash.playback.seek_end_live.DASHIF_livestream_testpic_2s
      
      https://bugzilla.gnome.org/show_bug.cgi?id=752603
      2c394304
  12. 06 Jun, 2018 2 commits
  13. 28 May, 2018 2 commits
  14. 25 May, 2018 5 commits
  15. 24 May, 2018 4 commits
  16. 23 May, 2018 1 commit
  17. 22 May, 2018 1 commit
  18. 21 May, 2018 2 commits
  19. 18 May, 2018 1 commit
  20. 10 May, 2018 5 commits