1. 01 Oct, 2019 1 commit
  2. 24 Sep, 2019 1 commit
  3. 25 Aug, 2019 1 commit
  4. 10 Aug, 2019 3 commits
  5. 07 Jul, 2019 1 commit
    • Mark Thompson's avatar
      libx264: Update ROI behaviour to match documentation · d76e2aaf
      Mark Thompson authored
      Fix the quantisation offset - use the whole range, and don't change the
      offset size based on bit depth.
      
      Iterate the list in reverse order.  The first region in the list is the one
      that applies in the case of overlapping regions.
      d76e2aaf
  6. 10 May, 2019 1 commit
  7. 17 Jan, 2019 1 commit
  8. 05 Nov, 2018 2 commits
    • Martin Storsjö's avatar
      libx264: Pass the reordered_opaque field through the encoder · 882ae091
      Martin Storsjö authored
      libx264 does have a field for opaque data to pass along with frames
      through the encoder, but it is a pointer, while the libavcodec
      reordered_opaque field is an int64_t. Therefore, allocate an array
      within the libx264 wrapper, where reordered_opaque values in flight
      are stored, and pass a pointer to this array to libx264.
      
      Update the public libavcodec documentation for the AVCodecContext
      field to explain this usage, and add a codec capability that allows
      detecting whether an encoder handles this field.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      882ae091
    • Martin Storsjö's avatar
      libx264: Pass the reordered_opaque field through the encoder · 80f85a95
      Martin Storsjö authored
      libx264 does have a field for opaque data to pass along with frames
      through the encoder, but it is a pointer, while the libavcodec
      reordered_opaque field is an int64_t. Therefore, allocate an array
      within the libx264 wrapper, where reordered_opaque values in flight
      are stored, and pass a pointer to this array to libx264.
      
      Update the public libavcodec documentation for the AVCodecContext
      field to explain this usage, and add a codec capability that allows
      detecting whether an encoder handles this field.
      Signed-off-by: 's avatarMartin Storsjö <martin@martin.st>
      80f85a95
  9. 24 Oct, 2018 1 commit
  10. 07 Aug, 2018 1 commit
  11. 27 Dec, 2017 1 commit
  12. 26 Dec, 2017 3 commits
  13. 14 Dec, 2017 2 commits
    • wm4's avatar
      avcodec: add metadata to identify wrappers and hardware decoders · b945fed6
      wm4 authored
      Explicitly identify decoder/encoder wrappers with a common name. This
      saves API users from guessing by the name suffix. For example, they
      don't have to guess that "h264_qsv" is the h264 QSV implementation, and
      instead they can just check the AVCodec .codec and .wrapper_name fields.
      
      Explicitly mark AVCodec entries that are hardware decoders or most
      likely hardware decoders with new AV_CODEC_CAPs. The purpose is allowing
      API users listing hardware decoders in a more generic way. The proposed
      AVCodecHWConfig does not provide this information fully, because it's
      concerned with decoder configuration, not information about the fact
      whether the hardware is used or not.
      
      AV_CODEC_CAP_HYBRID exists specifically for QSV, which can have software
      implementations in case the hardware is not capable.
      
      Based on a patch by Philip Langdale <philipl@overt.org>.
      
      Merges Libav commit 47687a2f.
      b945fed6
    • wm4's avatar
      avcodec: add metadata to identify wrappers and hardware decoders · 47687a2f
      wm4 authored
      Explicitly identify decoder/encoder wrappers with a common name. This
      saves API users from guessing by the name suffix. For example, they
      don't have to guess that "h264_qsv" is the h264 QSV implementation, and
      instead they can just check the AVCodec .codec and .wrapper_name fields.
      
      Explicitly mark AVCodec entries that are hardware decoders or most
      likely hardware decoders with new AV_CODEC_CAPs. The purpose is allowing
      API users listing hardware decoders in a more generic way. The proposed
      AVCodecHWConfig does not provide this information fully, because it's
      concerned with decoder configuration, not information about the fact
      whether the hardware is used or not.
      
      AV_CODEC_CAP_HYBRID exists specifically for QSV, which can have software
      implementations in case the hardware is not capable.
      
      Based on a patch by Philip Langdale <philipl@overt.org>.
      Signed-off-by: 's avatarLuca Barbato <lu_zero@gentoo.org>
      47687a2f
  14. 23 Oct, 2017 1 commit
  15. 23 Mar, 2017 1 commit
  16. 22 Nov, 2016 1 commit
  17. 14 Sep, 2016 1 commit
  18. 22 Jul, 2016 1 commit
  19. 23 Jun, 2016 1 commit
  20. 19 Jun, 2016 1 commit
  21. 05 Jun, 2016 1 commit
  22. 21 Apr, 2016 2 commits
  23. 23 Feb, 2016 1 commit
  24. 31 Jan, 2016 1 commit
  25. 28 Jan, 2016 2 commits
  26. 27 Jan, 2016 1 commit
  27. 21 Jan, 2016 4 commits
  28. 10 Jan, 2016 1 commit
  29. 07 Dec, 2015 1 commit