av1-avif
mp4parse-rust
Our great sponsors
av1-avif | mp4parse-rust | |
---|---|---|
25 | 2 | |
437 | 393 | |
0.7% | 1.0% | |
0.0 | 6.0 | |
over 1 year ago | about 2 months ago | |
HTML | Rust | |
BSD 2-clause "Simplified" License | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
av1-avif
-
FSF Slams Google over Dropping JPEG-XL in Chrome
So right away on the first item:
>Max image size is limited to 4K (3840x2160) in AVIF, which is a deal breaker to me. You can tile images, but seams are visible at the edges, which makes this unusable. JPEG XL supports image sizes of up to 1,073,741,823x1,073,741,824. You won’t run out of image space anytime soon.
>JXL has a maximum of 32 bits per channel. AVIF supports up to 10.
Max resolution and bit depth is certainly massively higher for for JPEG XL, but spec [0] says that:
>"NOTE: [AV1] supports 3 bit depths: 8, 10 and 12 bits, and the maximum dimensions of a coded image is 65536x65536, when seq_level_idx is set to 31 (maximum parameters level)."
And 12-bits per channel is considered a lot for end user final display formats? It also seems to be supported in browsers too so it's not just theoretical. It looks like back in 2021 there was discussion around this and clarifying that the profiles decided on in 2018/2019 were more about giving targets for hardware acceleration of the time, but software decoders by 2021 supported essentially the whole spec (and it appears to me that another 2 years later now final lingering stuff has been dealt with) [1,2]:
>Cyril has proposed a pull request (#130) to better clarify what is and is not supported in AVIF. In short, AVIF supports everything that AV1 supports, which includes 12-bit encoding. The current software decoder implementations also support more or less all of AV1, which can be seen if you try to decode a 12-bit AVIF file in a web browser.
And for still images, hardware acceleration isn't important, so as a practical matter unlike AV1 video pure software for max features is fine. So 65k x 65k and 36-bit color appear to be the limit, which definitely isn't as much as JPEG XL, but is pretty respectable for majority of end user usage?
----
0: https://aomediacodec.github.io/av1-avif/#profiles-overview
The article is about avif not webp. Note the editors for the AOM avif specification don't even include Google https://aomediacodec.github.io/av1-avif/
-
Whistleblowers Take Note: Don’t Trust Cropping Tools
This reminds me of something similar from the guy who implemented AVIF in Firefox. He gives a talk about the implementation [1] where he talks about the CLAP privacy problem. Basically the spec adds a field that allows for cropping of the image, but the binary file would still contain the original. This would lead users to believe some image data was deleted when it really wasn't. I always thought he spent a lot of time and effort on this for little gain, but now I'm starting to think it was worth his effort.
[1]: https://youtu.be/BUkRlfkv2D8?t=2199
And the related GitHub issue: https://github.com/AOMediaCodec/av1-avif/issues/188
-
AVIF images encoded with yuv422 appear black on iOS 16 / MacOS Ventura
So actually the same images I linked above are in the AOMediaCodec repo as well, under Link-U: https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles/Link-U And I see the same issue with the yuv422 images there as well. I'm guessing Apple's AVIF implementation must be incomplete?
Try also test files from here: https://github.com/AOMediaCodec/av1-avif/tree/master/testFiles
-
What is AVIF?
Created by Alliance for Open Media and worked on by Netflix, Microsoft, and Google developers, AVIF is open source - you can even weigh in on image processing and spec issues.
-
How can HDR AVIF stills be created?
I've been trying to find a way edit 14bit RAW files (.ARW) to an HDR capable format (HEIF/AVIF). In the process I found out there's an official AVIF encoder (1) by AOM that seems like it should be capable of creating HDR PQ stills.
-
Web developer's guide to AVIF images
AV1 has some support for progressive images as well. It hasn't been used much in AVIF yet, though there are a couple of PRs that contain some sample images encoded progressively: https://github.com/AOMediaCodec/av1-avif/pull/134 https://github.com/AOMediaCodec/av1-avif/pull/131
-
Firefox avif support delayed again until at least version 90 on 29th June 21
AV1 Image File Format (AVIF)
- Firefox usage is down 85% despite Mozilla's top exec pay going up 400%
mp4parse-rust
-
Firefox avif support delayed again until at least version 90 on 29th June 21
Instead of standard lib, Firefox uses a rust-based image parser, and there are problems with the compliance because all avif apps have to implement the following specs:
What are some alternatives?
ImageMagick - 🧙♂️ ImageMagick 7
libavif - libavif - Library for encoding and decoding .avif files
chromium - The official GitHub mirror of the Chromium source
brunsli - Practical JPEG Repacker
webp - webp for the Windows build of ImageMagick
lepton - Lepton is a tool and file format for losslessly compressing JPEGs by an average of 22%.
squoosh - Make images smaller using best-in-class codecs, right in the browser.
jekyll_picture_tag - Easy responsive images for Jekyll.
image_compression_comparison - Image Compression Comparison Framework
jpeg-xl - jpeg-xl for the Windows build of ImageMagick
libjxl - JPEG XL image format reference implementation
sumatrapdf - SumatraPDF reader