1. 28 May, 2015 5 commits
  2. 27 May, 2015 10 commits
  3. 26 May, 2015 5 commits
  4. 23 May, 2015 6 commits
  5. 22 May, 2015 4 commits
  6. 21 May, 2015 2 commits
  7. 20 May, 2015 5 commits
    • James Zern's avatar
      vp9_mvref_common.c: fix compile warning · a492bcef
      James Zern authored
      string literal to int within an assert
      
      Change-Id: Ifd7acc717e01ee1bb3955ef830ec0d1645942459
      a492bcef
    • Marco's avatar
      vp8_drop_encodedframe_overshoot: fix to return setting. · 6f41e290
      Marco authored
      Make sure force_maxqp is set to 0 for return 0.
      
      Change-Id: Ie7c57842637226e932a390e7080e5ebb99996da3
      6f41e290
    • Minghai Shang's avatar
      [decoder] Optimize context buffer re-allocation · 48bfee87
      Minghai Shang authored
      1. Check existing buffer sizes when re-allocate context buffers.
      2. Don't need to set mi buffers to 0 during setup_mi.
      
      Change-Id: I6b48b0e077a4d804312b605ad0dc34aec5795a6d
      48bfee87
    • Minghai Shang's avatar
      [svc] Turn on frame_parallel_decoding_mode · e2c6a633
      Minghai Shang authored
      Change-Id: I33b0384ee87f83950e03be6c999bc5f193055fd3
      e2c6a633
    • paulwilkins's avatar
      Fix issues with mixed ARF and GF groups. · ade9693a
      paulwilkins authored
      This patch addresses two issues that can occur when the
      encoder chooses to use a mixture of ARF and GF groups.
      
      The first issue relates to a failure to reset the "ARF active" flag
      correctly when transitioning from coding ARF groups to coding
      GF groups. This caused some golden frames to be  encoded
      with an incorrect bit rate target as if they were ARF overlay frames.
      
      The second issue relates to the encoding of a single short GF group
      just before a key frame.  Where the last group before a key frame
      is an ARF group we expect the final frame before the key frame  to
      be an low data rate overlay frame. However, when the last  group
      is a GF group, the final frame before the key frame should be a normal
      frame with a normal bit allocation. This issue had the potential to cause
      a single poorly coded frame just before a key frame. If that key frame
      were a forced key frame rather than a real scene cut, this might cause
      pulsing.
      
      Change-Id: Idf1eb5eaf63a231495a74de7899236e1ead9fb00
      ade9693a
  8. 19 May, 2015 3 commits