[sane-devel] OT: list for discussing scanners in general ?

2011-07-14 Thread Pete Lancashire
Is there a list for discussing the scanners ? For example I'm looking
for a scanner that will do a sheet size of 12 x 18

-pete



[sane-devel] Proposed patch for scanimage in sane-backends-1.0.22

2011-06-26 Thread Pete Lancashire
Does the backend for your scanner have a wait for button option ?

Thats what I use, just wish my scanner had a jack on the back that let
me plug in
a foot switch. I'm marking off the days till the resellers warranty
runs out so I can
add one myself.

On Sun, Jun 26, 2011 at 3:58 AM, Yoann Seeleuthner yogos2 at gmail.com wrote:
 Hello,

 I would like to suggest a patch to add a new option to scanimage.
 The idea is to allow user to sleep scanner for a time between two scans in
 batch mode.

 I did this patch because I wanted to scan a book manually, and batch mode
 was too fast (not enough time to turn page), whereas a script looping on
 normal mode was too slow (at least 6 seconds between two scans with my
 scanner).
 So this patch add an option (--batch-delay=INT) that sleep scanimage for INT
 seconds.

 This patch have been generated on sane-backends-1.0.22 with diff -cr
 sane-backends-1.0.22-old/ sane-backends-1.0.22/  patch.diff

 I hope you will accept it.

 Best regards.

 Yoann

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org




[sane-devel] sane-find-scanner changes /proc/scsi/sg_def_reserved_size !

2011-06-18 Thread Pete Lancashire
as root

# echo 262144  /proc/scsi/sg/def_reserved_size

# cat /proc/scsi/sg/def_reserved_size
262144

as non-root user

[root at localhost ram0]# su - pete
[pete at localhost ~]$ cat /proc/scsi/sg/def_reserved_size
262144
$ sane-find-scanner -q
found SCSI processor EPSON SCANNER GT-3 1.53 at /dev/sg1
[pete at localhost ~]$ cat /proc/scsi/sg/def_reserved_size
32768

what gives ?

This is sane-find-scanner from sane-backends 1.0.22



[sane-devel] 90% off topic - color / gray test strip

2011-06-14 Thread Pete Lancashire
I was thinking of having a strip on each side of the scanned
documents, one for color
and one for gray-scale but I'll admint it is a bit overkill.

 I've been looking at the different IT8 targets.

I'll go with getting a Kodak one. It seems it varies quite a bit. but
the price is reasonable.

If anyone else is interested two URLs

http://www.colorwiki.com/wiki/Test_Images and
http://www.colorwiki.com/wiki/Kodak_IT8_%28Q60%29_Targets

http://www.computer-darkroom.com/it8cal/it8_page_1.htm
http://www.computer-darkroom.com/gamma/gamma_1.htm

another source of targets

http://www.targets.coloraid.de/

-pete









On Tue, Jun 14, 2011 at 6:37 AM, m. allan noah kitno455 at gmail.com wrote:
 Do they really need to be strips? If not, you might get a color
 scanning calibration target from someone like kodak.

 allan

 On Mon, Jun 13, 2011 at 3:48 PM, Pete Lancashire
 pete at petelancashire.com wrote:
 I'm looking for a strip or two strips one that is for color correction
 and one for grays. I saw such on each side of a drum scanner
 they looked to be about 1/4 wide.

 Idea's or pointers to where can ask

 thanks

 -pete

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org




 --
 The truth is an offense, but not a sin

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org




[sane-devel] 90% off topic - color / gray test strip

2011-06-13 Thread Pete Lancashire
I'm looking for a strip or two strips one that is for color correction
and one for grays. I saw such on each side of a drum scanner
they looked to be about 1/4 wide.

Idea's or pointers to where can ask

thanks

-pete



[sane-devel] Gt-30000 and epkowa - Was Fwd: sanner still jogs - more buffering ?

2011-06-08 Thread Pete Lancashire
My goal is something close to the advertised speed (8.058 seconds per page).
I would be happy with say 10 seconds which is 24% slower. Would be OK at
say 12 seconds which is almost 50% slower.

Will 15 to 17 seconds work, yes. but 85% to 120% slower then advertised
really hurts when ones ability to win contracts is based on ones reputation.

It is a pity the electronics in the GT-3 are a bit 'old'. What
would make this
pretty much the perfect scanner would be a new board with 1-2 GB of RAM and
a 1,000 MB/s Ethernet interface. Today building a dedicated controller costs no
more to have 1 GB then 128 MB. The last design I did using a single
commodity DDR-2 (or 3) memory module  plus its connector cost less then
512 MB of non commodity memory. 1,000 MB/s Ethernet today is basically free.
The only thing I would change in the scanner deck is from a CFL to LEDs.

Call it the GT-3E5 (GT-30) and Epson would have a winner.

-pete

PS Many years ago I worked for a company under Seikosha and the mechanical
part of our product was made by Epson.





On Tue, Jun 7, 2011 at 6:11 PM, Olaf Meeuwissen
olaf.meeuwissen at avasys.jp wrote:
 Please keep this on the mailing list. ?That way it will get archived and
 be searchable for everyone.

 Pete Lancashire pete at petelancashire.com writes:

 Here's the logs and some more information

 Your logs indicate that the epkowa backend is not limiting the size of
 its internal buffer to 32kb, so that shouldn't be the issue.

 If you want to make real, real sure, modify the epkowa backend source
 code at the end of backend/channel-scsi.c to read

 ?static size_t
 ?channel_scsi_max_request_size (const channel *self)
 ?{
 ? ?size_t max_request_size = sanei_scsi_max_request_size;
 ? ?if (getenv (SANE_SG_BUFFERSIZE))
 ? ? ?{
 ? ? ? ?max_request_size = atoi (getenv (SANE_SG_BUFFERSIZE));
 ? ? ?}
 ? ?return max_request_size;
 ?}

 and set the SANE_SG_BUFFERSIZE to, say, 1MB.

 I only got a chance to test a few things last night

 the log you requested is attached as scsi-debug.log, the other log
 file called just log is debug set at 4 and with SANE_SG_BUFFERSIZE set
 to 1048576 ( 1 meg), the size changed in the log file, but not to 1
 MB. I did not try making the SANE_SG_BUFFERSIZE bigger, ran out of
 time.

 Another non sane/epokwa issue is when I set
 /proc/scsi/sg/def_reserved_size to 1048576 anytime i run scanimage it
 resets back to 32768. Not sure what is going on there. I did not have
 time to try a smaller size.

 No clues on that here either.

 On a side note I've got a ticket open with Epson, basically all the
 literature on the GT-3 says that its SCSI interface supports
 SCSI-2 and SCSI-3.

 The specs on www.epson.com say that SCSI: Requires ASPI-compliant
 compatible SCSI 2 or SCSI 3 PCI card and cable (not included). ?My
 interpretation of that is that you can connect it to a SCSI-3 card and
 it'll work, not that it'll necessarily work at SCSI-3 specifications,
 let alone at the (theoretical) maximum band width.

 Going by the response from support, it is now confirmed the interface
 is SCSI-2 ONLY and that using the wide connector the maximum (raw my
 word) data rate is 20 MBytes per second, and thats a Megabyte being
 1,000,000 bytes. SCSI-2 is based on a 10 Megahertz clock so the real
 raw rate for a wide port is 20,000,000 bytes per second. The scanner
 in color mode is suppose to do 0.79 milliseconds per line or 9.079
 seconds per page.

 I only get to 8.058 seconds per page (and you did too, earlier).
 17 inches at 600 dpi with 0.79ms per line.

 A full page at 600 dpi, color is 214,812,000 bytes, which is
 23,662.921 bytes per seconds, the interface is a maximum of 20,000,000
 bytes per seconds.

 For the record, you are referring to an 8-bit RGB scan of the maximum
 available scan area (11.7x17 in^2), right.

 I get 26,658,227 bytes per second (at 8.058 seconds per page and
 23,660,315 at 9.079). ?Assuming that . is a typo ;-) Seeing that the max
 SCSI-3 throughput is 20MB/s, you can't do any better than 214,812,000
 bytes at 20MB/s is 10.740 seconds per page in getting images to your
 computer. ?Since you observe jogging several times per page (what
 size?), obviously, transfers are going a fair bit slower than the max.

 In private mail you mentioned that total scan times at 600dpi was
 between 16 and 20 seconds, with and without speed=yes and that the
 scanner jogs three or four times with speed=yes. ?That clearly indicates
 that the scan is speed-limited by the image data transfer. ?Based on
 your timings you're getting between 10.7 and 13.4 MB/s, which is above
 the maximum band width for Fast SCSI interfaces but well below that for
 Fast-Wide SCSI and Ultra SCSI[1].

 ?[1] http://en.wikipedia.org/wiki/SCSI#Parallel_SCSI

 Not good, both from a technical standpoint but if this is the issue,
 well .. i really hope this is not an issue, since I recommended quite
 a few GT-3's and well may have those that were bought returned.

 thanks for all

[sane-devel] Gt-30000 and epkowa - Was Fwd: sanner still jogs - more buffering ?

2011-06-08 Thread Pete Lancashire
Let me add to what I said

 Will 15 to 17 seconds work, yes. but 85% to 120% slower then advertised
 really hurts when ones ability to win contracts is based on ones reputation.

I was asked to come up with a solution to scanning documents. I 'sold' the
idea of using Linux and the GT-3. I selected the GT-3 based on two
things, the first from talking to users for their opinion of
reliability, my personal
experience with Epson scanners and finally on the published specifications for
performance  I'll toss in that Epson (at least the scanner group) supports
Linux via Sane.

10 vs 17 seconds may not sound like much, but when one is looking at over
100,000 documents it adds up pretty fast.

On Wed, Jun 8, 2011 at 8:16 AM, Pete Lancashire pete at petelancashire.com 
wrote:
 My goal is something close to the advertised speed (8.058 seconds per page).
 I would be happy with say 10 seconds which is 24% slower. Would be OK at
 say 12 seconds which is almost 50% slower.

 Will 15 to 17 seconds work, yes. but 85% to 120% slower then advertised
 really hurts when ones ability to win contracts is based on ones reputation.

 It is a pity the electronics in the GT-3 are a bit 'old'. What
 would make this
 pretty much the perfect scanner would be a new board with 1-2 GB of RAM and
 a 1,000 MB/s Ethernet interface. Today building a dedicated controller costs 
 no
 more to have 1 GB then 128 MB. The last design I did using a single
 commodity DDR-2 (or 3) memory module ?plus its connector cost less then
 512 MB of non commodity memory. 1,000 MB/s Ethernet today is basically free.
 The only thing I would change in the scanner deck is from a CFL to LEDs.

 Call it the GT-3E5 (GT-30) and Epson would have a winner.

 -pete

 PS Many years ago I worked for a company under Seikosha and the mechanical
 part of our product was made by Epson.





 On Tue, Jun 7, 2011 at 6:11 PM, Olaf Meeuwissen
 olaf.meeuwissen at avasys.jp wrote:
 Please keep this on the mailing list. ?That way it will get archived and
 be searchable for everyone.

 Pete Lancashire pete at petelancashire.com writes:

 Here's the logs and some more information

 Your logs indicate that the epkowa backend is not limiting the size of
 its internal buffer to 32kb, so that shouldn't be the issue.

 If you want to make real, real sure, modify the epkowa backend source
 code at the end of backend/channel-scsi.c to read

 ?static size_t
 ?channel_scsi_max_request_size (const channel *self)
 ?{
 ? ?size_t max_request_size = sanei_scsi_max_request_size;
 ? ?if (getenv (SANE_SG_BUFFERSIZE))
 ? ? ?{
 ? ? ? ?max_request_size = atoi (getenv (SANE_SG_BUFFERSIZE));
 ? ? ?}
 ? ?return max_request_size;
 ?}

 and set the SANE_SG_BUFFERSIZE to, say, 1MB.

 I only got a chance to test a few things last night

 the log you requested is attached as scsi-debug.log, the other log
 file called just log is debug set at 4 and with SANE_SG_BUFFERSIZE set
 to 1048576 ( 1 meg), the size changed in the log file, but not to 1
 MB. I did not try making the SANE_SG_BUFFERSIZE bigger, ran out of
 time.

 Another non sane/epokwa issue is when I set
 /proc/scsi/sg/def_reserved_size to 1048576 anytime i run scanimage it
 resets back to 32768. Not sure what is going on there. I did not have
 time to try a smaller size.

 No clues on that here either.

 On a side note I've got a ticket open with Epson, basically all the
 literature on the GT-3 says that its SCSI interface supports
 SCSI-2 and SCSI-3.

 The specs on www.epson.com say that SCSI: Requires ASPI-compliant
 compatible SCSI 2 or SCSI 3 PCI card and cable (not included). ?My
 interpretation of that is that you can connect it to a SCSI-3 card and
 it'll work, not that it'll necessarily work at SCSI-3 specifications,
 let alone at the (theoretical) maximum band width.

 Going by the response from support, it is now confirmed the interface
 is SCSI-2 ONLY and that using the wide connector the maximum (raw my
 word) data rate is 20 MBytes per second, and thats a Megabyte being
 1,000,000 bytes. SCSI-2 is based on a 10 Megahertz clock so the real
 raw rate for a wide port is 20,000,000 bytes per second. The scanner
 in color mode is suppose to do 0.79 milliseconds per line or 9.079
 seconds per page.

 I only get to 8.058 seconds per page (and you did too, earlier).
 17 inches at 600 dpi with 0.79ms per line.

 A full page at 600 dpi, color is 214,812,000 bytes, which is
 23,662.921 bytes per seconds, the interface is a maximum of 20,000,000
 bytes per seconds.

 For the record, you are referring to an 8-bit RGB scan of the maximum
 available scan area (11.7x17 in^2), right.

 I get 26,658,227 bytes per second (at 8.058 seconds per page and
 23,660,315 at 9.079). ?Assuming that . is a typo ;-) Seeing that the max
 SCSI-3 throughput is 20MB/s, you can't do any better than 214,812,000
 bytes at 20MB/s is 10.740 seconds per page in getting images to your
 computer. ?Since you observe jogging several times per page (what
 size

[sane-devel] Gt-30000 and epkowa - Was Fwd: sanner still jogs - more buffering ?

2011-06-07 Thread Pete Lancashire
with the change made below, and setting the SANE_SG_BUFFER_SIZE to 1 Meg
the scanner jogs 2 times and takes 15.21 (avg of 3 passes) seconds,
the max I can
set it to is 1,347,071 one more byte and it crashes with

sanei_scsi.issue: 0x17a6130
sanei_scsi.issue: bad write (errno=12) Cannot allocate memory -1
sanei_scsi.issue: SG_BIG_BUF inconsistency? Check file PROBLEMS.

sane_read: Out of memory

I'm going to hit up the sg maintainer about why /proc/scsi/sg/def_reserved_size
keeps getting put back to 32K

other tidbits

with speed=no scan time is consistently just over 17 seconds

with resolution=300 and speed=no the scanner jogs once with speed=yes
(and not a typo) it is
much faster and does NOT jog. That one has me really confused.

going to download the kernel sources etc .. for future fun.

I may also for grins build this server as a Ubuntu setup and see what happens.

-pete





On Tue, Jun 7, 2011 at 6:11 PM, Olaf Meeuwissen
olaf.meeuwissen at avasys.jp wrote:
 Please keep this on the mailing list. ?That way it will get archived and
 be searchable for everyone.

 Pete Lancashire pete at petelancashire.com writes:

 Here's the logs and some more information

 Your logs indicate that the epkowa backend is not limiting the size of
 its internal buffer to 32kb, so that shouldn't be the issue.

 If you want to make real, real sure, modify the epkowa backend source
 code at the end of backend/channel-scsi.c to read

 ?static size_t
 ?channel_scsi_max_request_size (const channel *self)
 ?{
 ? ?size_t max_request_size = sanei_scsi_max_request_size;
 ? ?if (getenv (SANE_SG_BUFFERSIZE))
 ? ? ?{
 ? ? ? ?max_request_size = atoi (getenv (SANE_SG_BUFFERSIZE));
 ? ? ?}
 ? ?return max_request_size;
 ?}

 and set the SANE_SG_BUFFERSIZE to, say, 1MB.

 I only got a chance to test a few things last night

 the log you requested is attached as scsi-debug.log, the other log
 file called just log is debug set at 4 and with SANE_SG_BUFFERSIZE set
 to 1048576 ( 1 meg), the size changed in the log file, but not to 1
 MB. I did not try making the SANE_SG_BUFFERSIZE bigger, ran out of
 time.

 Another non sane/epokwa issue is when I set
 /proc/scsi/sg/def_reserved_size to 1048576 anytime i run scanimage it
 resets back to 32768. Not sure what is going on there. I did not have
 time to try a smaller size.

 No clues on that here either.

 On a side note I've got a ticket open with Epson, basically all the
 literature on the GT-3 says that its SCSI interface supports
 SCSI-2 and SCSI-3.

 The specs on www.epson.com say that SCSI: Requires ASPI-compliant
 compatible SCSI 2 or SCSI 3 PCI card and cable (not included). ?My
 interpretation of that is that you can connect it to a SCSI-3 card and
 it'll work, not that it'll necessarily work at SCSI-3 specifications,
 let alone at the (theoretical) maximum band width.

 Going by the response from support, it is now confirmed the interface
 is SCSI-2 ONLY and that using the wide connector the maximum (raw my
 word) data rate is 20 MBytes per second, and thats a Megabyte being
 1,000,000 bytes. SCSI-2 is based on a 10 Megahertz clock so the real
 raw rate for a wide port is 20,000,000 bytes per second. The scanner
 in color mode is suppose to do 0.79 milliseconds per line or 9.079
 seconds per page.

 I only get to 8.058 seconds per page (and you did too, earlier).
 17 inches at 600 dpi with 0.79ms per line.

 A full page at 600 dpi, color is 214,812,000 bytes, which is
 23,662.921 bytes per seconds, the interface is a maximum of 20,000,000
 bytes per seconds.

 For the record, you are referring to an 8-bit RGB scan of the maximum
 available scan area (11.7x17 in^2), right.

 I get 26,658,227 bytes per second (at 8.058 seconds per page and
 23,660,315 at 9.079). ?Assuming that . is a typo ;-) Seeing that the max
 SCSI-3 throughput is 20MB/s, you can't do any better than 214,812,000
 bytes at 20MB/s is 10.740 seconds per page in getting images to your
 computer. ?Since you observe jogging several times per page (what
 size?), obviously, transfers are going a fair bit slower than the max.

 In private mail you mentioned that total scan times at 600dpi was
 between 16 and 20 seconds, with and without speed=yes and that the
 scanner jogs three or four times with speed=yes. ?That clearly indicates
 that the scan is speed-limited by the image data transfer. ?Based on
 your timings you're getting between 10.7 and 13.4 MB/s, which is above
 the maximum band width for Fast SCSI interfaces but well below that for
 Fast-Wide SCSI and Ultra SCSI[1].

 ?[1] http://en.wikipedia.org/wiki/SCSI#Parallel_SCSI

 Not good, both from a technical standpoint but if this is the issue,
 well .. i really hope this is not an issue, since I recommended quite
 a few GT-3's and well may have those that were bought returned.

 thanks for all the help so far !!

 Sorry that this is of not much help.
 --
 Olaf Meeuwissen, LPIC-2 ? ? ? ? ? FLOSS Engineer -- AVASYS CORPORATION
 FSF Associate Member #1962

[sane-devel] sanner still jogs - more buffering ?

2011-06-06 Thread Pete Lancashire
Looking for suggestions on how to get my scanner to scan a full page
at full speed and
not have to 'jog' 3 or 4 times.

Scanner is a Epson GT-3. In slow speed it works, in full speed it jogs

System: HP DL580G3
 4 ea dual core 3GHz Zeon cpus

 Adaptec 29320 PCI-X 133 on a bus not shared with any other PCI device
 LSI ?? 320 PCI-X 133 on a bus not shared with any other PCI Device

Fedora15

 8 GB  RAM DISK created from the above RAM

Latest packages from Epkowa

dll.conf consists of only epkowa

Scanner Epson GT-3 Connected VIA SCSI 68 pin (wide)
Scanner ONLY RUNs at SCSI-2, 20 MB/s (40 MB/s transfer since wide I AM
ASSUMING THIS, waiting to hear back from Epson)
NOTE: Just confirmed from Epson, their online documentation lies
in that it says SCSI-3
A full scan, 600 DPI color at full speed should take 8.058 Seconds and
create a file approx 204 MBytes
0.79 mS per line, 10,200 lines
7,020 x 10,200 or 71,604.000 pixels
24 bits per pixels

The key is 204.86 Megabytes in 8.058 Seconds which is 25.43 Megabytes
per second.

tests were done sending the output of scanimage to /dev/null.

time scanimage --color-correction='No Correction' --mode=Color
--resolution=600 --speed=yes  /dev/null

some of the things I've done and tried

installed the latest epkowa packages

changed dll.conf to just epkowa (deleted everything other then epson2
which is commented out)

increased /proc/scsi/sg/def_reserved_size to 1 Meg
changed .../allow_dio to 1 (enable)
increased SANE_SG_BUFFERSIZE to 1 Meg (and even higher)

I've also downloaded the lastest sane, built it with gcc -march / tune
= native, same resulits

=
Increasing the buffers to their max/1MB does help

From the sources can I increase the buffer(s) in sane ? I have 16 GB
or RAM to play with

Can I 'sniff' the SCSI bus to see if it is sane telling the scanner to
wait or is it the scanner it self ?

Other suggestions ?

TIA 

-pete



[sane-devel] Fedora 15epson2/scsi doesnt work but Fedora 11 - updated does

2011-05-30 Thread Pete Lancashire
CSI, Epson GT-3 backend epson. A Epson 1640 via USB works

New box is a HP DL580G3, 4 CPUs, 24 GB  RAM, and both a LSI and Adatec
SCSI-320 cards.

In testing ive even moved Adpatec 2940UW and cable from the PC with
FC11 to the Server with FC15


Attached is the output from the epson backend


FC11's sane

sane-backends-1.0.20-11.fc11.x86_64
libsane-hpaio-3.10.2-4.fc11.x86_64
sane-backends-libs-1.0.20-11.fc11.x86_64
xsane-0.997-1.fc11.x86_64

FC15's

sane-backends-1.0.22-3.fc15.x86_64
xsane-gimp-0.998-3.fc15.x86_64
libsane-hpaio-3.11.5-2.fc15.x86_64
xsane-0.998-3.fc15.x86_64
xsane-common-0.998-3.fc15.x86_64
sane-backends-libs-1.0.22-3.fc15.x86_64

first issue is there is no scanner in /etc/group (not in 11 either,
I'll hit fedora on that)

kernel finds the scanner

[2.246018] scsi4 : ioc0: LSI53C1030 B2, FwRev=01013c00h, Ports=1,
MaxQ=255, IRQ=74
[2.804838] scsi 4:0:1:0: Processor EPSONSCANNER
GT-3 1.53 PQ: 0 ANSI: 2
[2.804870] scsi target4:0:1: Beginning Domain Validation
[2.830787] scsi target4:0:1: Domain Validation skipping write tests
[2.830793] scsi target4:0:1: Ending Domain Validation
[2.830870] scsi target4:0:1: FAST-20 SCSI 20.0 MB/s ST (50 ns,
offset 127) [another issue but not sane]
[6.086769] scsi 4:0:1:0: Attached scsi generic sg1 type 3

it is the only device on the card

crw---. 1 root root 21, 1 May 30 07:40 /dev/sg1

there is no scanner device, and mode is 600 not 660, not sane but just
wanted to mention it

changing the mode to 660

scanimage -L returns

device `epson2:/dev/sg1' is a Epson SCANNER GT-3 flatbed scanner

epson2 is the same backend the FC11 PC used

scanimage --help -d epson2:/dev/sg1'

Options specific to device `epson2:/dev/sg1':
  Scan Mode:
--mode Lineart|Gray|Color [Lineart]
Selects the scan mode (e.g., lineart, monochrome, or color).
--depth 8 [inactive]
Number of bits per sample, typical values are 1 for line-art and 8
for multibit scans.
--halftoning None|Halftone A (Hard Tone)|Halftone B (Soft
Tone)|Halftone C (Net Screen)|Dither A (4x4 Bayer)|Dither B (4x4
Spiral)|Dither C (4x4 Net Screen)|Dither D (8x4 Net Screen)|Text
Enhanced Technology|Download pattern A|Download pattern B [Halftone A
(Hard Tone)]
Selects the halftone.
--dropout None|Red|Green|Blue [None]
Selects the dropout.
--brightness -4..3 [0]
Selects the brightness.
--sharpness -2..2 [0]

--gamma-correction Default|User defined|High density printing|Low
density printing|High contrast printing [Default]
Selects the gamma correction value from a list of pre-defined devices
or the user defined table, which can be downloaded to the scanner
--color-correction None|Built in CCT profile|User defined CCT
profile [Built in CCT profile]
Sets the color correction table for the selected output device.
--resolution
50|60|72|75|80|90|100|120|133|144|150|160|175|180|200|216|240|266|300|320|350|360|400|480|600|720|800|900|1200|1600|1800|2400|4800|9600dpi
[25]
|1200|1600|1800|2400|4800|9600dpi [25]
Sets the resolution of the scanned image.
--threshold 0..255 [128]
Select minimum-brightness to get a white point
  Advanced:
--mirror[=(yes|no)] [no]
Mirror the image.
--auto-area-segmentation[=(yes|no)] [yes]
Enables different dithering modes in image and text areas
--red-gamma-table 0..255,... [inactive]
Gamma-correction table for the red band.
--green-gamma-table 0..255,... [inactive]
Gamma-correction table for the green band.
--blue-gamma-table 0..255,... [inactive]
Gamma-correction table for the blue band.
--wait-for-button[=(yes|no)] [no]
After sending the scan command, wait until the button on the scanner
is pressed to actually start the scan process.
  Color correction:
--cct-type Automatic|Reflective|Colour negatives|Monochrome
negatives|Colour positives [inactive]
Color correction profile type
--cct-profile -2..2,...
Color correction profile data
  Preview:
--preview[=(yes|no)] [no]
Request a preview-quality scan.
  Geometry:
-l 0..297.18mm [0]
Top-left x position of scan area.
-t 0..431.8mm [0]
Top-left y position of scan area.
-x 0..297.18mm [297.18]
Width of scan-area.
-y 0..431.8mm [431.8]
Height of scan-area.
  Optional equipment:
--source Flatbed|Automatic Document Feeder [Flatbed]
Selects the scan source (such as a document-feeder).
--auto-eject[=(yes|no)] [no]
Eject document after scanning
--film-type Positive Film|Negative Film|Positive Slide|Negative
Slide [inactive]

--focus-position Focus on glass|Focus 2.5mm above glass [inactive]
Sets the focus position to either the glass or 2.5mm above the glass
--bay 1|2|3|4|5|6 [inactive]
Select bay to scan
--eject []
Eject the sheet in the ADF
--adf-mode 

[sane-devel] Fedora 15epson2/scsi doesnt work but Fedora 11 - updated does

2011-05-30 Thread Pete Lancashire
Olaf,

I will give the Epkowa backend a try next (on a side note the URL in
the sane documentation is 404)

what I've done in the mean time is to download various versions of the
sane backends
and configure/make.

here the results so far

.22 - same results as the one from the Fedora distribution
.21 - same
.20 - works. This is the same version I have on the 'working' PC.

-pete



On Mon, May 30, 2011 at 5:13 PM, Olaf Meeuwissen
olaf.meeuwissen at avasys.jp wrote:
 Pete Lancashire pete at petelancashire.com writes:

 CSI, Epson GT-3 backend epson. A Epson 1640 via USB works

 [...snip...]

 [epson2] e2_ext_read: cancel request received
 [epson2] e2_cancel
 scanimage: sane_read: Operation was cancelled

 stderr attached as a gzip'ed file, stdout as image.pnm

 Looking at the gzip'ed log, you are experiencing the same problem as
 discussed in this thread:

 ?http://lists.alioth.debian.org/pipermail/sane-devel/2010-December/027757.html

 The fix for the initial problem in that thread is responsible for the
 cancellation you are experiencing. ?You can try reverting the patch[1],
 hack up a model specific work-around as suggested in [2] or try the
 epkowa backend that comes with Image Scan! for Linux (available via my
 employer's website[3]).

 ?[1]
 ?http://anonscm.debian.org/gitweb/?p=sane/sane-backends.git;a=commitdiff;h=9a89932ab4624925794532ab5e5610e3b0190d53;hp=2f3300b4d1b05d6f75e51aa84a5bf0e0e9bebd5b
 ?[2]
 ?http://lists.alioth.debian.org/pipermail/sane-devel/2010-December/027867.html
 ?[3] http://avasys.jp/eng/linux_driver/

 Hope this helps,
 --
 Olaf Meeuwissen, LPIC-2 ? ? ? ? ? FLOSS Engineer -- AVASYS CORPORATION
 FSF Associate Member #1962 ? ? ? ? ? ? ? Help support software freedom
 ? ? ? ? ? ? ? ? http://www.fsf.org/jf?referrer=1962




[sane-devel] Fedora 15epson2/scsi doesnt work but Fedora 11 - updated does

2011-05-30 Thread Pete Lancashire
on a side note

May 30 18:34:52 localhost udevd[478]: can not read
'/lib/udev/rules.d/65-iscan.rules'
May 30 18:34:52 localhost udevd[478]: GOTO 'iscan_rules_end' has no
matching label in: '/lib/udev/rules.d/65-iscan.rules'
May 30 18:34:52 localhost udevd[478]: GOTO 'iscan_scsi_rules_begin'
has no matching label in: '/lib/udev/rules.d/65-iscan.rules'
May 30 18:34:52 localhost udevd[478]: GOTO 'iscan_usb_rules_end' has
no matching label in: '/lib/udev/rules.d/65-iscan.rules'
May 30 18:34:52 localhost udevd[478]: GOTO 'iscan_rules_end' has no
matching label in: '/lib/udev/rules.d/65-iscan.rules'
[chomp]

sane-find-scanner -v -v
hecking /dev/sg1... open ok
  Inquiry for device:
000: 03 00 02 02 23 00 00 30 45 50 53 4f 4e 20 20 20#..0EPSON
016: 53 43 41 4e 4e 45 52 20 47 54 2d 33 30 30 30 30SCANNER GT-3
032: 31 2e 35 33 00 00 00 ff1.53
found SCSI processor EPSON SCANNER GT-3 1.53 at /dev/sg1

I've can scan with iscan SLOW .. see below but not a sane issue ...

 the epkowa backend can not see the scanner, commented out everything
in epson and epson2 and only
have net, epson, epson2 and epkowa in dll.conf If I comment out SCSI
in epson and epson2 .. no can find.

could the issue be in the udevd ?

added SCSI in various forms, copied what was in epson, epson2 and
various other incarnations.

on another side note iscan took a LONG time to do the scan with a lot
of back and forth. change sg's buffer up to 1M that really didnt work.
The adapter is PCI-X on its own PCI bus, but the interface is 20 MHz
It starts at 320 and keeps going down, down and down.
The scanner is suppose to be SCSI-3 .. anyone at Epson can tell me
what I'm doing ? The last time I called they told me to call
Microsoft, they just didn't get it .. even made the output goto file
on a 512MB ram disk, didn't help.

this whole thing started because I though my desktop PC was too slow,
consumer PCI, old Adaptec 2940UW, etc etc

can anyone get at GT-3 to not have to jog ?

-pete







-pete

On Mon, May 30, 2011 at 7:12 PM, Olaf Meeuwissen
olaf.meeuwissen at avasys.jp wrote:
 Pete Lancashire pete at petelancashire.com writes:

 Olaf,

 I will give the Epkowa backend a try next (on a side note the URL in
 the sane documentation is 404)

 Which one? ?The link listed in this section[1] and this page[2] work
 fine for me.

 ?[1]
 ?http://sane.alioth.debian.org/lists/sane-backends-external.html#S-EPKOWA
 ?[2] http://sane.alioth.debian.org/sane-frontends.html

 what I've done in the mean time is to download various versions of the
 sane backends and configure/make.

 here the results so far

 .22 - same results as the one from the Fedora distribution
 .21 - same

 Makes sense. ?The fix for the initial problem in the thread mentioned
 earlier shipped in .21.

 .20 - works. This is the same version I have on the 'working' PC.

 Hope this helps,
 --
 Olaf Meeuwissen, LPIC-2 ? ? ? ? ? FLOSS Engineer -- AVASYS CORPORATION
 FSF Associate Member #1962 ? ? ? ? ? ? ? Help support software freedom
 ? ? ? ? ? ? ? ? http://www.fsf.org/jf?referrer=1962

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org




[sane-devel] Fuji Lanovia C-550.

2011-05-17 Thread Pete Lancashire
yep, thats why my offer for this thing is only $100. Be one of those projects
with the goal of someday finding either some internal docs or a Mac with the
code and dongle. There's a 43 wide x infinate length scanner in the garage
in the same state. .. but it was free.

-pete


On Tue, May 17, 2011 at 7:05 AM, m. allan noah kitno455 at gmail.com wrote:
 If you cannot run the machine due to missing software or dongle, you
 cannot snoop on the communication protocol. No snoops = no reverse
 engineering.

 allan

 On Mon, May 16, 2011 at 9:34 PM, Pete Lancashire
 pete at petelancashire.com wrote:
 Ever since Fuji got out of the scanner biz the price has been dropping
 fast, very fast. And as usual the PC, in this case a Mac that was
 dedicated to it along with the proprietary software and lic. dongle
 are usually long gone in another direction, thats the situation this
 one is in. So far I can't even get Fuji or Agfa who resold it to even
 give me more the the usual 'we don't support it anymore, click'.

 HP lost the sale of 250 printers when I got that replay a few years
 ago. The short term bean counters just don't get it.

 Unfortunately, at 5000 Dpi, I'd bet this thing uses some interesting 
 compression, which could be hard to decode.

 5000 x 18 x 13 ?x 48 (dpi, x, y, bits/pixel) , compression - I hope so !!!

 -pete


 PS C .. yes years ago, but it's like riding a bike :-)


 On Mon, May 16, 2011 at 5:13 PM, m. allan noah kitno455 at gmail.com wrote:
 Not that I've heard. Its a pretty pricey piece to 'play with' :)
 However, if you've got some C programming experience, you might be in
 luck. More expensive scanners tend to have simpler protocols.
 Unfortunately, at 5000 Dpi, I'd bet this thing uses some interesting
 compression, which could be hard to decode.

 allan

 On Mon, May 16, 2011 at 5:55 PM, Pete Lancashire
 pete at petelancashire.com wrote:
 Has anyone connected one of these beasts up to a Linux box and
 succeeded with sane ?

 I've been offered one at what I think is a reasonable price.

 -pete

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org




 --
 The truth is an offense, but not a sin





 --
 The truth is an offense, but not a sin




[sane-devel] Fuji Lanovia C-550.

2011-05-16 Thread Pete Lancashire
Has anyone connected one of these beasts up to a Linux box and
succeeded with sane ?

I've been offered one at what I think is a reasonable price.

-pete



[sane-devel] Fuji Lanovia C-550.

2011-05-16 Thread Pete Lancashire
Ever since Fuji got out of the scanner biz the price has been dropping
fast, very fast. And as usual the PC, in this case a Mac that was
dedicated to it along with the proprietary software and lic. dongle
are usually long gone in another direction, thats the situation this
one is in. So far I can't even get Fuji or Agfa who resold it to even
give me more the the usual 'we don't support it anymore, click'.

HP lost the sale of 250 printers when I got that replay a few years
ago. The short term bean counters just don't get it.

 Unfortunately, at 5000 Dpi, I'd bet this thing uses some interesting 
 compression, which could be hard to decode.

5000 x 18 x 13  x 48 (dpi, x, y, bits/pixel) , compression - I hope so !!!

-pete


PS C .. yes years ago, but it's like riding a bike :-)


On Mon, May 16, 2011 at 5:13 PM, m. allan noah kitno455 at gmail.com wrote:
 Not that I've heard. Its a pretty pricey piece to 'play with' :)
 However, if you've got some C programming experience, you might be in
 luck. More expensive scanners tend to have simpler protocols.
 Unfortunately, at 5000 Dpi, I'd bet this thing uses some interesting
 compression, which could be hard to decode.

 allan

 On Mon, May 16, 2011 at 5:55 PM, Pete Lancashire
 pete at petelancashire.com wrote:
 Has anyone connected one of these beasts up to a Linux box and
 succeeded with sane ?

 I've been offered one at what I think is a reasonable price.

 -pete

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org




 --
 The truth is an offense, but not a sin




[sane-devel] sane over the net .. backend ?

2011-05-06 Thread Pete Lancashire
I have a Epson GT-3 on a Fedora 11 box. running xsane it has what
looks like all its features, for example the ADF can be duplexing.

I've just set up saned on that box.

The client I'm using is Linux Mint 9 (Ubuntu under the covers), it
'see' the GT-3 just fine but many of its features are not
available,
and the ADF eject does not work.

Hoping this is a 'operator' error.

-pete



[sane-devel] sane over the net .. backend ?

2011-05-06 Thread Pete Lancashire
on the server (host with the scanner) sane-backends-1.0.20-11.fc11.x86_64

on the client libsane 1.0.20-13ubuntu2

On Fri, May 6, 2011 at 3:40 PM, m. allan noah kitno455 at gmail.com wrote:
 What version of sane-backends are you running on both boxes?

 allan

 On Fri, May 6, 2011 at 4:20 PM, Pete Lancashire pete at petelancashire.com 
 wrote:
 That directed me to what I was doing wrong

 when I start xsane it asks me to pick from two scanners

 device `net:foo:epson2:/dev/sg5' is a Epson SCANNER flatbed scanner
 device `net:foo:epson:/dev/sg5' is a Epson GT-3 flatbed scanner

 the first does not have the options, the second one does

 Thanks 

 -pete



 On Fri, May 6, 2011 at 12:02 PM, m. allan noah kitno455 at gmail.com wrote:
 If you run scanimage --help on both machines, you should see the same
 list of options. Is that true?

 allan

 On Fri, May 6, 2011 at 2:20 PM, Pete Lancashire pete at 
 petelancashire.com wrote:
 I have a Epson GT-3 on a Fedora 11 box. running xsane it has what
 looks like all its features, for example the ADF can be duplexing.

 I've just set up saned on that box.

 The client I'm using is Linux Mint 9 (Ubuntu under the covers), it
 'see' the GT-3 just fine but many of its features are not
 available,
 and the ADF eject does not work.

 Hoping this is a 'operator' error.

 -pete

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org




 --
 The truth is an offense, but not a sin





 --
 The truth is an offense, but not a sin

 --
 sane-devel mailing list: sane-devel at lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org