Skip to content
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

Progresssive JPEG export? #213

Closed
tomByrer opened this issue Dec 14, 2016 · 5 comments · Fixed by #1324
Closed

Progresssive JPEG export? #213

tomByrer opened this issue Dec 14, 2016 · 5 comments · Fixed by #1324
Labels
released This issue/pull request has been released.

Comments

@tomByrer
Copy link

In some cases, PJPEGs are smaller than the on progressives.
I found some C++ code if that's helpful.

@strandedcity
Copy link
Contributor

Jimp relies on https://github.com/eugeneware/jpeg-js for jpeg encoding/decoding. Progressive JPEG export would need to be added there, and then an option for progressive export would need to be added to Jimp. Would be great to have!

@thisconnect
Copy link

Have a look at imagemin. I use jimp + imagemin since a while

@strandedcity
Copy link
Contributor

They rely on https://github.com/mozilla/mozjpeg, which isn't a pure-JS implementation of the JPEG encoder. Unfortunately, won't work for Jimp.

@thisconnect
Copy link

thisconnect commented Jan 16, 2017

You are right, I always forget people use jimp in the browser. Just for correction: imagemin has various plugins. One of them is depending on mozjpeg. Others are guetzli, jpegtran, jpeg-recompress, jpegoptim and many pther for png or webp. They are all native code afaik, so not suitable for jimp :(

@hipstersmoothie
Copy link
Collaborator

🚀 Issue was released in v1.2.0 🚀

@hipstersmoothie hipstersmoothie added the released This issue/pull request has been released. label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released This issue/pull request has been released.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants