kopia lustrzana https://gitlab.com/sane-project/website
241 wiersze
7.1 KiB
HTML
241 wiersze
7.1 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
||
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
||
<HTML>
|
||
<HEAD>
|
||
<TITLE>sane-devel: Re: [snapscan] Core testing group</TITLE>
|
||
<META NAME="Author" CONTENT="Sebastien Sable (sebastien.sable@gmx.net)">
|
||
<META NAME="Subject" CONTENT="Re: [snapscan] Core testing group">
|
||
</HEAD>
|
||
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
|
||
<H1>Re: [snapscan] Core testing group</H1>
|
||
<!-- received="Fri Nov 3 10:46:28 2000" -->
|
||
<!-- isoreceived="20001103184628" -->
|
||
<!-- sent="03 Nov 2000 19:39:30 +0100" -->
|
||
<!-- isosent="20001103183930" -->
|
||
<!-- name="Sebastien Sable" -->
|
||
<!-- email="sebastien.sable@gmx.net" -->
|
||
<!-- subject="Re: [snapscan] Core testing group" -->
|
||
<!-- id="8766m4lx25.fsf@gmx.net" -->
|
||
<!-- inreplyto="Fri, 03 Nov 2000 23:25:31 +0800"" -->
|
||
<STRONG>From:</STRONG> Sebastien Sable (<A HREF="mailto:sebastien.sable@gmx.net?Subject=Re:%20[snapscan]%20Core%20testing%20group&In-Reply-To=<8766m4lx25.fsf@gmx.net>"><EM>sebastien.sable@gmx.net</EM></A>)<BR>
|
||
<STRONG>Date:</STRONG> Fri Nov 03 2000 - 10:39:30 PST
|
||
<P>
|
||
<!-- next="start" -->
|
||
<LI><STRONG>Next message:</STRONG> <A HREF="0043.html">Timothy Little: "Re: [snapscan] Core testing group"</A>
|
||
<UL>
|
||
<LI><STRONG>Previous message:</STRONG> <A HREF="0041.html">Paul Floyd: "Test procedures"</A>
|
||
<!-- nextthread="start" -->
|
||
<LI><STRONG>Next in thread:</STRONG> <A HREF="0043.html">Timothy Little: "Re: [snapscan] Core testing group"</A>
|
||
<LI><STRONG>Reply:</STRONG> <A HREF="0043.html">Timothy Little: "Re: [snapscan] Core testing group"</A>
|
||
<LI><STRONG>Reply:</STRONG> <A HREF="0085.html">Russ Burdick: "Re: [snapscan] Core testing group"</A>
|
||
<!-- reply="end" -->
|
||
<LI><STRONG>Messages sorted by:</STRONG>
|
||
<A HREF="date.html#42">[ date ]</A>
|
||
<A HREF="index.html#42">[ thread ]</A>
|
||
<A HREF="subject.html#42">[ subject ]</A>
|
||
<A HREF="author.html#42">[ author ]</A>
|
||
</UL>
|
||
<HR NOSHADE><P>
|
||
<!-- body="start" -->
|
||
<P>
|
||
Steve Underwood <<A HREF="mailto:steveu@coppice.org?Subject=Re:%20[snapscan]%20Core%20testing%20group&In-Reply-To=<8766m4lx25.fsf@gmx.net>">steveu@coppice.org</A>> writes:
|
||
<BR>
|
||
<P><EM>> It might be better to do this now. It might encourage people to provide the
|
||
</EM><BR>
|
||
<EM>> information to fill in the holes.
|
||
</EM><BR>
|
||
<P>All right, I will post it here regularly. I put the current version at
|
||
<BR>
|
||
the end of this mail.
|
||
<BR>
|
||
<P><P><EM>> Most of the 300dpi scanner have an actual optiocal resoltionof 300dpi in
|
||
</EM><BR>
|
||
<EM>> width and 600dpi in length. The 600dpi scanners are actually 600dpi in
|
||
</EM><BR>
|
||
<EM>> width x 1200 dpi in length. That asymmetric resolution is common to every
|
||
</EM><BR>
|
||
<EM>> model I know of. Running a 600x1200 scanner as 1200x1200 is quite
|
||
</EM><BR>
|
||
<EM>> meaningful. Beyong that its mostly blur!
|
||
</EM><BR>
|
||
<P>I saw this when I tried 600dpi with my model, the picture is deformed
|
||
<BR>
|
||
(2x high - 1x width). My scanner must be a 300 x 600.
|
||
<BR>
|
||
I already find 300dpi pictures take a lot of memory (well some may
|
||
<BR>
|
||
need more than that).
|
||
<BR>
|
||
<P><EM>> Although the bits per colour varies, the current snapscan software always
|
||
</EM><BR>
|
||
<EM>> reads 8 bits per pixel for full colour scans. The rest are absolbed in
|
||
</EM><BR>
|
||
<EM>> gamma correction. The actual scanning process is almost oblivious to the
|
||
</EM><BR>
|
||
<EM>> number of bits.
|
||
</EM><BR>
|
||
<P>I have this in snapscan.c.
|
||
<BR>
|
||
<P> case SNAPSCAN300:
|
||
<BR>
|
||
pd->depths = depths8;
|
||
<BR>
|
||
break;
|
||
<BR>
|
||
<P> case PRISA620S:
|
||
<BR>
|
||
pd->depths = depths12;
|
||
<BR>
|
||
break;
|
||
<BR>
|
||
<P> case VUEGO610S: /* SJU added */
|
||
<BR>
|
||
default:
|
||
<BR>
|
||
pd->depths = depths10;
|
||
<BR>
|
||
break;
|
||
<BR>
|
||
<P>Is it just not used (I would like it, that would make things easier)?
|
||
<BR>
|
||
<P>By the way, there are many changes that have been made for PRISA620S
|
||
<BR>
|
||
and VUEGO610S (they return SANE_UNSUPPORTED for example in inquiry and
|
||
<BR>
|
||
a few others things). Can we delete that (I think so, but I don't want
|
||
<BR>
|
||
to break everything)?
|
||
<BR>
|
||
<P>What do you think of only keeping 3 kinds of models (SNAPSCAN300 -
|
||
<BR>
|
||
SNAPSCAN600 - SNAPSCAN600P)? If the depth stuff is not used, I can
|
||
<BR>
|
||
make the change in 5 minutes and I'm rather sure everything will work
|
||
<BR>
|
||
the same than before. But before doing that I'd like to be sure that
|
||
<BR>
|
||
it is usefull and won't make things harder in the future. I will
|
||
<BR>
|
||
probably change the backend to automatically detect USB models too and
|
||
<BR>
|
||
so suppress the #define USB_STUFF.
|
||
<BR>
|
||
<P><P>The current feedback for snapscan scanners with snapscan-01112000:
|
||
<BR>
|
||
<P>Acer 300f
|
||
<BR>
|
||
ACERSCAN_A4____1
|
||
<BR>
|
||
Works
|
||
<BR>
|
||
300dpi
|
||
<BR>
|
||
SNAPSCAN300
|
||
<BR>
|
||
<P>AGFA Snapscan 310S
|
||
<BR>
|
||
??
|
||
<BR>
|
||
Works
|
||
<BR>
|
||
300dpi
|
||
<BR>
|
||
SNAPSCAN300
|
||
<BR>
|
||
<P>AcerScan (Prisa) 610ST
|
||
<BR>
|
||
FlatbedScanner_4
|
||
<BR>
|
||
Works
|
||
<BR>
|
||
600dpi
|
||
<BR>
|
||
SNAPSCAN600
|
||
<BR>
|
||
<P>Acer 610+
|
||
<BR>
|
||
??
|
||
<BR>
|
||
??
|
||
<BR>
|
||
??
|
||
<BR>
|
||
SNAPSCAN600P
|
||
<BR>
|
||
<P>Acer PrisaScan 640S
|
||
<BR>
|
||
FlatbedScanner18
|
||
<BR>
|
||
??
|
||
<BR>
|
||
??
|
||
<BR>
|
||
SNAPSCAN600
|
||
<BR>
|
||
<P>Acer 640BU
|
||
<BR>
|
||
FlatbedScanner20
|
||
<BR>
|
||
stops halfway (correction proposed waiting for feedback)
|
||
<BR>
|
||
19200 dpi I think.
|
||
<BR>
|
||
14bits
|
||
<BR>
|
||
<P>Agfa 1212U
|
||
<BR>
|
||
SNAPSCAN 1212U
|
||
<BR>
|
||
Works (to be confirmed)
|
||
<BR>
|
||
600dpi
|
||
<BR>
|
||
SNAPSCAN600P
|
||
<BR>
|
||
<P>Agfa Snapscan 1236s
|
||
<BR>
|
||
SNAPSCAN 1236
|
||
<BR>
|
||
Works (up to 300, problem at 600)
|
||
<BR>
|
||
600dpi
|
||
<BR>
|
||
SNAPSCAN600
|
||
<BR>
|
||
<P><PRE>
|
||
--
|
||
S<EFBFBD>bastien Sabl<62>
|
||
<A HREF="mailto:sebastien.sable@gmx.net?Subject=Re:%20[snapscan]%20Core%20testing%20group&In-Reply-To=<8766m4lx25.fsf@gmx.net>">sebastien.sable@gmx.net</A>
|
||
<P>--
|
||
Source code, list archive, and docs: <A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
|
||
To unsubscribe: echo unsubscribe sane-devel | mail <A HREF="mailto:majordomo@mostang.com?Subject=Re:%20[snapscan]%20Core%20testing%20group&In-Reply-To=<8766m4lx25.fsf@gmx.net>">majordomo@mostang.com</A>
|
||
</PRE>
|
||
<P><!-- body="end" -->
|
||
<HR NOSHADE>
|
||
<UL>
|
||
<!-- next="start" -->
|
||
<LI><STRONG>Next message:</STRONG> <A HREF="0043.html">Timothy Little: "Re: [snapscan] Core testing group"</A>
|
||
<LI><STRONG>Previous message:</STRONG> <A HREF="0041.html">Paul Floyd: "Test procedures"</A>
|
||
<!-- nextthread="start" -->
|
||
<LI><STRONG>Next in thread:</STRONG> <A HREF="0043.html">Timothy Little: "Re: [snapscan] Core testing group"</A>
|
||
<LI><STRONG>Reply:</STRONG> <A HREF="0043.html">Timothy Little: "Re: [snapscan] Core testing group"</A>
|
||
<LI><STRONG>Reply:</STRONG> <A HREF="0085.html">Russ Burdick: "Re: [snapscan] Core testing group"</A>
|
||
<!-- reply="end" -->
|
||
<LI><STRONG>Messages sorted by:</STRONG>
|
||
<A HREF="date.html#42">[ date ]</A>
|
||
<A HREF="index.html#42">[ thread ]</A>
|
||
<A HREF="subject.html#42">[ subject ]</A>
|
||
<A HREF="author.html#42">[ author ]</A>
|
||
</UL>
|
||
<!-- trailer="footer" -->
|
||
<HR NOSHADE>
|
||
<P>
|
||
<SMALL>
|
||
<EM>
|
||
This archive was generated by <A HREF="http://www.hypermail.org/">hypermail 2b29</A>
|
||
: <EM>Fri Nov 03 2000 - 10:47:15 PST</EM>
|
||
</EM>
|
||
</SMALL>
|
||
</BODY>
|
||
</HTML>
|