All this high speed fiber for nothing...
it's almost like a majority of the world is still consuming data and video on mobile networks.
AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
11–20 of 227 posts
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#12All this high speed fiber for nothing...
Saturation is only a goal if it's a bottleneck. It's good to remove bottlenecks.
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#13I always thought the name AV1 was partly a play on/homage to AVI (Audio Video Interlace), but AV2 breaks that. Even if it’s meant to be embedded into other container formats such as MP4, there are files with the .av1 extension and there is a video/AV1 MIME type (and possibly a UTI?). Does this mean we now need to duplicate all that to .av2 and video/AV2? What about the AVIF file format?
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#14I wait on new codec invented #AI
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#15We must be reaching the limit at which video codecs can only achieve better quality by synthesizing details. That's already pretty prevalent in still images - phone cameras do it, and there are lots of AI resizing algorithms that do it. It doesn't look like AV2 does any of that yet though fortunately (except film grain synthesis but I think that's fine).
I think Fabrice Bellard have been experimenting with neural codecs like that.
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#16It’s pretty amazing people are still finding ways to make video smaller. Is this just people being clever or is it also more processing power being thrown at the problem when decoding / encoding?
Yes, and it's allowing the format to change to allow more cleverness or apply more processing power.
For example, changes from one frame to the next are encoded in rectangular areas called "superblocks" (similar to a https://en.wikipedia.org/wiki/Macroblock). You can "move" the blocks (warp them), define their change in terms of other parts of the same frame (intra-frame prediction) or by referencing previous frames (inter-frame prediction), and so on... but you have to do it within a block, as that's the basic element of the encoding.
The more tightly you can define blocks around the areas that are actually changing from frame to frame, the better. Also, it takes data to describe where these blocks are, so there are special limitations on how blocks are defined, to minimise how many bits are needed to describe them.
AV2 now lets you define blocks differently, which makes it easier to fit them around the areas of the frame that are changing. It has also doubled the size of the largest block, so if you have some really big movement on screen, it takes fewer blocks to encode that.
That's just one change, the headline improvement comes from all the different changes, but this is an important one.
There is new cleverness in the encoders, but they need to be given the tools to express that cleverness -- new agreement about what types of transforms, predictions, etc. are allowed and can be encoded in the bitstream.
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#17I always thought the name AV1 was partly a play on/homage to AVI (Audio Video Interlace), but AV2 breaks that. Even if it’s meant to be embedded into other container formats such as MP4, there are files with the .av1 extension and there is a video/AV1 MIME type (and possibly a UTI?). Does this mean we now need to duplicate all that to .av2 and video/AV2? What about the AVIF file format?
Do you mean the file extension should only reflect the file format and not the codecs it has inside ?
Maybe that’s what we did in the past and it was a bad idea. It’d be useful to know if you can read the file by looking only at its extension
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#18I always thought the name AV1 was partly a play on/homage to AVI (Audio Video Interlace), but AV2 breaks that. Even if it’s meant to be embedded into other container formats such as MP4, there are files with the .av1 extension and there is a video/AV1 MIME type (and possibly a UTI?). Does this mean we now need to duplicate all that to .av2 and video/AV2? What about the AVIF file format?
Do you mean the file extension should only reflect the file format and not the codecs it has inside ? Maybe that’s what we did in the past and it was a bad idea. It’d be useful to know if you can read the file by looking only at its extension
That wouldn't scale well, something like .av1opusflacwebvtt?
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#19I always thought the name AV1 was partly a play on/homage to AVI (Audio Video Interlace), but AV2 breaks that. Even if it’s meant to be embedded into other container formats such as MP4, there are files with the .av1 extension and there is a video/AV1 MIME type (and possibly a UTI?). Does this mean we now need to duplicate all that to .av2 and video/AV2? What about the AVIF file format?
Files with the .av1 extension are for raw AV1 data. For AV2 this should become .av2, yes. That's by design, as they're two different incompatible formats. Typically you use a container like Matroska (.mkv, video/x-matroska), WebM or MP4 which contains your video stream with a type code specifying the codec (av01, av02).
AVIF is also a container format, and I believe should be adaptable to AV2, even if the name stands for "AV1 image format". It could simply just be renamed to AOMedia Video Image Format for correctness.
Re: AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
#20Is anyone else getting a cloudflare blocked on this page?