1. 10 Nov, 2017 1 commit
  2. 23 Oct, 2017 1 commit
    • Clément Bœsch's avatar
      lavc: drop VDA · 2b320318
      Clément Bœsch authored
      Deprecated (aka removed) in OSX 10.11, and we have a replacement for it
      (VideoToolbox).
      2b320318
  3. 12 Sep, 2017 1 commit
  4. 10 Aug, 2017 2 commits
  5. 05 Aug, 2017 1 commit
  6. 27 Jul, 2017 1 commit
    • Wan-Teh Chang's avatar
      avcodec/h264_slice: don't sync default_ref[] between threads. · 8c3b329d
      Wan-Teh Chang authored
      default_ref[] is unconditionally initialized in h264_initialise_ref_list()
      (called from ff_h264_build_ref_list(), called from h264_slice_init()).
      
      This fixes the following tsan warning when running fate-h264:
      
      WARNING: ThreadSanitizer: data race (pid=31070)
        Write of size 8 at 0x7bbc000082a8 by thread T1 (mutexes: write M1628):
          #0 memcpy /work/release-test/final/llvm.src/projects/compiler-rt/lib/tsan/../sanitizer_common/sanitizer_common_interceptors.inc:655:5
      (ffmpeg+0x10de9d)
          #1 h264_initialise_ref_list ffmpeg/libavcodec/h264_refs.c:214:29 (ffmpeg+0x1186b3f)
          #2 ff_h264_build_ref_list ffmpeg/libavcodec/h264_refs.c:306 (ffmpeg+0x1186b3f)
          #3 h264_slice_init ffmpeg/libavcodec/h264_slice.c:1900:11 (ffmpeg+0x1191149)
      [..]
        Previous read of size 8 at 0x7bbc000082a8 by main thread (mutexes:
      write M1630):
          #0 memcpy /work/release-test/final/llvm.src/projects/compiler-rt/lib/tsan/../sanitizer_common/sanitizer_common_interceptors.inc:655:5
      (ffmpeg+0x10de9d)
          #1 ff_h264_update_thread_context ffmpeg/libavcodec/h264_slice.c:411:5 (ffmpeg+0x118b7dc)
      Signed-off-by: 's avatarWan-Teh Chang <wtc@google.com>
      Signed-off-by: 's avatarRonald S. Bultje <rsbultje@gmail.com>
      8c3b329d
  7. 26 Jul, 2017 2 commits
  8. 05 Jul, 2017 1 commit
  9. 27 Jun, 2017 1 commit
    • wm4's avatar
      dxva: add support for new dxva2 and d3d11 hwaccel APIs · 70143a39
      wm4 authored
      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.
      
      Merges Libav commit f9e7a2f9.
      Also adds untested VP9 support.
      The check for DXVA2 COBJs is removed. Just update your MinGW to
      something newer than a 5 year old release.
      Signed-off-by: 's avatarDiego Biurrun <diego@biurrun.de>
      70143a39
  10. 09 Jun, 2017 1 commit
  11. 08 Jun, 2017 1 commit
  12. 26 May, 2017 2 commits
  13. 16 May, 2017 1 commit
  14. 07 Apr, 2017 2 commits
  15. 06 Apr, 2017 1 commit
    • Ronald S. Bultje's avatar
      pthread_frame: allow per-field ThreadFrame owners. · 083300be
      Ronald S. Bultje authored
      This tries to handle cases where separate invocations of decode_frame()
      (each running in separate threads) write to respective fields in the
      same AVFrame->data[]. Having per-field owners makes interaction between
      readers (the referencing thread) and writers (the decoding thread)
      slightly more optimal if both accesses are field-based, since they will
      use the respective producer's thread objects (mutex/cond) instead of
      sharing the thread objects of the first field's producer.
      
      In practice, this fixes the following tsan-warning in fate-h264:
      
      WARNING: ThreadSanitizer: data race (pid=21615)
        Read of size 4 at 0x7d640000d9fc by thread T2 (mutexes: write M1006):
          #0 ff_thread_report_progress pthread_frame.c:569 (ffmpeg:x86_64+0x100f7cf54)
      [..]
        Previous write of size 4 at 0x7d640000d9fc by main thread (mutexes: write M1004):
          #0 update_context_from_user pthread_frame.c:335 (ffmpeg:x86_64+0x100f81abb)
      083300be
  16. 28 Mar, 2017 1 commit
  17. 28 Feb, 2017 1 commit
  18. 14 Feb, 2017 1 commit
  19. 08 Feb, 2017 1 commit
  20. 31 Jan, 2017 1 commit
  21. 19 Jan, 2017 1 commit
  22. 16 Jan, 2017 1 commit
  23. 12 Jan, 2017 2 commits
  24. 09 Jan, 2017 1 commit
  25. 19 Dec, 2016 1 commit
  26. 14 Dec, 2016 1 commit
  27. 09 Dec, 2016 1 commit
  28. 04 Aug, 2016 2 commits
  29. 27 Jul, 2016 2 commits
  30. 19 Jul, 2016 1 commit
  31. 15 Jul, 2016 2 commits
    • Anton Khirnov's avatar
      h264: fix decoding multiple fields per packet with slice threads · 4a9bab3d
      Anton Khirnov authored
      Since we only know whether a NAL unit corresponds to a new field after
      parsing the slice header, this requires reorganizing the calls to slice
      parsing, per-slice/field/frame init and actual decoding.
      
      In the previous code, the function for slice header decoding also
      immediately started a new field/frame as necessary, so any slices
      already queued for decoding would no longer be decodable.
      
      After this patch, we first parse the slice header, and if we determine
      that a new field needs to be started we decode all the queued slices.
      4a9bab3d
    • Anton Khirnov's avatar
      h264: eliminate decode_postinit() · f450cc7b
      Anton Khirnov authored
      This function's purpose is not very well defined. Currently it does two
      (only marginally related) things: selecting the next output frame and
      calling ff_thread_finish_setup() for frame threading. The first of those
      more properly belongs under field_start(), while the second can be
      called directly from decode_nal_units().
      f450cc7b
  32. 11 Jul, 2016 1 commit
    • Anton Khirnov's avatar
      h264_ps: export actual height in MBs as SPS.mb_height · a8cbe5a0
      Anton Khirnov authored
      Currently, SPS.mb_height is actually what the spec calls
      PicHeightInMapUnits, which is half the frame height when interlacing is
      allowed. Calling this 'mb_height' is quite confusing, and there are at
      least two associated bugs where this field is treated as the actual
      frame height - in the h264 parser and in the code computing maximum
      reordering buffer size for a given level.
      
      Fix those issues (and avoid possible future ones) by exporting the real
      frame height in this field.
      a8cbe5a0