zopfli
libjxl
zopfli | libjxl | |
---|---|---|
9 | 85 | |
3,382 | 2,274 | |
0.5% | 30.3% | |
2.6 | 9.8 | |
about 1 month ago | about 17 hours ago | |
C++ | C++ | |
Apache License 2.0 | 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.
zopfli
-
How I use Devbox in my Elm projects
This project uses HTMLMinifier, optipng, and zopfli to create a custom production Elm build pipeline. You can see how I make use of these tools in this build script. Here are the results in case you're interested. I used the same ideas from this project to build and deploy dwayne/elm-conduit, which you can learn more about in my article Yet Another Tour of an Open-Source Elm SPA.
-
PSA: Use ZopfliPNG to compress your PNG assets
I'm making a 2D game with lots of PNG assets. I recently found that ZopfliPNG regularly reduces the sizes of my assets by ~3x compared to Asesprite's output. I've tried a few other PNG compression tools, but ZopfliPNG consistently outperforms the others.
-
Google Chrome Is Already Preparing To Deprecate JPEG-XL (~3x smaller than JPEG, HDR, lossless, alpha, progressive, recompression, animations)
I mean something better than Google's best engineers trying to optimize LZ77's compression as much as humanly possible, while remaining compatible with the DEFLATE/zlib bitstream.
- Improving App Performance
-
Losslessly Optimising Images
zopflipng typically beats pngcrus and optipng (on Linux at least) but by default it drops auxillary PNG chunks [0] which can result in browsers (and other applications) using a different color space, causing the resulting images to look more washed out than the original. To prevent this you need to explicitly pass --keepchunks=cHRM,gAMA,pHYs,iCCP,sRGB,oFFs,sTER to zopflipng.
Unfortunately it (and most other tools) don't have APNG support, keeping only the first frame.
[0] https://github.com/google/zopfli/issues/113
- Good, but slow, deflate or zlib compression library
- What am I doing wrong? ffv1 vs "h264 -crf 0"
-
webP animated
I tried going with a lot of different compression algorithms, in the end a lot of iterations of Zopfli delivers the best result. With that, I got the image down to 591 kB.
-
KB Club: With links to HN, Reddit, Lobsters threads for each website
I tried zopflipng [1] with the very expensive option suggested from the usage and got 2,493 bytes (original 2,740 bytes, nowhere practical as it took 3 minutes) so you don't have to sacrifice the palette, though I'm not sure if 16 or even 4 color palette will significantly alter the visual.
[1] https://github.com/google/zopfli
libjxl
-
JPEG XL and Google's War Against It
> Regarding JPEG XL's mobile support, it makes sense it would see limited development if the company that manages one of the biggest mobile players has been the greatest restriction on their success. The lack of support also disincentivises manufacturers to prioritise support.
There was literally no involvement from any hardware vendor in the standardization of JPEG XL. It went from a Call for Proposals in Sept 2018 to Committee Draft in Aug 2019 with very little time for industry feedback. Contrast this with AV1 which had involvement from hardware vendors Intel, NVIDIA, Arm, AMD, Broadcom, Amlogic from the beginning as well as companies who ship media on hardware at scale such as Cisco, Netflix, Samsung and yes Google. These companies reviewed and provided significant feedback on the format that made it suitable for hardware implementation.
https://news.ycombinator.com/threads?id=JyrkiAlakuijala is a lead on the project and a Google employee, and active in JPEG XL development https://github.com/libjxl/libjxl/commits?author=jyrkialakuij...
- 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)
https://github.com/libjxl/libjxl/issues/432
What are some alternatives?
oxipng - Multithreaded PNG optimizer written in Rust
qoi - The “Quite OK Image Format” for fast, lossless image compression
guetzli - Perceptual JPEG encoder
Android-Image-Filter - some android image filters
libavif - libavif - Library for encoding and decoding .avif files
DirectXMath - DirectXMath is an all inline SIMD C++ linear algebra library for use in games and graphics apps
PNG-spec - Maintenance of the PNG specification
optipng-bin - optipng bin-wrapper that makes it seamlessly available as a local dependency
jxl-migrate - A simple Python script to migrate images to the JPEG XL (JXL) format
Zpng - Better lossless compression than PNG with a simpler algorithm
squoosh - Make images smaller using best-in-class codecs, right in the browser.