Frank Bossen authored 6 years ago and Thomas Daede committed 6 years ago

Fix padding to begin at output frame boundaries instead of coded
frame boundaries.
Fixes #731
Update test to compare only samples that are within frame boundaries

Luca Barbato authored 6 years ago and Thomas Daede committed 6 years ago

Useful to make sure the non-nasm codepath works as intended

Luca Barbato authored 6 years ago and Thomas Daede committed 6 years ago

Needed by crav1e and other library-only consumers.

Raphaël Zumer authored 6 years ago and Thomas Daede committed 6 years ago

Remove specific frame rate number as it depends on hardware, update transforms

Set release as the default build type.

For a release build use build.sh --release

Mostly exclusive to 10 bit and 8 bit input. Roughly a 10% speedup when last measured.

This is a workaround for one of our deps having incorrect
minimum versions.

Luca Barbato authored 6 years ago and Thomas Daede committed 6 years ago

That match must be exaustive.

Frank Bossen authored 6 years ago and Thomas Daede committed 6 years ago

Fixes #722

Josh Holmer authored 6 years ago and Thomas Daede committed 6 years ago

Up to 3% improvement observed on write_b benchmarks

Josh Holmer authored 6 years ago and Luca Barbato committed 6 years ago

Fixes #720

Josh Holmer authored 6 years ago and Thomas Daede committed 6 years ago

This opens the path to finer control by the user over the encoding
options, and centralizes the speed preset logic in one location.

Closes #290

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

Straightforward addition of 14 more 2:1 and 4:12 rectangular
sized intra predictions, following current trait approach.

Simon Persson authored 6 years ago and Thomas Daede committed 6 years ago

I started with all tolerances at zero then increased when seeing a failure.
With these tolerances I have now run the test 150 times without failure.

Simon Persson authored 6 years ago and Thomas Daede committed 6 years ago

Tests are simple roundtrip of transforms, for all currently supported
sizes and types. Tolerance of +-1 is accepted.

Josh Holmer authored 6 years ago and Luca Barbato committed 6 years ago

Adds a new `--verbose` flag to display frame-by-frame info similar to
the old behavior.

It seems to make no difference in benchmark reliability for me.

Josh Holmer authored 6 years ago and Thomas Daede committed 6 years ago

Followup to #710

Josh Holmer authored 6 years ago and Thomas Daede committed 6 years ago

rav1e is no longer dependent on libaom unless running the comparative bench suite.

Inverse 64-point transform is added.
Forward 64-point transform computes all 4096 coefficients such
that distortion from zeroing high-frequency coefficients can
be easily computed

Josh Holmer authored 6 years ago and Thomas Daede committed 6 years ago

It is more performant to pass small types which implement `Copy` by
value, because they can be passed directly through registers. Clippy is
conservative with this lint and optimizes for 32-bit architectures. The
setting can be overridden in `clippy.toml` if we choose to further
optimize for 64-bit architectures.

Josh Holmer authored 6 years ago and Thomas Daede committed 6 years ago

`add` takes a `usize` parameter, so this method can be used to avoid an
unnecessary cast to `isize`.

* Modify frame management to allow for deeper hierarchies

Half the slots are used for top-level frames and the other half
for other frames, where each level in the hierarchy has a single slot
assigned to it

* Reuse probabilities from previous frames only when coding top level

* Increase order hint bits and remove outdated assert

Josh Holmer authored 6 years ago and Thomas Daede committed 6 years ago

`write` may not process the entire buffer, so if using it, it is
recommended to handle the return value (number of bytes written), or
strange runtime errors may occur. Since we are clearing the buffers
immediately after, it seems the desired behavior is to write the entire
buffer, for which `write_all` will guarantee correct behavior.

Josh Holmer authored 6 years ago and Thomas Daede committed 6 years ago

It is more idiomatic in Rust to omit the `return` keyword when possible.
This is a purely stylistic lint and has no effect on performance.