kopia lustrzana https://gitlab.com/sane-project/website
66 wiersze
2.9 KiB
HTML
66 wiersze
2.9 KiB
HTML
<!-- received="Tue Apr 6 04:19:45 1999 PDT" -->
|
||
<!-- sent="Tue, 6 Apr 1999 12:20:03 +0200" -->
|
||
<!-- name="Ewald R. de Wit" -->
|
||
<!-- email="ewald@pobox.com" -->
|
||
<!-- subject="Re: 16 bit per sample support" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="m10UIJD-00017lC@hex" -->
|
||
<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 12:20:03 +0200</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#96">[ date ]</a><a href="index.html#96">[ thread ]</a><a href="subject.html#96">[ subject ]</a><a href="author.html#96">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0097.html">becka@rz.uni-duesseldorf.de: "Re: 16 bit per sample support"</a>
|
||
<li> <b>Previous message:</b> <a href="0095.html">killian@lucent.com: "Epson GT-7000"</a>
|
||
<li> <b>In reply to:</b> <a href="0088.html">Jonathan A. Buzzard: "Re: 16 bit per sample support"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
Jonathan A. Buzzard (<a href="mailto:jab@hex.prestel.co.uk">jab@hex.prestel.co.uk</a>) wrote:<br>
|
||
<i>> Er, if I stretch to use the *full* dynamic range this is not the case.</i><br>
|
||
<br>
|
||
Does anyone know an efficient algorithm to upsample say 10 or 12 bits<br>
|
||
to 16? The example David gave earlier (4->8 bits) doesn't apply here well.<br>
|
||
<br>
|
||
<i>> SANE is for scanning, and what about those people that will be throwing</i><br>
|
||
<i>> their hands in the air if the scanning software is mugging their precious</i><br>
|
||
<i>> pixel values. For some applications this stretching of the values is</i><br>
|
||
<i>> simply not acceptable, why is SANE seeking to rule these applications</i><br>
|
||
<i>> out?</i><br>
|
||
<p>
|
||
I don't understand your aversion against upsampling in general but I<br>
|
||
feel too that it should not take place in the backend. IMHO the<br>
|
||
backend should just give you the data as the scanner sends it out and<br>
|
||
it's the responsibility of the frontend to make sense of it.<br>
|
||
Putting it in all the backends would mean more (duplicate) work.<br>
|
||
<p>
|
||
OTOH it would be nice to have simple access to the deep color data in<br>
|
||
a unified 16 bit format. Perhaps in the longer run this would be<br>
|
||
better.<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="0097.html">becka@rz.uni-duesseldorf.de: "Re: 16 bit per sample support"</a>
|
||
<li> <b>Previous message:</b> <a href="0095.html">killian@lucent.com: "Epson GT-7000"</a>
|
||
<li> <b>In reply to:</b> <a href="0088.html">Jonathan A. Buzzard: "Re: 16 bit per sample support"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|