sane-project-website/old-archive/2000-11/0037.html

155 wiersze
6.0 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="Thu Nov 2 19:58:29 2000" -->
<!-- isoreceived="20001103035829" -->
<!-- sent="03 Nov 2000 04:59:14 +0100" -->
<!-- isosent="20001103035914" -->
<!-- name="Sebastien Sable" -->
<!-- email="sebastien.sable@gmx.net" -->
<!-- subject="Re: [snapscan] Core testing group" -->
<!-- id="87zojh4sfh.fsf@gmx.net" -->
<!-- inreplyto="Wed, 01 Nov 2000 11:08:47 -0500&quot;" -->
<STRONG>From:</STRONG> Sebastien Sable (<A HREF="mailto:sebastien.sable@gmx.net?Subject=Re:%20[snapscan]%20Core%20testing%20group&In-Reply-To=&lt;87zojh4sfh.fsf@gmx.net&gt;"><EM>sebastien.sable@gmx.net</EM></A>)<BR>
<STRONG>Date:</STRONG> Thu Nov 02 2000 - 19:59:14 PST
<P>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0038.html">Dunphy Richard-rdunph01: "RE: Problems with Microtek E3 on Adaptec 1502 SCSI on SuSE Linux."</A>
<UL>
<LI><STRONG>Previous message:</STRONG> <A HREF="0036.html">Sebastien Sable: "Re: [snapscan] Core testing group"</A>
<!-- nextthread="start" -->
<LI><STRONG>Next in thread:</STRONG> <A HREF="0039.html">Steve Underwood: "Re: [snapscan] Core testing group"</A>
<LI><STRONG>Reply:</STRONG> <A HREF="0039.html">Steve Underwood: "Re: [snapscan] Core testing group"</A>
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#37">[ date ]</A>
<A HREF="index.html#37">[ thread ]</A>
<A HREF="subject.html#37">[ subject ]</A>
<A HREF="author.html#37">[ author ]</A>
</UL>
<HR NOSHADE><P>
<!-- body="start" -->
<P>
<A HREF="mailto:cbagwell@sprynet.com?Subject=Re:%20[snapscan]%20Core%20testing%20group&In-Reply-To=&lt;87zojh4sfh.fsf@gmx.net&gt;">cbagwell@sprynet.com</A> writes:
<BR>
<P><EM>&gt; This information is very useful. Do you think we should include it
</EM><BR>
<EM>&gt; in the snapscan.desc file somehow?
</EM><BR>
<P>I will put it on the web page when it will be ~complete. Some people
<BR>
reported other scanners (by mail to me not to the mailing-list). I
<BR>
don't have a report for all the models, but at least those that have
<BR>
been reported seem to work.
<BR>
<P><EM>&gt; Acer 640BU (Not labeled as a Prisa for some reason!)
</EM><BR>
<EM>&gt; FlatbedScanner20
</EM><BR>
<EM>&gt; Works under 1.0.1, stops halfway through with 1.0.3. Probably fixed
</EM><BR>
<EM>&gt; by Sebastien's patches.
</EM><BR>
<P>Probably not ;)
<BR>
<P>It's a FlatbedScanner20 so from snapscan.h it uses a PRISA620S. I have
<BR>
not made changes for this model, you have to look for ACER300F in:
<BR>
* snapscan-source.c (if it blocks (stop halfway?)) &lt;--
<BR>
* and/or snapscan-scsi.c (if the picture is full of noise)
<BR>
* and/or snapscan.c (if the picture has a puzzle problem : many blocks
<BR>
&nbsp;&nbsp;of pixels (m<>lang<6E>s?) badly sorted)
<BR>
<P>The change is quite obvious (there is a big test for many models -
<BR>
ugly but it works (I'd like to change it though) - just add your
<BR>
model).
<BR>
<P><EM>&gt; Its described as 48-bits on the box but I downloaded the specs for
</EM><BR>
<EM>&gt; the scanner chip it uses and it says something about 14 bits only.
</EM><BR>
<EM>&gt; I'll get back to you on this stuff. It may be more useful to
</EM><BR>
<EM>&gt; describe the scanners dpi not by model names but the actual optical
</EM><BR>
<EM>&gt; chip used.
</EM><BR>
<P>I though there were only 300dpi and 600dpi. Are there really
<BR>
resolutions higher than 600dpi or is it just some kind of
<BR>
interpolation?
<BR>
<P>I was pretty sure that I could group all scanners in 3 categories to
<BR>
simplify the code, and then I realized, that on top of resolution, bus
<BR>
and protocol differences, there was a difference between bits per
<BR>
color.
<BR>
<P>USB/SCSI difference can be easily detected (I looked in epson backend
<BR>
to see how they did and we can adapt it - they just put usb in front
<BR>
of /dev/usbscanner in their conf file and detect that).
<BR>
<P>It would be great if the bits_per_color could be obtained by an
<BR>
inquiry, that would not break my pseudo-classification (ok, that's not
<BR>
really a good scientific way of proceeding, I'm modifying facts so
<BR>
that they fit in my theory, but that would be so much pratical).
<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=&lt;87zojh4sfh.fsf@gmx.net&gt;">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=&lt;87zojh4sfh.fsf@gmx.net&gt;">majordomo@mostang.com</A>
</PRE>
<P><!-- body="end" -->
<HR NOSHADE>
<UL>
<!-- next="start" -->
<LI><STRONG>Next message:</STRONG> <A HREF="0038.html">Dunphy Richard-rdunph01: "RE: Problems with Microtek E3 on Adaptec 1502 SCSI on SuSE Linux."</A>
<LI><STRONG>Previous message:</STRONG> <A HREF="0036.html">Sebastien Sable: "Re: [snapscan] Core testing group"</A>
<!-- nextthread="start" -->
<LI><STRONG>Next in thread:</STRONG> <A HREF="0039.html">Steve Underwood: "Re: [snapscan] Core testing group"</A>
<LI><STRONG>Reply:</STRONG> <A HREF="0039.html">Steve Underwood: "Re: [snapscan] Core testing group"</A>
<!-- reply="end" -->
<LI><STRONG>Messages sorted by:</STRONG>
<A HREF="date.html#37">[ date ]</A>
<A HREF="index.html#37">[ thread ]</A>
<A HREF="subject.html#37">[ subject ]</A>
<A HREF="author.html#37">[ 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>Thu Nov 02 2000 - 19:59:25 PST</EM>
</EM>
</SMALL>
</BODY>
</HTML>