1. 25 Nov, 2010 1 commit
    • Pascal Massimino's avatar
      allow dimensions as low as 1 pixel · fd9f9dc0
      Pascal Massimino authored
      remove warning comment in vpxenc.c: in case of 1x1 picture,
      detect_bytes will be equal to '3' and we'll fall back to
      RAW_TYPE.
      fix read_frame() by tracking the pre-read buffer length
      in the struct detect
      
      Change-Id: If1ed86ee5260dcdbc8f9d10da6cbb84a4cc2f151
      fd9f9dc0
  2. 23 Nov, 2010 3 commits
  3. 22 Nov, 2010 2 commits
  4. 19 Nov, 2010 1 commit
  5. 18 Nov, 2010 1 commit
    • Pascal Massimino's avatar
      remove warning · ed5ab7fa
      Pascal Massimino authored
      was having: "vp8/encoder/onyx_if.c:5365: warning: comparison of unsigned expression >= 0 is always true"
      ed5ab7fa
  6. 17 Nov, 2010 7 commits
  7. 16 Nov, 2010 4 commits
  8. 15 Nov, 2010 4 commits
  9. 12 Nov, 2010 1 commit
  10. 11 Nov, 2010 4 commits
    • Yaowu Xu's avatar
      make rdmult adaptive for intra in quantizer RDO · ef2f27f1
      Yaowu Xu authored
      This intends to correct the tendency that VP8 aggressively favors rate
      on intra coded frames. Experiments tested different numbers in [0, 1]
      and found 9/16 overall provided about 2-4% gains for all-intra coded
      clips based on vpx-ssim metric. The impact on regular encoded clips
      is much smaller but positive overall. Overall impact on psnr is also
      positive even though very small.
      
      Change-Id: If808553aaaa87fdd44691f9787820ac9856d9f8a
      ef2f27f1
    • John Koleszar's avatar
      quantizer: fix assertion in fast quantizer path · 0a49747b
      John Koleszar authored
      The fast quantizer assembly code has not been updated to match the new
      exact quantizer, which was made the default in commit 6adbe090.
      Specifically, they are not aware of the potential for the coefficient
      to be scaled, which results in the quantized result exceeding the range
      of the DCT. This patch restores the previous behavior of using the
      non-shifted coefficients when in the fast quantizer code path, but
      unfortunately requires rebuilding the tables when switching between the
      two.
      
      Change-Id: I0a33f5b3850335011a06906f49fafed54dda9546
      0a49747b
    • Fritz Koenig's avatar
      Revert "Remove stack shadowing for x86-64" · 58083cb3
      Fritz Koenig authored
      This reverts commit 15acc84f.
      
      Change-Id: Ia640be8cbc134432914849c1750f62575ea084e6
      58083cb3
    • Paul Wilkins's avatar
      213f7b09
  11. 10 Nov, 2010 6 commits
    • Fritz Koenig's avatar
      configure : Incorrect syntax in configure · 692b1085
      Fritz Koenig authored
      Check to see if postproc was enabled when enabling the
      postproc visualizer was wrong.
      
      Fix for bug introduced in Change Ia74f357d
      
      Change-Id: I4bee9ad2caee3cfe3bac6972047f6af7c54cad4e
      692b1085
    • Fritz Koenig's avatar
      Merge "Remove stack shadowing for x86-64" · 9b1ece2c
      Fritz Koenig authored
      9b1ece2c
    • Fritz Koenig's avatar
      FDCT optimizations. · 5f0e0617
      Fritz Koenig authored
      Fixed up the fdct for mmx and 8x4 sse2 to match them
      most recent changes.
      
      Change-Id: Ibee2d6c536fe14dcf75cd6eb1c73f4848a56d719
      5f0e0617
    • Fritz Koenig's avatar
      postproc : Re-work posproc calling to allow more flags. · 647df00f
      Fritz Koenig authored
      Debugging in postproc needs more flags to allow for specific
      block types to be turned on or off in the visualizations.
      
      Must be enabled with --enable-postproc-visualizer during
      configuration time.
      
      Change-Id: Ia74f357ddc3ad4fb8082afd3a64f62384e4fcb2d
      647df00f
    • Paul Wilkins's avatar
      Relax rate control for last few frames · 513f8e68
      Paul Wilkins authored
      VBR rate control can become very noisy for the last few frames.
      If there are a few bits to spare or a small overshoot then the
      target rate and hence quantizer may start to fluctuate wildly.
      
      This patch prevents further adjustment of the active Q limits for
      the last few frames.
      
      Patch also removes some redundant variables and makes one small bug fix.
      
      Change-Id: Ic167831bec79acc9f0d7e4698bcc4bb188840c45
      513f8e68
    • Paul Wilkins's avatar
      Tuning for the more exact quantizer. · 6adbe090
      Paul Wilkins authored
      Small changes to the default zero bin and rounding tables.
      Though the tables are currently the same for the Y1 and Y2 cases
      I have left them as separate tables in case we want to tune this later.
      
      There is now some adjustment of the zbin based on the prediction mode.
      Previously this was restricted to an adjustment for gf/arf 0,0 MV.
      
      The exact quantizer now marginal outperforms and is the default.
      
      The overall average gain is about 0.5%
      
      Change-Id: I5e4353f3d5326dde4e86823684b236a1e9ea7f47
      6adbe090
  12. 09 Nov, 2010 1 commit
  13. 05 Nov, 2010 4 commits
    • John Koleszar's avatar
      Merge commit 'fix integer promotion bug in partition size check' · 4d1b0d2a
      John Koleszar authored
      Change-Id: I4081917b46013fa8f4218cade8bd12cb2d013aee
      4d1b0d2a
    • John Koleszar's avatar
      fix integer promotion bug in partition size check · 9fb80f71
      John Koleszar authored
      The check '(user_data_end - partition < partition_size)' must be
      evaluated as a signed comparison, but because partition_size was
      unsigned, the LHS was promoted to unsigned, causing an incorrect
      result on 32-bit. Instead, check the upper and lower bounds of
      the segment separately.
      
      Change-Id: I6266aba7fd7de084268712a3d2a81424ead7aa06
      9fb80f71
    • John Koleszar's avatar
      improve average framerate calculation · f7e187d3
      John Koleszar authored
      Change Ice204e86 identified a problem with bitrate undershoot due to
      low precision in the timestamps passed to the library. This patch
      takes a different approach by calculating the duration of this frame
      and passing it to the library, rather than using a fixed duration
      and letting the library average it out with higher precision
      timestamps. This part of the fix only applies to vpxenc.
      
      This patch also attempts to fix the problem for generic applications
      that may have made the same mistake vpxenc did. Instead of
      calculating this frame's duration by the difference of this frame's
      and the last frame's start time, we use the end times instead. This
      allows the framerate calculation to scavenge "unclaimed" time from
      the last frame. For instance:
      
        start |  end  | calculated duration
        ======+=======+====================
          0ms    33ms   33ms
         33ms    66ms   33ms
         66ms    99ms   33ms
        100ms   133ms   34ms
      
      Change-Id: I92be4b3518e0bd530e97f90e69e75330a4c413fc
      f7e187d3
    • John Koleszar's avatar
  14. 04 Nov, 2010 1 commit