Zpng
fpng
Zpng | fpng | |
---|---|---|
4 | 10 | |
254 | 830 | |
- | - | |
10.0 | 4.1 | |
almost 6 years ago | 5 months ago | |
C | C | |
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.
Zpng
- Zpng: Better lossless compression than PNG with a simpler algorithm
-
Quite OK Image is now my favorite asset format
> You'd probably get even better results by using PNG's filters instead of QOI
Did anybody ever try this? It would be quite interesting and does not seem too difficult.
The only thing I could find is https://github.com/catid/Zpng which does not use the normal PNG filtering.
-
Google Chrome Is Already Preparing To Deprecate JPEG-XL (~3x smaller than JPEG, HDR, lossless, alpha, progressive, recompression, animations)
Also, Chris Taylor published an experimental PNG library with Zstd hardwired in.
-
QOI: Lossless Image Compression in O(n) Time
- I feel like the benchmark suite is lacking. For better overview you probably should include libpng results with max compression level and lowest compression level. Lossless modes of AVIF and WEBP would be nice. (also could throw similar project to yours like https://github.com/catid/Zpng) Not saying the benchmark is bad, but IMHO doesn't paint the full picture. From quick test I got significantly better compression on libpng, ofc in expense of time, but you didn't optimize it for speed either. So we have some results, but they are not really representative imho.
fpng
-
png crate gets an ultrafast compression mode, up to 4x faster decompression
When the QOI format was first announced it wasn't clear that was even possible while keeping PNG format compatibility. But the fpng and fpnge C/C++ libraries showed it was, and today you can take advantage of those advances in a general purpose PNG library in Rust!
-
Hello, PNG
CRC is a table and 5 lines of code. That's trivial.
>zlib is 23k lines
It's not needed to make a PNG reader/writer. zlib is massive overkill for only making a PNG reader or writer. Here's a tiny deflate/inflate code [2] under 1k lines (and could be much smaller if needed).
stb[0] has single headers of ~7k lines total including all of the formats PNG, JPG, BMP,. PSD, GIF, HDR, and PIC. Here's [1] a 3k lines single file PNG version with tons if #ifdefs for all sorts of platforms. Removing those and I'd not be surprised if you could not do it in ~1k lines (which I'd consider quite simple compared to most of todays' media formats).
>Of course they're not common formats so you're stuck with complex formats like PNG
BMP is super common and easy to use anywhere.
I use flat image files all the time for quick and dirty stuff. They quickly saturate disk speeds and networking speeds (say recording a few decent speed cameras), and I've found PNG compression to alleviate those saturate CPU speeds (some libs are super slow, some are vastly faster). I've many times made custom compression formats to balance these for high performance tools when neither things like BMPs or things like PNG would suffice.
[0] https://github.com/nothings/stb
[1] https://github.com/richgel999/fpng/blob/main/src/fpng.cpp
[2] https://github.com/jibsen/tinf/tree/master/src
- Quite OK Image is now my favorite asset format
-
Computing Adler32 Checksums at 41 GB/s
This was actually considered, and other libraries do ignore checksums, or at least have options to:
https://github.com/richgel999/fpng/issues/9
-
QOI – The Quite OK Image Format
In the other direction, you can target a subset of PNG to get less optimized images but with QOI-like encode and decode speed: https://github.com/richgel999/fpng
-
ReShade 5.0 Released!
On specific operations like screenshots for example the new version is WAY faster though. We were using stb_image_write.h but switched to fpng which promised 12-19x faster compression at smaller sizes. That and the fact that screenshot saving have now been given it's own thread so it now longer causes a small stutter like when it was on the main thread, means that screenshot are now near instantaneous.
-
QOI – The “Quite OK Image Format” for fast, lossless image compression
I think QOI inspired the creation of https://github.com/richgel999/fpng which creates standard PNGs and compares itself directly to QOI.
-
Losslessly compresses RGB and RGBA images to a similar size of PNG, while offering a 20x-50x speedup in compression and 3x-4x speedup in decompression
BTW, today I found this fpng-fast PNG writer. There is a comparison with QOI in the readme.
What are some alternatives?
qoi - The “Quite OK Image Format” for fast, lossless image compression
ZLib - A massively spiffy yet delicately unobtrusive compression library.
fpnge - Demo of a fast PNG encoder.
qoi - Pure Go encoder/decoder of the QOI image format
libdeflate - Heavily optimized library for DEFLATE/zlib/gzip compression and decompression
zopfli - Zopfli Compression Algorithm is a compression library programmed in C to perform very good, but slow, deflate or zlib compression.
oss-nvjpg - Hardware-accelerated JPEG decoding on the Nvidia Tegra X1
qoi - A rust implementation of the “Quite OK Image” format for fast, lossless image compression
PNG-spec - Maintenance of the PNG specification
rawloader - rust library to extract the raw data and some metadata from digital camera images
php-qoi - QOI image encoder and decoder written in pure PHP