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 halftoning, > though broken. If it's done by the scanner, it could indicate then > it is capable of some kind of halftoning. The backend only calculates some matrices and downloads them to the scanner. The actual halftoning is done by the scanner itself. > > > PS: will be 2400 dpi enabled in the future? And why does the > > > windows driver allow 2400 dpi but not 1600? > > > > You'd have to ask the epson guys. My guess is that the scanner > > scans at 3200 DPI if 2400 DPI is requested and the decimating to > > 2400 DPI is done in software. > > Yes, it was also my guess. There is also decimation at 1600 dpi, > isn't it (and at all resolutions below 3200)? The decimation > patterns are evident for most if not all small resolution modes (I > checked it last time), only this decimation is maybe done in > hardware instead of software. But of course it is easier to throw > away every other column/line instead of one of four. Below 3200 DPI only one sensor line is used. 3200 DPI uses two sensor lines with a small offset (that's why the deinterlacer is needed for this resolution). For all other resolutions the decimation is done by the scanner itself. > One further question: do you know what the real hardware resolution > of the Perfection 3490 is? In the technical data sheet Epson states > it is 3200x6400 dpi. These 6400 dpi are maybe attained with the > stepper motor (as was the case with my former 600x1200 dpi > scanner). Yes, thats correct. However, the vertical resolution is fixed at 3200 DPI. For a usable image the backend would have to do some kind of interpolation to deliver 6400x6400 DPI. /Oliver -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051125/8624a326/attachment.pgp From s...@geekpages.co.uk Fri Nov 25 19:10:03 2005 From: s...@geekpages.co.uk (Chris) Date: Fri Nov 25 19:10:11 2005 Subject: [sane-devel] Canoscan LiDE 25 detected by find-scanner, not scanimage In-Reply-To: <20051125174609.gj7...@meier-geinitz.de> References: <eef4bad00511210647r7d6695e5y69e30e31372f5...@mail.gmail.com> <20051125174609.gj7...@meier-geinitz.de> Message-ID: <eef4bad00511251110w1708dd89uf14dd649d8098...@mail.gmail.com> Hi Guys, Thanks for the suggestions. I haven't got it working yet, but I think the reason for the failure may be getting closer. First I removed everything except plustek from the dll.conf file. As expected the TV card was no longer picked up by scanimage but unfortunately, neither was the CanoScan. So I did the following as per Henning's suggestion: export SANE_DEBUG_PLUSTEK=12 export SANE_DEBUG_DLL=12 export SANE_DEBUG_SANEI_USB=255 scanimage -L The output was as follows: [sanei_debug] Setting debug level of dll to 12. [dll] sane_init: SANE dll backend version 1.0.11 from sane-backends1.0.16-cvs [dll] sane_init: reading dll.conf [dll] add_backend: adding backend `plustek' [dll] sane_get_devices [dll] load: searching backend `plustek' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-plustek.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-plustek.so.1' [dll] init: initializing backend `plustek' [sanei_debug] Setting debug level of plustek to 12. [sanei_debug] Setting debug level of sanei_usb to 255. [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory [sanei_usb] sanei_usb_init: found 0 devices [plustek] Plustek backend V0.50-7, part of sane-backends 1.0.16-cvs [plustek] Retrieving all supported and conntected devices [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0010 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0011 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0017 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0015 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0017 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0013 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0013 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0011 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0010 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0014 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0015 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0014 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0016 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0017 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0017 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0007 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x000f [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x000f [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0005 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0014 [sanei_usb] sanei_usb_find_devices: vendor=0x07b3, product=0x0012 [sanei_usb] sanei_usb_find_devices: vendor=0x0400, product=0x1000 [sanei_usb] sanei_usb_find_devices: vendor=0x0400, product=0x1001 [sanei_usb] sanei_usb_find_devices: vendor=0x0400, product=0x1001 [sanei_usb] sanei_usb_find_devices: vendor=0x0458, product=0x2007 [sanei_usb] sanei_usb_find_devices: vendor=0x0458, product=0x2008 [sanei_usb] sanei_usb_find_devices: vendor=0x0458, product=0x2009 [sanei_usb] sanei_usb_find_devices: vendor=0x0458, product=0x2013 [sanei_usb] sanei_usb_find_devices: vendor=0x0458, product=0x2015 [sanei_usb] sanei_usb_find_devices: vendor=0x0458, product=0x2016 [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x0505 [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x0605 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010f [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x011d [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0050 [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0060 [sanei_usb] sanei_usb_find_devices: vendor=0x1606, product=0x0160 [sanei_usb] sanei_usb_find_devices: vendor=0x049f, product=0x001a [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x2206 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x2207 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x2208 [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x220d [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x220e [sanei_usb] sanei_usb_find_devices: vendor=0x04a9, product=0x2220 [plustek] Available and supported devices: [plustek] NONE. [plustek] ># Plustek-SANE Backend configuration file< [plustek] ># For use with LM9831/2/3 based USB scanners< [plustek] >#< [plustek] >< [plustek] ># each device needs at least two lines:< [plustek] ># - [usb] vendor-ID and product-ID< [plustek] ># - device devicename< [plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)< [plustek] ># [usb] 0x07B3 0x0017< [plustek] ># device /dev/usbscanner< [plustek] ># or< [plustek] ># device libusb:bbb:ddd< [plustek] ># where bbb is the busnumber and ddd the device number< [plustek] ># make sure that your user has access to /proc/bus/usb/bbb/ddd< [plustek] >#< [plustek] ># additionally you can specify some options< [plustek] ># warmup, lOffOnEnd, lampOff< [plustek] >#< [plustek] ># For autodetection use< [plustek] ># [usb]< [plustek] ># device /dev/usbscanner< [plustek] >#< [plustek] ># or simply< [plustek] ># [usb]< [plustek] >#< [plustek] ># or if you want a specific device but you have no idea about the< [plustek] ># device node or you use libusb, simply set vendor- and product-ID< [plustek] ># [usb] 0x07B3 0x0017< [plustek] ># device auto< [plustek] >#< [plustek] ># NOTE: autodetection is safe, as it uses the info it got< [plustek] ># from the USB subsystem. If you're not using the< [plustek] ># autodetection, you MUST have attached that device< [plustek] ># at your USB-port, that you have specified...< [plustek] >#< [plustek] >< [plustek] >[usb] 0x04a9 0x2220< [plustek] next device is a USB device (0x04A9-0x2220) [plustek] ... next device [plustek] >< <snip config stuff> [plustek] Decoding device name >auto< [plustek] >< [plustek] >#< [plustek] ># to define a new device, start with a new section:< [plustek] ># [usb]< [plustek] >#< [plustek] attach (auto, 0xbff4f4fc, (nil)) [plustek] Device configuration: [plustek] device name : >auto< [plustek] USB-ID : >0x04A9-0x2220< [plustek] model ovr. : 0 [plustek] warmup : -1s [plustek] lampOff : 300 [plustek] lampOffOnEnd : yes [plustek] cacheCalData : no [plustek] altCalibrate : no [plustek] skipCalibr. : no [plustek] skipFine : no [plustek] skipFineWhite: no [plustek] invertNegs. : no [plustek] dis.Speedup : no [plustek] pos_x : 0 [plustek] pos_y : 0 [plustek] pos_shading_y: -1 [plustek] neg_x : 0 [plustek] neg_y : 0 [plustek] neg_shading_y: -1 [plustek] tpa_x : 0 [plustek] tpa_y : 0 [plustek] tpa_shading_y: -1 [plustek] red gain : -1 [plustek] green gain : -1 [plustek] blue gain : -1 [plustek] red offset : -1 [plustek] green offset : -1 [plustek] blue offset : -1 [plustek] red lampoff : -1 [plustek] green lampoff: -1 [plustek] blue lampoff : -1 [plustek] red Gamma : 1.00 [plustek] green Gamma : 1.00 [plustek] blue Gamma : 1.00 [plustek] gray Gamma : 1.00 [plustek] --------------------- [plustek] usbDev_open(auto,0x04A9-0x2220) - (nil) [sanei_usb] sanei_usb_open: trying to open device `auto' [sanei_usb] sanei_usb_open: can't find device `auto' in list [plustek] sanei_usb_open failed: No such file or directory (2) [plustek] open failed: -1 [dll] init: backend `plustek' is version 1.0.0 [plustek] sane_get_devices (0xbff51648, 0) [dll] sane_get_devices: found 0 devices No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [dll] sane_exit: exiting [dll] sane_exit: calling backend `plustek's exit function [plustek] sane_exit [dll] sane_exit: finished This bit struck me as strange: sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory [sanei_usb] sanei_usb_init: found 0 devices Is that normal? Incase it's helpful, the output of lsusb is: Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 002: ID 04a9:2220 Canon, Inc. Bus 002 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 So as far as I can tell the usb system knows the scanner is there ok. Any ideas what's going on here? Thanks again - you guys rock :-) Chris
