kopia lustrzana https://gitlab.com/sane-project/website
194 wiersze
7.1 KiB
HTML
194 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: Some snapscan feedback</TITLE>
|
|
<META NAME="Author" CONTENT="Steve Underwood (steveu@coppice.org)">
|
|
<META NAME="Subject" CONTENT="Re: Some snapscan feedback">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
|
|
<H1>Re: Some snapscan feedback</H1>
|
|
<!-- received="Sat May 27 05:32:17 2000" -->
|
|
<!-- isoreceived="20000527123217" -->
|
|
<!-- sent="Sat, 27 May 2000 20:37:47 +0800" -->
|
|
<!-- isosent="20000527123747" -->
|
|
<!-- name="Steve Underwood" -->
|
|
<!-- email="steveu@coppice.org" -->
|
|
<!-- subject="Re: Some snapscan feedback" -->
|
|
<!-- id="392FC19B.6546B37D@coppice.org" -->
|
|
<!-- inreplyto="20000527010845.A6489@syd0128.fujitsu.com.au" -->
|
|
<STRONG>From:</STRONG> Steve Underwood (<A HREF="mailto:steveu@coppice.org?Subject=Re:%20Some%20snapscan%20feedback&In-Reply-To=<392FC19B.6546B37D@coppice.org>"><EM>steveu@coppice.org</EM></A>)<BR>
|
|
<STRONG>Date:</STRONG> Sat May 27 2000 - 05:37:47 PDT
|
|
<P>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0184.html">Michaël van Eeden: "SOLVED: 2 scanners scanning at the same time?"</A>
|
|
<UL>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0182.html">Steve Underwood: "Re: Acer Prisa 620P"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0176.html">Steffen Kluge: "Some snapscan feedback"</A>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#183">[ date ]</A>
|
|
<A HREF="index.html#183">[ thread ]</A>
|
|
<A HREF="subject.html#183">[ subject ]</A>
|
|
<A HREF="author.html#183">[ author ]</A>
|
|
</UL>
|
|
<HR NOSHADE><P>
|
|
<!-- body="start" -->
|
|
<P>
|
|
Hi,
|
|
<BR>
|
|
<P>Steffen Kluge wrote:
|
|
<BR>
|
|
<P><EM>> Hi,
|
|
</EM><BR>
|
|
<EM>> I've been playing a bit with my Acer Prisa 620ST and the new
|
|
</EM><BR>
|
|
<EM>> snapscan backend. This is what I found:
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> [...]
|
|
</EM><BR>
|
|
<EM>> - Steve's new snapscan backend (snapscan-20000514) does a
|
|
</EM><BR>
|
|
<EM>> remarkable job, the transparency unit works well and the three
|
|
</EM><BR>
|
|
<EM>> channels are aligned perfectly without post-processing.
|
|
</EM><BR>
|
|
<P>Good. I have only tried this software with my own Acer 610plus, so feedback about
|
|
<BR>
|
|
any failures on other models (or even on a 610plus) would be appreciated.
|
|
<BR>
|
|
<P><EM>> [a detailed description of some strange jerking behaviour during preview scans
|
|
</EM><BR>
|
|
<EM>> with xsane]
|
|
</EM><BR>
|
|
<P>I get a number of problems using xsane, but I haven't yet investigated if these are
|
|
<BR>
|
|
indeed xsane problems, or driver ones. I am using xsane 0.59.
|
|
<BR>
|
|
-I've never had pauses during preview scans, but I get complete lock ups - I can
|
|
<BR>
|
|
leave the machine for a while and it never seems to restart. These usually seem to
|
|
<BR>
|
|
occur if I wave the mouse around, and provoke some activity in the xsane preview
|
|
<BR>
|
|
window during scanning. If I don't touch the machine all is usually well.
|
|
<BR>
|
|
- If I preview in B/W and then try again in colour the preview goes crazy. If I stop
|
|
<BR>
|
|
and restart xsane, and select colour preview first, it previews just fine.
|
|
<BR>
|
|
- If I abort a preview scan in mid scan and then zoom the preview window it goes
|
|
<BR>
|
|
crazy.
|
|
<BR>
|
|
I haven't really played with xscanimage. xsane is a superior product, even if it
|
|
<BR>
|
|
currently has some some. I feel it is to be debugged, rather than avoided, so I have
|
|
<BR>
|
|
only worked with xsane.
|
|
<BR>
|
|
<P><EM>> 0.59, both versions behave this way. I also recompiled sane
|
|
</EM><BR>
|
|
<EM>> and xsane with no optimisations (I thought that might be a
|
|
</EM><BR>
|
|
<EM>> good idea since I'm using an Athlon), but it made no
|
|
</EM><BR>
|
|
<EM>> difference.
|
|
</EM><BR>
|
|
<P>I'm using a 700MHz Athlon with 256MB RAM. I think the amount of free RAM is more
|
|
<BR>
|
|
likely to be a significant factor between different machines than either speed or
|
|
<BR>
|
|
processor type - I could be wrong, of course.
|
|
<BR>
|
|
<P><EM>> - I can't for the heck of it scan at resolutions higher than
|
|
</EM><BR>
|
|
<EM>> 600dpi, although the scanner supports up to 19200dpi. The
|
|
</EM><BR>
|
|
<EM>> program (scanimage, xscanimage or xsane) just freezes (enters
|
|
</EM><BR>
|
|
<EM>> an endless loop) in function measure_transfer_rate. I can
|
|
</EM><BR>
|
|
<EM>> follow the loop in the debugger but I don't understand the
|
|
</EM><BR>
|
|
<EM>> program logic so I can't say what's going wrong. I believe
|
|
</EM><BR>
|
|
<EM>> (but am not sure) that I could use higher resolutions with
|
|
</EM><BR>
|
|
<EM>> previous versions of the backend.
|
|
</EM><BR>
|
|
<P>I can reproduce this effect, but I have yet to investigate the cause. I don't get it
|
|
<BR>
|
|
as a clean repeatable effect, the way you describe it, though. Only sometimes, and
|
|
<BR>
|
|
seemingly only at the higher resolutions, does this happen. I think the logic for
|
|
<BR>
|
|
sizing and handling the buffer for merging the chroma offsets falls over during the
|
|
<BR>
|
|
small speed test operation, for some reason. The speed test is not performed over an
|
|
<BR>
|
|
exact number of scan lines (I think it uses a nice round number of bytes, rather
|
|
<BR>
|
|
than a whole number of scan lines). I think this is the cause of the problem, but I
|
|
<BR>
|
|
should get some time to investigate next week.
|
|
<BR>
|
|
<P><EM>> - I'm doing all this with sane-1.0.2, kernel-2.2.14, sg-3.0.15,
|
|
</EM><BR>
|
|
<EM>> and the host adapter/scanner look like this:
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> scsi0 : Tekram DC395U/UW/F DC315/U V1.10, 1999/07/19
|
|
</EM><BR>
|
|
<EM>> scsi : 1 host.
|
|
</EM><BR>
|
|
<EM>> Vendor: Color Model: FlatbedScanner_9 Rev: 0117
|
|
</EM><BR>
|
|
<EM>> Type: Scanner ANSI SCSI revision: 02
|
|
</EM><BR>
|
|
<EM>> Detected scsi generic sg0 at scsi0, channel 0, id 2, lun 0, type 6
|
|
</EM><BR>
|
|
<P>I'm using RH 6.2 with the latest kernel updates, and an Adaptec 2940. I think this
|
|
<BR>
|
|
is a fairly stable driver, though I beleive it has seen some recent changes. It
|
|
<BR>
|
|
seems to be working OK for me.
|
|
<BR>
|
|
<P>Steve
|
|
<BR>
|
|
<P><P><P><PRE>
|
|
--
|
|
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:%20Some%20snapscan%20feedback&In-Reply-To=<392FC19B.6546B37D@coppice.org>">majordomo@mostang.com</A>
|
|
</PRE>
|
|
<P><!-- body="end" -->
|
|
<HR NOSHADE>
|
|
<UL>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0184.html">Michaël van Eeden: "SOLVED: 2 scanners scanning at the same time?"</A>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0182.html">Steve Underwood: "Re: Acer Prisa 620P"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0176.html">Steffen Kluge: "Some snapscan feedback"</A>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#183">[ date ]</A>
|
|
<A HREF="index.html#183">[ thread ]</A>
|
|
<A HREF="subject.html#183">[ subject ]</A>
|
|
<A HREF="author.html#183">[ 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>Sat May 27 2000 - 05:34:47 PDT</EM>
|
|
</EM>
|
|
</SMALL>
|
|
</BODY>
|
|
</HTML>
|