Google VP9 "Next Generation Open Video" information posted

[benwaggoner]

Originally Posted by utack

Is Google now actively killing 8k VP9?
A lot of videos only have AV1 as 8k option available, and I found reference to one a year back in a forum that clearly showed VP9 was still available at the time.

The bigger challenge is that reality is killing 8K video because of the limits of human perception. I challenge you to find video content that looks better encoded at native 8K than downscaled to 4K at the same bitrate when viewed at enough distances that the edges of the screen are at a minimally acceptable viewing angle. No one in Hollywood is doing any post production in 8K. Heck, most visual effects are still being done in 2K for cost/speed reasons, and because 2K looks just fine if there's some motion blur and/or grain.

And with everyone working from home, even experimenting in 8K is nigh impossible. There literally aren't any monitors that are 8K, HDR, and have DisplayPort. Monitoring 8K HDR means using a (WAY too big for a desk) TV and a $3K AJA Kona 5 with experimental and finicky HDMI 2.1 firmware.

[takla]

With libvpx-vp9 v1.9.0 auto-alt-ref only works in 2pass. was this changed or was this always the case?

[Beelzebubu]

Originally Posted by takla

With libvpx-vp9 v1.9.0 auto-alt-ref only works in 2pass. was this changed or was this always the case?

Yes (sadly).

[edit]
At --cpu-used=4 using VBR, it works also in one-pass mode in some cases. But at other speeds or in CRF, it works in 2-pass only.

See this code.

[takla]

Originally Posted by Beelzebubu

Yes (sadly).

[edit]
At --cpu-used=4 using VBR, it works also in one-pass mode in some cases. But at other speeds or in CRF, it works in 2-pass only.

See this code.

Thanks for clarifying. But I'm confused. Why was it changed? Was it not working correctly before?

[Beelzebubu]

Originally Posted by takla

Thanks for clarifying. But I'm confused. Why was it changed? Was it not working correctly before?

I meant: yes, it was always the case. Sorry for the confusing answer.

[takla]

Originally Posted by Beelzebubu

I meant: yes, it was always the case. Sorry for the confusing answer.

Ah alright then. Thanks.

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 10.2.0):

VPx v1.9.0-156-g24bd0733e

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 10.3.0):

VPx v1.10.0-61-g4808d831d

[takla]

2021-09-27
v1.11.0 "Smew Duck"

This maintenance release adds support for VBR mode in VP9 rate control
interface, new codec controls to get quantization parameters and loop filter
levels, and includes several improvements to NEON and numerous bug fixes.

- Upgrading:
New codec control is added to get quantization parameters and loop filter
levels.

VBR mode is supported in VP9 rate control library.

- Enhancement:
Numerous improvements for Neon optimizations.
Code clean-up and refactoring.
Calculation of rd multiplier is changed with BDRATE gains.

- Bug fixes:
Fix to overflow on duration.
Fix to several instances of -Wunused-but-set-variable.
Fix to avoid chroma resampling for 420mpeg2 input.
Fix to overflow in calc_iframe_target_size.
Fix to disallow skipping transform and quantization.
Fix some -Wsign-compare warnings in simple_encode.
Fix input file path in simple_encode_test.
Fix valid range for under/over_shoot pct.

Source

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 12.1.0):

VPx v1.11.0-218-g9f1329f8a

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 12.1.0):

VPx v1.12.0-72-g59acf6739

SVT-VP9 0.3.0-d9ef3cc

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 12.2.0):

VPx v1.12.0-153-ga46ca4b6b

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 12.2.0):

VPx v1.12.0-214-gddca3dec3

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 12.2.0):

VPx v1.12.0-228-gd998bd823

[LigH]

New upload (MSYS2; MinGW32 / MinGW64: GCC 13.1.0):

VPx v1.13.0-398-g9ad950a9c

[oibaf]

Some (not so) recent news:

2023-09-29 v1.13.1 "Ugly Duckling"
This release contains two security related fixes. One each for VP8 and VP9.
- Upgrading:
This release is ABI compatible with the previous release.
- Bug fixes:
https://crbug.com/1486441 (CVE-2023-5217)
Fix to a crash related to VP9 encoding (#1642)

2023-01-31 v1.13.0 "Ugly Duckling"
This release includes more Neon and AVX2 optimizations, adds a new codec
control to set per frame QP, upgrades GoogleTest to v1.12.1, and includes
numerous bug fixes.
- Upgrading:
This release is ABI incompatible with the previous release.
New codec control VP9E_SET_QUANTIZER_ONE_PASS to set per frame QP.
GoogleTest is upgraded to v1.12.1.
.clang-format is upgraded to clang-format-11.
VPX_EXT_RATECTRL_ABI_VERSION was bumped due to incompatible changes to the
feature of using external rate control models for vp9.
- Enhancement:
Numerous improvements on Neon optimizations.
Numerous improvements on AVX2 optimizations.
Additional ARM targets added for Visual Studio.
- Bug fixes:
Fix to calculating internal stats when frame dropped.
Fix to segfault for external resize test in vp9.
Fix to build system with replacing egrep with grep -E.
Fix to a few bugs with external RTC rate control library.
Fix to make SVC work with VBR.
Fix to key frame setting in VP9 external RC.
Fix to -Wimplicit-int (Clang 16).
Fix to VP8 external RC for buffer levels.
Fix to VP8 external RC for dynamic update of layers.
Fix to VP9 auto level.
Fix to off-by-one error of max w/h in validate_config.
Fix to make SVC work for Profile 1.

2022-06-17 v1.12.0 "Torrent Duck"
This release adds optimizations for Loongarch, adds support for vp8 in the
real-time rate control library, upgrades GoogleTest to v1.11.0, updates
libwebm to libwebm-1.0.0.28-20-g206d268, and includes numerous bug fixes.
- Upgrading:
This release is ABI compatible with the previous release.
vp8 support in the real-time rate control library.
New codec control VP8E_SET_RTC_EXTERNAL_RATECTRL is added.
Configure support for darwin21 is added.
GoogleTest is upgraded to v1.11.0.
libwebm is updated to libwebm-1.0.0.28-20-g206d268.
Allow SimpleEncode environment to take target level as input to match
the level conformance in vp9.
- Enhancement:
Numerous improvements on checking memory allocations.
Optimizations for Loongarch.
Code clean-up.
- Bug fixes:
Fix to a crash related to {vp8/vp9}_set_roi_map.
Fix to compiling failure with -Wformat-nonliteral.
Fix to integer overflow with vp9 with high resolution content.
Fix to AddNoiseTest failure with ARMv7.
Fix to libvpx Null-dereference READ in vp8.

[benwaggoner]

Sounds like meaningful development wrapped up around January? I wonder if many of the contributors moved on to SVT-AV1.

Kind of funny that per-frame QP control took that long to implement.

[oibaf]

Originally Posted by benwaggoner

Sounds like meaningful development wrapped up around January? I wonder if many of the contributors moved on to SVT-AV1.

Kind of funny that per-frame QP control took that long to implement.

There are still lot of commits in libvpx after 1.13: https://chromium.googlesource.com/webm/libvpx/+log

Also for classic AV1 libaom: https://aomedia.googlesource.com/aom/+log

Much more than on SVT-AV1 https://gitlab.com/AOMediaCodec/SVT-...ref_type=HEADS

[benwaggoner]

Originally Posted by oibaf

There are still lot of commits in libvpx after 1.13: https://chromium.googlesource.com/webm/libvpx/+log

Also for classic AV1 libaom: https://aomedia.googlesource.com/aom/+log

Much more than on SVT-AV1 https://gitlab.com/AOMediaCodec/SVT-...ref_type=HEADS

Yeah, no doubt that work continues apace on AV1 encoders, open source and proprietary.