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

72 wiersze
3.4 KiB
HTML

<!-- received="Thu Jul 29 19:41:11 1999 PDT" -->
<!-- sent="Thu, 29 Jul 1999 19:58:49 -0700" -->
<!-- name="Stephen Williams" -->
<!-- email="steve@icarus.com" -->
<!-- subject="scanners that do jpeg compression" -->
<!-- id="199907300258.TAA13262@icarus.com" -->
<!-- inreplyto="" -->
<title>sane-devel: scanners that do jpeg compression</title>
<h1>scanners that do jpeg compression</h1>
<b>Stephen Williams</b> (<a href="mailto:steve@icarus.com"><i>steve@icarus.com</i></a>)<br>
<i>Thu, 29 Jul 1999 19:58:49 -0700</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#219">[ date ]</a><a href="index.html#219">[ thread ]</a><a href="subject.html#219">[ subject ]</a><a href="author.html#219">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0220.html">Didier Carlier: "Re: SANE &amp; exposure times"</a>
<li> <b>Previous message:</b> <a href="0218.html">Nick Lamb: "Re: SANE &amp; exposure times"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>
<!-- body="start" -->
I have a whole bunch of high-performance scanners that are just<br>
screaming for SANE drivers. Some are color, some are grayscale.<br>
All can produce many views (i.e. color and binary) of the same image,<br>
and all compressed the image in hardware.<br>
<p>
I see that SANE is going to have some troubles with these scanners.<br>
It is reasonable to expect the driver to decompress these images and<br>
present them to the default application as RGB images, but I would like<br>
to write SANE applications that can receive these images as JFIF streams.<br>
The program may save them to disk, or preview the image, or both, but I<br>
would like to give a JFIF aware application the JFIF frame.<br>
<p>
For the particular scanners I have in mind, it is imperative that the<br>
image not be decompressed/recompressed unless it is to be displayed<br>
or passed on to non-compression aware applications. Otherwise, there is<br>
simply no chance of getting the 180PPM that some of these scanners can<br>
operate at.<br>
<p>
To accomplish this I can see obviously that I can create a driver<br>
option that enables JFIF frames. However, if the user does this, I do<br>
not see how to communicate with the application that the comming frame<br>
is JFIF. The scan_get_parameters result includes the format, and I see<br>
no way to express that the image is arriving compressed.<br>
<p>
TWAIN supports compression of frames, as does Pixel Translations Pixtools.<br>
<p>
So, what's a high performance scanner producer to do?<br>
<pre>
--
Steve Williams "The woods are lovely, dark and deep.
<a href="mailto:steve@icarus.com">steve@icarus.com</a> But I have promises to keep,
<a href="mailto:steve@picturel.com">steve@picturel.com</a> and lines to code before I sleep,
<a href="http://www.picturel.com">http://www.picturel.com</a> And lines to code before I sleep."
<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">majordomo@mostang.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0220.html">Didier Carlier: "Re: SANE &amp; exposure times"</a>
<li> <b>Previous message:</b> <a href="0218.html">Nick Lamb: "Re: SANE &amp; exposure times"</a>
<!-- nextthread="start" -->
<!-- reply="end" -->
</ul>