Google VP9 "Next Generation Open Video" information posted

[LigH]

VPx v1.7.0-217-g223f9e367

[LigH]

VPx v1.7.0-250-g933619766

[mandarinka]

Originally Posted by mzso

Is it normal for stuff that fades in to look this crappy, or is something going wrong on my end?
https://drive.google.com/open?id=1x3...goGBj1CRbFJ_JH

(It sucks with AVC too BTW: https://drive.google.com/open?id=1n-..._dj3P98PPCJ7R4)

VP9 (and I think AV1 is the same here, sadly) lacks weighted prediction, which is a special coding tool for fading. Without weighted prediction, the fade generates a lot of residual for every frame and the usual compression scheme fails to efficiently handle it, so the residual has to be quantized strongly, which means aggressive lossy compression and more artifacts.

If weighted prediction works right, the fade should look much better if the encoder tries to use it (weighted prediction is available in AVC and HEVC, but fast encoding profiles might not use it). Also if your source already has the fade ruined, you are out of luck.

[wiak]

Originally Posted by LigH

For AOM, a range of 5..8 was recommended to me to speed up remarkably. But VPx may either not support such levels, or it may decrease the quality too much...

i just use 0 ;P

[mzso]

Originally Posted by mandarinka

VP9 (and I think AV1 is the same here, sadly) lacks weighted prediction, which is a special coding tool for fading. Without weighted prediction, the fade generates a lot of residual for every frame and the usual compression scheme fails to efficiently handle it, so the residual has to be quantized strongly, which means aggressive lossy compression and more artifacts.

If weighted prediction works right, the fade should look much better if the encoder tries to use it (weighted prediction is available in AVC and HEVC, but fast encoding profiles might not use it). Also if your source already has the fade ruined, you are out of luck.

I used the preset slower as usual, which gave me this result. (which apparently resulted in this: weightb=1 / weightp=2 /)
Not sure what they mean, if anything since I never change anything other than quality and presets.

[LigH]

@wiak:

Too late to discuss that. Pages ago people mentioned this CLI option possibly being abandoned.

[cherishjoo]

How much is it than H.264 or H.265?

[LigH]

Originally Posted by cherishjoo

How much is it »better« than H.264 or H.265?

"I accidently ... is that dangerous?"

I don't have much own practical experience, but believe that VP9 can be (depending on parameters, and comparing vpxenc with other specific encoders) better than x264, yet slower than x265, and x265 can beat it for most kinds of material at similar bitrates, I read.

[LigH]

VPx 1.7.0-291-g3b460db21

[LigH]

VPx 1.7.0-309-ge4408a07b

[LigH]

Did you want to ask that in the AOM thread?

[mzso]

Originally Posted by LigH

Did you want to ask that in the AOM thread?

Yeah...

[bstrobl]

Looks like VP9 has been smuggled into the iOS Youtube App, allowing HDR Videos on some devices.

[Blue_MiSfit]

How do you know it's VP9 and not HEVC? I'd be utterly shocked if apple allows you to do VP9 via DASH on iOS! They certainly don't have a hardware decoder.

[bstrobl]

Originally Posted by Blue_MiSfit

How do you know it's VP9 and not HEVC? I'd be utterly shocked if apple allows you to do VP9 via DASH on iOS! They certainly don't have a hardware decoder.

The iOS app has a stats for nerds option. Video codec is declared as webm VP9.2 on HDR content with AAC audio.

Edit: Furthermore Apple is part of AOM, so they most likely softened up a bit. And it’s not like they don’t do HEVC with software on devices that are much slower.

[iwod]

https://www.reddit.com/r/apple/comme...one_x/dyrir7l/

[LigH]

VPx v1.7.0-387-ge27a33177

[benwaggoner]

Originally Posted by bstrobl

The iOS app has a stats for nerds option. Video codec is declared as webm VP9.2 on HDR content with AAC audio.

Edit: Furthermore Apple is part of AOM, so they most likely softened up a bit. And it’s not like they don’t do HEVC with software on devices that are much slower.

Wow, I wonder what the battery hit is like. And VP9's lack of b-frames and weird vertical slices don't make for efficient parallelization in software decoders.


All HDR capable iOS devices have HEVC Main10 hardware decoders, so choosing a built-in software decoder would not be a technically-driven decision.

[iwod]

Originally Posted by benwaggoner

Wow, I wonder what the battery hit is like. And VP9's lack of b-frames and weird vertical slices don't make for efficient parallelization in software decoders.


All HDR capable iOS devices have HEVC Main10 hardware decoders, so choosing a built-in software decoder would not be a technically-driven decision.

Very very very bad. Basically kills the iPhone within 1 to 2 hours of Youtube and making it extremely hot. As mentioned in Reddit.

However it doesn't seems everyone is getting it. May be it is only on new iPhone models?

I guess Apple had to support it since Youtube is only providing with H.264 encodes for below 2K resolution and 2K+ with HDR with VP9.

[IgorC]

I was surprised (in a good way) after visiting Netflix tech blog.

They make strong accent on VP9 in pretty every article that includes video compression topics. Good news for VP9.
Like here https://medium.com/netflix-techblog/...g-4b9464204830
or https://medium.com/netflix-techblog/...k-e19f1e3a277f

I can speak from my own experience about Netflix and VP9 on smartphone. Long battery life and very good quality. Thumb up.