kopia lustrzana https://gitlab.com/sane-project/website
78 wiersze
3.4 KiB
HTML
78 wiersze
3.4 KiB
HTML
<!-- received="Tue Apr 6 12:45:12 1999 PDT" -->
|
||
<!-- sent="Tue, 6 Apr 1999 20:45:50 +0200" -->
|
||
<!-- name="Ewald R. de Wit" -->
|
||
<!-- email="ewald@pobox.com" -->
|
||
<!-- subject="Re: 16 bit per sample support" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="Pine.LNX.3.96.990406142835.1576j-100000@mail.perspex.com" -->
|
||
<title>sane-devel: Re: 16 bit per sample support</title>
|
||
<h1>Re: 16 bit per sample support</h1>
|
||
<b>Ewald R. de Wit</b> (<a href="mailto:ewald@pobox.com"><i>ewald@pobox.com</i></a>)<br>
|
||
<i>Tue, 6 Apr 1999 20:45:50 +0200</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#114">[ date ]</a><a href="index.html#114">[ thread ]</a><a href="subject.html#114">[ subject ]</a><a href="author.html#114">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0115.html">Tripp Lilley: "Re: 16 bit per sample support"</a>
|
||
<li> <b>Previous message:</b> <a href="0113.html">Allan Strand: "Re: configuring sane-1.00"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
Tripp Lilley (<a href="mailto:tlilley@perspex.com">tlilley@perspex.com</a>) wrote:<br>
|
||
<p>
|
||
<i>> On Tue, 6 Apr 1999, Ewald R. de Wit wrote:</i><br>
|
||
<i>> </i><br>
|
||
<i>> > The SANE parameter 'depth' can remain what is currently (ie the native</i><br>
|
||
<i>> > depth), and not setting it to 16 for depths>8. Then we don't need a</i><br>
|
||
<i>> > new parameter.</i><br>
|
||
<i>> </i><br>
|
||
<i>> Personally, I vote for a separation between "actual" depth and</i><br>
|
||
<i>> "transmission" depth. I like the option of writing code driven entirely by</i><br>
|
||
<i>> the parameters, and not by "arbitrary" rules about certain parameters. In</i><br>
|
||
<i>> this case, overloading 'depth' this way would mean that depth=1 would</i><br>
|
||
<i>> imply 1-bit transmission, 8 >= depth >1 implies 8-bit transmission, etc.</i><br>
|
||
<p>
|
||
The transmission width should be calculated from parameters<br>
|
||
pixels_per_line and bytes_per_pixel. If I understand the SANE<br>
|
||
standard correctly, your code must NOT use depth for this.<br>
|
||
For example, my photosmart reports a depth of 10 and sends the data<br>
|
||
in 16 bits - that would certainly confuse your code.<br>
|
||
<p>
|
||
So, there is nothing overloaded, special or arbitrary about 'depth'<br>
|
||
and another parameter 'native_depth' would be redundant, as far as I <br>
|
||
can see anyway.<br>
|
||
<p>
|
||
<i>> But I don't like where that leaves us when we support 24-bit or 32-bit</i><br>
|
||
<i>> transmission.</i><br>
|
||
<p>
|
||
Let that be a problem for the engineers of the USS Enterprise. What we<br>
|
||
need now is a standard 16 bit format.<br>
|
||
<p>
|
||
<i>> If we go this route, may I suggest calling it SANE_FRAME_RGBIR instead?</i><br>
|
||
<i>> RGBI already has meaning (RGB+Intensity) in the video world.</i><br>
|
||
<p>
|
||
Better call it SANE_FRAME_RGBD then, the company that invented it<br>
|
||
calls the infrared channel the D channel.<br>
|
||
<p>
|
||
<pre>
|
||
--
|
||
-- Ewald
|
||
<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="0115.html">Tripp Lilley: "Re: 16 bit per sample support"</a>
|
||
<li> <b>Previous message:</b> <a href="0113.html">Allan Strand: "Re: configuring sane-1.00"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|