Kieran Kunhya

Or you have a black background behind me, for example.

The black is the same on the whole picture, right?

So you can say...

Well, you know, in this picture, take the pixels that you have on the top left and the one on the top right.

I'm not going to give the value.

I'm just going to tell you it's the same at the top left.

And then you can say for frame one, reuse something from the previous frame or the previous previous frame and so on and so on.

Right.

So you could basically it's unlimited, but then it's limited in terms of memory or in terms of compute power.

Because, for example, if you need to compare pixels on 200 frames in the past on 4K resolutions, it's a huge amount of compute.

Yes, exactly.

And those are two different trade-offs.

Are you going to compress more?

but then it might be more difficult to decode.

Are you going to make it a codec that is more complex to encode and easier to decode?

Are you going to make a codec that is easier to encode because you need to be fast, but then the client side, the player, is going to spend more time?

That's why you have so many different types of codecs, is that it's not always easy.

And to make it even more complex, modern codecs like AV1, AV2, or VVC are actually not codecs.

They are a collection of tools, right?

There are multiple tools, multiple codecs in the same codec to, depending on the image, get the more compression.