On Sunday 01 January 2006 14:30, Frank Zago wrote:
+#if defined(WORDS_BIGENDIAN)
for (p = buf; p buf + nread; p++)
{
b = *p;
*p++ = *(p + 1);
*p = b;
}
+#endif
}
Why not use htons() which should be a little more efficient?
Please note that
Hi,
I think I am the one who is responsible for the byte switch
problem. Indeed, I am using a big-endian machine.
However, I thought that the PNM standard specifies the byte order.
Please advise me if this is wrong.
Best regards,
Ulrich Deiters
Hi,
On Wed, Dec 28, 2005 at 10:58:14AM +0100, Ulrich Deiters wrote:
However, I thought that the PNM standard specifies the byte order.
Please advise me if this is wrong.
The pnm standard specifies the byte order for files saved in pnm
format.
However, the backend does not know what's done
On Wednesday 28 December 2005 10:58, Ulrich Deiters wrote:
Indeed, I am using a big-endian machine.
Ok, then it's easy:
On Tuesday 27 December 2005 20:07, Henning Meier-Geinitz wrote:
According to the SANE standard (3.2.1): the bytes of each sample
value are transmitted in the machine's
On Tuesday 27 December 2005 14:32, Henning Meier-Geinitz wrote:
Using imagemagick on the raw data give images with noise. Switching
bytes before using imagemagick' convert works ok.
The noise also appears in preview window when mode is raw, so the bug
is probably in sane and not
Hi,
On Tue, Dec 27, 2005 at 04:47:21PM +0100, Jean-Michel Vourg?re wrote:
On Tuesday 27 December 2005 14:32, Henning Meier-Geinitz wrote:
Using imagemagick on the raw data give images with noise. Switching
bytes before using imagemagick' convert works ok.
The noise also appears in
