1. 04 Jun, 2014 1 commit
  2. 01 Apr, 2014 1 commit
  3. 16 Mar, 2014 2 commits
  4. 28 Feb, 2014 2 commits
  5. 27 Feb, 2014 2 commits
  6. 13 Feb, 2014 1 commit
  7. 18 Jan, 2014 1 commit
  8. 02 Dec, 2013 2 commits
  9. 27 Nov, 2013 1 commit
  10. 18 Nov, 2013 1 commit
  11. 02 Nov, 2013 1 commit
  12. 25 Oct, 2013 1 commit
  13. 09 Oct, 2013 1 commit
  14. 20 Aug, 2013 1 commit
  15. 04 May, 2013 1 commit
  16. 27 Apr, 2013 1 commit
  17. 30 Mar, 2013 3 commits
  18. 28 Mar, 2013 1 commit
  19. 21 Mar, 2013 1 commit
  20. 17 Mar, 2013 1 commit
  21. 12 Mar, 2013 1 commit
  22. 11 Mar, 2013 1 commit
  23. 08 Mar, 2013 1 commit
  24. 25 Feb, 2013 1 commit
  25. 15 Feb, 2013 1 commit
    • Anton Khirnov's avatar
      h264: deMpegEncContextize · 2c541554
      Anton Khirnov authored
      Most of the changes are just trivial are just trivial replacements of
      fields from MpegEncContext with equivalent fields in H264Context.
      Everything in h264* other than h264.c are those trivial changes.
      
      The nontrivial parts are:
      1) extracting a simplified version of the frame management code from
         mpegvideo.c. We don't need last/next_picture anymore, since h264 uses
         its own more complex system already and those were set only to appease
         the mpegvideo parts.
      2) some tables that need to be allocated/freed in appropriate places.
      3) hwaccels -- mostly trivial replacements.
         for dxva, the draw_horiz_band() call is moved from
         ff_dxva2_common_end_frame() to per-codec end_frame() callbacks,
         because it's now different for h264 and MpegEncContext-based
         decoders.
      4) svq3 -- it does not use h264 complex reference system, so I just
         added some very simplistic frame management instead and dropped the
         use of ff_h264_frame_start(). Because of this I also had to move some
         initialization code to svq3.
      
      Additional fixes for chroma format and bit depth changes by
      Janne Grunau <janne-libav@jannau.net>
      Signed-off-by: 's avatarAnton Khirnov <anton@khirnov.net>
      2c541554
  26. 13 Feb, 2013 1 commit
  27. 20 Jan, 2013 3 commits
  28. 15 Jan, 2013 1 commit
    • Ronald S. Bultje's avatar
      h264: don't clobber mmco opcode tables for non-first slice headers. · f6badba1
      Ronald S. Bultje authored
      Clobbering these tables will temporarily clobber the template used
      as a basis for other threads to start decoding from. If the other
      decoding thread updates from the template right at that moment,
      subsequent threads will get invalid (or, usually, none at all) mmco
      tables. This leads to invalid reference lists and subsequent decode
      failures.
      
      Therefore, instead, decode the mmco tables only for the first slice in
      a field or frame. For other slices, decode the bits and ensure they
      are identical to the mmco tables in the first slice, but don't ever
      clobber the context state. This prevents other threads from using a
      clobbered/invalid template as starting point for decoding, and thus
      fixes decoding in these cases.
      
      This fixes occasional (~1%) failures of h264-conformance-mr1_bt_a with
      frame-multithreading enabled.
      Signed-off-by: 's avatarMichael Niedermayer <michaelni@gmx.at>
      f6badba1
  29. 14 Jan, 2013 2 commits
    • Anton Khirnov's avatar
      h264: fix ff_generate_sliding_window_mmcos() prototype. · ea382767
      Anton Khirnov authored
      It's been returning an error value since
      bad446e2
      
      Also check for the errors it returns.
      ea382767
    • Ronald S. Bultje's avatar
      h264: don't clobber mmco opcode tables for non-first slice headers. · bad446e2
      Ronald S. Bultje authored
      Clobbering these tables will temporarily clobber the template used
      as a basis for other threads to start decoding from. If the other
      decoding thread updates from the template right at that moment,
      subsequent threads will get invalid (or, usually, none at all) mmco
      tables. This leads to invalid reference lists and subsequent decode
      failures.
      
      Therefore, instead, decode the mmco tables only for the first slice in
      a field or frame. For other slices, decode the bits and ensure they
      are identical to the mmco tables in the first slice, but don't ever
      clobber the context state. This prevents other threads from using a
      clobbered/invalid template as starting point for decoding, and thus
      fixes decoding in these cases.
      
      This fixes occasional (~1%) failures of h264-conformance-mr1_bt_a with
      frame-multithreading enabled.
      Signed-off-by: 's avatarLuca Barbato <lu_zero@gentoo.org>
      bad446e2
  30. 11 Nov, 2012 1 commit
  31. 15 Oct, 2012 1 commit