Closed onethumb closed 6 years ago
Thanks for the report... it seems that your progressive image had the scans in an unexpected order and lepton rearranged them, producing a pixel-exact result, but not a roundtripping bit-exact result. Unfortunately most of the quality control was done with the -rejectprogressive command line, which would simply have banned this file
it's probably a minor change to serialize out the ordering somewhere in the file...feel free to submit a pull request if you'd like to improve the tool in this way.
Can you try downloading master and passing lepton the -permissive flag?
re-open if you're still experiencing an issue with the -permissive flag
On certain JPEGs that other pieces of software think are well-formed, Lepton fails validation:
Other JPEG-related commands work fine, such as
jpeginfo
, seem to work fine:ImageMagick
identify -verbose
doesn't detect any errors. Browsers, Photoshop, etc, all seem to operate fine, as does our internal tooling.jpegtran
operations work (-optimize
,-progressive
, etc). Afterjpegtran
execution, Lepton works on the resulting output.When
-skipvalidate
is used with Lepton, it produces the expected invalid JPEG.Example Photo 1: https://www.dropbox.com/s/4sufy9ws3scvovx/jpeg-produces-strange-lepton-errors.jpg?dl=0 Example Photo 2: https://www.dropbox.com/s/avgfd4s2wbuzlue/jpeg-produces-strange-lepton-errors-2.jpg?dl=0