An exhaustive check indicates that over the given parameter range, one of the clamp operations in the narrow deblocking filters is unneded.

Realized on Friday that an exhaustive search can be done in a single
pass by reducing the search to a radix sort; this is yet more
rearrangement of code flow to enable that loop setup.

Also, get a few more-Rusty idioms in place...

Split up more of the setup functions for a deblocking pass so that the
RDO need not perform redundant steps that won't change from test to
test.

No reason for the top level deblocking to be chunking things by SB in
the final filter.  There are fewer checks and corner-cases needed to
simply make full-frame passes.

This removes dependency on libaom for most of the CDFs.

Fix a subtraction that accidentally preceeded its guard statement.

Get the V and H passes closer together in memory to further reduce
memory/cache pressure during deblocking.  This is also a 'get the
pattern right' setup for the heavier RDO.

Testing indicates that the sharpness parameter has negligable effect,
and almost all of it is negative.  Increasing the value from zero
causes regression on all metrics.  As a result, nail it to 0 like in
libaom.

Dn't perform all the block-level delta math when block-level deltas aren't enabled.

* Add encoding of order_hint

For now a single bit is used for encoding order_hint

* Add intermediate variable

Add intermediate variable from which frame_type and order_hint are
derived

Don't test these modes at speed settings higher than 2

Fixes the extra silly indentation of this file.

Frank Bossen authored 6 years ago and Luca Barbato committed 6 years ago

Signed-off-by: Luca Barbato <lu_zero@gentoo.org>

And use a conditional slice outside the chroma loop.

Improve cache behavior by running vertical and horizontal deblocking in one pass.  Horizontal lags one SB behind vertical.

ME use predicted search center for topdown partition search

Yushin Cho authored 6 years ago and Yushin Cho committed 6 years ago

In ME search range setup, rename x_min, x_max, y_min and y_max variables
as mvx_min, mvx_max, ... since they are limits of mv allowed to code thus needed
to search.