- 25 Mar, 2016 4 commits
-
-
Adrian Grange authored
Change-Id: I7fce5490afdc78ac62dafc4616b617d251487979
-
Adrian Grange authored
Note: Check AOMD_SET_DESCRIPTOR; there was a VPX & VP8 version that when renamed become the same. Change-Id: I022a71c0dfcd77948dda35ec754167e03bca616d
-
Adrian Grange authored
Change-Id: I6593a44de3b571193c2a4c8787ddf3b2fc24a268
-
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
-
- 24 Mar, 2016 1 commit
-
-
Adrian Grange authored
Change-Id: I79d52362aec9565cc4b6fe7a1c1c08dcfb726465
-
- 22 Mar, 2016 1 commit
-
-
Yaowu Xu authored
Change-Id: Ibc7933fba85feeb30ef9b14b302d932aff19f54e
-
- 29 Jan, 2016 1 commit
-
-
Change-Id: I31e383b0e3312d6a07efa104c799ff9aa42d433f
-
- 12 May, 2015 1 commit
-
-
James Zern authored
+ the definitions in the examples silences a missing-prototype warning Change-Id: I7c064cacd6d2073a6107de6c3e2cc46ef8a68411
-
- 05 Feb, 2015 1 commit
-
-
Tom Finegan authored
The current file's directory, ".", is treated much more literally when building libvpx examples with Xcode than it is with make, and clang cannot find common include files included via "./" when those files actually reside one directory up in the tree. Change-Id: I5f66a026282e35d80248ca4052ebb882b859172e
-
- 03 Sep, 2014 1 commit
-
-
Dmitry Kovalev authored
Change-Id: I6fdcea0e0faf42386dd2b8f972a3b3fb2c21b2c7
-
- 22 Aug, 2014 1 commit
-
-
Jim Bankoski authored
Change-Id: I08e42adeab9f9fa0337173ba0923f3bc0dd36806
-
- 16 Aug, 2014 1 commit
-
-
Dmitry Kovalev authored
According to the current API spec we need to call vpx_codec_encode() until vpx_codec_get_cx_data() returns NULL. Change-Id: I4617f8042d50480a8f47b0b7114d4759fa566b14
-
- 15 Jul, 2014 1 commit
-
-
Deb Mukherjee authored
Renames interface to codec_interface since it is a reserved word on windows. Change-Id: I84f2cbf257a4c44f16dc2464127e35ee405c2c3e
-
- 16 May, 2014 1 commit
-
-
Yaowu Xu authored
The commit changed to use memset for initialiazation of non-trivial strucutures, where initialization using {0} caused warnings. Also, removed {0} initializations where appropriate initialization calls are in place. Change-Id: Ifd03e34aa80688e382124eb889c0fc1ec43c48e6
-
- 11 Mar, 2014 2 commits
-
-
Alex Converse authored
Change-Id: I8c3be3ed4d6bbc5fa3042a2d5637407d4d56afee
-
Alex Converse authored
Change-Id: I754a5c5e342cfa7c52c1a75424f18aea8b7657d2
-
- 20 Feb, 2014 1 commit
-
-
Tom Finegan authored
Use unsigned loop counters in set_roi_map() and set_active_map(). Change-Id: I9bbaed38b51ef73b82ba4ad4c4bc18ca5d2399f9
-
- 13 Feb, 2014 1 commit
-
-
Dmitry Kovalev authored
Change-Id: Id6e6b5a96c907261abe4348624241b4568707c1d
-
- 06 Feb, 2014 1 commit
-
-
James Zern authored
Change-Id: I371863fc68f4984a223a684f9e89b25e9991e1e7
-
- 07 Jan, 2014 1 commit
-
-
Dmitry Kovalev authored
All documentation will be provided as comments in the source files. Change-Id: Ie609852747733c181191f864204c787a6b23ef3a
-
- 04 Jun, 2012 1 commit
-
-
Johann authored
Using if(); triggers an empty body warning with clang Change-Id: I0fa2ee676400a974b40f8eaafca9ae668107eebb
-
- 09 May, 2011 1 commit
-
-
Johann authored
Change-Id: I9467d7a50eac32d8e8f3a2f26db818e47c93c94b
-
- 01 Mar, 2011 1 commit
-
-
John Koleszar authored
MSVC can't pass the address of global variables in a DLL correctly across DLL boundaries. This patch allows linking the examples to a libvpx dll build. Fixes issue #268. Change-Id: I1c52d076cfc68efb3efdfba019f12d53c5019f58
-
- 28 Oct, 2010 2 commits
-
-
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
-
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
-
- 09 Sep, 2010 1 commit
-
-
John Koleszar authored
Changes 'The VP8 project' to 'The WebM project', for consistency with other webmproject.org repositories. Fixes issue #97. Change-Id: I37c13ed5fbdb9d334ceef71c6350e9febed9bbba
-
- 18 Jun, 2010 1 commit
-
-
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
-
- 04 Jun, 2010 1 commit
-
-
John Koleszar authored
Change-Id: Ieebea089095d9073b3a94932791099f614ce120c
-
- 25 May, 2010 2 commits
-
-
John Koleszar authored
The output of simple_decoder, as well as the default format for the ivf{enc,dec} tools, is I420. The encoder examples are changed to default to I420 as well. This is desirable because passing the output of simple_encoder to simple_decoder would otherwise have the chroma planes flipped, which is unexpected. Change-Id: I9d4f10ace594a54a7fc4f9a1f9187365c01fd638
-
John Koleszar authored
This renames the vpx_codec/ directory to vpx/, to allow applications to more consistently reference these includes with the vpx/ prefix. This allows the includes to be installed in /usr/local/include/vpx rather than polluting the system includes directory with an excessive number of includes. Change-Id: I7b0652a20543d93f38f421c60b0bbccde4d61b4f
-
- 21 May, 2010 2 commits
-
-
James Zern authored
Avoid an potential name clashes and match other external types. s/IMG_FMT/VPX_$&/g s/img_fmt/vpx_$&/g Change-Id: Ia7ad5bbb6424416b37e71e5f5eb1eca31c3c707f
-
John Koleszar authored
This doesn't play well with autotools, and the preprocessor magic is confusing and unhelpful in the vp8-only context. Change-Id: I2fcb57e6eb7876ecb58509da608dc21f26077ff1
-
- 18 May, 2010 1 commit
-
-
John Koleszar authored
-