1. 16 Feb, 2019 4 commits
    • Philip Langdale's avatar
      avcodec/cuviddec: Add support for decoding HEVC 4:4:4 content · 317b7b06
      Philip Langdale authored
      This is the equivalent change for cuviddec after the previous change
      for nvdec. I made similar changes to the copying routines to handle
      pixel formats in a more generic way.
      
      Note that unlike with nvdec, there is no confusion about the ability
      of a codec to output 444 formats. This is because the cuvid parser is
      used, meaning that 444 JPEG content is still indicated as using a 420
      output format.
      317b7b06
    • Philip Langdale's avatar
      avcodec/nvdec: Explicitly mark codecs that support 444 output formats · 83c7ac2e
      Philip Langdale authored
      With the introduction of HEVC 444 support, we technically have two
      codecs that can handle 444 - HEVC and MJPEG. In the case of MJPEG,
      it can decode, but can only output one of the semi-planar formats.
      
      That means we need additional logic to decide whether to use a
      444 output format or not.
      83c7ac2e
    • Philip Langdale's avatar
      avcodec/nvdec: Add support for decoding HEVC 4:4:4 content · e06ccfbe
      Philip Langdale authored
      The latest generation video decoder on the Turing chips supports
      decoding HEVC 4:4:4. Supporting this is relatively straight-forward;
      we need to account for the different chroma format and pick the
      right output and sw formats at the right times.
      
      There was one bug which was the hard-coded assumption that the
      first chroma plane would be half-height; I fixed this to use the
      actual shift value on the plane.
      
      We also need to pass the SPS and PPS range extension flags.
      e06ccfbe
    • Philip Langdale's avatar
      avcodec/hevc_ps: Expose all SPS and PPS range extension flags · f4ea930a
      Philip Langdale authored
      We need all the flags to be exposed to be able to pass them on to
      HW decoders. I did not attempt to nuance any of the warnings about
      flags being unsupported as there's no way, at the point we extract
      flags, to say whether an HW decoder is being used.
      f4ea930a
  2. 14 Feb, 2019 4 commits
  3. 13 Feb, 2019 5 commits
  4. 12 Feb, 2019 8 commits
  5. 11 Feb, 2019 4 commits
  6. 10 Feb, 2019 9 commits
  7. 09 Feb, 2019 5 commits
  8. 08 Feb, 2019 1 commit