kopia lustrzana https://gitlab.com/sane-project/website
141 wiersze
7.8 KiB
HTML
141 wiersze
7.8 KiB
HTML
|
<!-- received="Thu Mar 25 18:15:49 1999 PST" -->
|
|||
|
|
<!-- sent="Thu, 25 Mar 1999 18:15:16 -0800" -->
|
|||
|
|
<!-- name="Dean Martin Townsley" -->
|
|||
|
|
<!-- email="townsley@physics.ucsb.edu" -->
|
|||
|
|
<!-- subject="Re: Calibration problem on UMAX Astra 1220S" -->
|
|||
|
|
<!-- id="199903260214.SAA05950@spacecase.physics.ucsb.edu" -->
|
|||
|
|
<!-- inreplyto="36F78450.BDA2BE00@wolfsburg.de" -->
|
|||
|
|
<title>sane-devel: Re: Calibration problem on UMAX Astra 1220S</title>
|
|||
|
|
<h1>Re: Calibration problem on UMAX Astra 1220S</h1>
|
|||
|
|
<b>Dean Martin Townsley</b> (<a href="mailto:townsley@physics.ucsb.edu"><i>townsley@physics.ucsb.edu</i></a>)<br>
|
|||
|
|
<i>Thu, 25 Mar 1999 18:15:16 -0800</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#232">[ date ]</a><a href="index.html#232">[ thread ]</a><a href="subject.html#232">[ subject ]</a><a href="author.html#232">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0233.html">Henning Meier-Geinitz: "Re: xsane-0.18 available"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0231.html"><EFBFBD><EFBFBD><EFBFBD> : "Relisys Scanner Backend development started"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0234.html">Dean Martin Townsley: "Re: Calibration problem on UMAX Astra 1220S"</a>
|
|||
|
|
<li> <b>Reply:</b> <a href="0234.html">Dean Martin Townsley: "Re: Calibration problem on UMAX Astra 1220S"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
Hey Oliver, thanks for the quick response, sorry I'm slow, had exams.<br>
|
|||
|
|
Comments below:<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> From: Oliver Rauch <<a href="mailto:oliver.rauch@Wolfsburg.DE">oliver.rauch@Wolfsburg.DE</a>></i><br>
|
|||
|
|
<i>> Dean Martin Townsley wrote:</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> > Hi all,</i><br>
|
|||
|
|
<i>> > My problem with the calibration is simple: I can't get it to perform the</i><br>
|
|||
|
|
<i>> > calibration. I'm using sane 1.00 with the build-1 patch for the umax drivers</i><br>
|
|||
|
|
<i>> > and xsane 0.18 for the frontend (tried xscanimage too).</i><br>
|
|||
|
|
<i>> > I stuck a debug message in the code to supplement the messages already</i><br>
|
|||
|
|
<i>> > there and found that dev->do_calibration was zero when the scan process went</i><br>
|
|||
|
|
<i>> > through the do_calibration() function even when the box for "Quality</i><br>
|
|||
|
|
<i>> > Calibration" was checked in the interface. The code checks and to me seems</i><br>
|
|||
|
|
<i>> > to only perform the calibration if this is nonzero. I don't know if this is</i><br>
|
|||
|
|
<i>> > a problem in the driver itself or somewhere else but both xsane and</i><br>
|
|||
|
|
<i>> > xscanimage exhibit the same problem. That's as far as I got, I have final</i><br>
|
|||
|
|
<i>> > exams for the next two days (take homes) so I won't be able to fiddle again</i><br>
|
|||
|
|
<i>> > until after that probably, but I figured I'd say something so someone with</i><br>
|
|||
|
|
<i>> > better knowledge of the code can maybe investigate.</i><br>
|
|||
|
|
<i>> ></i><br>
|
|||
|
|
<i>> > oh, btw, /proc/scsi/scsi says</i><br>
|
|||
|
|
<i>> > Host: scsi0 Channel: 00 Id: 05 Lun: 00</i><br>
|
|||
|
|
<i>> > Vendor: UMAX Model: Astra 1220S Rev: V1.1</i><br>
|
|||
|
|
<i>> > Type: Scanner ANSI SCSI revision: 02</i><br>
|
|||
|
|
<i>> ></i><br>
|
|||
|
|
<i>> > Which I presume means it's firmware 1.1, (out of a possible 1.5, ugh).</i><br>
|
|||
|
|
<i>> ></i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> Hi Dean,</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> like described in the sane-umax-docs the quality calibration does not work with</i><br>
|
|||
|
|
<i>> all scanners!</i><br>
|
|||
|
|
<p>
|
|||
|
|
I thought I remembered seeing this but still can't find it on the web page at<br>
|
|||
|
|
least. So which ones does it work with?<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> What happens or does not happen if you enable quality calibration?</i><br>
|
|||
|
|
<p>
|
|||
|
|
Okay I'll let you know the story. I'm trying to scan a card that's basically<br>
|
|||
|
|
an embossed white graphic on a slightly off-white background. Well, the<br>
|
|||
|
|
scanner sees that the thing is almost totally white, and saturates the scan<br>
|
|||
|
|
really bad. The histogram in xsane does not fall off at the high<br>
|
|||
|
|
Luminosities, it just saturates. From looking at other stuff on the net,<br>
|
|||
|
|
this appears abnormal, even for stuff on white backgrounds. I am under the<br>
|
|||
|
|
ipression that this is what the "Quality Calibration" is for (though I could<br>
|
|||
|
|
be wrong) is to set the white point so that it is not out of the scanner's<br>
|
|||
|
|
sensing range, as it apparently is on mine since white and off-white come up<br>
|
|||
|
|
as the same color -- ffffff white. I would assume it's just an impossible<br>
|
|||
|
|
scan but someone else did it on another scanner and it came out fine, I'm<br>
|
|||
|
|
just trying to match that (and not even coming close).<br>
|
|||
|
|
Now for what happens when when I try to use the calibration. Nothing.<br>
|
|||
|
|
There is no noticable difference in the scans or the activity performed by<br>
|
|||
|
|
the scanner. I assume that even if the firmware is doing the calibration<br>
|
|||
|
|
that it still has to DO something i.e. the lamp has to move prior to the<br>
|
|||
|
|
actual scan. (Again I could be wrong let me know if I am) In my case I find<br>
|
|||
|
|
no difference between having the button checked or not in the frontend.<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> Background:</i><br>
|
|||
|
|
<i>> There are some problems with calibration by driver. UMAX uses a different</i><br>
|
|||
|
|
<i>> kind of calibration for each scanner model and firmware. I only know the one of</i><br>
|
|||
|
|
<i>> the Umax Supervista S12 with firmware 2.0.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> If you set the quality calibration button, the driver requests a quality</i><br>
|
|||
|
|
<i>> calibration</i><br>
|
|||
|
|
<i>> from the scanner. If the scanner is not able to do the quality calibration on</i><br>
|
|||
|
|
<i>> its own,</i><br>
|
|||
|
|
<i>> it requests the driver to do this. In that case do_calibration is set in the</i><br>
|
|||
|
|
<i>> driver.</i><br>
|
|||
|
|
<i>> Then the scanner sends the calibration data, the driver does the calibration and</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> sends back the calibration data.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> If the scanner does not request that the driver has to do the calibration, there</i><br>
|
|||
|
|
<i>> is</i><br>
|
|||
|
|
<i>> nothing what the driver can do.</i><br>
|
|||
|
|
<p>
|
|||
|
|
Hopefully I'm not totally off base here. I think my scanner is capable of<br>
|
|||
|
|
doing calibration, since the starting of the driver says<br>
|
|||
|
|
[umax] f/w support function:<br>
|
|||
|
|
[umax] ---------------------<br>
|
|||
|
|
[umax] quality calibration<br>
|
|||
|
|
but it likely performs it in the firmware, since the<br>
|
|||
|
|
"change" to firmware 1.5 for this scanner was to add software calibration.<br>
|
|||
|
|
<p>
|
|||
|
|
I think I could do better if I had an idea what I was looking for. What is<br>
|
|||
|
|
the Quality Calibration supposed to work like? Should it happen at the<br>
|
|||
|
|
beginning of each scan when the button is checked? Should the scan process<br>
|
|||
|
|
be different? A two pass scan maybe? If it's not working is this because<br>
|
|||
|
|
the driver is just not telling the scanner to do it properly? Is this<br>
|
|||
|
|
documented anywhere or is this a trial and error type thing?<br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> Bye</i><br>
|
|||
|
|
<i>> Oliver</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
Thanks for the help, and thanks for your work on the driver, it scans<br>
|
|||
|
|
photographs great!<br>
|
|||
|
|
Regards,<br>
|
|||
|
|
-Dean Townsley<br>
|
|||
|
|
<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">majordomo@mostang.com</a>
|
|||
|
|
</pre>
|
|||
|
|
<!-- body="end" -->
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0233.html">Henning Meier-Geinitz: "Re: xsane-0.18 available"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0231.html"><EFBFBD><EFBFBD><EFBFBD> : "Relisys Scanner Backend development started"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0234.html">Dean Martin Townsley: "Re: Calibration problem on UMAX Astra 1220S"</a>
|
|||
|
|
<li> <b>Reply:</b> <a href="0234.html">Dean Martin Townsley: "Re: Calibration problem on UMAX Astra 1220S"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|