[sane-devel] Scanbd installation with an Canon MX700
Am Donnerstag, den 20.12.2012, 13:52 +0100 schrieb Nelson: Hey mailinglist, here is an german howto that's describes the installation of Scanbd with sane backends. My scanner is a Canon MX700. http://www.mehr4u.de/component/k2/item/99-mit-scanbd-scannertasen-an-einem-canon-mx700-nutzen.html Great! Thank you. But you should not write Scannertasen in the headline :-) -- Viele Gr??e Werner Holtfreter
[sane-devel] Left paper side lost on genesys and MD6228
2011-07-15 13:41 wrote Werner Holtfreter: 2011-07-15 12:35 wrote Stef: I have re-tuned MD5345/6228 scan area. With latest source code version the bug is now fixed. Thank you very much! That is really high speed debugging! (I will enjoy it after distribution in Robert Ancell's ppa.) Now I work with Ubuntu 11.10 (Oneiric Ocelot) on AMD 64. The bug is still alive in Oneiric, but Robert Ancell did not make a ppa for that. Robert, do you have the aim to make a new ppa? -- Viele Gr??e Werner Holtfreter
[sane-devel] Left paper side lost on genesys and MD6228
2011-07-15 13:41 wrote Werner Holtfreter: 2011-07-15 12:35 wrote Stef: I have re-tuned MD5345/6228 scan area. With latest source code version the bug is now fixed. Thank you very much! That is really high speed debugging! (I will enjoy it after distribution in Robert Ancell's ppa.) Now I work with Ubuntu 11.10 (Oneiric Ocelot) on AMD 64. The bug is still alive in Oneiric, but Robert Ancell did not make a ppa for that. Robert, do you have the aim to make a new ppa? -- Viele Gr??e Werner Holtfreter
[sane-devel] Left paper side lost on genesys and MD6228
Ubuntu 11.4, gscan2pdf or xsane, genesys sane 1.0.22, scanner MD6228 http://ppa.launchpad.net/robert-ancell/sane-backends/ubuntu Hallo Stef, 2008-05-19 18:00 I reported some bugs which you fixed properly. Only a minor problem still exist for long time: 4 mm on the left paper side is not scanned. Please give me detailed instruction to collect all needed info. -- Viele Gr??e Werner Holtfreter
[sane-devel] Left paper side lost on genesys and MD6228
Hello Stef, 2011-07-15 12:35:43 schrieben Sie: I have re-tuned MD5345/6228 scan area. With latest source code version the bug is now fixed. Thank you very much! That is really high speed debugging! (I will enjoy it after distribution in Robert Ancell's ppa.) -- Viele Gr??e Werner Holtfreter
[sane-devel] [OT?] discussion of front ends?
Am Donnerstag, 14.07.2011 10:02:04 schrieb Johannes Meixner: I need a format that will still be useful for decades into the future. I mean that I cannot imagine a format (perhaps except plain ASCII text) where I am sure as of today that it will stay for decades into the future. Could be, you are right. But PDF/A would created and standardised to long time archive! (To make it more complicated, it exist more than one version of PDF/A.) I think, it would be enough to using a popular format like PDF/A because it will exist some programs to change to the next format in the future. The next problem is to create a *correct* PDF/A. To make sure this, it exist some programs and online checker. It seems to be needed :-( And a last question: I mean, it is enough to made one bit per pixel (lineart) for letters, but it exist examples for color scan in such cases - I don't know why: http://openlibrary.org/books/OL24347298M/Muhammedanisches_Recht_nach_Schafiitischer_Lehre -- Viele Gr??e Werner Holtfreter
[sane-devel] Blank threshold adjustable?
Hello, I'm using Ubuntu10.10, sane1.0.14-9 (thanks to Robert Ancell for PPA) and Jeffrey Ratcliffe's great gscan2pdf0.9.31. If I scan in colour, white paper is light grey. It could be nice to see the exact colour of white, but it is not nice for normal use. (And it could make greater a compressed file.) gscan2pdf -- Preferences -- Blank threshold did not make a difference. I need help to adjust the white level. -- Viele Gr??e Werner Holtfreter
[sane-devel] Blank threshold adjustable?
Hallo m allan, am Dienstag, 2011-02-15 15:21:56 schrieben Sie: If you are leaving the image in gray or color, you would need brightness/contrast/gamma controls from the sane backend, or possibly from gscan2pdf itself. I found brightness/contrast/gamma controls in xsane. After find out the right position from 3 parameters, it works. Back to my preferred gscan2pdf: It can call gimp and it is possible to make the same after scanning with the internal files from gscan2pdf. It gives more control for the user, but I can not see a simple procedure to modify all scans in the job in one step... -- Viele Gr??e Werner Holtfreter
[sane-devel] installing scanner on ubuntu
Am Freitag, 2010-02-12 03:55:01 schrieb Robert Ancell: There is an easier way... I've made a PPA containing the latest GIT version of the SANE backends: https://edge.launchpad.net/~robert-ancell/+archive/sane-backends Hi Robert, thank you for your great service, it works fine and is a good support for ubuntu newuser like me. -- Viele Gr??e Werner
[sane-devel] unsubsrcibe
Am Montag, 2010-01-04 12:49:29 schrieb hans paul: please unsubscribe me from the mailing list. You can do it self. Who is wrote in each signature: -- Unsubscribe: Send mail with subject unsubscribe your_password ? ? ? ? ? ? ?to sane-devel-request at lists.alioth.debian.org -- Viele Gr??e Werner Holtfreter
[sane-devel] Scan as pdf gives only blank page
Am Montag, 2009-05-04 16:43:14 schrieb cool.chris65 at web.de: I'm using xsane to create PDF-Docs to achive eg bills or other documents. After the update from Kubuntu 8.10 intrepid to 9.04 jaunty the pdf-docs allways includes only a blank page. Yes, pdf-creating with xsane0.995 is broken also in Suse11.0. My result was readable only in some pdf-readers, in others not. Today, I updated to xsane0.996 and can *not* reproduce this problem. You should test with xsane0.996. -- Viele Gr??e Werner Holtfreter
[sane-devel] Scan as pdf gives only blank page
Am Montag, 2009-05-04 20:43:24 schrieb Julien BLACHE: There was a bug related to the xref table in this version, it has been partly fixed in 0.996 but the bug still exists for multipage PDF. Thank you for the information. But xsane create only single-page-pdfs, isn't it? In other case: Which switch on xsane make a multipage-pdf? Is the frontend topic in this mailing list? -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Dienstag, 2008-08-26 20:45:01 schrieb stef: Le Wednesday 16 July 2008 16:39:18 Werner Holtfreter, vous avez ?crit?: Am Montag, 30. Juni 2008 06:53:34 schrieb stef: the only difference I could spot is slightly different motor acceleration tables. The ones generated by the backend are very close to the ones in windows logs, but in case your scanner's motor is less tolerant (or failing ?), it might not like them. But I'd like to be sure at what point the trouble arise. Could you try to trigger the problem with scanning scanning script at 100 dpi and do a CTRL-C when there is a motor trouble ? The log will show us at what exact the problem is happening. Done! I hit CTRL-C in the first second after bad motor noise, but the noise ended after 1/2 min and the prompt is back also after 1/2 min. Therefore, in the next test, I made a copy in the bad moment: cp scan.log scan.copy then, I hit CTRL-C. I send both files direct to you. -- Viele Gr??e Werner Holtfreter Hello, while moving scanner detection fron sane_init() to sane_get_devices(), I have reproduced the bug you encountered. I don't know how to fix it yet, but iti is related to scanner detection. I may be find something soon. Regards, Stef Hallo Stef, it would be wonderful, to have your fix in the next release :-) -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Hallo stef, am Freitag, 2008-08-29 07:13:37 schrieben Sie: I have committed a couple a GPO fixes. I have also commented out ASIC reset for GL646. I don't think it is usefull, and suppose it may mess things. Could you try latest CVS version to see if it fixes things for you ? The result: 1. The starting point at the top of page is more constant. It varies between 0...0,8 mm at the top. (O...0,8 mm loss. Earlier 8 mm!) 2. In most resolutions the scanner works properly. Only with 100 dpi, gray, sometimes (30 % from tests) the scanner head starts to shake and does not move properly! The old problem. -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Montag, 30. Juni 2008 06:53:34 schrieb stef: the only difference I could spot is slightly different motor acceleration tables. The ones generated by the backend are very close to the ones in windows logs, but in case your scanner's motor is less tolerant (or failing ?), it might not like them. But I'd like to be sure at what point the trouble arise. Could you try to trigger the problem with scanning scanning script at 100 dpi and do a CTRL-C when there is a motor trouble ? The log will show us at what exact the problem is happening. Done! I hit CTRL-C in the first second after bad motor noise, but the noise ended after 1/2 min and the prompt is back also after 1/2 min. Therefore, in the next test, I made a copy in the bad moment: cp scan.log scan.copy then, I hit CTRL-C. I send both files direct to you. -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Dienstag, 17. Juni 2008 06:38:30 schrieb stef: I've gone through the logs, and I think they are logs of another usb device on the windows machine where they have been recorded. Sorry, I'm late, but my access to a Windows-PC is difficult. Yes, the old logs come from the mouse, but in each cases the scanner was selected. The UsbSnoop-programms seems to work a bit incorrect. It takes more than one try to snoop the right device and not the mouse. My indikation was the growth from the log file with automatic refresh 1 s. I found 2 scanner-devices in the UsbSnoop-window, but only 1 was connected. Also, I have made a log with each device. Both works, 100 dpi, A4. I hope it helps. Files are coming direct. -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Sonntag, 15. Juni 2008 07:12:50 schrieb stef: thanks for the data. Unfortunately, the log is too small. A typical log should be a few MB big. For instance I recorded a preview and 100 dpi gray scan a couple centimeters high, and that led to a 22 MB log. I'm going to analyze the log I done to try to find a bug in the backend. But if you can produce a more complete windows log, I'd be able to compare it with the one I have to find if we have similar or slightly different hardware. Hello Stef, here are the next 3 experiments with UsbSnoop: 1 all from plug in 2 prescan and scann 3 only scann, 100 dpi, gray, full A4. Odd, the snoop-log grew while the mouse was moving, but not while the scanning! Of course, the marker installed was set only on the line USB scanner. (Files direct to you.) -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Mittwoch, 11. Juni 2008 21:39:01 schrieb stef: so this isn't a USB_SUSPEND issue. Could you try your scanner at 100 dpi gray scan on a windows PC ? If so, you can check that the scanner is working (ie no hardware issue), then record the USB communication with the usb sniffer available at http://www.pcausa.com/Utilities/UsbSnoop/default.htm . Then send me the log file of a 100 pdi scan so that I check that your scanner has really the same hardware than mine. The scanner works on windows. I sent the UsbSnoop.log direct to you. -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Dienstag, 10. Juni 2008 06:37:42 schrieb stef: I finally got time to look at the log. I noticed that the scan is failing due to incorrect scan parameters, not to MD6228 related problems. Please edit the script, and change scan to only (no geometry options): ../frontend/scanimage -d genesys --resolution 50 2scan.log scan Thanks, this works fine! The starting point at the top of page varies only between 0,4...0,8. But --resolution 100 (I have short tested with others, but seen only with 100) the old problem sometimes: The scanner head starts to shake and does not move properly. Sometimes means about 30 %. (Log comes direct to you.) -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Dienstag, 10. Juni 2008 21:09:58 schrieb stef: Thanks, this works fine! The starting point at the top of page varies only between 0,4...0,8. But --resolution 100 (I have short tested with others, but seen only with 100) the old problem sometimes: The scanner head starts to shake and does not move properly. Sometimes means about 30 %. (Log comes direct to you.) I've inspected the log. The only difference I can see with a 'reference' run here is that the hack used to reset the AFE isn't trigger here. Since I believe this issues are related to powersaving, could check if your linux kernel has been built with CONFIG_USB_SUSPEND=y ? The config file used to build kernel is often stored in /boot. I configured my kernel without it. It may be the difference. Hello, /boot/config-2.6.22.17-0.1-default contains: . . . # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=m # CONFIG_USB_DEBUG is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_DEVICE_CLASS is not set # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_SUSPEND is not set - # CONFIG_USB_OTG is not set . . . I'm not sure that it is, what you searching. I use: Suse10.3 2.6.22.17-0.1-default By the way: I've seen the same problem (scanner head starts to shake) on a Window-PC. (My scanner was earlier on a other PC.) -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Freitag, 6. Juni 2008 21:08:24 schrieb stef: this strange. This could be related to the possible lack of libusb you mention. On distributions, libraries are often split in two packages, one for runtime and another for development. You may have to check you have the 'devel' libusb package installed (there should be an /usr/include/usb.h file and a /usr/lib/libusb.a or libusb.so on your system). Also, when running configure, you may add the '--enable-libusb' switch to be sure libusb support is compiled in. To be sure run the following commands: make distclean ./configure --prefix=/usr --sysconfdir=/etc --enable-libsub Hello, only with ./configure --prefix=/usr --sysconfdir=/etc --enable-libsub was the same, the scanner don't work. And the warning was also the same, while configure: *** Warning: sane-backends will be built without libusb support. There may *** be valid reasons to do so, e.g. if you don't use USB scanners or on *** platforms without libusb support but generally this means that you *** can't use USB devices with SANE. The most probable cause is that *** the libusb header file usb.h is not installed. If you use Linux *** you may need a package called 'libusb-dev', 'libusb-devel' or similar. By the way: Many /other/ warnings are printed. Also, I installed libusb-devel, replayed all steps, but without the option --enable-libsub. The same /other/ warnings are printed, but *usb* works! Only the scanner don't move the head. scan.log is very large, I send it not in the e-mail-list but direct. -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Mittwoch, 4. Juni 2008 21:09:56 schrieb stef: you can compile and test CVS without installing it system-wide. In a command shell, create a directory then 'cd' to it. First you have to get the sources with (see http://www.sane-project.org/cvs.html): cvs -d:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/sane login cvs -z3 -d:pserver:anonymous at cvs.alioth.debian.org:/cvsroot/sane co sane-backends Once you have the sources, 'cd' to sane-backends, then configure the build with: ./configure --prefix=/usr --sysconfdir=/etc then compile with: make Then you can use the attached 'genesys' script (which must be copied in the sane-backends/backend directory) and run it to test your scanner with the new backend without installing it. It runs with full debug. You can edit it to change resolution, width, height and coordinates. The scanned picture will be in 'scan.pnm'. Hallo Stef, thank you for the helpfully instruction! In case you run any problem, let us know. The scanner didn't do anything. When compiling (or configure) I read a warning without usb... The scan.log: [sanei_debug] Setting debug level of genesys to 511. [genesys] SANE Genesys backend version 1.1 build 9 from sane-backends 1.1.0-cvs [genesys] sane_init: authorize != null [genesys] sane_init: little endian machine [genesys] sane_init: reading config file `genesys.conf' [genesys] sane_init: config file line 1: ignoring comment line [genesys] sane_init: config file line 2: ignoring empty line [genesys] sane_init: config file line 3: ignoring comment line [genesys] sane_init: config file line 4: ignoring comment line [genesys] sane_init: config file line 5: ignoring comment line [genesys] sane_init: config file line 6: ignoring comment line [genesys] sane_init: config file line 7: ignoring empty line [genesys] sane_init: config file line 8: ignoring comment line [genesys] sane_init: config file line 9: ignoring comment line [genesys] sane_init: config file line 10: ignoring empty line [genesys] sane_init: config file line 11: ignoring comment line [genesys] sane_init: config file line 12: ignoring comment line [genesys] sane_init: config file line 13: ignoring empty line [genesys] sane_init: config file line 14: ignoring comment line [genesys] sane_init: config file line 15: ignoring comment line [genesys] sane_init: config file line 16: ignoring empty line [genesys] sane_init: config file line 17: ignoring comment line [genesys] sane_init: config file line 18: ignoring comment line [genesys] sane_init: config file line 19: ignoring empty line [genesys] sane_init: config file line 20: ignoring empty line [genesys] sane_init: config file line 21: ignoring comment line [genesys] sane_init: config file line 22: ignoring comment line [genesys] sane_init: config file line 23: ignoring comment line [genesys] sane_init: config file line 24: ignoring empty line [genesys] sane_init: config file line 25: ignoring comment line [genesys] sane_init: config file line 26: trying to attach `usb 0x0461 0x0377' [genesys] sane_init: config file line 27: ignoring empty line [genesys] sane_init: config file line 28: ignoring comment line [genesys] sane_init: config file line 29: trying to attach `usb 0x03f0 0x0901' [genesys] sane_init: config file line 30: ignoring empty line [genesys] sane_init: config file line 31: ignoring comment line [genesys] sane_init: config file line 32: trying to attach `usb 0x04a9 0x2213' [genesys] sane_init: config file line 33: ignoring empty line [genesys] sane_init: config file line 34: ignoring comment line [genesys] sane_init: config file line 35: trying to attach `usb 0x04a9 0x221c' [genesys] sane_init: exit [genesys] sane_open: start (devicename = `genesys') lt-scanimage: open of device genesys failed: Invalid argument [genesys] sane_exit: start [genesys] sane_exit: exit -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Dienstag, 3. Juni 2008 20:12:29 schrieb stef: I not sure this would correct the problem you had a low black and white resolution scans. If there is still some problem, could you send me the debug log produced by running theses commands in a shell: export SANE_DEBUG_GENESYS=511 export SANE_DEBUG_GENESYS_GL646=511 scanimage -d genesys --resolution 50 2scan.log scan.pnm So that I can try to figure ou what is happening ? Do you mean I should test with my old Sane version or with the new CVS? If the new CVS doesn't work, then please send me the log done with the newer version. Sorry, Stef, I'm a stupid Suse10.3 user and install normally only rpm. I'm still working with sane-backends1.0.19-0-pm.2 genesys. If I should install a new CVS, then I would need instruction. -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Hallo stef, am Dienstag, 2008-06-03 06:46 schrieben Sie: I have commit a fix for the offset of scan area in latest SANE's CVS. Thank you very much! I not sure this would correct the problem you had a low black and white resolution scans. If there is still some problem, could you send me the debug log produced by running theses commands in a shell: export SANE_DEBUG_GENESYS=511 export SANE_DEBUG_GENESYS_GL646=511 scanimage -d genesys --resolution 50 2scan.log scan.pnm So that I can try to figure ou what is happening ? Do you mean I should test with my old Sane version or with the new CVS? -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Am Montag, 19. Mai 2008 21:04:22 schrieb stef: ???could you try to run scanimage with debug logs enabled with the following commands in a shell: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_GL646=255 scanimage -d genesys scan.pnm 2scan.log Thank you for the completly commands. The tar.gz.file is coming separat. Other interested person welcome, please send a e-mail. ??BTW, is your model really a MD6228 ? Yes, this is the number on the type label. -- Viele Gr??e Werner Holtfreter
[sane-devel] problems with genesys and MD6228
Suse10.3 sane-backends1.0.19-0-pm.2 genesys Tevion-scanner MD6228 Hello, it works, but not perfectly: 1. The starting point at the top of page is not constant. It varies between 0...8 mm. This results in the scanner head to crashing into the bottom of the scanner. 2. If I scan on *medium* resolution, then the scanner head moves in regular fashion. If I scan on *high* resolution, then the scanner head starts to move forwards normally, then slightly backwards and then forwards normally again and so on. The result is OK. Is the USB or the PC too slow? If I scan on *low* resolution and black/white for low data rate, then the scanner head starts to shake and does not move properly! All things are independent from the front-end and I have done tests with Kooka, Xsane and Xscanimage. Any ideas? -- Viele Gr??e Werner Holtfreter
