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

Support for encoding progressive jpegs #12

Open
avalanche1 opened this issue Oct 19, 2015 · 8 comments
Open

Support for encoding progressive jpegs #12

avalanche1 opened this issue Oct 19, 2015 · 8 comments

Comments

@avalanche1
Copy link

Is it hard to implement? My proj does image manipulation client-side and it would be nice to be able to encode progressive jpegs.

@tomByrer
Copy link

I've done some research for another project. Tricky, but surprised no one transposed existing C code over.

@tomByrer
Copy link

Here is a PJEG splitter:
https://gist.github.com/Hodapp87/9220146

@avalanche1
Copy link
Author

avalanche1 commented Feb 25, 2017

Interesting. Will ask someone with C exp to replicate that in JS; when I have that someone)

@tomByrer
Copy link

@patrickhulce patrickhulce changed the title Support for progressive jpegs Support for encoding progressive jpegs Jul 11, 2017
@benwiley4000
Copy link
Collaborator

I'm no progressive jpeg expert (@patrickhulce have you looked into this?) however from the look of that code @tomByrer it looks like it's more related to decoding a progressive jpeg into separate slices? whereas if I understand your question correctly @avalanche1 you want to take an arbitrary image data array and encode it as a progressive jpeg?

I'm not really sure how complex this would be, but we'd welcome ideas or even a pull request!

@patrickhulce
Copy link
Collaborator

Encoding is slightly more hairy then decoding IMO, I haven't spent any time digging in to it. It might be worth establishing some goals of the project or at least guidelines for deciding if an aspect of JPEG should be worth maintaining here? Progressive encoding probably makes the cut, but the realm of possibilities is quite large and we have limited time :)

@benwiley4000
Copy link
Collaborator

It doesn't help that there don't seem to be any real progressive encoding solutions out there already in pure-javascript land! 😢

@tomByrer
Copy link

tomByrer commented Jul 16, 2017

Encoding is slightly more hairy then decoding IMO

Probably correct if you don't hardcode the scans.
Thanks for getting the decoding in @eugeneware!

Might be better as an 'plugin' or external include, since the code is unlikely to be used by all & likely to be sizable.

research notes:
http://cloudinary.com/blog/progressive_jpegs_and_green_martians

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants