Was this problem with the wrong colors already present in the 0.5
version of the backend, that was part of sane-1.00 ? The algorithm
how the the data that is processed, that is transferred from the device,
has completely changed between this version and the pre-0.6 release.
> have partially diagnosed the problem as occurring at any resolution with
> certain y sizes. For example, it always works fine if the y size is one
> of:
>
> 1843,1872,1824,1830,1829,1913,1828,1827,1837
>
> and always fails if one of:
>
> 1880,1825,1814,1836,1858
>
> Any thought or tests which I might conduct to further diagnose
> would be of great help.
One thing you can do is to send me two traces (not too big, if possible), one
trace of a succesful scan, and one of a scan with wrong colors, with
'option dump 2' set in the microtek2.conf file and the environment variable
SANE_DEBUG_MICROTEK2 set to 30.
Bernd
-- Bernd Schroeder Email: mailto:bernd@aquila.muc.de PGP public key available: mailto:pgp@aquila.muc.de | Subject: send key
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com