[sane-devel] Perl Bindings
2008/9/1 abel deuring adeuring at gmx.net: The test backend is a invaluably useful tool for testing: You get more or less any sort of device options; you can see if your bindings properly handle things like enabling/disabling of options, if you get the type conversion between Sane and Perl data types properly done etc etc. You even get perfectly reproducible, noise free, scan data :) Excellent. I'll use that. Additional tests with real-world devices are also useful, because the Sure, but I can only test it with mine :-) Is there a good reason why pkg-config files aren't built with SANE? The lack of them make dependency checking difficult before build-time. If I work up a patch to add them is it likely to be accepted? Regards Jeff
[sane-devel] Perl Bindings
On 02.09.2008 07:25, Jeffrey Ratcliffe wrote: 2008/9/1 abel deuring adeuring at gmx.net: The test backend is a invaluably useful tool for testing: You get more or less any sort of device options; you can see if your bindings properly handle things like enabling/disabling of options, if you get the type conversion between Sane and Perl data types properly done etc etc. You even get perfectly reproducible, noise free, scan data :) Excellent. I'll use that. Additional tests with real-world devices are also useful, because the Sure, but I can only test it with mine :-) Of course -- nobody expects that you'll be able to test your code with ten different scanners :) Is there a good reason why pkg-config files aren't built with SANE? The lack of them make dependency checking difficult before build-time. I think nobody yet bothered about that. If I work up a patch to add them is it likely to be accepted? I would not mind seeing Perl bindings included. But other Sane folks should give their opinion too. I could imagine that CPAN might be a better place for the bindings, since Perl developers might look for Perl modules there, I'd guess. (disclaimer: I am not a Perl developer, so I can't claim to have any real clue where/how to search for Perl modules...) Abel
[sane-devel] Perl Bindings
2008/9/2 abel deuring adeuring at gmx.net: I would not mind seeing Perl bindings included. But other Sane folks should give their opinion too. I could imagine that CPAN might be a better place for the bindings, since Perl developers might look for Perl modules there, I'd guess. (disclaimer: I am not a Perl developer, so I can't claim to have any real clue where/how to search for Perl modules...) I would certainly upload the module to CPAN, but that has no VCS or web space. My question was really whether the bindings should be included as part of SANE, or whether I should create a new project (probably also on Alioth). Regards Jeff
[sane-devel] Fujitsu FI-5220C and no Option for threshold possible?
Hello, I use scanner Fujitsu FI-5220C and it works fine. /usr/bin/scanadf --mode Gray --resolution 150 --source Flatbed -e 1 -s 1 -o foo.pnm -v scanadf: scanning image of size 1275x1650 pixels at 8 bits/pixel scanadf: acquiring gray frame scanadf: min/max graylevel value = 13/255 Scanned document foo.pnm Scanned 1 pages But I tried to modify the white point of scanned pages. But the option threshold, given by the help (scanadf --help -d fujitsu) is not recognized. /usr/bin/scanadf --mode Gray --resolution 150 --source Flatbed -e 1 -s 1 -o foo.pnm --threshold 100 -v /usr/bin/scanadf: unrecognized option `--threshold' So what is the right way to manipulate the brightness of scanned pages? with kind regards. Markus Haberkorn -- -- Markus Haberkorn mail : Markus_Haberkorn at genua.de Gesellschaft f?r UNIX- und tel. : +49 (89) 991950-0 Netzwerkadministration mbH fax. : +49 (89) 991950-999 Domagkstrasse 7www : http://www.genua.de D-85551 Kirchheim Gesch?ftsf?hrer: Dr. Magnus Harlander, Dr. Michaela Harlander, Bernhard Schneck. Amtsgericht M?nchen HRB 98238 --
[sane-devel] Fujitsu FI-5220C and no Option for threshold possible?
On Tue, Sep 2, 2008 at 7:56 AM, Markus Haberkorn Markus_Haberkorn at genua.de wrote: Hello, I use scanner Fujitsu FI-5220C and it works fine. /usr/bin/scanadf --mode Gray --resolution 150 --source Flatbed -e 1 -s 1 -o foo.pnm -v scanadf: scanning image of size 1275x1650 pixels at 8 bits/pixel scanadf: acquiring gray frame scanadf: min/max graylevel value = 13/255 Scanned document foo.pnm Scanned 1 pages But I tried to modify the white point of scanned pages. But the option threshold, given by the help (scanadf --help -d fujitsu) is not recognized. /usr/bin/scanadf --mode Gray --resolution 150 --source Flatbed -e 1 -s 1 -o foo.pnm --threshold 100 -v /usr/bin/scanadf: unrecognized option `--threshold' So what is the right way to manipulate the brightness of scanned pages? if you are running a recent version of sane, --brightness is what you want. --threshold is for setting the black/white break point in the lineart/halftone modes. your problem is that you need to run scanadf --help with your other parameters in it: scanadf --mode Gray --help if that does not show the brightness and contrast options, then a SANE upgrade might be required. allan with kind regards. Markus Haberkorn -- -- Markus Haberkorn mail : Markus_Haberkorn at genua.de Gesellschaft f?r UNIX- und tel. : +49 (89) 991950-0 Netzwerkadministration mbH fax. : +49 (89) 991950-999 Domagkstrasse 7www : http://www.genua.de D-85551 Kirchheim Gesch?ftsf?hrer: Dr. Magnus Harlander, Dr. Michaela Harlander, Bernhard Schneck. Amtsgericht M?nchen HRB 98238 -- -- 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] Perl Bindings
we have found that previous bindings that are included with sane are often not kept up-to-date by their authors, not installed by the distro vendors, and reimplemented by folks in their respective communities. I think outside hosting makes more sense. a patch for pkg-config would be accepted, if it is cross-platform. allan On Tue, Sep 2, 2008 at 7:04 AM, Jeffrey Ratcliffe jeffrey.ratcliffe at gmail.com wrote: 2008/9/2 abel deuring adeuring at gmx.net: I would not mind seeing Perl bindings included. But other Sane folks should give their opinion too. I could imagine that CPAN might be a better place for the bindings, since Perl developers might look for Perl modules there, I'd guess. (disclaimer: I am not a Perl developer, so I can't claim to have any real clue where/how to search for Perl modules...) I would certainly upload the module to CPAN, but that has no VCS or web space. My question was really whether the bindings should be included as part of SANE, or whether I should create a new project (probably also on Alioth). Regards Jeff -- 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] libusb-dev for Mac Leopard?
I'm still trying to get the Canon MP4150 working. In an attempt to debug, Nicolas recommended I use libusb-dev. Unfortunately, all I can find are packages and source for libusb. Does anyone have any experience creating a version of libusb-dev for mac? Even a location of source? Thanks, bob
[sane-devel] pixma MP810 working with sane
Hi, Concerning the vertical lines at 4800/2400 dpi for MP810, I'm wondering whether: - this is a normal behavior of the scanner (which would mean that it has to be compensated by the backend), - or if it's an alignment problem of the sensor, the lines corresponding each one to a particular sensor cell, but only at high dpi, the sensor uses all its cells to scan. I think it may be interesting that other MP810 users could give feedack on the current CVS backend, if possible, that's why I copy also the sane-devel list Do you know if there's an alignment procedure for MP810 ? This is usually the case when you get a new scanning device. Have you the possibility to test the Canon Windows driver, and see if it behaves the same ? FYI, the particular image encoding used by pixma devices at high dpi (giving a subset of images to be merged) is the same on newer generation devices (like MP610 with CIS sensor, or MP970 with CCD), but for those models, there's no effect of vertical lines, all cells are correctly aligned up to 4800 dpi. Also, I've not seen samples of scanned images for other older pixma devices (like MP600, MP960, ...), currently not supporting 2400 or 4800 dpi mode, but I'would be interested to know if those devices produces also such image subsets (which means it could be very easy to have them fully supported also by the pixma backend). Last point concerning the white lines at the bottom: this is simply due to the color planes shifting, as the backend algorithm to shift the color planes uses only that portion of the image that will contain data for the 3 colors. The bottom of the scanned image contains 2 and 1 color zones only, due to the color shift. So this is a little limitation for pixma CCD sensors, you must select a scan zone a little bit bigger at the bottom, then remove the image bottom white zone, that is padded on purpose by the backend to keep the image size the frontend expects. Another solution would have been to send to the frontend a smaller image, but this may raise some errors then in the frontend ... Nicolas Le mardi 02 septembre 2008 ? 00:38 +0200, Arne a ?crit : Hi Nicolas, here is the output from some scantests with the code you sent me: http://81.137.198.200/tmp/scantests2.tar.bz It's about 14 MB. I have scanned two small pictures at 4800dpi, 2400dpi and 1200dpi (the 1200dpi is so you can see how it's supposed to look like). The 4800dpi now has corect proportions and no duplication so there is some improvement, but it's still very fringed similar to the 2400dpi. Also in all resolutions there is always the bottom section that just stays white (despite it should contain scanned data as it's part of the selected area), I'm not sure if that's a xsane prblem or a MP810 driver specific problem? Best regards, Arne On Mon, 1 Sep 2008, Nicolas wrote: Hi Arne, I've added a small change to file pixma_mp150.c (attached), this should merge the 2 parts of the 4800 dpi image you get. The remaining resolutions should be unchanged. Could you give a try, and send the result of a small 4800 dpi scan ? Nicolas
[sane-devel] libusb-dev for Mac Leopard?
I just wanted a starting point. Don't worry. Your hand is safe. ;-) thanks bob On Sep 2, 2008, at 3:24 PM, BuildSmart wrote: On Sep 02, 2008, at 15:43 PM, Bob Dronski wrote: I'm still trying to get the Canon MP4150 working. In an attempt to debug, Nicolas recommended I use libusb-dev. Unfortunately, all I can find are packages and source for libusb. Does anyone have any experience creating a version of libusb-dev for mac? Even a location of source? Some people might say I have some experience in Mac OS X. Here's where I started, read how they generate the binaries for ubuntu, just ignore the .deb packaging related stuff and make sure you compile for i386 and x86_64 if you want proper support throughout the complete Leopard environment, the libraries are really useful, I'm just not interested in holding anyone's hand long enough for them to figure anything out, I've got my own issues to deal with. http://packages.ubuntu.com/hardy/i386/libusb-dev Thanks, bob -- 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 -- Dale -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080902/52663fd4/attachment-0001.htm
[sane-devel] libusb-dev for Mac Leopard?
Nicolas, That was the problem! Neither build of libusb that I had worked. I downloaded and built libusb from sourceforge and it is responding! Now back to rebuilding sane to the original mode and see what happens. Thanks! bob On Sep 2, 2008, at 4:13 PM, Nicolas wrote: I'm completely nuts about Mac OS, but I've browsed a little the libusb documentation (on libusb.sourceforge.net), and it seems that the libusb should compile straightforward for Mac, if you start from the libusb original package. So could you try also maybe to download the libusb from there, then compile/install it on your Mac, and then retry to build Sane after that ? Nicolas Le mardi 02 septembre 2008 ? 16:24 -0400, BuildSmart a ?crit : On Sep 02, 2008, at 15:43 PM, Bob Dronski wrote: I'm still trying to get the Canon MP4150 working. In an attempt to debug, Nicolas recommended I use libusb-dev. Unfortunately, all I can find are packages and source for libusb. Does anyone have any experience creating a version of libusb-dev for mac? Even a location of source? Some people might say I have some experience in Mac OS X. Here's where I started, read how they generate the binaries for ubuntu, just ignore the .deb packaging related stuff and make sure you compile for i386 and x86_64 if you want proper support throughout the complete Leopard environment, the libraries are really useful, I'm just not interested in holding anyone's hand long enough for them to figure anything out, I've got my own issues to deal with. http://packages.ubuntu.com/hardy/i386/libusb-dev Thanks, bob -- 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 -- Dale -- 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 -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080902/c3e8691d/attachment.htm
[sane-devel] Canon MP4150 - WORKS!!! (basically)
Dennis, Nicolas, and the rest of the list, Thanks so much for all your help. I'm thrilled to say that the scanner works after a new build of both libusb and Sane! There are a couple of issues that still occur, but basically, it works. I've done both flatbed and adf scanning. The only thing that is a problem is that it takes 2 attempts to actually scan. The first time generates an error Error during Device I/O. The second time, it scans fine. Also, attempting to scan a multi-page pdf only scanned a single page. I haven't gone back to the help pages to see if that's an issue or not. Thanks, bob
[sane-devel] pixma MP810 working with sane
On Tue, Sep 2, 2008 at 4:59 PM, Nicolas nicolas.martin at freesurf.fr wrote: Hi, Concerning the vertical lines at 4800/2400 dpi for MP810, I'm wondering whether: - this is a normal behavior of the scanner (which would mean that it has to be compensated by the backend), - or if it's an alignment problem of the sensor, the lines corresponding each one to a particular sensor cell, but only at high dpi, the sensor uses all its cells to scan. I think it may be interesting that other MP810 users could give feedack on the current CVS backend, if possible, that's why I copy also the sane-devel list Do you know if there's an alignment procedure for MP810 ? This is usually the case when you get a new scanning device. Have you the possibility to test the Canon Windows driver, and see if it behaves the same ? FYI, the particular image encoding used by pixma devices at high dpi (giving a subset of images to be merged) is the same on newer generation devices (like MP610 with CIS sensor, or MP970 with CCD), but for those models, there's no effect of vertical lines, all cells are correctly aligned up to 4800 dpi. Also, I've not seen samples of scanned images for other older pixma devices (like MP600, MP960, ...), currently not supporting 2400 or 4800 dpi mode, but I'would be interested to know if those devices produces also such image subsets (which means it could be very easy to have them fully supported also by the pixma backend). Last point concerning the white lines at the bottom: this is simply due to the color planes shifting, as the backend algorithm to shift the color planes uses only that portion of the image that will contain data for the 3 colors. The bottom of the scanned image contains 2 and 1 color zones only, due to the color shift. So this is a little limitation for pixma CCD sensors, you must select a scan zone a little bit bigger at the bottom, then remove the image bottom white zone, that is padded on purpose by the backend to keep the image size the frontend expects. Another solution would have been to send to the frontend a smaller image, but this may raise some errors then in the frontend ... i handle this specific issue for the old fujitsu M3091/2 by requesting a few more lines from the scanner than the user asked for, and throw away the extra ones after i shift the color planes. allan -- The truth is an offense, but not a sin
