kopia lustrzana https://gitlab.com/sane-project/website
88 wiersze
4.6 KiB
HTML
88 wiersze
4.6 KiB
HTML
<!-- received="Mon May 10 07:03:54 1999 PDT" -->
|
||
<!-- sent="Mon, 10 May 1999 07:02:43 -0700" -->
|
||
<!-- name="Brian Macy" -->
|
||
<!-- email="bmacy@sunshinecomputing.com" -->
|
||
<!-- subject="Re: [Announce] WinSANE 0.1.0.0 Release" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="[Announce] WinSANE 0.1.0.0 Release" -->
|
||
<title>sane-devel: Re: [Announce] WinSANE 0.1.0.0 Release</title>
|
||
<h1>Re: [Announce] WinSANE 0.1.0.0 Release</h1>
|
||
<b>Brian Macy</b> (<a href="mailto:bmacy@sunshinecomputing.com"><i>bmacy@sunshinecomputing.com</i></a>)<br>
|
||
<i>Mon, 10 May 1999 07:02:43 -0700</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#72">[ date ]</a><a href="index.html#72">[ thread ]</a><a href="subject.html#72">[ subject ]</a><a href="author.html#72">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0073.html">Nick Lamb: "Re: [Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<li> <b>Previous message:</b> <a href="0071.html">Nick Lamb: "Re: [Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0070.html">Brian Macy: "[Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<!-- nextthread="start" -->
|
||
<li> <b>Next in thread:</b> <a href="0074.html">Brian Macy: "Re: [Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
<i>> For a bit-oriented scan (lineart) you can safely assume everyone is agreed</i><br>
|
||
<i>> about which order the bits go in. Networks transfer a byte at a time.</i><br>
|
||
<i>></i><br>
|
||
<i>> For a byte-oriented scan (8-bit grey, 24-bit colour) there's also nothing</i><br>
|
||
<i>> to worry about, we're all agreed how to send a byte over a network.</i><br>
|
||
<i>></i><br>
|
||
<i>> However, multi-byte samples (10 bit grey, 36 bit colour etc.) require</i><br>
|
||
<i>> that you compare your endianess with the backend, and if they're different</i><br>
|
||
<i>> convert. This ONLY applies to image data, everything else uses network</i><br>
|
||
<i>> byte order to solve this problem.</i><br>
|
||
<i>></i><br>
|
||
<i>> If (as I suspect) this version of WinSANE doesn't support anything bigger</i><br>
|
||
<i>> than 8-bit samples, (ie 24-bit colour) then you needn't worry about it.</i><br>
|
||
<p>
|
||
Thanks... you are correct it doesn't. I was looking at the code for SANE and<br>
|
||
it didn't look like it handled >8bits per color too. There were a couple of<br>
|
||
locations in the frontends where it errored if bit depth was anything<br>
|
||
besides 1 or 8. Oh well... hopefully people will still find use for it<br>
|
||
without such support. I'd still like to know how in the world you would code<br>
|
||
this to be anything besides... swapping bits is kind of strange. So are you<br>
|
||
telling me that for MSB 10bit data you get:<br>
|
||
98765432 10987654 ... etc<br>
|
||
but for LSB 10bit you get:<br>
|
||
76543210 98543210 98763210 ... etc.<br>
|
||
or is it<br>
|
||
76543210 98765432 10987654 ... etc.<br>
|
||
<p>
|
||
I must say anything besides MSB is a bit psychotic.<br>
|
||
<p>
|
||
<i>> Hmm. The TWAIN toolkit, at least in recent versions looked like a pretty</i><br>
|
||
<i>> straight forward "fill in the blanks" piece of software. I can't offer to</i><br>
|
||
<i>> help here (no Win32 experience, and no desire to get some) but I suspect</i><br>
|
||
<i>> that plugging your GUI onto TWAIN is pretty easy.</i><br>
|
||
<i>></i><br>
|
||
<i>> Since SANE already handles all the fiddly decisions about how to express</i><br>
|
||
<i>> scanner capabilities, in the backend, you'll probably have less work to</i><br>
|
||
<i>> do than someone implementing TWAIN for a single device... I hope.</i><br>
|
||
<p>
|
||
I've looked at the TWAIN toolkit... I might have to install VC++ to not be<br>
|
||
pulling my hair out (uugggh). Anyways, I basically replemented the net<br>
|
||
backend from scratch to make my life easier and to help figure out the exact<br>
|
||
formatting of the protocol. But the information sane provides is still<br>
|
||
available and useful. I still wish the protocol had another behavior besides<br>
|
||
"if error, shutdown" but it doesn't.<br>
|
||
<p>
|
||
Brian Macy<br>
|
||
<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="0073.html">Nick Lamb: "Re: [Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<li> <b>Previous message:</b> <a href="0071.html">Nick Lamb: "Re: [Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<li> <b>Maybe in reply to:</b> <a href="0070.html">Brian Macy: "[Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<!-- nextthread="start" -->
|
||
<li> <b>Next in thread:</b> <a href="0074.html">Brian Macy: "Re: [Announce] WinSANE 0.1.0.0 Release"</a>
|
||
<!-- reply="end" -->
|
||
</ul>
|