Guillaume Gastebois schrieb:
Hello,
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
Hello,
It's a little bit better with these values.
In Genesys_Sensor I have :
regs_0x08_0x0b : {0x00, 0x21, 0x00, 0x00}
regs_0x10_0x1d : {0x02, 0x8b, 0x02, 0x8b, 0x02, 0x8b, 0x20, 0x06, 0x00
Stefan Lucke schrieb:
Hi,
I guess there are 3 possibilities for infinite loops.
Attached patch fixes this and adjusts loop threshold
to given comments..
Thanks for spotting these.
We have never had a problem with those loops, but it is certainly a good
idea to have the code working as the
Guillaume Gastebois schrieb:
Hello,
I need a little bit more informations befor testing (sorry for my poor
knowledge
in scanner)
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
I don't know why the image colors are reversed, but it may be worth
trying to flip the sign bits
Hi Guillaume,
Guillaume Gastebois schrieb:
Hello,
Why calibration is so long (~50/60s) ?
It is probably failing. Should take about 3-5 seconds. Look at the logs,
the calculated averages and calibration are dumped there.
What are /* Start of white strip in mm (y) */ and /* Start of black
Hi list,
anybody knows if/where to find $subject on the web? Something that
describes some details of motor control, lamp control and analog/digital
postprocessing, as well as the general scanning operating. Just enough
for a developer of a driver for a dumb chip(like the genesys chips).
If
Reinhard Biegel schrieb:
Am Monday, 11. February 2008 schrieb Stefan Lucke:
...
[genesys_gl841] reg[0x6b] = 0x02
[genesys_gl841] reg[0x6e] = 0x6d
[genesys_gl841] gl841_bulk_write_register: failed while writing command:
Invalid argument
scanimage: open of device
Gerhard Jaeger schrieb:
On Tuesday 12 February 2008 03:41:49 Reinhard Biegel wrote:
On Monday, 11. February 2008, Pierre Willenbrock wrote:
Did someone post the bcdDevice value of a LiDE 80? GL841 goes up to
3.0.5, as someone said, and GL842 begins with 3.0.6
that was me. But it's not quite
Guillaume Gastebois schrieb:
Hello,
I modified registers 10-1d with :
{0x04, 0xd3, 0x04, 0xd3, 0x02, 0xa3, 0x20, 0x06, 0x00, 0xff, 0x24, 0x00,
0x00, 0x04},
and now the led is really white (red green and blue by moving eyes).
Led calibration seems to be good.
But calibration is
Guillaume Gastebois schrieb:
Hello,
I see that reg[2] was like 0x07. So INVOP was still set !!!
I comment out offset_calibration in genesys_flatbed_calibration, set
reg[2] to 0x03, and I get a black image with a gray vertical line in the
middle !!!
I try to reenable offset_calibration
Pierre Willenbrock schrieb:
Guillaume Gastebois schrieb:
Hello,
I see that reg[2] was like 0x07. So INVOP was still set !!!
I comment out offset_calibration in genesys_flatbed_calibration, set
reg[2] to 0x03, and I get a black image with a gray vertical line in the
middle !!!
I try
Pierre Willenbrock schrieb:
Stefan Lucke schrieb:
Hi,
I guess there are 3 possibilities for infinite loops.
Attached patch fixes this and adjusts loop threshold
to given comments..
Thanks for spotting these.
We have never had a problem with those loops, but it is certainly a good
idea
Guillaume Gastebois schrieb:
Hello,
OK, I'll try it tonight.
How do I cleanly remove shading_calibration ?
The code for the actual calibration is in genesys.c, line 3362:
/* shading calibration */
to line 3414, before
/* send gamma tables if needed */
Regards
Guillaume
Stefan Lucke schrieb:
On Monday 11 February 2008, Pierre Willenbrock wrote:
Reinhard Biegel schrieb:
Am Monday, 11. February 2008 schrieb Stefan Lucke:
At that moment, I guess you'll see messages like:
new high speed USB device using ehci_hcd and address nn
via dmesg.
Hi,
Yes, thats
Guillaume Gastebois schrieb:
Hello,
You can find all of that on :
http://ggastebois.free.fr/lide90_snoop/no_shading.tar
What seems strange in calibration ?
The minimum/maximum values retrieved from the scans do not scale with
the offset values, but in a rather random manner. The
Pierre Willenbrock schrieb:
Guillaume Gastebois schrieb:
Hello,
You can find all of that on :
http://ggastebois.free.fr/lide90_snoop/no_shading.tar
What seems strange in calibration ?
The minimum/maximum values retrieved from the scans do not scale with
the offset values
Vidar S?terb? schrieb:
Hi,
FYI, I was googling for information on the GL646 (I have a HP Scanjet
2400) when I came across this datasheet:
http://www.ic-on-line.cn/IOL_gl646/PdfView/833184.htm
Another source for that datasheet is probably
Guillaume Gastebois schrieb:
Hello,
You can find the result of this test here :
http://ggastebois.free.fr/lide90_snoop/no_shading_2bright_2dark.tar
The calibration is about 25s long.
Resulting image is bad (as befor).
Please try with bit 4+5 of frontend setup register 1 set to 3:
Guillaume Gastebois schrieb:
Hello,
I try both {0x00, 0x3f, 0x03, 0x26}, and {0x00, 0x3f, 0x00, 0x26},
you can find result under :
http://ggastebois.free.fr/lide90_snoop/17_test1.tar
and http://ggastebois.free.fr/lide90_snoop/17_test2.tar
Looks a lot better. The offset*.pnm actually show a
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
Guillaume Gastebois schrieb:
Hello,
I made two tests today :
test 1 : too bright/too dard = 10/65525 WITH flag :
SCAN_FLAG_DISABLE_LAMP. Result can bee found on :
http://ggastebois.free.fr/lide90_snoop/18_test1.tar
test 2 : too
brackets perhaps? copy+pasto when calculating the second set?), or send
the source.
Regards,
Pierre
Regards
Guillaume
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
Hello,
OK, I'll try this tonight. What is the best : WITH or WITHOUT
SCAN_FLAG_DISABLE_LAMP ?
Not using
that the calibration dump images are really grayscale images,
although stored in color pnms. 1 pixel in image is 3 pixels for the
calibration...
I hope this fixes that part of the calibration.
Regards,
Pierre
Regards
Guillaume
Pierre Willenbrock a ?crit :
Guillaume Gastebois schrieb:
Hello,
I
Pierre Willenbrock schrieb:
Hi,
Guillaume Gastebois schrieb:
Hello,
So, what's the next step ? Re-enabling shading ?
Yes, but only after the shading-calibration is able to get black level
information.(This really needs a better api..)
I commited a prerequisite for shading calibration
Guillaume Gastebois schrieb:
Hello,
Selon Pierre Willenbrock pierre at pirsoft.dnsalias.org:
Hi,
Guillaume Gastebois schrieb:
Hello,
So, what's the next step ? Re-enabling shading ?
Yes, but only after the shading-calibration is able to get black level
information.(This really needs
when the
genesys_dark_shading_calibration requests that. That change is just the
small bit in genesys_gl841.c, gl841_set_lamp_power.
Oh, and please update from cvs again. A small mistake in
gl841_bulk_write_registers made the debug register dumps useless.
Regards,
Pierre
Pierre Willenbrock
Hi,
Guillaume Gastebois schrieb:
Hello,
So, we need to check what parts of the clocking we need to setup
differently.
Candidates:
reg sane windows
0x1a 0x00 0x24 enable clock 3,4 manual output, invert clock 4
0x1d 0x04 0x02 just a smaller toggle shoulder.
0x71 0x00
Rene Rebe schrieb:
litlle girl wrote:
AFE settings looks more stable:
grep \[gt68xx\] afe ./*
./color-1.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04
./color-2.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04
./color-3.log:[gt68xx] afe 0x0f 0x04 0x10 0x05 0x0f 0x04
./gray-1.log:[gt68xx] afe
Hi Guillaume,
Guillaume Gastebois schrieb:
Hello,
I'm back with my LiDE 90 !
I see in my windows logs the following sequence for gpios (reg 0x6C) :
02
12
0e
1a
0a
0e/3e (3e for half ccd log) (seems to be scanning moment)
0e
0a
0e/3e (3e for half ccd log)
02
With tests I
Hi,
guillaume.gastebois at free.fr schrieb:
Hello,
Thank you for answer Pierre.
Some questions again !
Hi Guillaume,
Guillaume Gastebois schrieb:
Hello,
I'm back with my LiDE 90 !
I see in my windows logs the following sequence for gpios (reg 0x6C) :
02
12
0e
1a
0a
0e/3e (3e for
Hi Keith,
Vital Mission Software schrieb:
I would like to see if I can get my LiDE 80 to work. It is marked as
unsupported since 2007-01-28. It appears in the udev/libsane.rules, but
not in genesys_devices.c. However, that does include support for LiDE
up to 60 and I note that the tables
guillaume.gastebois at free.fr schrieb:
Hello,
It seems that in Windows snoop calibration of LiDE 90 is done with
half CCD even if scanning is in full sensor resolution.
Is it so in sane ?
If not, is it usefull to implement it ? Where to do that ?
To be on the safe side, all calibration
stef schrieb:
Hello Pierre,
I am currently studying how to add support for the HP2400/G2410 to the
gl646
part of the genesys backend. I am currently trying to figure out how to fill
the values for the motor struct in genesys_devices. How did you find the
current values, are
Dhi Aurrahman schrieb:
Dear All!
I have CanonScan LiDE 50 with me (working well with SANE genesys backend),
but I need to have a buttons-daemon for it.
Anyone could help me how to do it? I think the first step is to snoop the
USB message sent by the button when it is pressed.
If you have
m. allan noah schrieb:
On Wed, Jan 7, 2009 at 1:09 PM, Pierre Willenbrock
pierre at pirsoft.dnsalias.org wrote:
[...]
I have no experience with the sane interface itself, so comments/patches
are gladly accepted.
We have settled on exposing buttons via options with:
opt-cap
m. allan noah schrieb:
On Fri, Jan 9, 2009 at 5:02 PM, Pierre Willenbrock
pierre at pirsoft.dnsalias.org wrote:
[...]
Another question: Is it okay to only look at the hardware state if the
frontend asks for the state of the option? That way shorter presses can
be lost, if the frontend does
m. allan noah schrieb:
On Sat, Jan 10, 2009 at 1:11 PM, Pierre Willenbrock
pierre at pirsoft.dnsalias.org wrote:
m. allan noah schrieb:
On Fri, Jan 9, 2009 at 5:02 PM, Pierre Willenbrock
pierre at pirsoft.dnsalias.org wrote:
[...]
Another question: Is it okay to only look at the hardware
m. allan noah schrieb:
On Sat, Jan 10, 2009 at 2:55 PM, Pierre Willenbrock
pierre at pirsoft.dnsalias.org wrote:
m. allan noah schrieb:
On Sat, Jan 10, 2009 at 1:11 PM, Pierre Willenbrock
pierre at pirsoft.dnsalias.org wrote:
m. allan noah schrieb:
On Fri, Jan 9, 2009 at 5:02 PM, Pierre
Hi list,
i tried to build sane with different source and build directories and
ended up needing the attached patch to tools/Makefile.in. I am not sure
if i got the build-directory creation right, but it works for different
source/build directories as well as when they are identical. If no one
Dhi Aurrahman schrieb:
Dear All!
I have CanonScan LiDE 50 with me (working well with SANE genesys backend),
but I need to have a buttons-daemon for it.
Anyone could help me how to do it? I think the first step is to snoop the
USB message sent by the button when it is pressed.
If you have
Roland Graf schrieb:
Am Samstag, 17. Januar 2009 15:41:51 schrieben Sie:
Roland Graf schrieb:
Hello Pierre,
I'm the owner of an HP G4010, and I would collaborate with you to insert
this scanner in the genesys backend.
I read in the mailing lists that it is not absolutely clear whether the
Yes, feeder jammed is a bad error message. I see we have
SANE_STATUS_HW_LOCKED now -- that is probably a better error code. Fixed
in cvs.
Regards,
Pierre
Tobias Preclik schrieb:
Thanks for sorting this out. Didn't know the device has a lock switch
and was confused by the document feeder
guillaume.gastebois at free.fr schrieb:
Hello,
I'm back with my LiDE 90. No more significant result since month. I don't
know where to find.
Just a little question. I see in windows snoop that inversion bit is set in
frontend, not in sane.
Is it possible that this inversion has an effect
Tom Brush schrieb:
For a scanner-camera project featured in Make magazine, (
http://makezine.com/14/scannercamera/ ) the author uses SANE to bypass the
calibration step, because it would fail after his physical modifications to
the sensor. The model he uses is a Canon CanoScan LiDE 20. His
Roland Graf schrieb:
Hallo Pierre,
was it possible to decode my log?
Thanks
Roland
Hi Roland,
it decodes fine, but i need to find some time to put the test program
together. My scripts decode the usbsniff into some pseudo c-code, that
needs to be cleaned/modified to work.
Regards,
robert w hall schrieb:
In message 498B15E0.9070805 at pirsoft.dnsalias.org, Pierre Willenbrock
pierre at pirsoft.dnsalias.org writes
it decodes fine, but i need to find some time to put the test program
together. My scripts decode the usbsniff into some pseudo c-code, that
needs
Roland Graf schrieb:
Hallo Pierre,
the testprogram gives me only an:
roland roland # /home/roland/Doku/G4010/testprog
Fatal: Device not found!
roland roland #
With #lsusb I can see the scanner. I
Best regards
Roland
Hello Roland,
either my guess for your device-id was
off,
if needed.
Regards,
Pierre
Am Sonntag 08 Februar 2009 16:49:12 schrieb Pierre Willenbrock:
Roland Graf schrieb:
Hallo Pierre,
the testprogram gives me only an:
roland roland # /home/roland/Doku/G4010/testprog
Fatal: Device not found!
roland roland #
With #lsusb I can see
Hello,
stef schrieb:
I'm answering you through the mailing list since my private mail has
been
bounced back by some blacklisting system.
Sorry about that, looks like that blacklist is collecting more
legitimate smtp-servers than it used to. I removed it from my
mailserver-config.
Hi,
i added support for Ambir(Syscan) DocketPort 665 and Visioneer
Roadwarrior, thanks to the hardware donation of Jack McGill. Those two
use the same mainboard, only differently sized sensors. There may be
other models using this mainboard, and adding support should be simple.
Attached is a
Hi Jack,
Jack McGill schrieb:
To list and Pierre,
I recently received a Visioneer XP100, rev 3, usb vid x04a7 pid
0x049b, which has a GL842 chip inside. The model number on the
bottom of the scanner is 85-0110-200. This scanner works very well
using the Visioneer Roadwarrior settings. I
Charles Dahl schrieb:
Hi,
Just a quick line to see if anyone knows when this will be
accomplished? It seems this has been going on for quite a while.
CanoScan 8600FUSB 0x04a9/0x2229 Unsupported GL841 based, to
be
added to genesys backend
Hi Charles,
to my
Julien BLACHE schrieb:
Ilia Sotnikov hostcc at gmail.com wrote:
Hi,
** Updating scanners lists
From git://git.debian.org/sane/sane-backends
764aa7c..e232f54 master - origin/master
Updating 354b9a5..e232f54
backend/.gitignore: needs update
frontend/.gitignore: needs update
Ozan ?a?layan schrieb:
Hi,
I've just noticed that my Canon LiDE 50 is broken with sane-backends 1.0.20
(1.0.19 was OK). I've bisected it to:
Thanks for bisecting, but this bug should be fixed in git master. See
bug #311691.
Regards,
Pierre
Hi Sivananda,
sivananda schrieb:
Dear Mr. Pierre,
I have problem with CanoScan LiDE 100 to work with ubuntu. The reason
behind my worry is I have purchased these scanners( more than 5000
pieces) for school at very remote places but found not working. I got
your references from the
chrome://messenger/locale/messengercompose/composeMsgs.properties:
Hello Stef,
Thank you for your prompt reply.
Please find in the attachment the requested debug.log file.
Thank you in advance for your help, have a good day.
Hi Georg,
thanks for the log, this is a known and fixed bug.
stef schrieb:
Le mercredi 24 f?vrier 2010 03:00:16 Chris Berry, vous avez ?crit :
Hey Stef,
I think I have sorted out the white shading data but the black is still
a mystery. I have uploaded some files to the project site (here
http://sites.google.com/site/bez625/updates-1/update240210 )
Chris Berry schrieb:
On 02/24/2010 10:33 AM, Pierre Willenbrock wrote:
stef schrieb:
Le mercredi 24 f?vrier 2010 03:00:16 Chris Berry, vous avez ?crit :
Hey Stef,
I think I have sorted out the white shading data but the black is still
a mystery. I have uploaded some files
Gernot Hassenpflug schrieb:
On Thu, Feb 25, 2010 at 1:05 AM, m. allan noah kitno455 at gmail.com wrote:
Attached is a copy of a script I wrote that clears up these verbose
logs. I don't know if it is the most recent version, I cannot reach my
development machine, and i just found this copy
Gernot Hassenpflug schrieb:
On Thu, Feb 25, 2010 at 7:05 PM, Pierre Willenbrock
pierre at pirsoft.dnsalias.org wrote:
Gernot Hassenpflug schrieb:
On Thu, Feb 25, 2010 at 1:05 AM, m. allan noah kitno455 at gmail.com
wrote:
/../
Are endpoints apart from the default 0x able to have
stef schrieb:
Le mardi 2 mars 2010 16:40:21 Chris Berry, vous avez ?crit :
Hey guys, I resolved the issue I was having with the dark_shading
calibration. The lamp was turning off fine but the | REG03_LAMPPWR in
gl842_begin_scan was turning the light back on for the scan :/ . Having
resolved
m. allan noah schrieb:
On Mon, Apr 19, 2010 at 10:33 AM, Fabian Eichst?dt f.eichstaedt at fabz.de
wrote:
Hi all!
We recently aquired a Canon DR-2020U scanner and I tried to test it
with a recent sane git-snapshot. It compiled without problems and
I tried to use it with the canon_dr backend.
CCing sane-devel, as i don't really know the policy for the last item.
Gernot Hassenpflug schrieb:
Hello Pierre,
I attach the diff for the genesys doc/description/genesys.desc where I
added the LiDE40 as good (change from untested).
When sending patches, please use git format-patch, git
Jane85 schrieb:
I used 'export SANE_DEBUG_SANEI_USB=255' then retried 'scanimage ?d genesys
picture1.pnm'.
New log is attached. The file with the result of 'dmesg' is attached also.
Regards,
Jane.
http://old.nabble.com/file/p29211849/xeroxTS100.sanei.log
xeroxTS100.sanei.log
Jane85 schrieb:
There are two usb ports on my computer. I tried both ports, also I tried
another usb cable. If it is necessary I can attach the logs. But the new
logs are identical with the old logs.
I able to recompile sane-backends with a patch.
Regards,
Jane.
Okay, then please
This first puts a 27 Ohm resistor between USB power and non-gl841
electronics before actually directly connecting.
---
backend/genesys_gl841.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/backend/genesys_gl841.c b/backend/genesys_gl841.c
index 0a614fa..4a4fabf
Jane85 schrieb:
Pierre Willenbrock-2 wrote:
Okay, then please try the attached patch. If that works, try to reduce
the time in the usleep until it breaks again.
Regards,
Pierre
I copied the patch to the folder sane-backends-git20100716. Then I used:
$patch -p1 patch_name
Jane85 schrieb:
Pierre Willenbrock-2 wrote:
Oops, patch was wrong, used incorrect register. Please try the attached
patch(reverting the original one before). (Or manually replace the 6D/6d
by 6C/6c in the affected code.)
I tried the new patch. The new log seems very similar
Hi,
golan...@aol.com schrieb:
I made the changes you suggested and troubleshot a few things and got
the scanner to be found as a LiDE 60 with scanimage. I got an invalid
argument error when I tried to do 'scanimage image.pnm'.
Below is a debugging log after I issued 'export
Hello Parag,
Parag N() schrieb:
Hello,
On 12/29/05, Parag N() panem...@gmail.com wrote:
Hello Pierre,
[...]
here i am attaching my windows USB log + linux debug log where after
modification(i already mailed to list) + new frontend structre from my
windows log is
[0x01] =
Hi Aaron,
golan...@aol.com schrieb:
After patching the backend and a recompile I get the following when
attempting a 'scanimage image.pnm' :
[more log]
[sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 4, value = 131,
index =, len = 2
[sanei_usb] : 06 18
Parag N() schrieb:
Hello Pierre,
On 12/29/05, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Hello Parag,
[...]
--- genesys_gl646.c 2005-12-29 15:32:52.078821000 +0100
+++ genesys_gl646.c.patched 2005-12-29 15:30:29.209892250 +0100
@@ -1772,6 +1772,17 @@
return
Jean-Baka Domelevo schrieb:
[...]
Okay, I don't like the question mark after the name of the chip. On
the sane-project webpage listing the unsupported devices, it is said
probably a GL841, based upon a trial by sane-find-scanner, probably.
To make sure, the first thing I did after unpacking my
Jean-Baka Domelevo schrieb:
On 1/28/06, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
gl841 and gl842 are identical from the driver side. The genesys backend
works for my scanner which is a gl842 based Canon LiDE 35.
Hi Pierre,
I've downloaded the genesys files from the CVS
Hello
Jean-Baka Domelevo-Entfellner schrieb:
Following on my project to include support for the OpticFilm 7200 (by
Plustek) to the genesys backend, I have some questions to the
maintainer(s) of the latter:
1) Are the AFEs taken into account for the moment all made by Wolfson
? The
Hi Luke,
Luke Campagnola schrieb:
First I want to thank everybody for their great work on the genesys backend,
we really appreciate your hard work!
Now the complaining bit. I've been comparing the sane driver to the windows
driver and I've come up with a few notes:
- The windows driver
Hi all,
i am planning to complete the endian conversion code in the genesys backend.
I identified the following fields where endian conversion is neccessary:
Going down to scanner:
* slope tables
* shading tables
* gamma tables
The registers need to be addressed bytewise anyways, so they don't
Hi Jon,
Jon Chambers schrieb:
On Tue, 7 Mar 2006, Pierre Willenbrock wrote:
[...] I am planning to add a function that swaps the
bytes in place if needed which should be called on the pixel data.
You may find the byte ordering calls built into the socket library
(htons, htonl, etc) useful
St?phane VOLTZ schrieb:
I had to put an ifdef WORDS_BIGENDIAN (like for slope tables), so that
my
MD6471 could work again after the endianess changes you done.
To be exact, the code i used for gamma was meant to work for both
endianesses, but does not work for either.. I forgot to
Laurent Charpentier schrieb:
Hi Everyone,
I would like to submit a patch for the genesys backend (Canon LIDE 50). The
patch adds the threshold feature for black/white mode (in 1.0.17 the threshold
is set to 50% and can't be changed).
The attached patch is relative to sane-backends-1.0.17
Jeff Shrowder schrieb:
Michael and Pierre,
Looking through the archives I see a number of postings on developing a
driver for the Canon Canoscan LiDE 500F. How far did you get?
I didn't do any further work, apart from those postings. I don't know if
Michael made any progress.
If you are
Laurent Charpentier schrieb:
I would like to submit a patch for the genesys backend (Canon LIDE 50). The
patch adds the threshold feature for black/white mode (in 1.0.17 the threshold
is set to 50% and can't be changed).
The attached patch is relative to sane-backends-1.0.17 (files
Hi List,
as some of you may have noticed, the genesys backend now has the ability
to set a motor power level, leading to much quieter scans in high dpi
modes(if it is implemented for the scanner).
This feature is currently available in the experimental module, as the
settings for this new mode
Hi,
Parag N() schrieb:
Is that experimental module can be used with HP 2400 scanner also?
It can be used for development and other experimental code. So, yes, the
experimental cvs module can be used for developing support for the HP
2400 scanner. But no, there is no code supporting
Hi Gerald,
Gerald Murray schrieb:
Tested:
LiDE 35: 150,300,600,1200 using usb-1.1.
Motor ok. Scans at 150,300 are excellent quality.
At 600, 1200 minor image flaws: there is faint but noticable streaks
down the longest length of the image, from color reception or brightness
not being
Gerald Murray schrieb:
Quoting Pierre Willenbrock pie...@pirsoft.dnsalias.org:
Hi Gerald,
Gerald Murray schrieb:
Tested:
LiDE 35: 150,300,600,1200 using usb-1.1.
--snip--
That is probably a calibration problem. There is no easy way to fix
that. What helped Henning was to clean
Hi list,
i am trying to make the scanning speed of my scanner depend on the usb
speed available. I first attempted to use the detection from the cs3200f
backend, but found that it only detects if the device is high speed
capable, not if it is currently communicating with high speed.
On further
Hi Ralph,
Ralph Sontag schrieb:
I have an Canon CanoScan LiDE 500F.
I've added in backend/genesys_devices.c a section as a copy from
the LiDE 60 - ok, now scanimage list the device:
scanimage -L
device `genesys:libusb:001:050' is a Canon LiDE 500F flatbed scanner
But it don't
...
Name: canon-500f.diff
Type: text/x-patch
Size: 26419 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060512/6ada0c43/canon-500f-0001.bin
From pie...@pirsoft.dnsalias.org Fri May 12 21:18:52 2006
From: pie...@pirsoft.dnsalias.org (Pierre Willenbrock
Hi Ralph,
Ralph Sontag schrieb:
These scanners are pretty low-level. To do anything useful, you need to
setup the motor and ccd. This includes calibration. The calibration is
done only once in win98.
So I will setup win98 once again and made a start the sniffer before the
first connect.
Hi Ralph,
Ralph Sontag schrieb:
Hi Pierre,
I put my scripts here:
http://pirsoft-dsl-dropzone.de
I made a new scan:
0 .. ~ 5 MB : USB starts
5 .. ~ 15 MB : ScanGear - the Canon-Program starts
15 .. ~ 110 MB : Calibration.
110 .. ~ 200 MB : Scan (visiting card, 300, ca. 1.5
Hi Henrik
Henrik Uggla schrieb:
I've got a Canoscan Lide 50. I have discovered that when I scan at 150
dpi or more the greys are missing in depth (in the black end). But when
I scan at only 75 dpi the result looks much better since darker and
lighter pixels are mixed to show the right grey
Jaagup Rep?n schrieb:
Jaagup Rep?n wrote:
Hello.
I have Canon 4400F scanner. This is not supported, but it must to be
added to genesys backend. I am trying to add, but I need help. I
have to find SENSOR, DAC, GPO and motor type, shading and search lines,
start of scan area, white strip and
Maximilian Fabricius schrieb:
Hi all,
I have been working on trying to get the OpticSlim 2420 to work.
Is disassembled the scanner (hardware) and made pictures. they may be
found here
http://rosa.physik.tu-berlin.de/~mxhf/OS2420/
They are fairly high resolution ~1MB per image so that
Maximilian Fabricius schrieb:
On 1/1/07, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Maximilian Fabricius schrieb:
Hi all,
I have been working on trying to get the OpticSlim 2420 to work.
Is disassembled the scanner (hardware) and made pictures. they may be
found here
colors, use SANE_DEBUG_GENESYS=255 and
SANE_DEBUG_GENESYS_GL841=255 with scanimage in color mode, and send the
resulting error output and the generated .pnms.
Regards,
Pierre
On 3/7/06, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
- Color reproduction is better with the sane driver
there.. the darks may be slightly better but now the
lights are clipped too. I've attached output + pnms.
Thanks.
On 1/4/07, Pierre Willenbrock pie...@pirsoft.dnsalias.org wrote:
Luke Campagnola schrieb:
It's been a while since I originally brought this up, but I've pulled
out
the ol' scanner
Pierre Willenbrock schrieb:
Luke Campagnola schrieb:
It's been a while since I originally brought this up, but I've pulled out
the ol' scanner for another go.
to recap: color calibration isn't quite right on my canon lide35--the dark
colors drop out to black. I turned
Hi Igncio,
J. Ignacio Gij?n schrieb:
Sorry if you receive this message twice, I sent a similar one
yesterday but it looks
like it is lost.
It is right there.
My question es about the HP G4050 scanner that uses a gl843 chip. I
have had
one of this for a couple of weeks now, and have been
Ren? Kjellerup schrieb:
Hi' all,
Now I've made a few logs, and I've come across something
odd.
I start the sniffer, then open the preview/scanning
interface from my photo editor (PS7).
And when it's running, the sniffer just stops getting any
more packets even when scanning an image
kent whitten schrieb:
I'm trying to get this going, and could use any hints
what the gpio pins might be used for. This guy has
lots more pins set for output, than any other genesys
device. I'm actually scanning, but getting nothing
back but zeros, so I'm taking all 200 passes in
Mohammad Tabbara schrieb:
Hi all,
I've installed backends 1.0.18 on debian etch on arm and have a Canon
Lide 50 attached that is detected by the backend but results in a seg
fault when trying to scan. I've tried the various combinations of the
following:
pre-built debian packages
1 - 100 of 182 matches
Mail list logo
