1. 02 May, 2017 1 commit
  2. 27 Apr, 2017 1 commit
  3. 25 Apr, 2017 1 commit
  4. 21 Apr, 2017 1 commit
  5. 17 Apr, 2017 1 commit
    • Edward Hervey's avatar
      qtdemux: Reset adapter in more discontinuity cases · 58e30337
      Edward Hervey authored
      In push mode we process as much as possible in the adapter. When we receive
      a DISCONT buffer which we can't match to an actual sample (based on the existing
      sample table) and there is still data remaining in the incoming adapter,there is
      one of two cases happening:
      1) We are doing reverse playback, in which case we should flush out all pending
        data
      2) We have leftover data from the previous incoming buffer... which we can't do
        anything about.
      
      For the second case, make sure we flush out the remaining data so that we can start
      parsing again from scratch.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=781319
      58e30337
  6. 16 Apr, 2017 1 commit
  7. 13 Apr, 2017 1 commit
  8. 12 Apr, 2017 5 commits
  9. 11 Apr, 2017 2 commits
  10. 03 Apr, 2017 1 commit
    • Edward Hervey's avatar
      qtdemux: Update variables before early exit · 1e4cdc6d
      Edward Hervey authored
      This is an update of d78d5896
      
      We still exit as early as possible in case of non-ok/non-unlinked combined
      flow, but we first make sure that we update the internal position variables.
      
      This ensures that if upstreams "ignores" the flow return (and carries on pushing),
      we don't end up processing data with completely bogus variables/positions.
      1e4cdc6d
  11. 27 Mar, 2017 1 commit
  12. 22 Mar, 2017 1 commit
  13. 21 Mar, 2017 2 commits
  14. 14 Mar, 2017 2 commits
  15. 03 Mar, 2017 1 commit
    • 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
  16. 28 Feb, 2017 1 commit
  17. 27 Feb, 2017 1 commit
    • Sebastian Dröge's avatar
      qtdemux: Fix compilation with gcc 7 · 4c30cbfe
      Sebastian Dröge authored
      qtdemux.c: In function ‘qtdemux_parse_samples’:
      qtdemux.c:8450:39: error: ‘*’ in boolean context, suggest ‘&&’ instead [-Werror=int-in-bool-context]
               if (stream->samples_per_frame * stream->bytes_per_frame) {
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~
      4c30cbfe
  18. 17 Feb, 2017 1 commit
  19. 31 Jan, 2017 3 commits
  20. 19 Jan, 2017 3 commits
  21. 18 Jan, 2017 2 commits
  22. 14 Jan, 2017 2 commits
  23. 12 Jan, 2017 1 commit
  24. 10 Jan, 2017 1 commit
  25. 07 Jan, 2017 1 commit
  26. 02 Jan, 2017 2 commits
    • Jan Schmidt's avatar
      qtdemux: Always snap to the start of the keyframe · 107902ec
      Jan Schmidt authored
      When performing a key-unit seek, always snap to the start ts
      of the keyframe buffer we landed on so that the keyframe is
      entirely within the resulting outgoing segment. That seems
      the most sensible result, since the user requested snapping
      to the keyframe position.
      107902ec
    • Jan Schmidt's avatar
      qtdemux: Omit cslg_shift when snapping seeks · f415730f
      Jan Schmidt authored
      Segments times and seek requests are stored and handled
      in raw 'PTS' time, without the cslg_shift - which only applies
      to outgoing samples. Omit the cslg_shift portion when
      extracting PTS to compare for internal seek snaps.
      
      If the cslg_shift is included, then keyframe+snap-before seeks
      generate a segment start/stop time that already includes the
      cslg_shift, and it's then added a 2nd time, causing the
      first buffer(s) to have timestamps that are out of segment.
      f415730f