[hi_herbert]

I regularly have atrocious transient 144p like compression artefacts and lighting absurdities using Netflix both in chrome and via their native h265 app. It is pathetic.

Tangent if they really cared about user experience and Ecology they would implement h265 and h266 support in chromium (aka a mere function call to the embedded ffmpeg). H266 is revolutionary but it's adoption is of zero because of AV1 lobbyists a bit like so called environmentalists once launched a RPG rocket on the superphenix thorium mankind saving reactor.

[suzumer]

FFMPEG hasn't even implemented VVC yet, and neither have web browsers, so Netflix can't just make "a mere function call" to get H.266 support.

[ksec]

>H266 is revolutionary but it's adoption is of zero

Adoption on the Web. Most broadcasting companies are getting ready to move to H.266.

I wish we could get a JPEG XL based Video codec.

[hi_herbert]

Good point I hope is true but I was also mostly referring to the inexistant (not even in roadmap) hardware acceleration support.

> I wish we could get a JPEG XL based Video codec. Well i'm curious about that but FLIF, the predecessor (and maybe XL too) is based on MANIAC which is a variation of H264 encoding.. https://en.wikipedia.org/wiki/Free_Lossless_Image_Format#:~:...

[ksec]

>inexistant (not even in roadmap) hardware acceleration support.

Oh they are definitely on the roadmap ( Qualcomm and Mediatek ). I think a lot of people forget there are long lead time in hardware development. Especially with Mobile where energy usage is a key issue. The conformance test of H.266 only finished in mid 2021 if I remember correctly and continued being refined in 2022. If you are going to test your silicon in 2021, your earliest chance of any mobile solution with VVC is going to be 2023.

I would guess both AV1 and VVC lands in Qualcomm SoC in ~2023. MediaTek and Apple coming in 2024.

[miniman1337]

jpeg-xs?