Skip to content
Snippets Groups Projects
  1. Oct 28, 2010
    • 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
  2. Oct 27, 2010
  3. Oct 26, 2010
    • Fritz Koenig's avatar
      postproc: Add mode and refrence frame visualizers. · a0ccc97d
      Fritz Koenig authored
      Post process option to color the block for either the mode
      of the macro block, or the frame that the macro block references.
      
      Change-Id: Ie498175497f2d20e3319924d352dc4ddc16f4134
      a0ccc97d
    • John Koleszar's avatar
      vpxenc: add deterministic output option · 75afcee9
      John Koleszar authored
      By baking the version number into the output file, a hash of the file
      will vary from commit to commit, even if the output is otherwise bit
      exact. Add a -D option to suppress this behavior, for use when
      bisecting or other debugging.
      
      Change-Id: I5089a8ce5719920ffaf47620fa9069b81fa15673
      75afcee9
    • John Koleszar's avatar
      Merge "Update AUTHORS" · 91d927f9
      John Koleszar authored
      91d927f9
    • John Koleszar's avatar
      Update AUTHORS · ad760b96
      John Koleszar authored
      Change-Id: I18e0a9e00731c23a2bdd1a978c8cb38f71e9029d
      ad760b96
    • John Koleszar's avatar
      make vp8_recon16x16mb{,y} RTCD functions · d6c67f02
      John Koleszar authored
      ARM NEON has a platform specific version of vp8_recon16x16mb, though
      it's just a stub to extract the various parameters from the
      MACROBLOCKD struct and pass them to vp8_recon16x16mb_neon(). Using
      that function's prototype directly will be a better long term solution,
      but it's quite an invasive change.
      
      Change-Id: I04273149e2ade34749e2d09e7edb0c396e1dd620
      d6c67f02
    • John Koleszar's avatar
      make arm hex search the generic implementation · 96cf6588
      John Koleszar authored
      The ARM version of vp8_hex_search() is a faster implementation
      of the same algorithm. Since it doesn't use any ARM specific
      code, it can be made the default implementation. This removes
      a linking error.
      
      Change-Id: I77d10f2c16b2515bff4522c350004e03b7659934
      96cf6588
    • John Koleszar's avatar
      1e7c05e0
    • John Koleszar's avatar
      arm: move unrolled loops back to generic code · 19638c23
      John Koleszar authored
      Some of the ARM functions differed from their generic counterparts
      only by unrolling their loops. Since this change may be useful
      on other platforms, or might even supercede the looped version
      in the generic case, move it back to the generic file.
      
      This code is left under #if ARCH_ARM for now, but it may be worth
      considering a different (possibly new) conditional for these. If
      it turns out that this should be runtime selectable, these
      functions will have to move to the RTCD infrastructure. Don't want
      to take that step at this time without more profile data.
      
      Change-Id: I4612fdbc606fbebba4971a690fb743ad184ff15f
      19638c23
    • John Koleszar's avatar
      arm: remove duplicate functions · d330a587
      John Koleszar authored
      These functions were true duplicates of functions present in the
      generic code. This fixes some of the link errors when building
      with --enable-shared --enable-pic.
      
      Change-Id: Idff26599d510d954e439207883607ad6b74df20c
      d330a587
Loading