-
-
Notifications
You must be signed in to change notification settings - Fork 481
-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PNGoo - command-line version (cli/cmd) #354
Comments
All pngoo does is launch pngquant command line. It does nothing else. |
Then how to explain, that when I compressing this file with with PNGoo, i get 5kb output file, but with same settings if i launch pngquant, it produces 20kb output file. Can you advise how to execute pngquant (with what parameters) to get the same result for that file? |
Try setting the same number of colors or quality as the GUI. Are you calling the same exe as pngoo, or a different version? It really is just a launcher for pngquant exe: |
|
that's why I am surprised too. UPDATE: so, obviously, PNGoo is not just launched of pngquant, instead it does some more file optimization/reduction before sending to pngquant too. you can try yourself with my above linked .png file and see that is the case. Would be nice if you integrate that optimization in pngquant too, so we could disregard PNGoo in command-line, and directly use pngquant. |
Did you have a chance (really 1 minute) to confirm that behavior on the above provided sample image? maybe it's related to the bytes of transparency being ignored in PNGoo, and not in PNGquant? |
pngquant is incapable of preserving RGB values of transparent bytes due to the colorspace it uses internally. It couldn't have that bug even if it wanted to :) Can you provide the tmp file, the direct pngquant, and pnggoo files to compare? |
I have deleted previous messages, and now, briefly, here I am sending a real proof of the misbehavior (which is caused by something I was unable to find, other than that PNGoo does something else). Here I am attaching several image samples - https://we.tl/t-vsC2aWMItO in each sample folder, there are 4 images: so, you see the differences yourself. not only they have different results, but even (B) and (D) have different results (even though the same pngquant exe is used in those occasions) |
well, it's a pitty author ignored this topic. Unfortunately, the above "wetransfer" files has been deleted and I don't have time to generate them again. just for historical purposes if anyone ever will take a minute to check and confirm themselves, i will attach the original file here - https://drive.google.com/file/d/1yzevMqZz-0fDaJ5nipVw4wrnPeRu36X8/view?usp=sharing i have already mentioned the steps (only 1 minute needed) to reproduce the problem. |
Hi.
I don't know what i am missing, but tried many times with different (transarent) images, and the results I am getting from PNGoo, i cant get with any command line arguments with pngquant. If original file is 300kb, pngquant produces around 150kb, while PNGoo around 50kb.
So, i've switched to use PNGoo from command line. at this moment, i've created Console Application ( dependent project onto PNGoo, which is closed and cant commit there), so, when I drag&drop file, or execute like
pngoo-cmd image.png
.so, what I ask, can you please add an ability to run PNGoo from command line too? so, the main PNGoo exe could determine if it is run from command-line, it should output form, instead work under cmd.
or otherwise, give us some insights how to run pngquant samely from cmd to get same results as PNGoo.
The text was updated successfully, but these errors were encountered: