Hi,
I am not quite sure if I can help you. I dont know the Mustek scanners.
But I know the phenomenon from another scanner. The problem is that the
data
the scanner generates is not picked up fast enough by the application
(or the
SCSI-driver). To prevent a buffer overrun, the scanner stops until the
data
has been picked up. Then it has to continue the scan at the scanline
where
it stopped. To get sufficient scan speed, it moves a little bit backward
and then restarts scanning in the correct direction.
You may experience that the moving forward/backward is not so bad in
lineart
(b/w) mode (if it exists) because the amount of data to transmit is much
less.
Specifying an option like --speed Fastest will make it even more worse.
I am quite sure you have tried the option --speed Slowest. But maybe
this
would be in fact faster.
Unnecessary to mention that the outputfile should not be written over a
slow
network.
--Peter
-- Peter Kirchgessner WWW: http://www.kirchgessner.net e-mail: peter@kirchgessner.net
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com