1. 10 Feb, 2018 1 commit
  2. 24 Jan, 2018 1 commit
  3. 04 Sep, 2017 1 commit
  4. 02 Sep, 2016 1 commit
  5. 01 Sep, 2016 2 commits
  6. 10 Aug, 2016 1 commit
  7. 26 Jul, 2016 1 commit
  8. 25 Mar, 2016 2 commits
    • Adrian Grange's avatar
      Change "VPX" to "AOM" · ff00fc0f
      Adrian Grange authored
      Change-Id: I6593a44de3b571193c2a4c8787ddf3b2fc24a268
      ff00fc0f
    • Adrian Grange's avatar
      Convert "vpx" to "aom" · cebe6f0c
      Adrian Grange authored
      Change the name of source files to replace "vpx" with "aom".
      Change occurences of "vpx" in the code to "aom".
      
      Change-Id: I002c0eaa2c350cf1a895bf01bea5788c61328027
      cebe6f0c
  9. 24 Mar, 2016 1 commit
  10. 22 Mar, 2016 2 commits
    • Yaowu Xu's avatar
      libvpx -> libaom · 3d26d916
      Yaowu Xu authored
      Change-Id: I820483aefdc14f2ae946e08fe10fa01f3e845767
      3d26d916
    • Yaowu Xu's avatar
      Rename vpx to aom · bf4202ed
      Yaowu Xu authored
      Change-Id: Ibc7933fba85feeb30ef9b14b302d932aff19f54e
      bf4202ed
  11. 28 Jan, 2016 1 commit
  12. 08 Oct, 2014 1 commit
  13. 03 Oct, 2014 1 commit
  14. 03 Sep, 2014 1 commit
  15. 22 Aug, 2014 2 commits
  16. 11 Jul, 2014 1 commit
    • Yaowu Xu's avatar
      Silent -wextra warnings · 618e7ef0
      Yaowu Xu authored
      1. vpxenc.c
      2. y4minput.c
      
      Change-Id: I1cfe1ef84a3eec11376976c09947fe6178ee039f
      618e7ef0
  17. 05 Jul, 2014 1 commit
    • Deb Mukherjee's avatar
      Adds support for reading and writing 10/12-bit y4m · 5820c5d6
      Deb Mukherjee authored
      The y4m extension used is the same as the one used in ffmpeg/x264.
      The patch is adapted from the highbitdepth branch.
      
      Also adds unit tests for y4m header parsing and md5 check
      of the raw frame data, as well as y4m writing.
      
      [build fix for Mac/VS by not using tuples with strings]
      
      Change-Id: I40897ee37d289e4b6cea6fedc67047d692b8cb46
      5820c5d6
  18. 03 Jul, 2014 1 commit
  19. 02 Jul, 2014 1 commit
    • Deb Mukherjee's avatar
      Adds support for reading and writing 10/12-bit y4m · 82dc1332
      Deb Mukherjee authored
      The y4m extension used is the same as the one used in ffmpeg/x264.
      The patch is adapted from the highbitdepth branch.
      
      Also adds unit tests for y4m header parsing and md5 check
      of the raw frame data, as well as y4m writing.
      
      Change-Id: Ie2794daf6dbafd2f128464f9b9da520fc54c0dd6
      82dc1332
  20. 18 Mar, 2014 1 commit
  21. 12 Mar, 2014 1 commit
  22. 06 May, 2013 1 commit
    • John Koleszar's avatar
      Y4M input support for 4:2:2, 4:4:4, 4:4:4:4 · 8dd8287e
      John Koleszar authored
      Adds a new experiment CONFIG_NON420 that allows other chroma subsamplings
      to be passed to the codec. This commit allows the data to be passed from
      a y4m input file through vpxenc to the codec, where they're currently
      rejected. Later commits will finish support for this inside the codec.
      
      Change-Id: Ib3aac604d8cad9e24cef395fa1067f16ba7e8e43
      8dd8287e
  23. 06 Nov, 2012 1 commit
  24. 20 Aug, 2012 1 commit
  25. 17 Jul, 2012 1 commit
  26. 09 May, 2011 1 commit
  27. 28 Oct, 2010 2 commits
    • 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
    • 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
  28. 09 Sep, 2010 1 commit
  29. 18 Jun, 2010 1 commit
    • John Koleszar's avatar
      cosmetics: trim trailing whitespace · 94c52e4d
      John Koleszar authored
      When the license headers were updated, they accidentally contained
      trailing whitespace, so unfortunately we have to touch all the files
      again.
      
      Change-Id: I236c05fade06589e417179c0444cb39b09e4200d
      94c52e4d
  30. 04 Jun, 2010 1 commit
  31. 03 Jun, 2010 1 commit