[sane-devel] Xsane 0.996 Canon LIDE50 Ubuntu Karmic
I have done 4 scans at different resolutions as follows: 75, 150, 300, 600. My scanner won't accept 1200 or 2400. It says Failed to start scanner. Document feeder jammed. All scans are too dark and seem to be out of focus. Also, cannot close Xsane. Have to 'Force Quit' Scanner works perfectly with Windows. Cannot attach results due to limitations of this service. Would appreciate some help. Thanks...David -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100425/7ce6a57d/attachment.htm
[sane-devel] Xsane 0.996 Canon LIDE50 Ubuntu Karmic
2010/4/25 David Liell opus9743 at gmail.com: Cannot attach results due to limitations of this service. The maximum size is 100Ko for the attachment. - compress your files and see if the size decreases enough - host it with a webserver or ftp server - use a webservice -- St?phane
[sane-devel] SANE source compilation problems
you dont need to compile sane-frontends from devel source. use the last release, or skip it entirely. scanimage can do most things scanadf can, and the other programs in sane-frontends are not actively developed. allan On Sun, Apr 25, 2010 at 4:25 PM, Ilm?rs Poik?ns ilmars at delibero.lv wrote: Hi, I downloaded source from git repositories (sane-backends and sane-frontends) and tired to compile them. I have Ubuntu 9.10, needed dev library packages were there. sane-backends configure, make, make install was fine. sane-frontends configure failed. I traced problem down to /user/local/bin/sane-config having line: LIBS= -ldl -lv4l1?? -lm -ltiff -ljpeg? -lgphoto2 -lgphoto2_port -lexif -lm -lusb?? -lusb? @REGMGR_LIBS@ When I deleted @REGMGR_LIBS@ from that line, then sane-frontends configure run successfully. I didn't care about graphical frontends, so configure disabled GUI. Previously gcc tried to find that file and failed to compile some tests. So, my first question - Is it normal to have something like @REGMGR_LIBS@ unreplaced with some text after sane-backends make install? Then I got to second problem while making sane-frontends - compiling scanadf.c failed, make reported error: scanadf.c:995: error: ?SANE_STATUS_WARMING_UP? undeclared (first use in this function) Source for SANE_STATUS_WARNING_UP undeclared problem was in /usr/local/include/sane/sane.h (installed by make install in sane-backends) on line 74. Missing define is deactivated with #if 0 line above. When I changed #if 0 to #if 1 and enabled following two #define declarations, sane-frontends make was successful finally. Is it supposed to be so, that user needs to manually change something in installed files to make sane successfully? Or I found a feature or bug? Best regards, Ilmars Poikans -- 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 source compilation problems
It should compile fine in Ubuntu/Debian Make sure you have these pkgs before you configure: build-essential libusb-dev Cheers, Alejandro Imass On Sun, Apr 25, 2010 at 4:25 PM, Ilm?rs Poik?ns ilmars at delibero.lv wrote: Hi, I downloaded source from git repositories (sane-backends and sane-frontends) and tired to compile them. I have Ubuntu 9.10, needed dev library packages were there. sane-backends configure, make, make install was fine. sane-frontends configure failed. I traced problem down to /user/local/bin/sane-config having line: LIBS= -ldl -lv4l1?? -lm -ltiff -ljpeg? -lgphoto2 -lgphoto2_port -lexif -lm -lusb?? -lusb? @REGMGR_LIBS@ When I deleted @REGMGR_LIBS@ from that line, then sane-frontends configure run successfully. I didn't care about graphical frontends, so configure disabled GUI. Previously gcc tried to find that file and failed to compile some tests. So, my first question - Is it normal to have something like @REGMGR_LIBS@ unreplaced with some text after sane-backends make install? Then I got to second problem while making sane-frontends - compiling scanadf.c failed, make reported error: scanadf.c:995: error: ?SANE_STATUS_WARMING_UP? undeclared (first use in this function) Source for SANE_STATUS_WARNING_UP undeclared problem was in /usr/local/include/sane/sane.h (installed by make install in sane-backends) on line 74. Missing define is deactivated with #if 0 line above. When I changed #if 0 to #if 1 and enabled following two #define declarations, sane-frontends make was successful finally. Is it supposed to be so, that user needs to manually change something in installed files to make sane successfully? Or I found a feature or bug? Best regards, Ilmars Poikans -- 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
[sane-devel] SANE source compilation problems
On Sun, Apr 25, 2010 at 3:25 PM, Ilm?rs Poik?ns ilmars at delibero.lv wrote: Hi, I downloaded source from git repositories (sane-backends and sane-frontends) and tired to compile them. I have Ubuntu 9.10, needed dev library packages were there. sane-backends configure, make, make install was fine. sane-frontends configure failed. I traced problem down to /user/local/bin/sane-config having line: LIBS= -ldl -lv4l1?? -lm -ltiff -ljpeg? -lgphoto2 -lgphoto2_port -lexif -lm -lusb?? -lusb? @REGMGR_LIBS@ When I deleted @REGMGR_LIBS@ from that line, then sane-frontends configure run successfully. I didn't care about graphical frontends, so configure disabled GUI. Previously gcc tried to find that file and failed to compile some tests. This part was my fault. I recently fixed oen sane-config bug and introduced another. I've just submitted a fix so if you re-pulled sane-backends from git and reinstall, this part of the problem should go away. Others have replied about the remaining issues once @RESMGR@ typo is fixed. sane-frontend in current git contains some next generation API's that sane-backends has disabled. The released sane-frontends package is the one to use with released and git versions of sane-backends. Chris
[sane-devel] ADF Duplex performance problems
On Sun, Apr 25, 2010 at 4:45 PM, Ilm?rs Poik?ns ilmars at delibero.lv wrote: Hi, I'm running latest SANE from git source on Ubuntu 9.10. I was testing scaning A4 on Fujitsu ScanSnap 500 in 300 dpi Color uncompressed using scanadf. Everything is fine when scanning only one side of sheet (image size 24MB). But when scanning with ADF Duplex as source, scanner pauses 3 times during scanning. Two 24MB files are saved successfully. Clearly pausing is caused by data transfer issues somewhere. Does this happen on windows? Any ideas where could be the bottleneck? Scanner can't send data so fast over USB? Almost certainly. Buffer too small for USB transfers, so too many data exchange transactions creates delay and slowdown of throughput? You can try increasing the buffer-size option in /etc/sane.d/fujitsu.conf. I guess scanner is sending data from duplex scan interleaved - data block for front side, data block for back side. for the low-memory scanners like the S500, yes. Inefficient processing of such data in fujitsu-backend? Maybe problem caused by scanadf (or any other frontend), that can read images only one by one? Any ideas? as long as you have enough ram in the system to buffer the back side image, the backend can usually outrun the scanner. What is the status of SANE 2.0? Is there any functionality for retrieving many images simultaneously from one physical scan, like front and back of page during duplex scan, several image regions on pages? neither of those have been discussed for sane 2.0, but the 'multi-region' idea is probably a not going to happen. The first idea actually is already supported by the fujitsu backend. The 'low-memory' option causes the backend to do alternate transfers if required. You have to inspect the value of the 'side' option before each transfer to determine which image the next block will be for. This is only useful with a custom frontend, as nothing commonly used will support it. allan -- The truth is an offense, but not a sin
