libavif
libjxl
Our great sponsors
libavif | libjxl | |
---|---|---|
44 | 84 | |
1,364 | 2,178 | |
4.0% | 31.1% | |
9.7 | 9.8 | |
1 day ago | 3 days ago | |
C | C++ | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
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.
libavif
-
CVE-2023-4863: Heap buffer overflow in WebP (Chrome)
It's 2023, surely this is not yet another bug related to memory unsafety that could be avoided if we'd stop writing critical code that deals with extremely complex untrusted input (media codecs) in memory unsafe languages?
Yep, of course it is: https://github.com/webmproject/libwebp/commit/902bc919033134...
I guess libwebp could be excused as it was started when there were no alternatives, but even for new projects today we're still committing the same mistake[1][2][3].
[1] -- https://code.videolan.org/videolan/dav1d
[2] -- https://github.com/AOMediaCodec/libavif
[3] -- https://github.com/AOMediaCodec/libiamf
Yep. Keep writing these in C; surely nothing will go wrong.
- Libavif 1.0 Released
-
Is there any clear documentation on how to make avif collections and how to read them?
As far as I understand you are talking about this plugin. I don't know c++ and half of the code was like a black magic, but if I get it correctly, it encodes your images with libavif, and adds custom metadata ([solar/time of day] -> json -> base64).
-
FSF Slams Google over Dropping JPEG-XL in Chrome
So a few dozen comments, but so far it doesn't look like any mention the immediate thing that jumped out at me which was the claims vs AVIF:
>"In turn, what users will be given is yet another facet of the web that Google itself controls: the AVIF format."
Huh? I'll admit I haven't been following codecs as super ultra closely as I used to, but I thought AOM was a pretty broad coalition of varying interests and AV1 an open, royalty free codec that was plenty open source friendly? I've heard plenty of reasonable arguments that JPEG XL has some real technical advantages over AVIF and as well as superior performance is much more feature rich and scalable. So I could see people being bummed for that. But this is the first time I've heard the assertion that it's somehow a Google project? I mean, AOM's libavif reference is BSD too [0]? I'd love some more details on that from anyone who has been following this more closely. I can even understand if AOM isn't as community friendly and an accusation that it's dominated by big corps, but in that case why single out Google alone? From wiki:
>The governing members of the Alliance for Open Media are Amazon, Apple, ARM, Cisco, Facebook, Google, Huawei, Intel, Microsoft, Mozilla, Netflix, Nvidia, Samsung Electronics and Tencent.
Like, Google is certainly significant, but that's a lot of equally heavy hitters. And interesting that Mozilla is there too.
----
-
JPEG XL support has officially been removed from Chromium
> You have a good point that AVIF layered image items can act like such P/B-frames. Do libavif (or other AVIF implementations if any) make use of them?
Seemingly. As search for "libavif progressive encoding" shows several issues about this, and a search for "progressive" in https://github.com/AOMediaCodec/libavif/blob/main/include/av... shows an enum for avifProgressiveState, appears to show support for it.
-
Wavif discussion
I mean, it already has it: https://github.com/AOMediaCodec/libavif/commit/570c42c2c10a878c8cc896f1c5daf1a955274142
-
Animated AVIF and JXL tools for Windows
Apart from mpv and ffplay, the only software I currently have installed that can play animated AVIF is Chromium. And from what I've read from this libavif bug report, I'm not sure if looping animated files in general is something that's just done by default by a lot of software regardless of whether the file is marked as a loop or not.
-
How to create progressive AVIF images?
The support for progressive AVIF decoding has landed in libavif and in Chromium. But are there any docs on how to create and test progressive AVIF images?
-
The Case for JPEG XL
The "for example" is the key here, because AVIF does support multi-layer coding per the spec now (though not currently implemented in libavif from what I can tell).
-
Google Outlines Why They Are Removing JPEG-XL Support From Chrome
libavif is at version 0.11.1, see https://github.com/AOMediaCodec/libavif/tags
libjxl
- JPEG XL Reference Implementation
-
JPEG XL and the Pareto Front
https://github.com/libjxl/libjxl/blob/main/doc/format_overvi... is a pretty detailed but good overview. The highlights are variable size DCT (up to 128x128), ANS entropy prediction, and chroma from luminance prediction. https://github.com/libjxl/libjxl/blob/main/doc/encode_effort... also gives a good breakdown of features by effort level.
-
Compressing Text into Images
For JPEG XL, refer to its format overview [1]. In short its lossless mode uses a combination of multiple techniques: the rANS coding with an alias table, LZ77, reversible color transforms, a general vector quantization that subsumes palettes, a modified Haar transform and a learnable meta-adaptive decision tree for context modelling.
One good thing about JPEG XL is that its lossy mode also largely uses the same tool, with a major addition of specialized quantization and context modelling for low- and high-frequenty components.
[1] https://github.com/libjxl/libjxl/blob/main/doc/format_overvi...
- JPEG XL v0.9.0 Released
-
Stripping Metadata
The cjxl source is here. If you spot any reason why -x strip=exif may not work, tell me.
-
Www Which WASM Works
The problem is that the instructions for actually running the WASM file are not that clear... the docs the author mentions shows how to compile to WASM, which is easy enough, but then here's the instructions to make that actually work in the browser:
https://github.com/libjxl/libjxl/blob/main/tools/wasm_demo/R...
Yeah, you need some mysterious Python script, a JS service worker at runtime, choose whether you want the WASM or WASM_SIMD target, use a browser that supports Threads and SIMD if you chose that, make sure to serve everything with the appropriate custom HTTP headers... just reading that, I can see that to get this stuff working on non-browser WASM targets would likely require expertise in WASM, which is the point of the OP. WASM's UX is just not there yet.
-
First automatic JPEG-XL cloud service
https://github.com/libjxl/libjxl#usage
> Specifically for JPEG files, the default cjxl behavior is to apply lossless recompression and the default djxl behavior is to reconstruct the original JPEG file (when the extension of the output file is .jpg).
-
Why "sudo make install"?
I mean compiling a bleeding edge kicad, inkscape or jpeg-xl is easy. But will probably trash your system if you already have an older version installed.
-
XYB JPEG: Perceptual Color Encoding Tested
But you look at your image viewer that could have the lossless indicator? (and there is an issue open to add this indicator to the jxl files)
-
Heyo Everyone! - is there a win or mac software to batch convert imgs to avif?
You might want to use libjxl directly, e.g. for visually lossless images: cjxl --effort 9 --brotli_effort 11 --distance 1.0 --num_threads (nproc) --lossless_jpeg 0 input.png output.jxl on linux (if you're on windows/mac, just replace the (nproc) with the number of cpu threads you have, e.g. --num_threads 16).
What are some alternatives?
rav1e - The fastest and safest AV1 encoder.
qoi - The “Quite OK Image Format” for fast, lossless image compression
cavif-rs - AVIF image creator in pure Rust
Android-Image-Filter - some android image filters
av1-avif - AV1 Image File Format Specification - ISO-BMFF/HEIF derivative
DirectXMath - DirectXMath is an all inline SIMD C++ linear algebra library for use in games and graphics apps
WebKit - Home of the WebKit project, the browser engine used by Safari, Mail, App Store and many other applications on macOS, iOS and Linux.
jxl-migrate - A simple Python script to migrate images to the JPEG XL (JXL) format
benchmarks - Test images and results of compression benchmarks.
squoosh - Make images smaller using best-in-class codecs, right in the browser.
fastapprox - Approximate and vectorized versions of common mathematical functions