-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Scan made from ADF are corrupted #413
Comments
Just used the latest docker image and confirm the corrupted files when scanning via ADF. Scanning with flatbed works. The Image file of one A4 page has dimensions of 1654 × 65535. |
Tested on my HP OfficeJet 6500A, same issue there. |
@autumnwalker No I don't think it's the same issue |
Seeing the same issue on my HP OfficeJet Pro 8025e |
The binary stream that is downloaded from the device is not corrupted during transfer. If I use this online service, the document content can be revealed, but the height of the image is not accurate : https://jpg.repair/fix-picture.php?uid=626f9a48c4c1d4.00253158 |
If I set the image dimension inside the JPEG stream inside the header, the picture can then be opened I'm going to implement that fix. |
It's not enough to fully fix it, there is now a pink banner at the bottom of each page (see #455) |
I've analyzed the image on which size has been overridden with this online tool https://processing.compress-or-die.com/analyze-process, and it states that the file contains a DNL marker.
|
The scan is fixed by defining inside the jpeg stream the height of the document that can be found in the stream after the DNL marker |
The scan from ADF (Automatic Document feed) are corrupted, images are corrupted and can't be viewed
Sample corrupted image :![scanPage1](https://user-images.githubusercontent.com/5827164/154764138-ec980762-43f0-474e-a1be-7f666f402d6c.jpg)
If I open it in some software, it says that :
Maximum supported image dimension is 65500 pixels
The text was updated successfully, but these errors were encountered: