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

Why JPEGs for input? #3

Closed
daveloyall opened this Issue May 7, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@daveloyall

daveloyall commented May 7, 2018

Hi, shouldn't you use RAW format images for input instead of JPEG compressed files?

@catid

This comment has been minimized.

Show comment
Hide comment
@catid

catid May 7, 2018

Owner
Owner

catid commented May 7, 2018

@daveloyall

This comment has been minimized.

Show comment
Hide comment
@daveloyall

daveloyall May 8, 2018

Ah, I'm sorry. I meant to ask if it is intentional that the README shows test results for compressing JPEGs, rather than raw files. My understanding is that the raster of pixels you get out of a JPEG decoder will always have some certain characteristics which will make it inherently compressible--you know, those blocks of pixels that are smooth gradients rather than the "random" bag of values you'd observe in a RAW file. I think compression performance statistics on RAW files would tell us more.

daveloyall commented May 8, 2018

Ah, I'm sorry. I meant to ask if it is intentional that the README shows test results for compressing JPEGs, rather than raw files. My understanding is that the raster of pixels you get out of a JPEG decoder will always have some certain characteristics which will make it inherently compressible--you know, those blocks of pixels that are smooth gradients rather than the "random" bag of values you'd observe in a RAW file. I think compression performance statistics on RAW files would tell us more.

@catid catid closed this May 8, 2018

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