kopia lustrzana https://gitlab.com/sane-project/website
108 wiersze
5.3 KiB
HTML
108 wiersze
5.3 KiB
HTML
<!-- received="Thu Dec 18 19:06:02 1997 PST" -->
|
|
<!-- sent="Thu, 18 Dec 1997 22:05:34 -0500" -->
|
|
<!-- name="Matto Marjanovic" -->
|
|
<!-- email="maddog@mir.com" -->
|
|
<!-- subject="Re: Probable Bugs & Suggestions" -->
|
|
<!-- id="199712190305.WAA26565@yoo-hoo.ai.mit.edu" -->
|
|
<!-- inreplyto="Probable Bugs & Suggestions" -->
|
|
<title>sane-devel: Re: Probable Bugs & Suggestions</title>
|
|
<h1>Re: Probable Bugs & Suggestions</h1>
|
|
<b>Matto Marjanovic</b> (<a href="mailto:maddog@mir.com"><i>maddog@mir.com</i></a>)<br>
|
|
<i>Thu, 18 Dec 1997 22:05:34 -0500</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#109">[ date ]</a><a href="index.html#109">[ thread ]</a><a href="subject.html#109">[ subject ]</a><a href="author.html#109">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0110.html">A. Leidenfrost: "Re: Probable Bugs & Suggestions"</a>
|
|
<li> <b>Previous message:</b> <a href="0108.html">Ian Tester: "Re: Probable Bugs & Suggestions"</a>
|
|
<li> <b>Maybe in reply to:</b> <a href="0103.html">A. Leidenfrost: "Probable Bugs & Suggestions"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0122.html">A. Leidenfrost: "Re: Probable Bugs & Suggestions"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
o the scan resolution is not saved correctly, i.e. when setting it to 200<br>
|
|
dpi it is set to 198 after a new start of xscanimage<br>
|
|
<p>
|
|
[with regards to the Microtek E6...]<br>
|
|
Yes and no. The resolution can only be set in 1% increments (e.g. 6dpi for<br>
|
|
the E6) -- 198 is valid, 200 is not. The scale on xscanimage doesn't <br>
|
|
reflect the quantization right away (fixable?).<br>
|
|
[Actually, there are special resolution codes for 200dpi and 400dpi; that's<br>
|
|
on low-end of the ToDo list.]<br>
|
|
<p>
|
|
o setting the value for Exposure to -13 or less results in an error<br>
|
|
(besides 0 is 0 when coming from positive values and -0 when coming<br>
|
|
from negative ones)<br>
|
|
<p>
|
|
I don't get any errors, but I do get a really ugly buzzing noise with values<br>
|
|
< -13. Beats me. I can see the -0 thing (happens when you slide the slider<br>
|
|
with the mouse) --- that would be another GTK/xscanimage thing.<br>
|
|
<p>
|
|
o trying to change any parameter during a preview or a scan results in both<br>
|
|
xscanimage and the scanner to go nuts. There is a error popup and the<br>
|
|
following error message is repeated eternally on the terminal where<br>
|
|
xscanimage was started:<br>
|
|
<p>
|
|
Error: Failed to set value of option brightness: Device busy.<br>
|
|
<p>
|
|
I don't know about *all* parameters, but I do see this behavior with sliders;<br>
|
|
looks like xscanimage drops into a loop of sorts when it doesn't get what it<br>
|
|
wants.<br>
|
|
<p>
|
|
While a scan is in progress, the microtek backend responds to any requests<br>
|
|
to change parameters with SANE_STATUS_DEVICE_BUSY... Is this a reasonable<br>
|
|
behavior? This response is actually not enumerated as a valid response<br>
|
|
to sane_control_option in the API documentation. Should the frontend retry<br>
|
|
on its own volition, or pop up an error for the user and drop the issue?<br>
|
|
<p>
|
|
<p>
|
|
o when using xscanimage as a gimp plugin the transfer of the image from<br>
|
|
xscanimage to gimp sometimes doesn't seem to work. In fact, nothing<br>
|
|
seems to happen and monitoring the process list with top reveals that<br>
|
|
xscanimage is growing and growing and xscanimage and gimp use nearly<br>
|
|
the whole CPU. (When xscanimage reached 23 MB I killed it, and that<br>
|
|
was for a fairly small image of about 5 MB.)<br>
|
|
<p>
|
|
???????? Never had any problem like this.<br>
|
|
<p>
|
|
<p>
|
|
o Automatic Color Calibration: Ok, although I know nearly nothing about<br>
|
|
scanning and image processing, here is my thoughts about color calibration<br>
|
|
for a certain printer. Suppose you have an image with three linear gradient<br>
|
|
<p>
|
|
<p>
|
|
perspective, is that it's crazy stuff. A lot of standardization structure<br>
|
|
is already in place; anyone who wants to try this should spend some time in<br>
|
|
the library first, and realize that what you really want to do is to<br>
|
|
calibrate your scanner, printer, and monitor independently to CIE standard<br>
|
|
color indices.<br>
|
|
<p>
|
|
<p>
|
|
-matt m.<br>
|
|
<p>
|
|
<p>
|
|
ps: As always, the general rule is if you have a reproducible problem, send<br>
|
|
an error log... helps immensely with tracking down what is going on inside.<br>
|
|
(For example, I know of at least three different model codes for the<br>
|
|
"Scanmaker E6" --- who knows which one anyone has, and what the subtle<br>
|
|
differences in behavior might be?)<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">majordomo@mostang.com</a>
|
|
</pre>
|
|
<!-- body="end" -->
|
|
<p>
|
|
<ul>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0110.html">A. Leidenfrost: "Re: Probable Bugs & Suggestions"</a>
|
|
<li> <b>Previous message:</b> <a href="0108.html">Ian Tester: "Re: Probable Bugs & Suggestions"</a>
|
|
<li> <b>Maybe in reply to:</b> <a href="0103.html">A. Leidenfrost: "Probable Bugs & Suggestions"</a>
|
|
<!-- nextthread="start" -->
|
|
<li> <b>Next in thread:</b> <a href="0122.html">A. Leidenfrost: "Re: Probable Bugs & Suggestions"</a>
|
|
<!-- reply="end" -->
|
|
</ul>
|