1. 04 May, 2021 1 commit
  2. 28 Apr, 2021 1 commit
  3. 23 Apr, 2021 1 commit
  4. 22 Apr, 2021 1 commit
  5. 21 Apr, 2021 1 commit
  6. 16 Apr, 2021 2 commits
  7. 14 Apr, 2021 1 commit
  8. 13 Apr, 2021 1 commit
  9. 07 Apr, 2021 1 commit
  10. 28 Mar, 2021 1 commit
  11. 25 Mar, 2021 2 commits
    • Seungha Yang's avatar
      mfvideoenc: Don't pass 0/1 framerate to MFT · c0c80438
      Seungha Yang authored
      Some MFT implementations do not accept 0/1 framerate and it will
      result in encoder open failure. If framerate is unknown,
      we will use arbitrary 25/1 framerate value.
      
      Part-of: <!2109>
      c0c80438
    • Sebastian Dröge's avatar
      h2645parser: Catch overflows in AVC/HEVC NAL unit length calculations · 0cfbf7ad
      Sebastian Dröge authored
      Offset and size are stored as 32 bit guint and might overflow when
      adding the nal_length_size, so let's avoid that.
      
      For the size this would happen if the AVC/HEVC NAL unit size happens to
      be stored in 4 bytes and is 4294967292 or higher, which is likely
      corrupted data anyway.
      
      For the offset this is something for the caller of these functions to
      take care of but is unlikely to happen as it would require parsing on a
      >4GB buffer.
      
      Allowing these overflows causes all kinds of follow-up bugs in the
      h2645parse elements, ranging from infinite loops and memory leaks to
      potential memory corruptions.
      
      Part-of: <!2107>
      0cfbf7ad
  12. 15 Mar, 2021 2 commits
  13. 12 Mar, 2021 3 commits
  14. 11 Mar, 2021 1 commit
  15. 10 Mar, 2021 1 commit
  16. 07 Mar, 2021 1 commit
  17. 04 Mar, 2021 2 commits
    • Seungha Yang's avatar
      d3d11h264dec: Keep track of actually configured DPB size · fe278578
      Seungha Yang authored
      ... instead of the largest we ever seen.
      Note that d3d11h264dec element holds previously configured DPB size
      for later decoder object re-open decision.
      
      This is to fix below case:
      1) Initial SPS, required DPB size is 6
        - decoder object is opened with DPB size 6
        - max_dpb_size is now 6
      2) SPS update with resolution change, required DPB size is 1
        - decoder object is re-opened with DPB size 1
        - max_dpb_size should be updated to 1, but it didn't happen (BUG)
      3) SPS update without resolution change, only required DPB size is updated to 6
        - decoder object should be re-opened but didn't happen
          because we didn't update max_dpb_size at 2).
      
      Part-of: <!2057>
      fe278578
    • Seungha Yang's avatar
      d3d11h264dec: Reconfigure decoder object on DPB size change · c87f178e
      Seungha Yang authored
      Even if resolution and/or bitdepth is not updated, required
      DPB size can be changed per SPS update and it could be even
      larger than previously configured size of DPB. If so, we need
      to reconfigure DPB d3d11 texture pool again.
      
      Part-of: <!2057>
      c87f178e
  18. 01 Mar, 2021 1 commit
  19. 26 Feb, 2021 2 commits
  20. 25 Feb, 2021 1 commit
  21. 19 Feb, 2021 1 commit
  22. 30 Jan, 2021 1 commit
  23. 28 Jan, 2021 1 commit
  24. 21 Jan, 2021 1 commit
  25. 14 Jan, 2021 1 commit
  26. 13 Jan, 2021 3 commits
  27. 31 Dec, 2020 1 commit
  28. 30 Dec, 2020 2 commits
  29. 29 Dec, 2020 2 commits