Alexander> Hello, I recently bought a transparancy-adapter for my
Alexander> Paragon 1200SP. The problem is now, that the scan area
Alexander> of the adapter is not as big as that of the scanner. So
Alexander> the scanner automaticaly reduces its scan area to
Alexander> 203x254mm by moving the "head" towards the middle of the
Alexander> scanner whenever trancparancy is used. It seems the sane
Alexander> backend doesn't know this and tries to scan the whole
Alexander> area, with the well-known noisy results.
And potential for scanner destruction... ;-(
Alexander> Is there any way to define the scan area depending on the
Alexander> document type? Or what else can I do?
In theory, the Mustek backend can already detect the presence of a
transparency adapter (but it doesn't know much else). If you set
environment variable SANE_DEBUG_MUSTEK to a value >=2, you should see
a message of the form:
[mustek] attach: found Mustek scanner model BLAH (BLAH), 1-pass, TA
The important thing being the "TA". If you see this, the backend
detected the transparency adapter and dev->flags will have flag
MUSTEK_FLAG_TA set. With this, it would be easy to adjust the
scanning area.
Patches for supporting transparancy adapters would be of course very
welcome (I don't have such a beat myself). If you end up playing with
this, let me know and I'll see about getting the Mustek SCSI command
docs to you.
--david
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com