Why don't you change gamma, to dust off?
Georges
Laurent-jan wrote:
Hi,
I am now able to dust-off my slides when scanning with the
coolscan2-backend. I use a combination of the original dust-off plugin
from Andreas and a little fu-script (which looks a bit like the one I
posted
It works quite nice, though still not perfect. You can get a complete
tar from my homepage (www.xs4all.nl/~ljm).
I'm afraid the tar link doesn't work for me: The requested URL
/~ljm/dirtyduster.tar was not found on this server.
Andras
Hi Rob,
On Monday, May 19, 2003 at 20:20:10, rob wrote:
: Hi,
:
: I've just discovered that scanning crashes the usb system. What I get in
: syslog is this message:
: [snip]
: The command used is:
:
: scanimage --focus-position 'Focus 2.5mm above glass' --source
: 'Transparency Unit' --mode
Hi,
I'm sending a cc to the sane-devel mailing list.
On Mon, May 19, 2003 at 11:04:46PM +0700, T.M.Thanh wrote:
Does sane-find-scanner fin the scanner? If not, it's a kernel issue.
I think so but do not know exactly what it is. Probably due to the
kernel 2.4.x load modules dynamically.
So
On Tue, 2003-05-20 at 02:55, Gene Heskett wrote:
On Monday 19 May 2003 15:20, rob wrote:
Hi,
I've just discovered that scanning crashes the usb system. What I
get in syslog is this message:
May 19 19:53:03 samantha kernel: uhci.c: a400: host system error,
PCI problems?
May 19 19:53:03
Why did the original message refer to (firewire)? Does scanning via
the IEEE-1394 interface screw up your USB devices? This should not happen,
and if it does, it's definitely not Sane's fault. If you have the scanner
connected on both the USB and the FireWire bus, remove one connection.
This is
Can anyone point me at a sane small light USB (ideally bus-powered) scanner,
that can actually saturate the USB1.1 bus, with scan times at 300dpi
8 bit grayscale of say 10 seconds.
Or is this another thing I need to add into the CCD driver I'm
building (for other purposes)
georges.r...@pacageek.org said:
Why don't you change gamma, to dust off?
That shows a profound lack of understanding of what is going on.
Changing the gamma setting is *not* the same as using a separate
infrared scan of the image to find out where the dust is, and then
using a special algorithm
On Tuesday, May 20, 2003 at 07:28:28, k...@khk.net wrote:
:
: The TPU is not the cause for the problems: It may trigger the problem,
: but it's not the root cause. When you scan using the TPU, it takes a lot
: longer until the first data is sent from the scanner, therefore, the USB
: system runs
ONe thing you could try is to get rid of the scanner.o driver completely
and use libusb. One way to accomplish this is to manually remove the
scanner driver (rmmod scanner.o). Then edit the epson.conf file and
put a comment sign (#) in front of your usb /dev/... line and add
a new line that just
On Tuesday 20 May 2003 06:38, rob wrote:
On Tue, 2003-05-20 at 02:55, Gene Heskett wrote:
On Monday 19 May 2003 15:20, rob wrote:
Hi,
I've just discovered that scanning crashes the usb system. What
I get in syslog is this message:
May 19 19:53:03 samantha kernel: uhci.c: a400: host
Hi,
On Tue, May 20, 2003 at 02:50:01PM +0200, Roberto Lumbreras wrote:
Well, I've set the timeout to 300 seconds, with modprobe scanner
read_timeout=300 and it doesn't solve it. The following happened when
I tried to use the TPU of my Epson Perfection 2400 Photo (xsane died and
oopsed).
The
Gerhard (and anyone else interested in the matter),
At this point (apologies for slowness, but it isn't my scanner) my friend
has run check-usb-scanner on his Artec 1236USB and captured the output to
a log file. Here is the result which unfortunately seems to me rather
negative.
Of course, it
Hello Henning,
I've discovered that a change I made in the umax_pp backend prevent it
to work in many
settings (clearing epp timeout). I'm going to revert it by tomorrow morning.
Regards,
Stef
14 matches
Mail list logo
