FileOptimizer 15.50 - PNG file get bigger during optimization
Javier Gutiérrez Chamorro (Guti) Open source projects
Brought to you by:
nikkho
Menu
▾
▴
Today I optmimized a big (15 MB) PNG file 3024x4032 pixels and 24 bit color depth.
My program settings are at the highest compression level.
After the first optimization tools I recognized at the processing of leanify, that the original filesize was smaller than the current filesize of 15.838.807 bytes.
Is it possible, that FileOptimizer does not check the filesize of the last optimization to the next optimization?
Maybe one of the first optimization tools work better than leanify or others.
It can be done, but will not be optimal in most cases. I did some tests in the past and setted up the most optimal order of plugins.
I am sure you have chosen the best optimisation sequence.
Maybe it is a single case.
The new guetzli cuda encoder is a great piece of software! Thank you.
My gpu workload is sometimes not very high, but the speed advantage is great!
Last edit: James Pous 2022-02-17
Still, all programs should probably use the option that tells them to fail if the result is larger than the input. And if a program lacks such an option, it would be good if you'd check instead.
No one optimizing a file wants a result that's larger than the original.
Also, where is the changelog so I can see if I want to update yet?
FO is discarding output file if larger.
Updated changelog for stable reasons is always posted at FO official page: https://nikkhokkho.sourceforge.io/static.php?page=FileOptimizer
Development changelog is available at SVN repository: https://sourceforge.net/p/nikkhokkho/code/HEAD/tree/trunk/FileOptimizer/Changelog.txt