1. 07 May, 2021 2 commits
  2. 05 May, 2021 2 commits
  3. 04 May, 2021 2 commits
  4. 23 Apr, 2021 2 commits
  5. 21 Apr, 2021 1 commit
  6. 12 Apr, 2021 2 commits
  7. 11 Apr, 2021 1 commit
  8. 10 Apr, 2021 1 commit
  9. 09 Apr, 2021 1 commit
  10. 08 Apr, 2021 1 commit
  11. 07 Apr, 2021 1 commit
  12. 31 Mar, 2021 1 commit
  13. 30 Mar, 2021 1 commit
  14. 28 Mar, 2021 1 commit
  15. 22 Mar, 2021 4 commits
  16. 18 Mar, 2021 5 commits
  17. 11 Mar, 2021 1 commit
  18. 09 Mar, 2021 1 commit
  19. 08 Mar, 2021 2 commits
  20. 03 Mar, 2021 1 commit
  21. 01 Mar, 2021 1 commit
  22. 19 Feb, 2021 1 commit
  23. 17 Feb, 2021 3 commits
  24. 16 Feb, 2021 1 commit
    • Mathieu Duponchelle's avatar
      h264parse: fix timestamping of interlaced fields in output · 8ae56d60
      Mathieu Duponchelle authored
      Instead of relying on GstBaseParse default behaviour of computing
      the duration of a parsed buffer based on the framerate passed
      to gst_base_parse_set_framerate(), we instead compute the duration
      ourselves, as we have more information available.
      
      In particular, this means we now output buffers with a duration
      that matches that of raw interlaced buffers when each field is
      output in a separate buffer.
      
      This fixes DTS interpolation performed by GstBaseParse, as the
      previous behaviour of outputting each field with the duration of
      a full frame was messing up the base class calculations.
      
      When not enough information is available, h264parse simply falls
      back to calculating the duration based on the framerate and hope
      for the best as was the case previously.
      
      Part-of: <!1973>
      8ae56d60
  25. 03 Feb, 2021 1 commit