This topic contains 6 replies, has 4 voices, and was last updated by Srivatsan 2 weeks ago.
August 29, 2012 at 7:23 pm #22777
I’m creating a small interface in Delphi to use a twain source with Envision component.
The driver of “kodak i2600”, have in your profile/config an TAB called “Size” -> in side the combobox “DOCUMENT” with the options: “Automatically Detect and Straighten“, “Automatically Detect” and “Manually Select“.
I need set to “Manually Select” to use DAT_IMAGELAYOUT definitions. I want set this option via twain.
I read 2.2 spec, and tryed several caps… But, no one work 🙁 Which CAP_ should I use?
I already used (disable/turn off): ICAP_MAXFRAMES, ICAP_UNDEFINEDIMAGESIZE, ICAP_AUTOMATICLENGTHDETECTION, ICAP_AUTOSIZE, ICAP_SUPPORTEDSIZES, ICAP_OVERSCAN, ICAP_AUTOMATICDESKEW, ICAP_AUTOMATICCROPUSESFRAME …
Any help is welcome 🙁
Thanks,September 4, 2012 at 8:14 pm #25687
Setting ICAP_AUTOMATICBORDERDETECTION to FALSE and ICAP_AUTOMATICDESKEW to FALSE should be enough to make the change you want.
You can also try the custom ICAP_CROPPINGMODE, setting it to TWCR_TRANSPORT.
The GUI always reflects changes made in state 4, so if you bring it up after setting these values you should be able to confirm that your app code is working.September 12, 2012 at 1:22 pm #25688
Setting ICAP_AUTOMATICBORDERDETECTION to FALSE …
Very thanks Mark, setting ICAP_AUTOMATICBORDERDETECTION to false solved my problem. 😀
CyaDecember 18, 2013 at 12:01 pm #25689
There is no hardware specification. Nearly any scanner hardware can be supported by a TWAIN DS which supports the TWAIN spec.June 1, 2017 at 9:36 am #30115
Using Twain API with Kodak i2620
I am facing an issue using the Twain APi with Kodak i2620 scanner. I am not able to scan more than 20 sheets. It scans for 20 and then fails with Out of Memory Exception. It is a C# application and x86 platform. Request your kind help on the same. Thank you.
S.SrivatsanJune 2, 2017 at 9:00 pm #30117
Good News, the issue is resolved. It was a Memory issue. Running a x86 application in an x64 processor would reserve only 1.3GB of memory to the Process and since ours is a thread based solution the memory is always under use. So, once the memory level is reached, it explodes. See the below link for more info:
Do contact me over my email for any further discussions. Thank you.
S.SrivatsanJune 22, 2017 at 3:12 am #30201
Guys, one more addition to this. Ensure that the “size in Kb” of the image which you are trying to scan is lesser. This also holds a point in continuous scanning as the images are continuously maintained in the memory till the scan process is complete. I changed the Compression mode of the Images in the Settings ans was able to see improvements in the scanning process. Thank you.