[sane-devel] Descreening halftones
well , maybe I thought this would be efficient to handle the picture cleaning very close to the scan process (as in usual scan softwares). On software side at this time no real descreen feature is available in GIMP or else, this is the missing link I advocate for. This commercial, binary only Windows junk software pieces also only do blur and re-sharpen and the like. not that sure, since some of those software ask the LPI http://en.wikipedia.org/wiki/Lines_per_inch (not to be mismatched with DPI!) and the screens angles in order to compute descreening, as seen in professional DTP world (binary Mac junk in that case ;-) You can use ImageMagick, ExactImage, Gimp, etc. to perform those tasks. yep but as a crap a dirty bluring or despeckle workaround, as you already mentionned here is some links about haltones and descreening http://home.att.net/~cthames/DeScreen1.htm http://en.wikipedia.org/wiki/Halftone http://www.descreen.net/eng/soft/descreen/descreen.htm thank you for reading -- On Friday 27 July 2007 09:39:40 Bertrik Sikken wrote: Quentin Bierent wrote: Hi there I've been checking sane from time to time and a key feature is still missing at this time every serious scanner user need descreen feature to get clean scan. Goole shows it's been various requests about this feature (aka detramage) Every other descreen workaround methods are quality degrading (blur, despeckle etc etc) only a specific and efficient descreen algorythm (with LPI and screens angles settings) can do a good job for profesionnal quality. This is the only way to get a good resolution scan with a low print quality original (halftone pictures in newspaper can be acquired and smoothed WITHOUT sacrifying resolution and final quality) This feature is available on every serious scanner software (agfa, binuscan...) I will send some examples later. I am aware this feature is tricky to implement but it will for sure lift SANE to new heights... What you propose sounds much like an image processing step, while sane is (currently) more about simply getting the data from the scanner. Before adding image processing to sane itself, I think there should at least be some kind of framework where it can fit in cleanly. -- *ORDICURE SARL* Tel : 0870785140 - Fax : 0320240535 31, rue de la Fonderie - 59200 Tourcoing - RCS RXTG 443 136 874 http://www.ordicure.com
[sane-devel] Error Messages
Le jeudi 19 juillet 2007, Edward Barton a ?crit?: Trying to get a Lexmark scanner portion of a X1185 to work in Ubuntu 6.06 with Sane. Consistently get 3 error messages as follows: a) Error during save: Broken pipes b) Error during save: Success c) Failed to execute printer command: lpr Have no idea of the meanings! Any idea's will be appreciated Hello, I didn't answered earlier since I was on hollydays. The X1185 model is only supported with the experimental version of the lexmark backend. You can get it at http://stef.dev.free.fr/sane/lexmark . This is a testing version that let you test scanning. It is allready working for at least one person. Once it will work for you, I'll consider moving this experimental version into regular sane backends. Let me know if it works or any problem you could have. Regards, Stef
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'nevir at inevir.com' 2. Manufacturer (e.g. Mustek): 'SYSCAN Inc.' 3. Model name (e.g. ScanExpress 1200UB): 'TravelScan Pro 2300U' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x0a82' 6. Product id (e.g. 0x0002): '0x2000' 7. Chipset (e.g. lm9831): 'LM9832/3' 8. Comments (e.g. similar to Mustek 1234): 'This USB chip looks like a LM9832/3 (result from sane-backends 1.0.18).' 9. Data (e.g. sane-find-scanner -v -v): 'This is sane-find-scanner from sane-backends 1.0.18 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking
[sane-devel] Workaround for CONFIG_USB_SUSPEND now in CVS
On Sun, 2007-07-29 at 20:52 +0200, Julien BLACHE wrote: So, as of a few minutes ago, the udev rules generated by sane-desc include a new RUN rule that will disable the USB autosuspend feature for all the scanners we know. That's the end of black scans as long as you run a kernel = 2.6.22 and this sysfs interface doesn't change :-) (For those new to the issue you can read an Ubuntu bug about the issue over on https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/85488 ). I'm not 100% sure this is the right thing. Perhaps there should be a whitelist packaged up with SANE that tracks those scanners that do not need USB autosupsend disabled? I mention this because any power savings that USB autosupend was intended to implement will be undone by this if a scanner is plugged in (although you can argue that you probably don't care about power if you use a scanner). Additionally, is it possible to only implement this just before scanning? -- Sitsofe | http://sucs.org/~sits/
[sane-devel] Workaround for CONFIG_USB_SUSPEND now in CVS
Sitsofe Wheeler sitsofe at yahoo.com wrote: Hi, I'm not 100% sure this is the right thing. Perhaps there should be a whitelist packaged up with SANE that tracks those scanners that do not need USB autosupsend disabled? I mention this because any power savings We've had this problem with pretty much every popular brand of scanners, so if there are non-buggy scanners out of there I can probably count them on the fingers of my right hand. (before you ask, I've got 5 fingers on each hand ;) that USB autosupend was intended to implement will be undone by this if a scanner is plugged in (although you can argue that you probably don't care about power if you use a scanner). The power savings only benefits to laptop users when they're on battery. Moreover, most scanners aren't bus-powered. For laptop users, they'll just learn to unplug their scanner and that's it. (keeping the scanner plugged in usually means that the lamp will stay on until it's unplugged, so they'll save on that too) Additionally, is it possible to only implement this just before scanning? Not easily. As most scanners do an unplug/plug cycle when they're suspended, their address on the bus changes and their device ID may change too, which makes it even harder to go and disable suspend when the application is started. You can add to that all the scanners that change their USB ID and do an unplug/plug cycle once they've got their firmware... Countless hours of fun. Anyway, you're free to use this workaround or not :) Now, for the manufacturers that may read us, if you could fix your hardware... JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] Workaround for CONFIG_USB_SUSPEND now in CVS
On 7/29/07, Julien BLACHE jb at jblache.org wrote: That's the end of black scans as long as you run a kernel = 2.6.22 and this sysfs interface doesn't change :-) Julien- many thanks, both for the code, and for the description of the solution. Now we just have to get all the distros to use it :) allan -- The truth is an offense, but not a sin
[sane-devel] Workaround for CONFIG_USB_SUSPEND now in CVS
m. allan noah kitno455 at gmail.com wrote: That's the end of black scans as long as you run a kernel = 2.6.22 and this sysfs interface doesn't change :-) Julien- many thanks, both for the code, and for the description of the solution. Now we just have to get all the distros to use it :) You're welcome ;) As for the distros, it shouldn't take long :] I just hope the sysfs attribute won't disappear in the next kernel version. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] Problems to install a Mustek BearPaw 2448 TA Pro
Hello, I have now tried SANE_DEBUG_MUSTEK_USB2=4 ; xscanimage and the scanner is recognized. [sanei_debug] Setting debug level of mustek_usb2 to 4. [mustek_usb2] SANE Mustek USB2 backend version 1.0 build 10 from sane-backends 1.0.18 [mustek_usb2] sane_init: authorize == null [mustek_usb2] attach_one_scanner: devname = libusb:002:002 [mustek_usb2] Asic_Open: device libusb:002:002 successfully opened In syslog, however I find Jul 30 17:41:42 tux kernel: ppdev0: registered pardevice Jul 30 17:41:42 tux kernel: ppdev0: unregistered pardevice Jul 30 17:41:43 tux kernel: ppdev0: registered pardevice Jul 30 17:41:45 tux kernel: ppdev0: negotiated back to compatibility mode because user-space forgot Jul 30 17:41:45 tux kernel: ppdev0: released pardevice because user-space forgot Jul 30 17:41:45 tux kernel: ppdev0: unregistered pardevice and The problem I still have, is that Xsane hangs while trying to detect the scanner and Kooka doesn?t start at all. One thing I have found out is that there is no device /dev/usbscanner0 present as I have turned on in mustek_usb.conf. What can I do? Regards Harry
