1. 12 Mar, 2012 1 commit
  2. 22 Feb, 2012 1 commit
    • Marco Paniconi's avatar
      Remove the frame rate factor for key frame size. · 507ee87e
      Marco Paniconi authored
      When temporal layers is used (i.e., number_of_layers > 1),
      we don't use the frame rate boost for setting the key
      frame target size. The factor was forcing the target size to be
      always at its minimum (2* per_frame_bandwidth) for low frame rates
      (i.e., base layer frame rate).
      
      Generally we should modify or remove this frame rate factor;
      for now we turn if off for number_of_layers > 1.
      
      Change-Id: Ia5acf406c9b2f634d30ac2473adc7b9bf2e7e6c6
      507ee87e
  3. 27 Jan, 2012 4 commits
    • John Koleszar's avatar
      Update CHANGELOG for v1.0.0 (Duclair) release · 2b0aee4b
      John Koleszar authored
      Change-Id: I64472f717e5ef3672e1032b7ee24e73c4d0fff1f
      2b0aee4b
    • John Koleszar's avatar
      Update AUTHORS · 5e3f607e
      John Koleszar authored
      Change-Id: I5b0578f126308b4ec65d72553cc247b8e29c21a9
      5e3f607e
    • John Koleszar's avatar
      Update .mailmap · 21071373
      John Koleszar authored
      Change-Id: Ie7d94a884c81fab4d5dc48833a57ec2283e61fc2
      21071373
    • John Koleszar's avatar
      Hook up VP8D_GET_LAST_REF_USED · 8be41bba
      John Koleszar authored
      Commit 892e23a5 introduced support for the VP8D_GET_LAST_REF_USED,
      but missed the mapping of the control id to the underlying function,
      so it was unavailable to applications.
      
      In addition, the underlying function vp8_references_buffer() is
      moved from common/postproc.c to decoder/onyxd_if.c as postproc.c is
      not built in all configurations.
      
      Change-Id: I426dd254e7e6c4c061b70d729b69a6c384ebbe44
      8be41bba
  4. 26 Jan, 2012 1 commit
    • John Koleszar's avatar
      Correct clamping in use of vp8_find_near_mvs() · 83cef816
      John Koleszar authored
      Commit e06c242b introduced a change to call vp8_find_near_mvs() only
      once instead of once per reference frame by observing that the only
      effect that the frame had was on the bias applied to the motion
      vector. By keeping track of the sign_bias value, the mv to use could
      be flip-flopped by multiplying its components by -1.
      
      This behavior was subtley wrong in the case when clamping was applied
      to the motion vectors found by vp8_find_near_mvs(). A motion vector
      could be in-bounds with one sign bias, but out of bounds after
      inverting the sign, or vice versa. The clamping must match that done
      by the decoder.
      
      This change modifies vp8_find_near_mvs() to remove the clamping from
      that function. The vp8_pick_inter_mode() and vp8_rd_pick_inter_mode()
      functions instead track the correctly clamped values for both bias
      values, switching between them by simple assignment. The common
      clamping and inversion code is in vp8_find_near_mvs_bias()
      
      Change-Id: I17e1a348d1643497eca0be232e2fbe2acf8478e1
      83cef816
  5. 24 Jan, 2012 1 commit
    • John Koleszar's avatar
      Revert "Multithreaded encoder, late sync loopfilter" · 630d3b95
      John Koleszar authored
      This commit is incomplete, as it does not synchronize the loop filter
      before returning a handle to the reconstructed frame in
      vpx_codec_get_preview_frame(), which can cause (false?) failures
      when running the test_reconstruct_buffer test.
      
      This may be related to a bug that does cause visible artifacts, which
      is also under investigation.
      
      This reverts commit 380d64ec.
      
      Change-Id: Iad710941e7731d44fc2bde63bc63d6763cc4629e
      630d3b95
  6. 20 Jan, 2012 2 commits
  7. 19 Jan, 2012 2 commits
  8. 18 Jan, 2012 10 commits
  9. 17 Jan, 2012 1 commit
  10. 14 Jan, 2012 1 commit
    • Adrian Grange's avatar
      Fixed bugs in multi-layer code related to changing params · e479379a
      Adrian Grange authored
      When running multi-layer (ML) encodes and dynamically
      changing coding parameters on the fly (e.g. frame
      duration/rate, bandwidths allocated to each layer)
      the encoder would not produce sensible output.
      
      In certain cases the rate targeting would be
      hideously inaccurate.
      
      These fixes make it possible to change these coding
      parameters correctly and to maintain accurate control
      of the rate targeting.
      
      I also added the specification of the input timebase
      into the test program, vp8_scalable_patterns.c.
      
      Patch 2: Moved declaration to appease MS compiler)
      
      Change-Id: Ic8bb5a16daa924bb64974e740696e040d07ae363
      e479379a
  11. 11 Jan, 2012 2 commits
  12. 10 Jan, 2012 6 commits
  13. 09 Jan, 2012 3 commits
  14. 06 Jan, 2012 5 commits