paperwork icon indicating copy to clipboard operation
paperwork copied to clipboard

"Scan from ADF" (batch mode) should support source selection (duplex)

Open kalinjul opened this issue 9 years ago • 10 comments

I recently got an HP Officejet 8720, which features ADF with Duplex mode. It shows 3 sources in every sane application: "flatbad", "adf" and "duplex". Flatbed and ADF will only scan single-sided, duplex will scan double-sided with the ADF.

In XSane, i can just specify input source: Duplex, number of pages = 2*n (n is number of papers in the tray). In Paperwork, i guess i would have to use the "Scan from ADF" option, but this seems to select "ADF" as input, while i need "duplex".

Do you have a workaround (or a fix, of course)? diag.txt

kalinjul avatar Dec 15 '16 22:12 kalinjul

Related to #535

tiramiseb avatar Dec 15 '16 22:12 tiramiseb

One addition: I changed frontend/multiscan/init.py so it prefers "Duplex" over "ADF" for testing purposes. Sadly, even if i configure Scan from ADF with 2 pages, after receiving the data for page 1, paperwork logs "scan done" and does not wait for further pages. Relevant log part attached.

So duplex handling may require more work than just setting the input ;)

diag_duplexsource.txt

kalinjul avatar Dec 15 '16 22:12 kalinjul

That's because a "simple" scan always scans only one page. To scan multiple pages, you need to use the related option in the drop-down menu. This option always uses the ADF, even when another source is selected. I guess a "duplex" checkbox must be added to this option's screen...

I too am waiting for this addition :)

tiramiseb avatar Dec 15 '16 23:12 tiramiseb

For me, this is a duplicate of #535. So I'm going to close this ticket. Please comment if I missed something, and I will reopen it.

jflesch avatar Dec 16 '16 01:12 jflesch

@jflesch : the option doesn't seem to work the same way : a separate option for me, a different source for julakali. You may want to take into account this diag.txt on #535 too...

tiramiseb avatar Dec 16 '16 06:12 tiramiseb

That's because a "simple" scan always scans only one page. To scan multiple pages, you need to use the related option in the drop-down menu. This option always uses the ADF, even when another source is selected.

That's what I did. I replaced Line 172 in frontend/multiscan/init.py with: preferred_sources=["Duplex", "ADF", "Feeder"] So now, the multiscan option prefers my Duplex source.

But as i wrote yesterday, even with Duplex set as source and number of pages set to 2 (This setup works with xsane), paperwork ignores the data for the backside of the page and keeps displaying an empty second "page" after processing the first "page" (front side of the page).

So I guess a checkbox won't be enough to fix this.

kalinjul avatar Dec 16 '16 09:12 kalinjul

Ok, I keep it open as a reminder, but I will probably do it at the same time than #535

jflesch avatar Dec 16 '16 12:12 jflesch

:+1:

tiramiseb avatar Dec 16 '16 12:12 tiramiseb

Additional info: I think it's a problem with pyinsane in my case. I ran your Multiple scans using an automatic document feeder (ADF) example (using my "Duplex" source) with the same result. Attached you find the sane debug output for scanning one double-sided page with

I don't know how to find out the actual commands that are issued by xsane during the successful duplex scan, however...

kalinjul avatar Dec 20 '16 21:12 kalinjul

For those with duplex scanners, can you run the test program IronScanner to add your scanners in openpaper.work's database please ? I would like to make sure that all Sane drivers handle duplex scanning in a similar manner.

jflesch avatar Mar 05 '18 22:03 jflesch