Re: problems with snapscan and scanimage

=?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= (mikko@securitydynamics.com)
Mon, 11 May 1998 20:46:14 +0200 (CEST)

On Mon, 11 May 1998, KH Jeron wrote:

> i am running linux 2.0.32
> find-scanner output looks good.
> find-scanner: found scanner "AGFA SNAPSCAN 310 1.20" at device
> /dev/scanner
> find-scanner: found scanner "AGFA SNAPSCAN 310 1.20" at device /dev/sg2
> but scanimage doesnt work with sane0.72 agfa snapscan 310.
> i tried the following like the README says :
> test:/home/kheinz/sane-0.72/frontend # ./scanimage -d
> snapscan:/dev/scanner >t.pnm
> scanimage: scanimage.c:813: scan_it: Assertion `parm.depth == 8' failed.
>
> IOT trap/Abort
> test:/home/kheinz/sane-0.72/frontend # scanimage: stopping scanner...
>
> please help me
>

Using the xscanimage as a gimp plugin runs into the same problem. The
snapscan backend produces 10-bits per colour (*), though as far as I
can see no frontends really support it (e.g. output files are always
8-bit pnm files, or some other one-byte-per-component data).

The following Q&D workaround makes it work with gimp, so I guess
scanimage should be happy too:

--- ../../sane-pre0.72.org/backend/snapscan.c Fri Apr 3 11:14:09 1998
+++ snapscan.c Sun Apr 5 20:47:10 1998
@@ -2594,7 +2594,7 @@
for black and white */
p->depth = pss->pdev->depths[mode];

- if (pss->preview && p->depth > 8)
+ if (/* pss->preview && */ p->depth > 8)
p->depth = 8;

switch (mode)

This may be diffed from a slightly hacked version of snapscan.c, but
you get the point -- force depth to never be more than eight bits...

Hope this helps,
/Mikko

(*) After a closer look I'd say it does not produce 10 bits -- it just
*claims* to :-)

Mikko Tyo"la"ja"rvi________________________________mikko@securitydynamics.com
SecurityDynamics

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