1. 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
  2. 12 Jun, 2017 1 commit
  3. 04 May, 2016 1 commit
  4. 27 Jul, 2015 1 commit
  5. 13 Oct, 2014 1 commit
    • Anton Khirnov's avatar
      lavc: use a separate field for exporting audio encoder padding · 2df0c32e
      Anton Khirnov authored
      Currently, the amount of padding inserted at the beginning by some audio
      encoders, is exported through AVCodecContext.delay. However
      - the term 'delay' is heavily overloaded and can have multiple different
        meanings even in the case of audio encoding.
      - this field has entirely different meanings, depending on whether the
        codec context is used for encoding or decoding (and has yet another
        different meaning for video), preventing generic handling of the codec
        context.
      
      Therefore, add a new field -- AVCodecContext.initial_padding. It could
      conceivably be used for decoding as well at a later point.
      2df0c32e
  6. 24 Aug, 2014 1 commit
  7. 03 Oct, 2013 1 commit
  8. 04 Jul, 2013 1 commit
  9. 09 Mar, 2013 1 commit
  10. 06 Mar, 2013 1 commit
  11. 02 Nov, 2012 1 commit
  12. 04 Sep, 2012 1 commit
  13. 15 Aug, 2012 1 commit
  14. 07 Aug, 2012 1 commit
  15. 30 Jul, 2012 1 commit
  16. 06 Apr, 2012 1 commit
  17. 23 Mar, 2012 1 commit
  18. 22 Mar, 2012 1 commit
  19. 21 Mar, 2012 1 commit
  20. 25 Feb, 2012 1 commit
  21. 28 Jan, 2012 1 commit
  22. 12 Oct, 2011 1 commit
  23. 29 Jul, 2011 1 commit
  24. 07 Jul, 2011 1 commit
  25. 18 Apr, 2011 1 commit
  26. 13 Apr, 2011 9 commits
  27. 12 Apr, 2011 4 commits
  28. 11 Apr, 2011 1 commit