kopia lustrzana https://gitlab.com/sane-project/website
260 wiersze
8.9 KiB
HTML
260 wiersze
8.9 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: problems with 1.0.3 and color scanning</TITLE>
|
|
<META NAME="Author" CONTENT="Lawrence Glaister (lg@jfm.bc.ca)">
|
|
<META NAME="Subject" CONTENT="Re: problems with 1.0.3 and color scanning">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
|
|
<H1>Re: problems with 1.0.3 and color scanning</H1>
|
|
<!-- received="Thu Sep 21 08:10:56 2000" -->
|
|
<!-- isoreceived="20000921151056" -->
|
|
<!-- sent="Thu, 21 Sep 2000 08:16:24 -0700" -->
|
|
<!-- isosent="20000921151624" -->
|
|
<!-- name="Lawrence Glaister" -->
|
|
<!-- email="lg@jfm.bc.ca" -->
|
|
<!-- subject="Re: problems with 1.0.3 and color scanning" -->
|
|
<!-- id="006801c023de$e7cc1f40$bf0aa8c0@dufusiii" -->
|
|
<!-- inreplyto="39CA1FAF.D5557DB4@coppice.org" -->
|
|
<STRONG>From:</STRONG> Lawrence Glaister (<A HREF="mailto:lg@jfm.bc.ca?Subject=Re:%20problems%20with%201.0.3%20and%20color%20scanning&In-Reply-To=<006801c023de$e7cc1f40$bf0aa8c0@dufusiii>"><EM>lg@jfm.bc.ca</EM></A>)<BR>
|
|
<STRONG>Date:</STRONG> Thu Sep 21 2000 - 08:16:24 PDT
|
|
<P>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0216.html">Jonathan Buzzard: "Re: Future-proofing SANE."</A>
|
|
<UL>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0214.html">Steve Underwood: "Re: problems with 1.0.3 and color scanning"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0214.html">Steve Underwood: "Re: problems with 1.0.3 and color scanning"</A>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#215">[ date ]</A>
|
|
<A HREF="index.html#215">[ thread ]</A>
|
|
<A HREF="subject.html#215">[ subject ]</A>
|
|
<A HREF="author.html#215">[ author ]</A>
|
|
</UL>
|
|
<HR NOSHADE><P>
|
|
<!-- body="start" -->
|
|
<P>
|
|
Hi Steve
|
|
<BR>
|
|
I have a couple of other ideas on the RGBRouter problem.... as I understand
|
|
<BR>
|
|
it, the router was designed to perform the data unpacking from scanner
|
|
<BR>
|
|
buffer format to the internal RGB sane buffer format while at the same time
|
|
<BR>
|
|
accommodating any color offset shifts needed (spatially aligning RGB). The
|
|
<BR>
|
|
new code uses offsets reported by the scanner... It could be possible that
|
|
<BR>
|
|
the snapscan 1212u is reporting bogus offsets that are getting the router
|
|
<BR>
|
|
totally confused... I will try and figure out how to ignore the offsets from
|
|
<BR>
|
|
the scanner and see if that makes things better. If you could describe how
|
|
<BR>
|
|
the elements of the rgbrouter structure are supposed to be used, it would
|
|
<BR>
|
|
help me decipher what is going on.
|
|
<BR>
|
|
An update on my earlier comment... the scanning of small color image at
|
|
<BR>
|
|
50dpi
|
|
<BR>
|
|
doesn't really work.... it doesn't hang xscanimage but the generated file is
|
|
<BR>
|
|
missing about 10-20% of its bytes and fails to open in gimp with an
|
|
<BR>
|
|
premature EOF message.
|
|
<BR>
|
|
I feel this is directly related to the rgbrouter problems. I'm getting quite
|
|
<BR>
|
|
an education in the sane code... its not one of the easier pieces of code to
|
|
<BR>
|
|
get ones mind wrapped around with all the nested virtual functions.
|
|
<BR>
|
|
<P>Thankyou for your comments... I'll post some dumps of the router related
|
|
<BR>
|
|
stuff later today.
|
|
<BR>
|
|
<P>=======================================================
|
|
<BR>
|
|
Lawrence Glaister VE7IT email: <A HREF="mailto:lg@jfm.bc.ca?Subject=Re:%20problems%20with%201.0.3%20and%20color%20scanning&In-Reply-To=<006801c023de$e7cc1f40$bf0aa8c0@dufusiii>">lg@jfm.bc.ca</A>
|
|
<BR>
|
|
1462 Madrona Drive <A HREF="http://jfm.bc.ca">http://jfm.bc.ca</A>
|
|
<BR>
|
|
Nanoose Bay BC Canada
|
|
<BR>
|
|
V9P 9C9
|
|
<BR>
|
|
=======================================================
|
|
<BR>
|
|
----- Original Message -----
|
|
<BR>
|
|
From: Steve Underwood <<A HREF="mailto:steveu@coppice.org?Subject=Re:%20problems%20with%201.0.3%20and%20color%20scanning&In-Reply-To=<006801c023de$e7cc1f40$bf0aa8c0@dufusiii>">steveu@coppice.org</A>>
|
|
<BR>
|
|
To: <<A HREF="mailto:sane-devel@mostang.com?Subject=Re:%20problems%20with%201.0.3%20and%20color%20scanning&In-Reply-To=<006801c023de$e7cc1f40$bf0aa8c0@dufusiii>">sane-devel@mostang.com</A>>
|
|
<BR>
|
|
Sent: Thursday, September 21, 2000 7:48 AM
|
|
<BR>
|
|
Subject: Re: problems with 1.0.3 and color scanning
|
|
<BR>
|
|
<P><P><EM>> Lawrence Glaister wrote:
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> > I am trying to get sane 1.0.3 working with my snapscan 1212u usb
|
|
</EM><BR>
|
|
scanner.
|
|
<BR>
|
|
<EM>> > The scanner works properly under 1.0.1 but fails in various ways under
|
|
</EM><BR>
|
|
1.0.2
|
|
<BR>
|
|
<EM>> > and 1.0.3 and the cvs code as of sept 19. I have narrowed the problem
|
|
</EM><BR>
|
|
down
|
|
<BR>
|
|
<EM>> > to the snapscan-sources.c RGBRouter_remaining() function.
|
|
</EM><BR>
|
|
<EM>> > - grayscale scanning works fine
|
|
</EM><BR>
|
|
<EM>> > - color scanning a small image at 50dpi works
|
|
</EM><BR>
|
|
<EM>> > - color scanning same image at 75dpi breaks xscanimage
|
|
</EM><BR>
|
|
<EM>> > by broken, I mean that xscanimage enters into an infinite loop using
|
|
</EM><BR>
|
|
100%
|
|
<BR>
|
|
<EM>> > cpu time.
|
|
</EM><BR>
|
|
<EM>> > the cause for this appears to be a negative result returned by
|
|
</EM><BR>
|
|
<EM>> > RGBRouter_remaining(). There are two possible return values calulated in
|
|
</EM><BR>
|
|
<EM>> > RGBRouter_remaining() and one of them always looks like the correct
|
|
</EM><BR>
|
|
<EM>> > answer... the problem comes in that the conditional used doesn't seem to
|
|
</EM><BR>
|
|
<EM>> > work in all cases (sometimes the wrong value is returned and when this
|
|
</EM><BR>
|
|
<EM>> > is -ve, all hell breaks loose.). I have been getting a headache trying
|
|
</EM><BR>
|
|
to
|
|
<BR>
|
|
<EM>> > decipher how the new RGBRouter code is supposed to work... could the
|
|
</EM><BR>
|
|
author
|
|
<BR>
|
|
<EM>> > (pere) or someone have a look at the function and see if they see any
|
|
</EM><BR>
|
|
<EM>> > obvious errors. I have not seen a lot of postings about 1.0.3, so the
|
|
</EM><BR>
|
|
<EM>> > problem may be related only to the snapscan backend with a usb patch
|
|
</EM><BR>
|
|
applied
|
|
<BR>
|
|
<EM>> > to it.
|
|
</EM><BR>
|
|
<EM>> > I can supply some rather detailed dumps of the good scans and bad scans
|
|
</EM><BR>
|
|
as I
|
|
<BR>
|
|
<EM>> > have added a lot of dbg calls into the snapscan code.
|
|
</EM><BR>
|
|
<EM>> >
|
|
</EM><BR>
|
|
<EM>> > Are there any snapscan scanners usb or scsi out there working with sane
|
|
</EM><BR>
|
|
<EM>> > 1.0.3???
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Excellent. This look likes a really solid lead for what goes wrong. I will
|
|
</EM><BR>
|
|
try
|
|
<BR>
|
|
<EM>> to look at the RGBRouter code in the next couple of days, and see if I can
|
|
</EM><BR>
|
|
spot
|
|
<BR>
|
|
<EM>> what goes amiss. Actually, I thought the current RGBRouter code was fairly
|
|
</EM><BR>
|
|
<EM>> straightforward, but maybe that's only to my own twisted mind! The
|
|
</EM><BR>
|
|
existing
|
|
<BR>
|
|
<EM>> code certainly does work for some scanners. It works just fine for my Acer
|
|
</EM><BR>
|
|
<EM>> 610+, and a few other people have reported success with some scanners.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Lets hope this is the root cause of several not quite identical problems
|
|
</EM><BR>
|
|
people
|
|
<BR>
|
|
<EM>> have reported.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> If you have any debug logs, or other useful info please mail it to me. my
|
|
</EM><BR>
|
|
code
|
|
<BR>
|
|
<EM>> hasn't given me any trouble so far, so a log of an actual failure would be
|
|
</EM><BR>
|
|
<EM>> helpful.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Steve
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> --
|
|
</EM><BR>
|
|
<EM>> Source code, list archive, and docs: <A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
|
|
</EM><BR>
|
|
<EM>> To unsubscribe: echo unsubscribe sane-devel | mail <A HREF="mailto:majordomo@mostang.com?Subject=Re:%20problems%20with%201.0.3%20and%20color%20scanning&In-Reply-To=<006801c023de$e7cc1f40$bf0aa8c0@dufusiii>">majordomo@mostang.com</A>
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<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:%20problems%20with%201.0.3%20and%20color%20scanning&In-Reply-To=<006801c023de$e7cc1f40$bf0aa8c0@dufusiii>">majordomo@mostang.com</A>
|
|
</PRE>
|
|
<P><!-- body="end" -->
|
|
<HR NOSHADE>
|
|
<UL>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0216.html">Jonathan Buzzard: "Re: Future-proofing SANE."</A>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0214.html">Steve Underwood: "Re: problems with 1.0.3 and color scanning"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0214.html">Steve Underwood: "Re: problems with 1.0.3 and color scanning"</A>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#215">[ date ]</A>
|
|
<A HREF="index.html#215">[ thread ]</A>
|
|
<A HREF="subject.html#215">[ subject ]</A>
|
|
<A HREF="author.html#215">[ 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 Sep 21 2000 - 08:11:24 PDT</EM>
|
|
</EM>
|
|
</SMALL>
|
|
</BODY>
|
|
</HTML>
|