1. 11 Nov, 2010 2 commits
  2. 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
  3. 09 Nov, 2010 1 commit
  4. 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
  5. 04 Nov, 2010 4 commits
    • John Koleszar's avatar
      vpxdec: report parse errors from webm_guess_framerate() · bd05d9e4
      John Koleszar authored
      If this function fails silently, the nestegg context is destroyed and
      future nestegg calls will segfault.
      
      Change-Id: Ie6a0ea284ab9ddfa97b1843ef8030a953937c8cd
      bd05d9e4
    • Fritz Koenig's avatar
      Merge "postproc : Update visualizations." · 507eb4b5
      Fritz Koenig authored
      507eb4b5
    • Fritz Koenig's avatar
      postproc : Update visualizations. · 0e7b6061
      Fritz Koenig authored
      Change color reference frame to blend the macro block edge.
      This helps with layering of visualizations.
      
      Add block coloring for intra prediction modes.
      
      Change-Id: Icefe0e189e26719cd6937cebd6727efac0b4d278
      0e7b6061
    • Yaowu Xu's avatar
      Increase the resolution of default timebase · a5397dba
      Yaowu Xu authored
      The old value 1000 was too low, which caused the effective duration and
      frame rate calculation to have an 1% error for typical 30 frame/second
      inputs. Symptom of the issue has been that most 2 pass encodings were
      undershooting target bit rate by 1% or so for 30 fps input.
      
      Change-Id: Ice204e86f844ceb9ce973456f2b995cc095283cf
      a5397dba
  6. 03 Nov, 2010 2 commits
  7. 02 Nov, 2010 3 commits
    • Fritz Koenig's avatar
      postproc : Fix display of motion vectors. · 0a29bd97
      Fritz Koenig authored
      Split motion vectors were all being treated as 4x4
      blocks.  Now correctly handle 16x8, 8x16, 8x8, 4x4
      blocks.
      
      Change-Id: Icf345c5e69b5e374e12456877ed7c41213ad88cc
      0a29bd97
    • Scott LaVarnway's avatar
      Merge "SSSE3 version of fast quantizer" · b8f43aec
      Scott LaVarnway authored
      b8f43aec
    • John Koleszar's avatar
      fix pipe support on windows · c377bf0e
      John Koleszar authored
      STDIO streams are opened in text mode by default on Windows. This patch
      changes the stdin/stdout streams to be in binary mode if they are being
      used for I/O from the vpxenc or vpxdec tools.
      
      Fixes issue #216. Thanks to mw AT hesotech.de for the fix.
      
      Change-Id: I34525b3ce2a4a031d5a48d36df4667589372225b
      c377bf0e
  8. 01 Nov, 2010 4 commits
  9. 29 Oct, 2010 2 commits
  10. 28 Oct, 2010 10 commits
    • Yunqing Wang's avatar
      Save XMM registers in asm functions · 6614563b
      Yunqing Wang authored
      XMM6/7 are used in these functions, and need to be saved.
      
      Change-Id: I3dfaddaf2a69cd4bf8e8735c7064b17bac5a14e5
      6614563b
    • Yunqing Wang's avatar
    • John Koleszar's avatar
      Merge branch 'aylesbury' · 9d93dabe
      John Koleszar authored
      9d93dabe
    • Yunqing Wang's avatar
      Fix full-search SAD function crash in Visual Studio · 7e3a1e73
      Yunqing Wang authored
      Unlike GCC, Visual Studio compiler doesn't allocate SAD output
      array 16-byte aligned, which causes crash in visual studio.
      
      Change-Id: Ia755cf5a807f12929bda8db94032bb3c9d0c2362
      7e3a1e73
    • John Koleszar's avatar
      CHANGELOG: correct date · cad21649
      John Koleszar authored
      Change-Id: I146a7f241efad4f0684cf8613c7fa42bd5cf42f3
      cad21649
    • John Koleszar's avatar
      Update CHANGELOG for v0.9.5 (Aylesbury) release · 686b217e
      John Koleszar authored
      Change-Id: Ic9f05dbbe90480d5b172233c87eaf1d4e2f1b48e
      686b217e
    • Timothy B. Terriberry's avatar
      Eliminate more warnings. · 97b766a4
      Timothy B. Terriberry authored
      This eliminates a large set of warnings exposed by the Mozilla build
       system (Use of C++ comments in ISO C90 source, commas at the end of
       enum lists, a couple incomplete initializers, and signed/unsigned
       comparisons).
      It also eliminates many (but not all) of the warnings expose by newer
       GCC versions and _FORTIFY_SOURCE (e.g., calling fread and fwrite
       without checking the return values).
      There are a few spurious warnings left on my system:
      
      ../vp8/encoder/encodemb.c:274:9: warning: 'sz' may be used
       uninitialized in this function
      gcc seems to be unable to figure out that the value shortcut doesn't
       change between the two if blocks that test it here.
      
      ../vp8/encoder/onyx_if.c:5314:5: warning: comparison of unsigned
       expression >= 0 is always true
      ../vp8/encoder/onyx_if.c:5319:5: warning: comparison of unsigned
       expression >= 0 is always true
      This is true, so far as it goes, but it's comparing against an enum,
       and the C standard does not mandate that enums be unsigned, so the
       checks can't be removed.
      
      Change-Id: Iead6cd561a2afaa3d801fd63f1d8d58953da7426
      97b766a4
    • Fritz Koenig's avatar
      postproc: Tweaks to line drawing and blending. · 6fda7668
      Fritz Koenig authored
      Turned down the blending level to make colored blocks obscure
      the video less.
      Not blending the entire block to give distinction to macro
      block edges.
      Added configuration so that macro block blending function can
      be optimized.
      Change to constrain line as to when dx and dy are computed.
      Now draw two lines to form an arrow.
      
      Change-Id: I986784e6abff65ea3e0d1437dfca7d06d44ede71
      6fda7668
    • Frank Galligan's avatar
      Output the PSNR for the entire file. · 483ce403
      Frank Galligan authored
      If --psnr option is enabled vpxenc will output PSNR values for the
      entire file. Added a \n before final output to make sure the output
      is on its own line. Overall and Avg psnr matches the values written
      to opsnr.stt file.
      
      Change-Id: Ibac5fa9baf8d5a626ea0d6ba161b484e6e8427ee
      483ce403
    • Timothy B. Terriberry's avatar
      Eliminate more warnings. · c4d7e5e6
      Timothy B. Terriberry authored
      This eliminates a large set of warnings exposed by the Mozilla build
       system (Use of C++ comments in ISO C90 source, commas at the end of
       enum lists, a couple incomplete initializers, and signed/unsigned
       comparisons).
      It also eliminates many (but not all) of the warnings expose by newer
       GCC versions and _FORTIFY_SOURCE (e.g., calling fread and fwrite
       without checking the return values).
      There are a few spurious warnings left on my system:
      
      ../vp8/encoder/encodemb.c:274:9: warning: 'sz' may be used
       uninitialized in this function
      gcc seems to be unable to figure out that the value shortcut doesn't
       change between the two if blocks that test it here.
      
      ../vp8/encoder/onyx_if.c:5314:5: warning: comparison of unsigned
       expression >= 0 is always true
      ../vp8/encoder/onyx_if.c:5319:5: warning: comparison of unsigned
       expression >= 0 is always true
      This is true, so far as it goes, but it's comparing against an enum, and the C
       standard does not mandate that enums be unsigned, so the checks can't be
       removed.
      
      Change-Id: Iaf689ae3e3d0ddc5ade00faa474debe73b8d3395
      c4d7e5e6
  11. 27 Oct, 2010 2 commits