View Single Post
Old 01-25-2024, 06:04 PM   #33
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,497
Karma: 169115146
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Freeshadow View Post
I have no idea what you actually used then
I thought I made it clear that I was using zopfli/zopflipng. They were built from the zopfli source on GitHub.

When I tried the maximum compression command line with zopflipng, it took close to 4 days to compress a single 32MB png and managed to save 1679 bytes over the original command line compression. The original PNG converted from a Gigapixel Project image was 32,916,531 bytes, the first command line gave a 19,724,422 byte output file and the second command line gave a 19,722,743 byte output file.

zopflipng --iterations=15 big_png1.png png_ncomp.png

zopflipng --iterations=500 --filters=01234mepb --lossy_8bit --lossy_transparent big_png1.png png_maxcomp.png

Last edited by DNSB; 01-25-2024 at 06:13 PM.
DNSB is offline   Reply With Quote