danielgtaylor / danielgtaylor/jpeg-archive
Looking for some clarification on the code's capabilities
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Description
I initially thought from the documentation that I could run jpeg-recompress against a high quality jpeg and it would produce a visually identical jpeg at a reduced file size: "Compress JPEGs by re-encoding to the smallest JPEG quality while keeping perceived visual quality the same ... This is a lossy operation, but the images are visually identical..."
However, two things confuse me and I wondered if you could clarify them for me so I can get the most out of this excellent code?
1. Some of the images that are produced show a lot of those strange jpeg compression blocks and striated shadows. I originally found that issue using "jpeg-recompress --quality high --accurate --method smallfry --min 60 input.jpg output.jpg". I switched to SSIM and had better luck, but I'm confused as I thought the whole point was that it would always save out something that was visually identical to the input? Am I misunderstanding that? Or would this be a bug?
2. The quality settings also confuse me. If the script is supposed to produce visually identical images at "Medium" setting, what are the High and Veryhigh settings for? And equally, does Low imply that the output will be less visually identical? I'm confused.
Thanks for any clarification you can offer me on these points, and for all the hard work you've put into this.
Original 100% quality JPEG from photoshop

--quality medium --loops 20 --method ssim --accurate

--quality high --loops 20 --method ssim --accurate

--quality medium --loops 20 --method smallfry --accurate

--quality high --loops 20 --method smallfry --accurate

Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the quoted documentation and the example jpeg-recompress commands using the medium and high quality settings, SSIM, and smallfry methods. Reproduce the reported outputs if the example images remain available, then trace how the documentation describes visual similarity and quality levels. Done means the quality-setting behavior and the reported artifacts are clearly explained or the documentation is corrected.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100