Google VP9 "Next Generation Open Video" information posted

[Blue_MiSfit]

Indeed ^^

I've been looking forward to trying out Socionext's FPGA AV1 encoder

[osgZach]

Originally Posted by benwaggoner

Using F1 instances is a lot cheaper than buying a FPGA for experimentation.

https://aws.amazon.com/ec2/instance-types/f1/

Sent from my SM-T837V using Tapatalk

It's neat to know something like this exist, however it's not really feasible for my usage case due to a processing time / bandwidth required point of view. I need local hardware, ahh... beggars can't be choosers and all that

[osgZach]

And a bit of a rando question, not sure whether this is ffmpeg specific or VPX/VP9 specific.

2-pass CRF is nice, I like it, and it actually seems to run a tad bit faster than a traditional 2pass, which bringing potentially better compression. However I'm also interesting in vbv/constained buffer values. I have found examples of how to do such in a regular 2-pass encode, but I cannot find anything that says whether it will/won't work if you try it with a 2pass CRF encode.

Can anyone elaborate on whether this would work, or how I could at least verify it with some test cases ? I'm worried if I specify anything other than b:v 0 it will fall back to some other mode, or not generally drop the bitrate below b:v X even if it can go lower than X

[GTPVHD]

https://github.com/intel/media-drive...oding-features

Intel Gen12/Xe GPU in Tiger Lake supports VP9 12-bit & 12-bit 4:4:4 hardware decoding.

[LigH]

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

VPx v1.8.2-184-gf80e88872

[Sagittaire]

Originally Posted by LigH

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

VPx v1.8.2-184-gf80e88872

thx ... ;-)

[LigH]

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

VPx v1.8.2-219-g8c7142d77

[kerry7]

Originally Posted by osgZach

It's neat to know something like this exist, however it's not really feasible for my usage case due to a processing time / bandwidth required point of view. I need local hardware, ahh... beggars can't be choosers and all that

Also you can considere to use GCP Cloud computing. It is an alternative to EC2, but with the huge advantage that most likely google offers a better integration with VP9

[Blue_MiSfit]

Also you can considere to use GCP Cloud computing. It is an alternative to EC2, but with the huge advantage that most likely google offers a better integration with VP9

Nope. EC2 is just renting VM time. Google Cloud's Compute Engine is the same thing. You get an instance, typically with some Linux distro on it. The rest is up to you.

If you want video transcoding as a service you have a lot of options, but that's separate from any conversation about EC2 vs the equivalent on GCP.

[dapperdan]

Apple appear to be rolling out VP9 suppprt across iOS, tvOS and MacOS/Safari.

Most of the news stories just say "4K Youtube support" but it appears to be via VP9.2 and hardware accelerated where the hardware supports it.

https://webkit.org/blog/11183/releas...y-preview-112/

[Blue_MiSfit]

Very exciting. I've had my Apple TV on the beta for awhile, but YouTube is still HD-only there. I wonder what Apple devices actually offer hardware VP9 decoding under the hood that's just been disabled all this time?

[LigH]

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

VPx v1.9.0-61-gc413c8f18

[LigH]

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

VPx v1.9.0-103-g3f7fee29e

[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.

[GTPVHD]

Google killed 4K H.264 encodes for VP9, you shouldn't be surprised they're killing 8K VP9 encodes for AV1, bandwidth consumption is enormous for Youtube.
This will force laggards like Apple to adopt AV1 just like they did with VP9 support finally in Apple products this year, 3 years after Google stopped 4K H.264 encodes for VP9.

[Blue_MiSfit]

Good luck "forcing" Apple to do anything

[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?