Sorry for undefined question!
The question is what to do next and why I have no drivers and how to get
them?
brgds
Janeks
- Original Message -
From: Janeks Kamerovskis s...@apollo.lv
To: sane-devel at lists.alioth.debian.org
Sent: Thursday, October 02, 2008 5:09 PM
Subject:
I'm on the way to upgrade the pixma backend to support TPU scanning, at
least for MP970.
TPU scanning with this PIXMA model requires to set up the 48 bits mode,
the images supplied seems (but still to be confirmed) to be 2
bytes/color (so 6 bytes/pixel), in the form:
rRgGbBrRgGbB...
The
Strange.
I did exactly the same as you did, and I get those lines from the
backend (When I start Xsane from a client), which are inserted in the
log you sent:
[saned] process_request: waiting for request
[saned] process_request: got request 1
[sanei_debug] Setting debug level of pixma to 10.
Nicolas nicolas.martin at freesurf.fr writes:
So my question is: I know Sane standard defines image format to be RGB,
8 bits/color.
Not completely correct. See below.
But is it possible to request a Sane frontend to get a 16 bits/color
image format and deal with that, or do I have to
Le Wednesday 01 October 2008 06:52:05 stef, vous avez ?crit?:
Le Thursday 25 September 2008 22:01:35 stef, vous avez ?crit?:
Hello,
there is a SANE_CURRENT_MAJOR defined. To ease the compilation of
frontends outside SANE tree, how about adding a SANE_CURRENT_MINOR define
?
You need the HPlip drivers from http://www.hplipopensource.com,
version 1.7.4 or higher.
Do I need drivers on scanner server machine at all or only on client PCs?
They should be available in your distribution. The backend is called
hpaio.
When I open
nano /usr/local/etc/sane.d/hp.conf
Ok, thanks a lot for this clarification, I understand that 16 bits per
color images are supported by the standard, so no special scaling would
be necessary.
But do you or someone knows if scanimage or Xsane can handle 16 bits per
color appropriately ?
Nicolas
Le vendredi 03 octobre 2008 ?
Yes, this is exactly what is needed, but looks like there's only a
single page scan here.
Could you produce a same trace (but select a _small_ scan area for
smaller log size) of a 2 page ADF scan with the issue you get.
Note that I'll commit very soon some changes that have been tweaked with
a
part --
An embedded and charset-unspecified text was scrubbed...
Name: scan.log
Url:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20081003/fa486549/attachment-0001.txt
part --
An embedded and charset-unspecified text was scrubbed...
Name: scan.log
Url:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20081003/66e9fe6c/attachment-0001.txt
Hi,
yes, at least some frontends definitely support this, my avision backend
supports 16 bit channels (including upscaling 10 and 12 bit to 16 bit
for devices which support that) for years.
However, I do not remember which frontends worked well, maybe most
worked to some degree, but IIRC the
On Fri, Oct 3, 2008 at 8:02 AM, Ren? Rebe rene at exactcode.de wrote:
Hi,
yes, at least some frontends definitely support this, my avision backend
supports 16 bit channels (including upscaling 10 and 12 bit to 16 bit
for devices which support that) for years.
However, I do not remember
was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20081003/4619d4ca/attachment.htm
those files were not distributed in the sane source tarball. either
get them from cvs, or (even better) do your work in the cvs version of
sane.
allan
2008/10/3 Kisliakov, A. - Andrew - Andrew.Kisliakov at canon-europe.com:
Hi all,
I've just tried adding a new backend file and, as
:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20081003/b5864194/attachment.htm
Looks like the best robust solution is to convert 16 bits/color image to
8 bits/color.
Will place some modifications in the pixma backend for that.
Nicolas
Le vendredi 03 octobre 2008 ? 08:12 -0400, m. allan noah a ?crit :
On Fri, Oct 3, 2008 at 8:02 AM, Ren? Rebe rene at exactcode.de wrote:
Have some presumptions on where this could come from, as ADF code in the
pixma backend isn't very clear.
But before any change, I'd like to submit a newer version of the
backend, that should enhance ADF scanning (tested on MX850 currently).
I'll keep you posted when commit to CVS, as I've some
Ok, thank you very much. I'll be waiting for it.
Pascal
Nicolas wrote:
Have some presumptions on where this could come from, as ADF code in the
pixma backend isn't very clear.
But before any change, I'd like to submit a newer version of the
backend, that should enhance ADF scanning (tested
18 matches
Mail list logo
