My fault, that was a float (not integer) which was converted to int64_t.

This reverts commit a885e1cb

Change-Id: Ic50708b959e1c3cb3e37da1429d334fafc3391d6

Change-Id: I156419fdf68056759a4cd4206cc829a00025ef78

This reverts commit 5509b7fd


Observed a big drop in compression quality and speed for speed 1 for a 360p test clip, revert this now for investigation.

Change-Id: If69dc8d77a225b34dc7907a9472e1a7a0a22762d

Change-Id: Ic53b2fb69e6eee600ea222e4d06424a1bbca496c

Johann authored Aug 15, 2014 and James Zern committed Aug 15, 2014

Change-Id: I5ca3400aec1f77fd92762d0c4fc86ba3694de1ca

Gordana Cmiljanovic authored Aug 07, 2014 and James Zern committed Aug 15, 2014

Change-Id: I78e27bf942b4a825543e76be25546b6458bad8b6

According to the current API spec we need to call vpx_codec_encode() until
vpx_codec_get_cx_data() returns NULL.

Change-Id: I4617f8042d50480a8f47b0b7114d4759fa566b14

Now everything is int64_t, so we don't need that function.

Change-Id: I7dd2023677b4943ecd968d68cc06f9d4862c3c3f

Add a speed feature to give the tighter partition search
range. Before partition search, calculate the histogram
of the partition sizes of the left, above and previous
co-located blocks of the current block. If the variance of
observed partition sizes is small enough, adjust the search
range around the mean partition size, which will be tigher.

The feature is currently turned on at speed 2. Experiments on
sample youtube clips show on average the runtime is reduced
by 3-7%.

For hard stdhd clips:
park_joy_1080p @ 15000kbps:       509251 ms -> 491953 ms (3.3%)
pedestrian_area_1080p @ 2000kbps: 223941 ms -> 214226 ms (4.3%)

The PSNR performance is changed:
derf: -0.112%
yt:   -0.099%
hd:   -0.090%
stdhd:-0.102%

Change-Id: Ie205ec5325bf92ec5676c243e30ba9d0adca10f2

- Fix nit: make test function definitions match test order.
- Fix nit: use elog instead of echo for env verification error.

Change-Id: I0eec078fc056a5bb2bd88d5833e43de48d77ec08

Change-Id: Ib52e1ce5aa4a22d70e124c3c29a92e00ffac50e4

Change-Id: I4f0bac3367b1a7c5e7f746b97ca619b81c8dfc49

When configuring the buffer make sure to set all the (now) required
fields. Use the canonical variables and match the style from vpx_scale.

https://code.google.com/p/webm/issues/detail?id=841

Change-Id: I71b43d4a03756b8b2d6d60fdf8d7bf41b8041787

this test allocates >2GB currently. depending on the order of the test
runs the allocation may fail most regularly with mingw+wine.

Change-Id: Ibee1c18cfbe29a4de6c65075647ec3955d8206c0

Change-Id: I50f4485cfbdaadc3084aa5bc63bf3a2f15a0d903

Change-Id: I960c26dcb0db230e50f923d00f64ded1a39bf783

Removed disable_split_var_thresh, which is not used anymore.

Change-Id: I50119b150442e1571157433b5effc6aae0dbe0fd

- Remove vpxdec and vpxenc from the exclude list.
- vpx{dec,enc}.sh: Updates to support finding their executable when
  LIBVPX_BIN_PATH is setup for the examples.
- tools_common.sh: New library function, vpx_tool_path(). Provides
  support for finding the exectuables in vpx{dec,enc}.sh.

Change-Id: I730f11cceb44646491a7a7ff58603a4a760129ef

According to the current API spec we need to call vpx_codec_encode() until
vpx_codec_get_cx_data() returns NULL.

Change-Id: Ide0c531dc0d453df8ec1edb8acb894856d6cc22e