sane-project-website/old-archive/1999-07/0078.html

57 wiersze
2.9 KiB
HTML
Czysty Wina Historia

This file contains invisible Unicode characters!

This file contains invisible Unicode characters that may be processed differently from what appears below. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to reveal hidden characters.

<!-- received="Thu Jul 15 02:32:41 1999 PDT" -->
<!-- sent="Thu, 15 Jul 1999 11:18:22 +0200" -->
<!-- name="abel deuring" -->
<!-- email="a.deuring@satzbau-gmbh.de" -->
<!-- subject="Re: SnapScan 0.7 sources available; working patch upcoming" -->
<!-- id="" -->
<!-- inreplyto="SnapScan 0.7 sources available; working patch upcoming" -->
<title>sane-devel: Re: SnapScan 0.7 sources available; working patch upcoming</title>
<h1>Re: SnapScan 0.7 sources available; working patch upcoming</h1>
<b>abel deuring</b> (<a href="mailto:a.deuring@satzbau-gmbh.de"><i>a.deuring@satzbau-gmbh.de</i></a>)<br>
<i>Thu, 15 Jul 1999 11:18:22 +0200</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#78">[ date ]</a><a href="index.html#78">[ thread ]</a><a href="subject.html#78">[ subject ]</a><a href="author.html#78">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0079.html">Oliver Rauch: "Re: Xsane questions and wish list"</a>
<li> <b>Previous message:</b> <a href="0077.html">Steve Gunnell: "Xsane questions and wish list"</a>
<li> <b>Maybe in reply to:</b> <a href="0074.html">Kevin Charter: "SnapScan 0.7 sources available; working patch upcoming"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Doug,<br>
<p>
<i>&gt; Abel Deuring &lt;<a href="mailto:a.deuring@satzbau-gmbh.de">a.deuring@satzbau-gmbh.de</a>&gt; is also getting</i><br>
<i>&gt; some impressive speedups with his SnapScan using larger</i><br>
<i>&gt; buffers and "pseudo" command queuing.</i><br>
<p>
I'm working with a Sharp JX250, not an Agfa Snapscan :) But the<br>
remaining is right: the usage of (pseudo) command queueing, large<br>
buffers, a separate reader process and shared memory for the data<br>
transfer between the reader process and its parent avoids many, if not<br>
all, carriage stops with higher resolutions, at least with the Linux box<br>
to which my JX250 is connected (P166, 64 MB, Adaptec 2940). On the other<br>
hand, it seems that the JX250 has not the largest internal buffer, or a<br>
poor buffer management. The scan time decrease from more than 20 seconds<br>
to less than 10 seconds (A4, grayscale, 400 dpi) may be a somewhat<br>
special situation, compared with other scanners.<br>
<p>
Abel<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="0079.html">Oliver Rauch: "Re: Xsane questions and wish list"</a>
<li> <b>Previous message:</b> <a href="0077.html">Steve Gunnell: "Xsane questions and wish list"</a>
<li> <b>Maybe in reply to:</b> <a href="0074.html">Kevin Charter: "SnapScan 0.7 sources available; working patch upcoming"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>