You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a want to be able to use AVIF for small to very small images. One of the hurdles there is the overhead of the container itself, which is looked into here: AOMediaCodec/av1-avif#121 MPEGGroup/FileFormat#59
But I'm kind of assuming that AV1 has not really been optimized for small still images, and especially for small lossless still images.
It would be great if some time is spent during AV2 research to look into if there are any extra tweaks that can be made to compress this use-case better.
The text was updated successfully, but these errors were encountered:
As an example, quite a lot of web content consist of JPGs or PNGs that are really small (on the order of 32x32).
Maybe there are coding tools that only make sense for images this small?
Or maybe some gains could be made by initializing adaptive entropy coding statistics differently?
On Wed, Sep 7, 2022 at 7:17 AM leo-barnes ***@***.***> wrote:
As an example, quite a lot of web content consist of JPGs or PNGs that are
really small (on the order of 32x32).
Maybe there are coding tools that only make sense for images this small?
Or maybe some gains could be made by initializing adaptive entropy coding
statistics differently?
The reverse is true to, i.e. tools for larger blocks no longer makes sense,
the syntax for them such as larger prediction block sizes and transform
sizes probably can be conditionally removed.
There is a want to be able to use AVIF for small to very small images. One of the hurdles there is the overhead of the container itself, which is looked into here:
AOMediaCodec/av1-avif#121
MPEGGroup/FileFormat#59
But I'm kind of assuming that AV1 has not really been optimized for small still images, and especially for small lossless still images.
It would be great if some time is spent during AV2 research to look into if there are any extra tweaks that can be made to compress this use-case better.
The text was updated successfully, but these errors were encountered: