Kieran Kunhya

What I call north-east, north-west, and so on, right?

But that's eight directions.

Then you can do more directions.

You can do 16 or 69 or 128, right?

You can... And every time your encoder is going to spend more time to see, oh, well, these blocks is exactly this one.

And those type of tools that you can bring.

And the encoder needs to check which of the tools are going to compress you better.

And so...

I guess that AV1 encoding is two order of magnitudes more than H.264 in terms of CPU cycle, right?

Order of magnitudes, right?

But also, it's the fact that you encode once and you have hundreds of millions of users, right?

So, for example, YouTube, a very good example.

YouTube encodes almost everything in H.264, but the popular video gets re-encoded in AV1 because...

It costs more, of course, to encode, but you encode once and you send that to millions, right?

So it's a trade-off between encoding time and complexity and CPU usage on the server side and on the client side.

Because at the end, if you're distributing a video to hundreds of thousands of people and the size is half of the other, then it's better.

It's better for your batteries, better for your modem, et cetera, et cetera.

So you can cut, so you can do cuts.

This is what we call intra-only codecs, right?

So I'm going to explain quickly what is IPB frames.