sane-project-website/old-archive/1999-04/0077.html

83 wiersze
4.0 KiB
HTML

<!-- received="Mon Apr 5 02:37:04 1999 PDT" -->
<!-- sent="Sun, 04 Apr 1999 17:13:40 +0000" -->
<!-- name="Jonathan A. Buzzard" -->
<!-- email="jab@hex.prestel.co.uk" -->
<!-- subject="Re: 16 bit per sample support" -->
<!-- id="m10TqSr-00019RC@hex" -->
<!-- inreplyto="Pine.LNX.3.96.990404122354.30186A-100000@chef.ecs.soton.ac.uk" -->
<title>sane-devel: Re: 16 bit per sample support</title>
<h1>Re: 16 bit per sample support</h1>
<b>Jonathan A. Buzzard</b> (<a href="mailto:jab@hex.prestel.co.uk"><i>jab@hex.prestel.co.uk</i></a>)<br>
<i>Sun, 04 Apr 1999 17:13:40 +0000</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#77">[ date ]</a><a href="index.html#77">[ thread ]</a><a href="subject.html#77">[ subject ]</a><a href="author.html#77">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0078.html">Milon Firikis: "Re: Sane drivers"</a>
<li> <b>Previous message:</b> <a href="0076.html">Jonathan A. Buzzard: "Re: Sane drivers"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0082.html">Andreas Dilger: "Re: 16 bit per sample support"</a>
<li> <b>Reply:</b> <a href="0082.html">Andreas Dilger: "Re: 16 bit per sample support"</a>
<li> <b>Reply:</b> <a href="0085.html">Nick Lamb: "Re: 16 bit per sample support"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
<a href="mailto:njl98r@ecs.soton.ac.uk">njl98r@ecs.soton.ac.uk</a> said:<br>
<i>&gt; &gt;Possibly depending on the device this should be configurable. If I</i><br>
<i>&gt; &gt;was scanning an X-ray at say 12bits I would be very upset if the</i><br>
<i>&gt; &gt;backend then stretched it to 16bits.</i><br>
<i>&gt;</i><br>
<i>&gt; I'm not sure why. The only (small) disadvantage is that there is an</i><br>
<i>&gt; increase in bandwidth from the backend to the frontend. For most</i><br>
<i>&gt; users, especially those looking for maximum performance, this is CPU</i><br>
<i>&gt; bandwidth, and thus very expendable. </i><br>
<i>&gt;</i><br>
<i>&gt; There is no data loss (watch this...</i><br>
<i>&gt; 0xabc (12bit) --&gt; 0xabca (16bit) --&gt; 0xabc (12bit)</i><br>
<i>&gt; 0x123 (12bit) --&gt; 0x1231 (16bit) --&gt; 0x123 (12bit) </i><br>
<p>
Because you have mugged the values. X-rays where only an example, but the<br>
same could be said of other sources such as aerial photography etc.<br>
With these sorts of things you often want to do calculations on the<br>
scanned images.<br>
<p>
For example I might have three Xrays of an object, that after some sort<br>
of registration I wish to stack on top of one another. The Xrays have<br>
been scanned say at 12 bits, now if you have stretched them though to<br>
the full dynamic range of 16 bits adding the pixel values together<br>
will result in loss of information. If they had stayed as 12 bits inside<br>
a 16 bit value there is no problem.<br>
<p>
These are dozens of similar cases where stretching the values is simply<br>
not acceptable. A little check button somewhere which can be unchecked<br>
for those that don't want stretching would suffice.<br>
<p>
<p>
JAB.<br>
<p>
<p>
<pre>
--
Jonathan A. Buzzard Email: <a href="mailto:jab@hex.prestel.co.uk">jab@hex.prestel.co.uk</a>
Northumberland, United Kingdom. Tel: +44(0)1661-832195
<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="0078.html">Milon Firikis: "Re: Sane drivers"</a>
<li> <b>Previous message:</b> <a href="0076.html">Jonathan A. Buzzard: "Re: Sane drivers"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0082.html">Andreas Dilger: "Re: 16 bit per sample support"</a>
<li> <b>Reply:</b> <a href="0082.html">Andreas Dilger: "Re: 16 bit per sample support"</a>
<li> <b>Reply:</b> <a href="0085.html">Nick Lamb: "Re: 16 bit per sample support"</a>
<!-- reply="end" -->
</ul>