Friendly reminder to crush your pngs

Attached: Untitled.png (1000x1000, 3.82M)

Attached: 1540174444981.png (1000x1000, 5K)

pingo can be either
too bad it's not foss.
also not sure about how it decompresses.
would affect things if you tried to animate the outputs.

>pingo

Attached: tenor[1].gif (498x298, 934K)

Pathetic

my.mixtape.moe/qnhdhe.webp

>no y axis
How utterly useless, OP. For all we know, it could mean the time they take.

Attached: op-16.jpg (355x397, 28K)

I like graphs without labels on the axis

css-ig.net/png-tools-overview

Your mom crushes my dick in her cunt.

Here's the complete graph. Details can be seen in pngquant

Attached: Technology_Chart_PNG_Optimization.png (770x702, 17K)

is there a program on wangblows 10 to batch optimize png?

CLI cucks need not apply

Maybe you can fool some of the older phone posters with this.

how to compress png: convert to jpg

>speed
time or time-1? why u no label axis?

>why u no label axis?
You have to ask the author. But you are right, it needs some context.

Attached: Technology_Chart_PNG_Optimization.png (873x1188, 74K)

what about pngcrush -brute?

I tested it on the same test pictures. Please take the time with a grain of salt as I used a bash built-in to roughly estimate it.
These results would put pngcrush on the 14th rank in the speed and the 19th rank in the size rating.

Also fuck the code tags for messing with my formatting and forcing me to post the results as a picture.

Attached: results.png (943x685, 41K)

Literally how do I use any of these then?

Faggot

Attached: 1540174444981.png (1000x1000, 17K)

>thread about png compression
>doesn't compress his png

Attached: compression.png (728x284, 5K)

For those that thing ect or other similar png crushers are too slow when batch compressing, be sure to use GNU Parallel to make it faster

>takes graph about lossless png optimization
>introduces losses

Attached: diff.png (728x284, 3K)

>ctrl-f lossless
>only see your post
>extreme hyperbole.png

Please notice how I referred to the graph and not this thread.

Doesn't state lossless either, but alright. Now I know it's a rule.

I'm familiar with the source (see ). That's why I know.
I just think it's important to differentiate between lossy and lossless optimization, especially when a combination of the two provides the biggest file size savings.

So was wrong?

Of course it depends on what you're working with and what your goal is. If you want to store your pictures lossless than using any kind of lossy compression is out of the question and for line art and other strong suits of png, lossless optimization usually nets good enough results that a prior lossy compression is unnecessary.
But if you're looking at e.g. high resolution photos then lossless png optimization will do shit. Applying lossy png compression first and then using lossless optimization will get you further.

Anybody got the download link for pingo? Can't seem to find it on the website ( css-ig.net/pingo )

Attached: 1539490714600.jpg (3036x4048, 1.04M)

it's literally at the top of the page user

Where?

Attached: Screen Shot 2018-10-22 at 21.38.26.png (1676x1889, 393K)

get a decent browser user, jesus christ

css-ig.net/downloads/pingo-win

Attached: screencapture-css-ig-net-pingo-2018-10-22-11_36_26.png (1920x3995, 678K)

Right...

WTF is this? Some sort of sick joke?
Anyone able to upload it elsewhere for me?

Attached: Screen Shot 2018-10-22 at 21.41.49.png (1676x1889, 130K)

When did pingo start supporting Linux? I thought it was Windows exclusive?

nice chart retarded faggot

Attached: iPad-3-A5X-graphics-performance-vs-NVIDIA-Tegra-quad-core-processor.jpg (1000x593, 43K)

ufile.io/dxppe

Or we could just use HEIF or the upcoming AV1-based image compression or even just WebP.

thanks bro.

I'll gladly do that once they are as widely supported as PNG (and they improved AVIF's encoding speed).

Attached: comparison.png (2250x1350, 89K)

Does running ect with the --strict option significantly reduce its compression effectiveness?

In many cases it has no influence on ECT's effectiveness. From the documentation:
>--strict
>Enable strict losslessness. Without this, image data under fully transparent pixels can be modified to increase compression. This data is normally invisible and not needed. However, you may want to use this option if you are still going to edit the image.
>Also preserves rarely used GZIP metadata.

I've been using optipng all this time but it's looking like this new-fangled ect thing is the way to go

No Y axis labels, 3d graphs.
>garbage

They are all command line tools. Some of them (like pingo) offer pre-build binaries. Others (like ECT) you need to compile yourself.

up you go :)

Attached: true_wisdom.jpg (460x302, 35K)