1. 20 6月, 2017 4 次提交
  2. 19 6月, 2017 4 次提交
  3. 18 6月, 2017 8 次提交
  4. 15 6月, 2017 1 次提交
  5. 14 6月, 2017 1 次提交
  6. 13 6月, 2017 3 次提交
  7. 12 6月, 2017 1 次提交
  8. 10 6月, 2017 1 次提交
  9. 09 6月, 2017 5 次提交
    • W
      dxva: add support for new dxva2 and d3d11 hwaccel APIs · f9e7a2f9
      wm4 提交于
      This also adds support to avconv (which is trivial due to the new
      hwaccel API being generic enough).
      
      The new decoder setup code in dxva2.c is significantly based on work by
      Steve Lhomme <robux4@gmail.com>, but with heavy changes/rewrites.
      Signed-off-by: NDiego Biurrun <diego@biurrun.de>
      f9e7a2f9
    • W
      dxva: move d3d11 locking/unlocking to functions · 831cfe10
      wm4 提交于
      I want to make it non-mandatory to set a mutex in the D3D11 device
      context, and replacing it with user callbacks seems like the best
      solution. This is preparation for it. Also makes the code slightly more
      readable.
      Signed-off-by: NDiego Biurrun <diego@biurrun.de>
      831cfe10
    • W
      dxva: preparations for new hwaccel API · 4dec101a
      wm4 提交于
      The actual hwaccel code will need to access an internal context instead
      of avctx->hwaccel_context, so add a new DXVA_CONTEXT() macro, that will
      dispatch between the "old" external and the new internal context.
      
      Also, the new API requires a new D3D11 pixfmt, so all places which check
      for the pixfmt need to be adjusted. Introduce a ff_dxva2_is_d3d11()
      function, which does the check.
      Signed-off-by: NDiego Biurrun <diego@biurrun.de>
      4dec101a
    • W
      lavc: set avctx->hwaccel before init · bd747b92
      wm4 提交于
      So a hwaccel can access avctx->hwaccel in init for whatever reason. This
      is for the new d3d hwaccel API. We could create separate entrypoints for
      each of the 3 hwaccel types (dxva2, d3d11va, new d3d11va), but this
      seems nicer.
      Signed-off-by: NDiego Biurrun <diego@biurrun.de>
      bd747b92
    • W
      lavu: add new D3D11 pixfmt and hwcontext · fff90422
      wm4 提交于
      To be used with the new d3d11 hwaccel decode API.
      
      With the new hwaccel API, we don't want surfaces to depend on the
      decoder (other than the required dimension and format). The old D3D11VA
      pixfmt uses ID3D11VideoDecoderOutputView pointers, which include the
      decoder configuration, and thus is incompatible with the new hwaccel
      API. This patch introduces AV_PIX_FMT_D3D11, which uses ID3D11Texture2D
      and an index. It's simpler and compatible with the new hwaccel API.
      
      The introduced hwcontext supports only the new pixfmt.
      
      Frame upload code untested.
      
      Significantly based on work by Steve Lhomme <robux4@gmail.com>, but with
      heavy changes/rewrites.
      Signed-off-by: NDiego Biurrun <diego@biurrun.de>
      fff90422
  10. 06 6月, 2017 1 次提交
  11. 04 6月, 2017 4 次提交
  12. 03 6月, 2017 1 次提交
    • J
      avutil/md5: fix misaligned reads · a876958d
      James Almer 提交于
      This makes ubsan happy and also considerably increases performance on
      big endian systems.
      
      Tested on an IBM POWER7 3.55 GHz
      
      Before:
      
      2.24user 0.14system 0:02.39elapsed 99%CPU (0avgtext+0avgdata 2624maxresident)k
      2.26user 0.11system 0:02.38elapsed 99%CPU (0avgtext+0avgdata 2688maxresident)k
      2.23user 0.15system 0:02.38elapsed 99%CPU (0avgtext+0avgdata 2624maxresident)k
      2.25user 0.12system 0:02.38elapsed 100%CPU (0avgtext+0avgdata 2624maxresident)k
      2.20user 0.15system 0:02.36elapsed 99%CPU (0avgtext+0avgdata 2624maxresident)k
      
      After:
      
      1.86user 0.13system 0:02.00elapsed 99%CPU (0avgtext+0avgdata 2624maxresident)k
      1.89user 0.11system 0:02.01elapsed 99%CPU (0avgtext+0avgdata 2624maxresident)k
      1.85user 0.14system 0:02.00elapsed 99%CPU (0avgtext+0avgdata 2624maxresident)k
      1.84user 0.15system 0:01.99elapsed 99%CPU (0avgtext+0avgdata 2624maxresident)k
      1.89user 0.13system 0:02.02elapsed 99%CPU (0avgtext+0avgdata 2688maxresident)k
      Tested-by: NNicolas George <george@nsup.org>
      Reviewed-by: NMichael Niedermayer <michael@niedermayer.cc>
      Signed-off-by: NJames Almer <jamrial@gmail.com>
      Signed-off-by: NSean McGovern <gseanmcg@gmail.com>
      a876958d
  13. 02 6月, 2017 1 次提交
    • D
      tls: Hide backend implementation details from users · 61cec5ad
      Diego Biurrun 提交于
      TLS is currently implemented over either OpenSSL or GnuTLS, with more
      backends likely to appear in the future. Currently, those backend libraries
      are part of the protocol names used during e.g. the configure stage of a
      build. Hide those details behind a generically-named declaration for the
      TLS protocol to avoid leaking those details into the configuration stage.
      61cec5ad
  14. 01 6月, 2017 4 次提交
  15. 31 5月, 2017 1 次提交