Andrew,
>> What is the current status?
>
> I would call it at least 'Good'. I have used this code to scan over a hundred
> negatives. But then only I have used it. Others may want something else. I am
> open to adding to it although I would prefer to get an initial implementation
> committed b
Andrew,
I'm sorry, but I haven't received any emails from you lately. The last message
I got from you is from January 26th.
Can you please resent your emails, I'll double check for any over-eager spam
filter.
Kind regards,
Oliver
> I was working with Oliver Schwartz to
Zed,
the log from "scanimage -L" looks fine (there is no error in the log)
and the console output shows that the scanner is correctly detected.
The Gtk-warnings are xsane related and you can probably ignore them.
If you still cannot scan in xsane I need the backend log while running
xsane,
Hi,
>> Please remove the line containing the USB device from your config
>> file
>> (/dev/usb/scanner0) - it's no longer useable for systems using
>> libusb and
>> the specified device does not exist on your system. After removing
>> the
>> line the scanner should be found automatically.
>
>
Hi,
On 02.02.2010, at 10:09, Zed wrote:
> I am using LinuxMint v8.0 and having difficulty in getting my Benq
> S2W 4300U
> Scanner to work on my system.
>
> After installing u176v046.bin in .usr/share/sane/snapscan, and editing
> /etc/sane.d/snapscan.con to read:
>
> #--
Hi Allan,
>> Anyway, I've commited a hash function now. The new code should also
>> work on FreeBSD 8.0. If anyone can try it, I'd be much obliged.
>
>
> I did not see any commit message. did you git push?
Err - yes, and it told me that it had pushed 4 or 5 objects. That was
my first git comm
Hi all,
On 28.01.2010 at 14:39 m. allan noah wrote:
> I would do both- process ID combined with a hash of the device name,
I believe that would defeat the purpose. The whole point of the mutex is to
protect the USB device from simultaneous access from two processes, e.g. the
reader process and
Hi all,
On 26.01.2010, at 15:46, m. allan noah wrote:
> Seems like an individual backend should not need to parse the device
> string. Isn't there some other way to come up with a unique semaphore,
> like process id?
the process id could be used, but it may fail theoretically. One
example is
Hi all,
On 25.01.2010, at 12:26, Torfinn Ingolfsen wrote:
> In the meantime, another FreeBSD user found a way to fix it, it is
> just a one-line patch:
> http://lists.freebsd.org/pipermail/freebsd-usb/2010-January/
> 008172.html
>
> With Andrew's patch, my scanner now works:
> root at kg-v2#
Hi,
> I have an old Agfa Snapscan 1212U scanner which have served me well for
> years, using SANE under FreeBSD.
>
> To make a long story short; FreeBSD 8.0-release came with a new usb stack,
> and is using libusb.
> And my scanner no longer works. Has anyone managed to get the snapscan
> back
Hi,
What list exactly are you referring to?
On http://www.sane-project.org you'll find it listed under Benq 640U
(Acer Peripherals renamed itself to Benq several years ago, as is also
mentioned in the same list). The scanner has been supported for more
than seven years.
So, what exactly ar
John,
You don't need to create any '/dev/usb/scanner' device, nor should you
specify the scanner device in snapscan.conf. Your scanner will be
detected automatically provided that the USB ID is listed in
snapscan.conf, which should be the case for the snapscan 1212 on any
standard sane ins
Hello all,
> IIRC the person who wrote XSane is indeed german (Oliver Schwartz)
well, I'm german, but I didn't write XSane :-( That honour belongs to
Oliver Rauch (who is also german AFAIK).
Regards,
Oliver
e why the Xserver crashes when a child process is killed,
but maybe the people at X.org would find the information useful.
Kind regards,
Oliver
Am 24.06.2008 um 18:07 schrieb Christoph M. Schr?der:
> Sorry, now i got it.
>
> Oliver Schwartz schrieb:
>> Hi,
>>
>> the int
Hi,
the interesting part is the contents of the file 'debug.log', which
should be created in the directory from which you started xsane.
Regards,
Oliver
On 24.06.2008, at 17:50, Christoph M. Schr?der wrote:
> Hi,
>
> thanks Oliver.
>
> This is what i'm getting showed in the terminal:
> $ SAN
Hi,
please also provide the log produced by
SANE_DEBUG_SNAPSCAN=255 xsane 2 > debug.log
then use xsane until the error occurs. The logs tend to get quite big,
so you should compress it.
Regards,
Oliver
On 21.06.2008, at 17:46, Christoph M. Schr?der wrote:
> Hi,
>
> thanks for the informatio
Hi,
you need the firmware file for your scanner ("Snapscan 1212U_2.bin"
from your scanner driver CD). Save it under a name without spaces and
specify the filename (with full path) in the file /usr/local/etc/
sane.d/snapscan.conf
After that, check if "scanimage -L" on the command line finds t
Hi,
> The patch only works for libusb devices. Applying it as is means the
> backend will now fail hard if you're using a non-pthread build of SANE
> with a non-libusb access method.
>
> I'm not sure such a combination exists. If I'm not mistaken, OS/2 uses
> pthread by default, so does OS X and a
Hi,
I assume you are using the snapscan backend. In this case:
> My Epson 3490 works just fine if the firm ware is loaded from a
> Windows
> box first. I also have located the binary that needs to be loaded.
>
> Is there a bash command I can run to manually load the binary file
> into
> the s
Hi all,
> The snapscan backend uses a mutex to lock the USB device it's
> working with when sending "atomic" commands.
First off, the original code wasn't written by me and I don't claim I
fully understand it. The background, as far as I understand it, is
this:
The backend may fork a reader pr
Hi,
you also need to specify the path to the firmware file in
snapscan.conf, which is installed in /usr/local/etc/sane.d/ on OS X,
IIRC.
The firmware file itself (esfw30.bin) should be contained on the
windows driver CD.
See http://snapscan.sourceforge.net for some additional infos on the
Hi,
On 07.12.2007, at 15:26, Patrick wrote:
> I have an Epson 3490. It did work in Ubuntu Edgy but not too well.
> If I
> used it in Windoze and then Ubuntu it worked fine. However if it
> was not
> re-initialized under windoze every so often it would not work.
> ...
> but I get this message w
Hi,
I've written a small perl script that parses the output of usbsnoop
and translates it to snapscan commands. I'll send it to you tomorrow.
Regards,
Oliver
On 26.10.2007, at 11:20, matei kolt wrote:
>
> OK, the code with benoit's usb sniffer.
> Pluging in, a few prewiews and a scan.
>
> ht
ian.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
! Oliver Schwart
Hi,
On Sunday 30 September 2007 18:01, Tanguy Eric wrote:
> When i launch xsane from command line i can see this
> warming :
> [snapscan] Scanner warming up - waiting 6 seconds.
> [snapscan] Scanner warming up - waiting 36 seconds.
>
> and after when i ask a scan xsane spend also times warming :
>
255 Vendor Specific Class
> bDeviceSubClass 255 Vendor Specific Subclass
> bDeviceProtocol 255 Vendor Specific Protocol
> bMaxPacketSize064
> bNumConfigurations 1
> Device Status: 0x0001
> Self Powered
>
> Anything else I can provide to you, please ask, I will be more than
> happy to help you. I even can get some coding done if there is nothing
> developed yet, please send me some starting docs and I will gladly
> do it!
>
> Thanks,
> Adrian
>
> --
> 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
>
>
! Oliver Schwartz Tel.: +41 / (0)44 / 461 06 29 (fest) !
! D?ltschiweg 3 +41 / (0)76 / 566 29 72 (mobil) !
! CH-8055 Z?richE-Mail: Oliver.Schwartz at gmx.de!
Hi,
On Monday 30 April 2007 21:34, Y P wrote:
> as you will see, the scanner is found/recognized,
> but xsane seems to find his Logitech QuickCam and doesn't give him
> the choice to tell that's his intensions are to scan, not to webcam
>
> :-)
>
> He also did tried to add ln -s /dev/sg0 /dev/scan
Hi,
On Monday 30 April 2007 16:57, L? H?ng B?i wrote:
> Hi everybody,
> I'm using an Epson Stylus CX-1500. I can scan image from it with
> snapscan backend. However, the image is green, no red, no blue. It
> seems that I need to specify a firmware to upload to the scanner. I
> look in Windows inst
Hi Abel,
> > As far as I can tell I'm issuing a sanei_scsi_cmd with a send
> > buffer of ten bytes and a receive buffer of 130176 bytes. Both
> > should fit into the SCSI buffer of 131072 bytes easily.
>
> is 130176 a typo, or does the backend really wants to read 4 bytes
> more than reserved? (or
Hi SCSI experts,
a user reported a problem with an Acer 620ST plugged into a Artop
Electronic Corp AEC6712D SCSI controller (atp870u driver). The system
causing problems is running linux-2.6.17-gentoo-r8, gcc 4.1.1 and
glibc-2.4, sane-backends-1.0.18.
On this system the following error occurs:
Hi,
> I own a Acer Flatbed scanner (620 ST) which I use rarely. So I can
> not exactly tell you, when this error started to occur on my
> computer.
>
> # scanimage
> scanimage: sane_start: Out of memory
>
> Does anybody have an idea, what the heck is going wrong, or how to
> get rid of that probl
Hi,
> > When I try to scan in lineart mode, it makes garbage on output.
> > The scan seems "misaligned".
> > But if I first make a scan in gray or color mode, and then switch
> > to lineart, it works !
>
> It works ... sometimes :(
>
> I acquire a scan in Lineart mode and make a log :
> http://www
Hi,
On Tuesday 01 August 2006 08:31, marcela castro wrote:
> Who may concernI have Open source software in my PC
> and I would like to configure my scanner "Benq Saw 4300U" to work
> with this system Suse 10.1 http://www.novell.com/linux/ but it is
> require the firmware upload. dr
Hi,
> I just upgraded to SANE-Backends-1.0.18 and my Epson 2480 works
> better than ever. Thanks!
>
> I have a question/comment about the scanner lamp. This scanner
> doesn't have an on/off button, so it remains on whenever it's
> plugged in (I remember a Dilbert strip about this very theory of
>
Hi,
it seems that there's a problem with your snapscan.conf file. If
you're using libusb you *must not* have a device line, i.e. you
should delete any line stating /dev/usb/scanner0 or similar. The
backend will automatically probe all USB devices for a suitable
scanner.
However, in all the lo
Hi,
> I have searched the archives, but found nothing definitive; read
> all the docs and other stuff on sane-project.org/ and
> snapscan.sourceforge.net/ websites.
>
> I know that the scanner part of the CX3700 works
> [http://www.sane-project.org/cgi-bin/driver.pl?manu=epson&model=cx3
>700&bus=u
Hi,
>I'm using an Agfa SnapScan 310 scanner, its working just fine.
> However, its status shows 'good' rather than 'complete' in the
> support matrix at sane-project site. I would like to know which
> features are still unimplemented (or where to find this information
> if it's available) and
Hi,
> Epson 3490 is inexpensive scaner and is listed on the sane page as
> beeing supported (as "good").
> The question is.. does sane supporr olso slide/negative scaning,
> and how good this scaner behaves under Linux...
> Does anybody on the list had any experience with this scaner and
> transpa
Hi,
I've used usbsnoop (version 1.8,
http://benoit.papillault.free.fr/usbsnoop/) successfully several
times, on various flavours of Windows. There is some documentation
(http://benoit.papillault.free.fr/usbsnoop/doc.php.en) available. It
doesn't answer each and every question but was sufficien
Hi,
> Here goes, with first sane-find-scanner and then with scanimage -L,
> both
> as root:
The interesting information is after the firmware download, which
doesn't happen with scanimage -L. You can send the (compressed) log
of a regular "scanimage" command to me in a private mail.
> You
Hi,
> i reinstalled sane-backends-1.0.16_2 from freebsd ports
>
> i get:
>
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.50
This is _not_ sane-backends-1.0.16. The snapscan backend version in
Hi,
it seems there's a problem with CVS. My password is not accepted, cvs
keeps asking for it. Anonymous access doesn't work either:
oliver@oliverspc:/tmp> cvs -z3
-d:pserver:anonym...@cvs.alioth.debian.org:/cvsroot/sane co sane
Fatal error, aborting.
anoncvs_sane: no such system user
/Oliver
Hi,
> The above appears to agree with the information on the
> sane-snapscan page, which gives the USB ID for the Acer/Benq 5300
> as "0x04a5, 0x20fe" and identifies the firmware to use is
> u254v042.bin.
Yes, that should be correct.
> Of course, the firmware file I have might be corrupt. I down
On Saturday 25 March 2006 05:00, Olaf Meeuwissen wrote:
> didi.segb...@arcor.de (Dietmar Segbert) writes:
> > Hello,
> >
> > does the auto film feeder of the epson perfection 3590 photo work
> > to scan negative films?
>
> Not with the epkowa backend (as per limitations in the iscan
> README). Mayb
On Thursday 23 March 2006 15:18, breach0r wrote:
> Hi,
>
> I tried, now sane-backends-1.0.16_2 is installed, i still get I/O
> error when trying to init the scanner. I/O error the first try and
> device unavailable the next tries. set SANE_DEBUG_SNAPSCAN=255 no
> longer produces any output (but i t
Hi,
> Once that was done, "scanimage -L" finds an "Acer FlatbedScanner22
> flatbed scanner", which corresponds to an Benq 4300 scanner. (I was
> expecting FlatbedScanner24, which corresponds to my scanner.)
The scanner should report FlatbedScanner24 after a successful firmware
download. Before
Hi,
> I have a major issue with my Epson perfection 2480 photo scanner.
> It used to run in FreeBSD. I haven't used it in a few weeks during
> which upgrades occured and I noticed this week it stopped working.
> Portupgrade of sane had replaced the snapscan.conf file, I put back
> there my correct
Hi,
> [snapscan] usb_read Only 64 bytes read
> [snapscan] usb_read: reading: 0x06 0x00 0x02 0x02 0x49 0x00 0x00
> 0x00 0x45 0x50 ...
> [snapscan] Read 64 bytes
> [snapscan] inquiry: snapscan_cmd command failed: Error during
> device I/O [snapscan] sane_snapscan_open: error in inquiry command:
Th
Hi,
> also with mac and official cd found in the box the scanner would go
> nut and block itself. i am clueless
> [snapscan] sense_handler: sense key: 0x04, asc: 0x00, ascq: 0x00,
> i1: 0x00, i2: 0x04 [snapscan] sense_handler: Hardware error. (0x00,
> 0x04)
> [snapscan] test_unit_ready: snapscan_
Hi,
> I just bought this scanner -- it seems that the problem is related
> to one I've just seen on the mailing list.
Yes, probably. In your case it is definitely a "scan module locked
error" - which means you should check the manual and remove the
transportation lock.
> [snapscan] sense_handl
Hi,
> i report from the chat since i dunno if someone is listening :)))
>
> hi everybody
> got a problem with an epson 3490
> it should work
> from web research
> it works for anybody
> but I get an ERROR :((
> nihil:/etc/udev/rules.d# /usr/bin/scanimage
> [sanei_debug] Setting debug l
Hi,
> result is here:
> http://rmrmg.com/jaroslav/scanner-debug/SANE_DEBUG_SNAPSCAN_255-xsa
>ne.log
According to the log the scanner is correctly identified. The margins
of the transparency range should be set correctly.
> however, I've got strange issues. Sometimes after turning on the
> scann
Hi,
> I've got Epson Perfection 2580 Photo which is recognized by
> snapscan as 2480, because they both got the same id: 0x04b8/0x0121.
>
> I'm wondering if there is a way to know real model in such a
> situation. It can be helpful, because 2580 differs from 2480 (has a
> motor which transports 36
Hi,
> On another subject, can we get the JNI code rolled
> into the SANE project distribution? The current japi
> code in sane-backend has not been maintained for about
> 9 years now. Our company will sponsor the code and
> code maintenance. Can we do this please? Java is
> part of the future
Hi,
> I have made an updated version that should fix the
> bugs you reported on the depth issue, and on the
> no-scanners issue.
yes, it works now - nice. One thing I noticed is that the scan button
becomes inactive after the scan, so you can only run the applet once.
The clear button seems to
Hi,
> I didn't include more verbose output from the commands here, to
> avoid making this mail very big, but I'll gladly include output
> with
> SANE_DEBUG_SNAPSCAN=2
> level, as well as the output of any command, if needed.
Please send me the log in private mail, preferably with
SANE_DEBUG_SNAP
Hi,
> Thank you for the orientaion.
> On both computers I simply changed the id in the corresponding line
> of /etc/sane.d/hotplug/libsane.db from 0664 to 0660 and it worked
> fine. In case of BenQ 5000 it was also necessary to change the
> product code from 0x20fc to 0x20f8, acording to the infor
Hi,
> Ok, I did some testing with my BenQ 5150C.
>
> My first try was in 300dpi color mode (because this was default).
> There are no color stripes anymore. However, the scanned area was
> not very wide. Although the full available range
> ((0,0)x(216.0,297.0)mm^2) was selected in xscanimage. The
Hi,
> I do not understand how automated firmware upload should work
> if there is more than one scanner connected which use the same
> backend but which need different firmware files.
For the snapscan backend that's currently not possible, as there is
only a single firmware file entry in snapsca
Hi,
> He doesn't want to recompile
> for 64bit because the amount of money he makes from the Linux
> version doesn't justify it.
Err... excuse me? I don't think the amount of money any of the SANE
developers makes from SANE development justifies any effort on this
behalf.
> I can understand yo
Hi all,
I've added some basic support for the Benq 5150C / 5250C scanner to
the snapscan backend. Anyone owning such a scanner is encouraged to
test it and inform me of any problems.
You can get a snapshot of the latest SANE sources from
http://www.sane-project.org/snapshots
At present the ca
Hi,
> I'm writting this to know if anyone are/have
> write/written a backend for this scanner. (Guttenprint
> have support for printing).
>
> If not, i have one of these i "will ***TRY***" (I'm no
> a programmer any longer since some years ago, but i
> can remember C more or less clearly) to write
Hi,
> 1. Someone should change the sane compatibility list to show that
> it does NOT work as of sane-backends-1.0.16. It should be noted
> you need CVS or .17 once it's released.
Where did you get the information that it does work with
sane-backends-1.0.16? The device list for 1.0.16 doesn't l
Hi,
On Monday 12 December 2005 13:22, dmeret...@repsolypf.com wrote:
> Sorry for disturbing, but I would like to know if there are someone
> with experience in Agfa SnapScan 1212p (parallel). Or some place to
> go.
The parallel protocol for Agfa scanners is unknown. It's probably some
sort of SC
Hi,
> I've 5250C benq scanner that I would like to get working under
> linux. I've tried the sane CVS snapshot from December 4th 2005
> without any luck. After some time spent by googling I've found
> following information:
>
> http://lists.alioth.debian.org/pipermail/sane-devel/2004-December/0
>1
Hi,
> Is there anything I can do to help get the Transparency unit to
> work?
As far as I know the transparency unit of the 3490 works ok. The only
thing not supported is the automatic film feeder of the 3590. Please
make sure you use the latest version of the snapscan backend from
CVS.
If y
Hi,
> A little googling turned up this thread from last December:
> http://lists.alioth.debian.org/pipermail/sane-devel/2004-December/0
>12758.html
> ...
> The image is recognisable, but has vertical colour bars all the way
> across it. (*For reference, a test scan is attached, so you can see
> wh
Hi,
> > Same applies to interpoliation. I have a huge patch in my inbox
> > that adds scaling to my avision backend just because some
> > el-cheapo OEM scanners do not appear to deliver any resolution -
> > and for the highest resolution of 2400 dpi have a memory shortage
> > and thus the author i
On Wednesday 30 November 2005 21:12, St?phane VOLTZ wrote:
> since Pierre has added lineart emulation.
I'll need to add something similar to the snapscan backend in the long
run, since some new scanners don't support lineart mode. It still
would be nice to have lineart for OCR etc. on th
Hi,
> The new CVS code did not completely solve the remaining interlacing
> problems at 3200 dpi. While now grayscale work well at both 8bit
> and 16bit, lineart is still combing, but rather differently than
> before. Now interlacing is periodically present or absent by blocks
> of 8 vertical scan
Hi,
> When I power up the scanner, I get pretty much the same behavior I
> was getting before, although maybe slightly improved. The scanner
> seems to be resetting every second or so... in dmesg I get a series
> of messages like this:
>
> [4352427.799000] usb 5-7: new high speed USB device using
Hi,
> > Lineart and grayscale should be fixable.
I've commited a fix to CVS, please test.
> What does the snapscan backend for halftoning? Are there halftoning
> algorithms implemented in software or does it only pass a flag to
> the scanner? I'm asking this because there is a kind of halftonin
Hi,
> Can i hope, that the auto film feeder of the epson 3590 will work?
At the moment the film feed for the 3590 is not supported. I'll need
to get USB traces from a windows scan with film feeder before there's
any chance of supporting it. Anybody who'd like to provide a trace is
welcome to c
Hi,
> I confirm the 3200 dpi works well for me, and there isn't any
> interlacing problems. I apologise for my previous message which was
> not enough clear.
>
> In fact, it seem's that if I do a 2400 dpi scan which does not
> work, then the following 3200 dpi scan are bad. But it works again
> if
Hi,
> - at 2400 dpi :
> I have done several try, at least a dozen.
> Sometimes it's all dark, sometimes all white, sometimes a
> succession of colored bands, and sometimes I have a good scanning,
> but at least it doesn't scale the entire selection I have made on
> the preview screen. And I have a
Hi,
> I don't think the sensors is defective, because it works very well
> on Windows2000 with the Epson software. And I have try the quality
> calibration with no result.
Hm - I don't think so. Quality calibration (i.e. the option named
"Quality calibration", not "Quality scan") was disabled fo
Hi,
> I'm using the tpu on the 3490 with backend-11-10. It works ok
> though the scans seem quite dark compared to the original slide.
> However adjusting the gamma settings on the scanned file gives a
> nice 1024x768 display size. I'm very much a newbie at this so sorry
> I can't give more detail
Hi,
> I've just bought an epson 3490, and download the
> sane-backends-2005-11-10.tar.gz and
> sane-frontends-2005-11-10.tar.gz.
>
> While the flatbed seems to work as expected, the transparency unit
> doesn't.
>
> I want to scan a negative film, but the resulting file is crossed
> by a thick gree
Hi,
> I own an Epson Perfection 3490 and I am beginning to use it with
> the CVS version of SANE (snapscan backend). While it seems to work
> well at resolutions up to 1200 dpi (but I did not yet perform
> really thorough testing), I noticed a kind of interlacing behaviour
> when scanning negative
Hi,
> I have a chance to pick up a used AGFA Snapscan 1212U from a friend
> (he moved to XP and it's not supported, and gives dire warnings
> against trying).
>
> I see that the support on both the current stable version and the
> dev version is marked as "good". Is there any important features
>
Hi,
> When you scan a DIN-A4 page with 200x200 dpi and save it e.g. as a
> tiff file then you get an image with about 1700 x 2200 pixels. At
> this point there is no relation to a size in millimeter,
> centimeter, inch or DIN-A3 or something like that.
I don't think this is completely true. Tiff
Hi,
>> > Argh, my 2480 is changing to 5.5cm by 7.5cm (judging from the
>> > preview window). Debug log attached.
Your boundaries are fine. From the output of your scanimage command:
> ? Geometry:
> ? ? -l auto|0..55mm [0]
> ? ? ? ? Top-left x position of scan area.
> ? ? -t auto|0..125mm [0]
> ?
Hi,
> Argh, my 2480 is changing to 5.5cm by 7.5cm (judging from the
> preview window). Debug log attached.
That's very strange. It can either be 5.5 cm x 8 cm or 5.5 cm x 12.0
cm. Everything else is, well, extremely unlikely.
Please send me the file scanimage.txt, resulting from executing
scani
Hi,
In the last weeks there have been some improvements to the SnapScan
backend for 2480/2580. Most of them were contributed by Simon Munton,
who deserves all the credit :-) In particular there is now support
for 16 bit/color scans for the 2480/2580.
The backend also distinguishes now between
Hi,
> I have an Epson 2480 and I'm quite satisfied with it. I haven't
> used it for negatives, only slides; for many purposes the results
> are quite good. Some random thoughts:
>
> * Sane support is very good, but native support (in windows) is
> still better. In particular:
> The windows dri
Hi,
> I just downloaded the CVS-version of the snapscan backend and
> tested it. It works (for the flatbed part of the scanner)!
>
> The only thing that needs correction is the list of resolutions,
> which at present is
>
> Options specific to device `snapscan:libusb:004:002':
> Scan Mode:
>
Hi,
> I tried more resolutions. The results are funny:
> - 200 dpi is OK
> - 150 dpi works, too
> - 100 dpi works, but the scanned area was displaced in y direction
> - 75 dpi works, but scans a larger y distance than expected
> - 50 dpi is OK,
> - values under 50 are rounded to 50
I've added 1
Hi,
> i use a epson perfection 3590 photo with sane-cvs 2005-10-09
> version.if i use the options
>
> -x auto and -y auto
>
> scanimage gives back a error. Can i not use the options -x auto and
> -y auto to detect the scanmaterial automaticaly?
"auto" in this case just means that you do not have
Hi,
On Monday 03 October 2005 18:43, Bauke Jan Douma wrote:
> On Fri, Sep 30, 2005 at 03:15:41AM +0200, Ulrich Deiters wrote:
> > I set the no-preview bit (source |= 0x40;) in snapscan-scsi.c
> > after line 922, and the problem vanished, i.e., the scanner
> > does a quick, undistorted scan of the
Hi,
the behaviour you describe is perfectly normal, as far as the ID of
the scanner is concerned. Initially the scanner identifies itself as
FlatbedScanner_13. After downloading the firmware (which seems to
work only in windows in your case) the scanner identifies itself as
FlatbedScanner_21.
Hi,
> The scanner is slow in preview mode and makes a different noise
> (probably because it is doing very small y steps). Right now
> the preview mode is not the same as the normal 200 dpi mode.
> But this is not surprising: Somewhere around line 870 in
> snapscan-scsi.c you inform the scanner th
Hi,
> I installed the latest SANE backend version, applied Jan Bouke's
> correction, and got the scanner working (after some confusion
> about the firmware file) - at least for paper scanning.
>
> The only problem I have is with the preview mode:
> "scanimage --preview=yes" uses a too high y rsolu
Hi,
> scanner Epson Perfection 3590 Photo Firmware esfw52.bin
>
> The scanner did not work.
> sane-findscanner finds the scanner:
>
> ...
> found usb scanner vendor 0x04b8 epson scanner productid 0x0122
The 3590 is not tested yet but should work with the snapscan backend.
The latest version from
Hi,
> I have an Epson 2580 scanner, which is capable of 16-bit output for each
> channel, including what it calls monochrome. I'd like to use xsane to
> preview the old black-and-white photographs that I have, and to set the
> tone levels appropriately for each photograph, and then acquire the
Hi,
> I am using xsane v0.97 together with the snapscan backend (from
> sane-backends v1.0.15) to drive an Epson 2580 Photo scanner. I'm
> scanning old black and white photographs. Scanning works fine, but the
> preview does not.
There seems to be a problem with previews on the 2580 in the
Hi,
> The CVS snapshot I downloaded for 20050815 didn't contain that
> patch. And the CVS version doesn't work for me now (whether I make
> that modification or not), I alternately get messages like
>
> scanimage: open of device snapscan:libusb:001:003 failed: Error
> during device I/O
>
> and
>
>
Hi,
> > If it is always the same ratio of real distance to scanned
> > distance (also for -l and -t) it is most likely that the
> > calculation of the scan area is not handled correctly. That could
> > be corrected by changing the value of pos_factor in function
> > set_window() in snapscan-scsi.c
Hi,
> I don't have access to that information right now, so I'll check
> that tonight also. It is whatever firmware came with the scanner -
> esfw52.bin.
yes, but at least for other epson scanners these firmware files are
available in different versions. The filename is always the same.
Anothe
Hi,
> That made scanimage recognize and use the scanner, but it is unable
> to scan the full page. It only scans 75-80% of the width and
> height. Subsequent questions have gone unanswered and I've had
> limited time to look into the backend code myself so I think my
> solution is to return the s
Hi,
> It says that that scanner is supported with support level "basic"
> by the snapscan backend.
>
> > sane-find-scanner gets vendor and product code but scanimage -L
> > finds nothing.
>
> Maybe your sane-backends package is just too old? As far as I know,
> you need version 1.0.16 for that sca
1 - 100 of 340 matches
Mail list logo
