Re: Coolscan LS-30 + best scanner

Andreas Rick (rickand@gemse.fr)
Tue, 18 May 1999 08:56:29 +0200

Erwald send me a link to "Vuescan" on www.hamrick.com, which
will help me a lot in adapting the Coolscan-SANE backend
to the LS30.

It writes all the SCSI-commands passed to the scanner to a log file.
Now I have all the pieces of the puzzle and I only need
some time to put them together.
(I actually got the first image data from the scanner already
- completely overexposed and wrong line sizes - but image data!)
I am pretty optimistic about beeing able to make it work
soon.

I'm not finished yet, but I would like to start asking questions
about how to integrate the infrared channel of the LS30
correctly into SANE.
Nikons TWAIN interface does the dust removal
before sending the image to the calling programm.
This has the advantage of not requiring the
calling programm to know about the ClearImage feature
and the disadvantage of not beeing able to adjust the amount
of noise detected + removed and the second disadvantage
of beeing slow during the scanning.
I would prefer to save the infrafred channel with the image
and do the dust-removal offline after scanning.
Should I define a new image frame format like SANE_FRAME_RGBI
for RedGreenBlueInfrared ?
The Viewscan software allows 40-bit (10bits*(R+B+G+I)) scans.

This way the actual scanning time should be slower
(during this time we require a lot of user interaction like selecting
the scanning area and some color/brightness adjustments)
and we could do the dust-removal offline in a big batch on
all the image scanned.
I am very interested to make the SANE backend for the LS30
more efficient (in terms of users time) than the
TWAIN interface - which I consider very inefficient.

Some timing data (not very precise as I noted them at home
and recall them here from memory) for the scanning times
using the TWAIN interface:
(Pentium 133,160MB-Ram,Tekram-390F-SCSI)
Full size diapositive at 2700 dpi including ClearImage (sharpen): 4 minutes.
Full size diapositive at 1350 dpi including ClearImage (sharpen): 1:45
I don't recall the time without ClearImage, but it was much faster.
For those who are afraid when reading "160MB-Ram": Scanning time was the same with 32MB
but image processing of 28MB-images is no fun with only 32MB-Ram.
I'll send more precise measurements later...

-- Andreas

-------------------------------------------------------------
Andreas RICK e-mail: rickand@gemse.fr
-------------------------------------------------------------

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com