?
Regards,
Pierre
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send
.
Regards,
Pierre
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
On 02/15/2017 11:19 AM, Johannes Meixner wrote:
On Feb 12 19:33 Pierre Couderc wrote (excerpt):
... my USBs are USB2 ...
[genesys] genesys_flatbed_calibration:
led calibration failed: Error during device I/O
I don't know any details about the genesys driver/backend
but I guess it i
On 02/09/2017 01:49 PM, Johannes Meixner wrote:
See "Trouble-Shooting (Debugging)" at
https://en.opensuse.org/SDB:Configuring_Scanners
Thank you, after many trials, I am sure that my USBs are USB2, that the
scanner works with Windows.
So I thnk there is a problem with genesys handler. I have
Thank you. I shall search in this direction.
Anyway, the computer seems too old to have USB3... (BIOS 2002... ?).
On 02/09/2017 01:49 PM, Johannes Meixner wrote:
Hello,
On Feb 9 12:29 Pierre Couderc wrote (excerpt):
env SANE_DEBUG_DLL=255 scanimage ...
...
[dll] ...
...
Is there a way to
calling backend `genesys's exit function
[dll] sane_exit: finished
Is there a way to have more information...?
Thanks
Pierre Couderc
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: S
Dears,
(sane-backends git version from yesterday)
I'm able to scan (and preview) at 300dpi a full page
But not at 600dpi and not if I restrict the area to a smaller part!
I will try to follow the situation.
At the mmoment on my debian-jessie I had to manually moves all the
libsane stuff from
That worked ! Thanks !! :-D
For your information: epkowa.conf was missing in /etc/sane.d installed by the
git version. I had to copy it from my previous ubuntu install.
Thank you again !!! (Happy!)
Le Mardi 18 novembre 2014 0h49, Olaf Meeuwissen a
écrit :
Hi Pierre,
I've seen
an on
https://gist.github.com/lindenb/bc7b85f7a4bf71ff500f
iscan failed . Again, I noticed a few binary chars in the trace.
Pierre
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject
dev/bus/usb
$ ls -la /dev/bus/usb/002/
total 0
drwxr-xr-x 2 root root 80 Nov 17 17:52 .
drwxr-xr-x 9 root root 180 Nov 17 17:52 ..
crw-rw-r-- 1 root root 189, 128 Nov 17 18:34 001
crw-rw-r-- 1 root root 189, 130 Nov 17 18:34 003
thank you for your help.
Pierre
--
sane-devel m
Did you install the non-free plugin that is needed for the Perfection
3170?
Yes see above, I'm not sure what you meant by non-free: the plugin is available
for download from epson.com
> Is it found by the backend?
how can I check this ?
Thank you for your help,
Pierre
-
initializing backend `net'
[dll] init: backend `net' is version 1.0.25
[dll] sane_get_devices: found 1 devices
any idea ?
P.
Le Samedi 15 novembre 2014 12h44, Guillaume Courtois a écrit
:
Hi Pierre,
Seems like we know each other :-) It's a small world after all !
Did you
ng to load `/usr/lib/i386-linux-gnu/sane/libsane-hpaio.so.1'
[dll] load: couldn't open `/usr/lib/i386-linux-gnu/sane/libsane-hpaio.so.1' (No
such file or directory)
[dll] load: trying to load `/usr/lib/sane/libsane-hpaio.so.1'
[dll] load: dlopen()ing `/usr/lib/sane/libsane-hpaio.so.1&#
Jane85 schrieb:
>
>
>
> Pierre Willenbrock-2 wrote:
>>
>>
>> Okay, i am officially out of ideas. To me, this looks very much like
>> defective hardware.
>>
>> Does this scanner work with any other systems, for example with the
>&g
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.)
>>
>
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
ards,
> Jane.
Okay, then please try the attached patch. If that works, try to reduce
the time in the usleep until it breaks again.
Regards,
Pierre
-- next part --
An embedded and charset-unspecified text was scrubbed...
Name: 0001-Try-to-reduce-current-inrush-of-D
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 1
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 1
erent usb port and a different cable?
If that fails, are you able to recompile sane-backends with a small patch?
Regards,
Pierre
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
ight place. This
machine has a register space going up to (at least) register 0xff, so it
is not one of the currently supported chip versions. Also, my script
finds at least one unknown control transfer.
Regards,
Pierre
e the temporary files subdirectory (the multipage project)
after creation of the multipage file to reduce disk usage!
---
Things would even be clearer if the word "project" disappeared being
everywhere replaced by "temporary files subdirectory".
With hope this message will receive some attention,
Cheerfully,
Pierre Pietri
Paris - France
mailto: pf.pietri at free.fr
nky' format (for CCD) was needed.
> Surely an issue in the genesys_send_shading_coefficient() where
> compute_coefficient() is for chunky, compute_planar_coefficient() is for
> planar and the CCD_CANONLIDE35 case looks for the planar case to me. Pierre
> may confirm this last point.
Gernot Hassenpflug schrieb:
> On Thu, Feb 25, 2010 at 7:05 PM, Pierre Willenbrock
> wrote:
>> Gernot Hassenpflug schrieb:
>>> On Thu, Feb 25, 2010 at 1:05 AM, m. allan noah
>>> wrote:
>>> /../
>>> Are endpoints apart from the default 0x000
t; direction.
>
> So I expected a URB "coming back" to contain a TransferFlags with
> DIRECTION_IN, but often it has instead DIRECTION_OUT. Is that
> relevant?
This is just the USB Request Block(URB) that goes down to the lower
levels of the usb stack and coming back from there. It is just the same
URB going through usbsnoop in different directions, as evidenced by the
same URB number. Remember that usbsnoop sits in the stack and acts like
a filter, and that urb processing happens asynchronously.
Regards,
Pierre
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
g data will be taken from
> an all white area and black data will be inferred from the small black areas
> still in the picture.
>
GENESYS_FLAG_DARK_WHITE_CALIBRATION is just a way to scan the black and
white strip in one go. Chris, you should try to figure out if the
backend goes through genesys_dark_shading_calibration with
GENESYS_FLAG_DARK_CALIBRATION, and if so, why the lamp does not switch off.
Regards,
Pierre
, this is a known and fixed bug. Either use sane
1.0.19 or git, any commit after 2009-06-03. You can also try to only
patch commit a0ea955e91837156d2112c0ffd12c8afebe86efa into your local
copy. The latter two solutions require to recompile sane-backends.
Regards,
Pierre
I would apreciate if dcp 7030 Brother will wull be added in libsane rules
Thanks
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 r
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
sanei/test_wire.c | 12 +-
> tools/check-usb-chip.c|2 +-
> 92 files changed, 1110 insertions(+), 949 deletions(-)
> create mode 100644 backend/genesys_gl646.h
> chgrp: changing group of
> `/org/alioth.debian.org/chroot/home/groups/sane/lists/sane-backends-external.html':
> Operation not permitted
> chgrp: changing group of
> `/org/alioth.debian.org/chroot/home/groups/sane/lists/sane-backends-cvs.html':
> Operation not permitted
> chgrp: changing group of
> `/org/alioth.debian.org/chroot/home/groups/sane/lists/sane-mfgs-cvs.html':
> Operation not permitted
> chgrp: changing group of
> `/org/alioth.debian.org/chroot/home/groups/sane/lists': Operation not
> permitted
> error: hooks/post-receive exited with error code 1
Regards,
Pierre
d
>
Hi Charles,
to my knowledge, no work to support the CanoScan 8600F has been done,
yet. There are a few GL841-based scanners supported by the genesys
backend, but i'd guess none of them is compatible with the 8600F.
Regards,
Pierre
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 Vis
,
Pierre
-- next part --
A non-text attachment was scrubbed...
Name: syscan.jpg
Type: image/jpeg
Size: 11296 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20090302/a4ce8802/attachment.jpg
oing to push the three in the original mail today, and merge
the rest of my changes later this week.
Regards,
Pierre
Hello Roland,
Roland Graf schrieb:
> Hello Pierre,
>
> I tried the testprog under root. I think in root I must have the permission
> for the device. I controlled the the line 86 for the device and vendor ID.
> The
> vendor ID and the device ID are correct.
>
> E
ouble-width sensor.
Regards,
Pierre
PS1: don't try to test this on current cvs -- at least for me, it
creates libsane-*.so.0.1.0, instead of libsane-*.so.1.1.0.
PS2: Sorry Jack, but the XP300 was far more interesting than the
Roadwarrior ;-) -- i am working on it.
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 Rola
robert w hall schrieb:
> In message <498B15E0.9070805 at pirsoft.dnsalias.org>, Pierre Willenbrock
> 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
>> nee
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
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 "
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.
l struct and try if that works.
Regards,
Pierre
objects, i will commit this in about 2 days.
Regards,
Pierre
-- next part --
A non-text attachment was scrubbed...
Name: sane-build-fixes.diff
Type: text/x-patch
Size: 1341 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/sane-devel/attachments
m. allan noah schrieb:
> On Sat, Jan 10, 2009 at 2:55 PM, Pierre Willenbrock
> wrote:
>> m. allan noah schrieb:
>>> On Sat, Jan 10, 2009 at 1:11 PM, Pierre Willenbrock
>>> wrote:
>>>> m. allan noah schrieb:
>>>>> On Fri
m. allan noah schrieb:
> On Sat, Jan 10, 2009 at 1:11 PM, Pierre Willenbrock
> wrote:
>> m. allan noah schrieb:
>>> On Fri, Jan 9, 2009 at 5:02 PM, Pierre Willenbrock
>>> wrote:
>> [...]
>>>> Another question: Is it okay to only look at the hardwa
m. allan noah schrieb:
> On Fri, Jan 9, 2009 at 5:02 PM, Pierre Willenbrock
> 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
m. allan noah schrieb:
> On Wed, Jan 7, 2009 at 1:09 PM, Pierre Willenbrock
> 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:
>
polling in a thread.
I have no experience with the sane interface itself, so comments/patches
are gladly accepted.
Regards,
Pierre
LAMP
You may need to change values on lines 100, 101 in genesys_devices.c.
Those are the analog offset(line 100) and gain(line 101), in hexadecimal.
Regards,
Pierre
hank you).
> They can be found at :
> http://ggastebois.free.fr/lide90_snoop/UsbSnoop_600_216x17.4_nocal.log and
> http://ggastebois.free.fr/lide90_snoop/UsbSnoop_600_216x17.4_nocal_parsed.log
> (be carefull with headake !)
>
> Regards
> Guillaume
>
Regards,
Pierre
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 f
ets commited,
because it would reduce the number of calibrations to at most 2.
(Currently it is in the experimental repository, and i could not get
myself to add support in the gl646-part, yet.)
> Regards
> Guillaume
Regards,
Pierre
m could not be coaxed to deliver data.
> Keith Harwood.
Regards,
Pierre
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 s
ng the previously setup
registers. All of these call gl841_init_scan_regs and gl841_feed to get
their work done, but the register set can be modified after that call.
The initial bit-fiddling (if needed) happens in gl841_init_registers,
starting off from the values stored in genesys_devices.c:
static Genesys_Gpo Gpo[].
> Regards
> Guillaume
Regards,
Pierre
> scan, at least the Mac driver for the Canon Lide 70 does
> only calibrate once after unpacking.
>
> Yours,
>
Regards,
Pierre
h out on one.
The genesys based LiDE 60 has some calibration quality problems(I.e. it
is good enough, but could be better).
>In general, it would be nice if the scanner support table showed such
> information very briefly for all scanners with a "good" rating.
>
> Regards,
> David
Regards,
Pierre
nd two clock
pulses, for example 0x001c7. If clk3 is connected to the ccd, this may
give interesting results(like, reducing the resolution by half), but for
the 4-bit latch/D-FlipFlop, only the last clock pulse before the gl841
samples the data bits is relevant.
> regards,
> Guillaume
Regards,
Pierre
g2[1]=0x09,reg2[2]=?,
>
> I anybody able to replace "?" and/or correct mistakes in text before ?
There are some AFEs that use these registers, and some, that don't. If
the windows driver does not set them, most likely they are not
used/defined and ignored by the AFE. So it should be safe to set them to 0.
> Thanks
>
> Regards
> Guillaume
Regards,
Pierre
gt; DPIHW is set for the 2400dpi mode.
>> When that works, figure out how to setup gpios for half_ccd mode. From
>> the view of the current code base, you are done here. You can try to
>> find a quarter_ccd mode(which would show up as half-width in the
>> half_ccd modes), and
de(which would show up as half-width in the
half_ccd modes), and leave a comment in the code, or even implement the
quarter_ccd mode for real.
Regards,
Pierre
ge data.
>>> in genesys_gl841.c line ~2053 I had image compressed x2 in the left and
>>> second right part black with 0x6c=12 and not with 0x6c=1a. Strange.
>>>
>>> I decided to comment out these lines yet for tests.
>>>
>>> In genesys_841.c I see conditions with GPO_CANONLIDE35 for gl841_feed
>>> function (lines ~4309 and ~4913). I added GPO_CANONLIDE90 too. What is
>>> this function for ? Is it usefull to add lide 90 ?
>> no, these don't help your scanner. the feed is used to position the
>> scanning head at the white calibration strip. This is(should not) be
>> needed for your scanner.
>>
>
> Regards
> Guillaume
>
Regards,
Pierre
off 0x6c. I think looking at
> 0x6c=32 or 3a is very interesting.
>
> Why sane always produces black images with same 0x1a value as windows
> driver
>
> Regards
> Guillaume
>
> ps. : Pierre can you send me a sample entropy processed offset image to
> see what I must obtain. Thank you.
lses to move the
electrical charges. No charge means black pixel. It should be possible
to simulate the behavior when the clock generators are switched to
"automatic", but this default behavior is not well documented.
> Regards
> Guillaume
>
> ps. : Pierre can you send me
black led selectors, of which the
latter is not needed(At least my scanner does not need it, even when
doing black-level calibration on a white target).
> Thank you.
>
> Regards
> Guillaume
Regards,
Pierre
Pierre Willenbrock schrieb:
>
> Now for the real reason i am answering: I did play around with my
> scanner, trying to get the shading calibration to work only on the white
> strip. The trick was to do a real scan over the white strip, not just
> sampling a single line over
Hi Guillaume,
Sorry for not answering sooner.
Guillaume Gastebois schrieb:
> Hello,
>
> Selon Pierre Willenbrock :
>> Guillaume Gastebois schrieb:
>>> > Hello,
>>> > > Yesterday I added CCD_CANONLIDE90 in genesys.c. I did two
>>> successi
hich log seeems to be the best for calibration ? (in
> 3_test1.txt, I see device I/O errors !!!)
> What are good values for offset_calibration: black/white pixels ?
>
> Another thing : Pierre, you send me few weeks ago a code named entropy2D.c. I
> compile it with : gcc -c
Guillaume Gastebois schrieb:
> Hello,
>
> Pierre Willenbrock a ?crit :
>> Guillaume Gastebois schrieb:
>> > Hello,
>> >
>> > You can find attached a patch which works like my original code (with
>> > different contrast and calibration betw
Ralf Haueisen schrieb:
> I tried again, an now not even pressing a button help.
> What code do you need, and how can i get it?
>
Please try the patch from Guillaume Gastebois.
Regards,
Pierre
e reason. I don't know what causes that.
May be a power issue, depending on correctly setting the gpios or sth
like that.
> Regards
> Guillaume
Regards,
Pierre
Guillaume Gastebois schrieb:
> Hello,
>
>
> > > Volker Grabsch schrieb:
> > > > > On Wed, Mar 19, 2008 at 03:24:45PM +0100, Pierre Willenbrock wrote:
> >> > > >> + ,
> >> > > >> + /* CANONLIDE90 */
> >> &
verything as root, so acces-rights should not be the reason.
>
> Ralf
>
Does scanimage -L list the scanner? If not, i need to look deeper into
the probing-code..
Regards,
Pierre
Volker Grabsch schrieb:
> On Wed, Mar 19, 2008 at 03:24:45PM +0100, Pierre Willenbrock wrote:
>> + ,
>> + /* CANONLIDE90 */
>> + {
>> +/*
>> +00 :
>> +02 : image ?? la con et inverse video
>> +0a : image ?? la con et inverse video et moteur ne
Hi Guillaume,
Pierre Willenbrock schrieb:
> Guillaume Gastebois schrieb:
>> Pierre Willenbrock schrieb:
>>> But this seems to be basically working. Please send your changes leading
>>> to a usable scan, so i can integrate them.
>> For now, my code is ugly. I on
at this helps at all.
> I tryed that (upper threshold to 1500 and lower to 250 and it doesn't
> work. You can find the same test as test2 without the same result on :
> http://ggastebois.free.fr/lide90_snoop/10_test2b.tar (I just make two
> consecutive scanimage without recompiling sane).
That is not unexpected.
> One other thing : we can see vertical lines with different contrast on
> result images. What is it ?
The shading correction not doing its work correctly. I see similar
behavior when using the method of scanning a single line multiple times
with/without lights for acquisition of dark/bright levels. I don't see
this when using a scan over my black+white calibration area. Currently,
i don't know what causes this difference.
> Regards
> Guillaume
Regards,
Pierre
ase send your changes leading
to a usable scan, so i can integrate them.
Regards,
Pierre
> Regards
> Guillaume
>
> Pierre Willenbrock a ?crit :
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> I modified these registers. But the scanner locks writ
I'd play around with different sets of
registers and see if they work. But i guess, register 0x1a is a key to
get the rest working.
> I will be long for next answer as I take one week holidays !
I hope you had a nice week holidays.
Regards,
Pierre
> regards
> Guillaume
>
>
here are no plans to add a genesys_gl842.c, as the GL842 is essentially
the same as the GL841. This is not true for the GL843, but it is similar
to the GL841/2, so the genesys_gl841.c may be a good starting point.
Regards,
Pierre
Pierre Willenbrock schrieb:
> 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
>
> Further, we need to figure out a way to get the LEDs go completely dark.
> 0x101 is just about half of 675. I will experiment a bit with my
> scanner, to find out if the gl842 can do that.
>
cvs now gives completely dark LEDs when needed.
Regards,
Pierre
pr * 2000) / avge;
expg = (expg * 2000) / avge;
expb = (expb * 2000) / avge;
Reducing the lower threshold may be needed, too. The current values for
your scanner are:
expr: 1235
expg: 1235
expb: 675
No guarantee that this helps at all.
> Regards
> Guillaume
Further, we need to figure out a way to get the LEDs go completely dark.
0x101 is just about half of 675. I will experiment a bit with my
scanner, to find out if the gl842 can do that.
Regards,
Pierre
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 a ?crit :
>> Pierre Willenbrock schrieb:
>>> Hi,
>>>
>>> Guillaume Gastebois
Guillaume Gastebois schrieb:
> Hello,
>
> Selon Pierre Willenbrock :
>
>> Hi,
>>
>> Guillaume Gastebois schrieb:
>>> Hello,
>>>
>>> So, what's the next step ? Re-enabling shading ?
>> Yes, but only after the shading-calibr
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.
et1_0.pnm is only black).
The image should show a fuzzy vertical and horizontal bar, near
top/left. Currently, the horizontal bar is more a line, the vertical bar
is correct(it shows the relationship between the low byte of one pixel
and the high byte of the _next_ pixel).
> Regards
> Guillaume
idn't realize until just now. I
missed 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
>
&
em(misplaced
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.
Guillaume Gastebois schrieb:
> Hello,
>
> OK, I'll try this tonight. What is the best : WITH or WITHOUT
> SCAN_FLAG_DISABLE_LAMP ?
Not using SCAN_FLAG_DISABLE_LAMP is a bit counter productive when trying
to get black levels on a white-only calibration area.
Regards,
Pie
4596 and 4712:
- for (i = 0; i < num_pixels; i++)
+ for (i = 150; i < num_pixels; i++)
{
if (dev->model->is_cis)
val =
Regards,
Pierre
re the lower 3
bits). We may be sampling the digital image data at the wrong times. As
the most significant byte seems to come through correctly, this does not
need immediate fixing. (On a second thought, this may affect the offset
calibration. See the thesholds. We'll see.)
Regards,
Pierre
ontend setup register 1 set to 3:
{0x00, 0x3f, 0x03, 0x26},
...
And, while you are at it, try if you can get setup register 2, bits 0+1
set to 0 to work. that may affect the position of the data, so you may
need to fiddle with gl842 registers 0x52-0x57.
> Regards
> Guillaume
Regards,
Pierre
m/_en/product_01_1.php?id=44
> Cheers,
> Vidar
Regards,
Pierre
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 retr
er random manner. The calibration
expects a linear relationship.
Regards,
Pierre
ge. when running scanimage with the two
debug environment variables set to 255, you get a set of calibration
files(*.pnm). Please put them together with the error-output of the run
into some kind of compressed archive(compressed .tar or .zip). Put them
online or send them here(but i doubt they are < 37k).
Thanks,
Pierre
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 d
1 - 100 of 241 matches
Mail list logo
