How fucked is H265?

>>61189345
Fucked right in the pucci.

>>61189417
How hard?

>>61189345
>still no bitstream freeze
>no hardware support until late 2018

>>61189345
I want to love AOM and AV1, but it's so late, and SO SLOOOW.
It takes literally days to encode a short video, and it's only 30% better than HEVC

>>61189862
>30% better than HEVC

Where are you taking this figure from? I though not all techniques were even enabled so it would perform like crap anyways.

>>61190019
Check out AWCY, depending on what's enabled it can change quite a lot.

A while ago the goal was 50% smaller than HEVC, but this has been scaled back considerably, now they just aim to do better.

>>61190239
I don't think they even have to do better, it's enough the standard offers similar gains and by doing so cuts the mpeg string.

Also are they working on a public encoder concurrently too? Or is the software simply exemplary?

anyone tried encoder or decoder?

https://aomedia.googlesource.com/aom

>>61190467
The code is open source, so you can always go and compile it.

But originally their goal was to be a next-next gen codec, competing with what came after HEVC, so scaling back their goals like that is a little worrying

I'm still dumbfounded that Apple chose to go with HEVC when practically everyone else chose to unite under AVI.
>tim cook is a faggot

>>61190785
There's no reason Apple couldn't use the technology anyhow. After all, it's open source with no implementation fees.

I think they have more than a few arguments to be against it.
First, they invested into HEVC, offered patents so expect a return. Supporting a free competing format signals abandoning their source of revenue and market influence.
Second, Apple's HLS streaming relies on MPEG TS. MPEG TS however only supports MPEG line of encoding standards. In effect AV1 will be exclusively streamed only using MPEG DASH. Apple is losing the streaming market too.