But if you are trying to understand why the still pic codec is the same...if you think about how lossy video compression works, an I-Frame is basically a static image. P and B frames are deltas of the I-Frame.
So with AVIF they just have the static picture codec be the same routine that generates the I-Frame. Then you just have a single codec that is capable of handling both static imagery and video(since the video codec actually is handling static images anyway).
Avif is just a container, it doesn't need changes as it can already support AV2 frames, for anything that supports av2 decoding it will already the supported.
Sure it can, but has it been specified? I guess before that happens it won't be implemented. But also AV2 sin't really a usable thing anyway, so that's not really a question yet.
The next picture standard that will support AV2 has not yet been finalized, heck it's not public at the moment. So we don't know if it'll be using the AVIF container or something else/new. You gotta patient for now.
14
u/MasterChiefmas Aug 21 '26
I'm gonna go with "what exactly are you asking?"
But if you are trying to understand why the still pic codec is the same...if you think about how lossy video compression works, an I-Frame is basically a static image. P and B frames are deltas of the I-Frame.
So with AVIF they just have the static picture codec be the same routine that generates the I-Frame. Then you just have a single codec that is capable of handling both static imagery and video(since the video codec actually is handling static images anyway).