[sane-devel] UMax Astra 2200 in 12-bit mode
I've seen this in 0.97 and 0.98. There's the option of scanning in 12-bit mode instead of 8-bit, but it doesn't seem to work. In my understanding of how it should work, if your scanner has 12/36 bit color instead of 8/24 bit you should be able to use some of that added dynamic range when scanning by using the level controls. If the image you're scanning doesn't have anything in the dark end, say 1/16 of the range, you should be able to set your dark slider above that and use the upper 15/16 of the 4096 range which would then get mapped into the 0..255 range for output. There shouldn't be any gaps in the "enhanced image" histogram because there's still a surplus. Anyway, I've put a small capture of what the preview window looks like in 12-bit mode at http://128.119.200.7/astra2200_12bit_preview.jpg The document is a black and white one, so the color in this is false. The actual scanned image looks about the same. Alan Still using an operating system that gets viruses, costs money, insults your intelligence, and then accuses you of stealing it? Why? www.openbsd.org __ Yahoo! DSL ? Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com
[sane-devel] Canon LiDE 60: Semi-success report
Henning Meier-Geinitz schrieb: > > I only get backtracking here with high load of the computer. However > I can confirm the horizontal lines. Looks like something connected to > backtracking at 16 bit doesn't fully work yet. I don't have > these lines in 8 bit mode. > Those corrupted horizontal lines are the result of a buffer overrun. I thought i did setup the "words per line" parameter correctly, but obviously i did not. In this case "word" seems to mean 1 byte while in other contexts it means 2 bytes. I will look into that, forcing backtracking in 16bit modes should not be too hard. Regards, Pierre
[sane-devel] Canon LiDE 60: Semi-success report
Hi, On Mon, Dec 05, 2005 at 12:00:30AM +0100, Reinhard Mayr aka Czerwinski wrote: > sorry, I did not realize that there is a difference between current CVS > and experimental. Are you really sure that you use experimental now? :-) Some of your errors occur for me with the normal CVS, but not with experimental. Also, when you get an error, make sure you unplug and replug the scanner when you do another test. Otherwise it may still be confused by the earlier test. Which frontend do you use? Is the scanner connected to a USB2 hub? Just to be sure: xsane 0.98 does have a bug that can cause stack corruption in the backend. While I didn't see this in connection with the genesys backend, it happend with other backends. Try to use xsane 0.98b or apply the bug fix Oliver Rauch posted on this list. I use xsane 0.98b for testing. Details: > gray/8bit: > 75: ok > 150: ok > 300: ok > 600: ok > 1200: ok > 2400: Error during read: error during device I/O. I can avoid this by > enforcing backtracking through system load (e.g. by task switching) No backtracking here. No I/O errors. Image is ok but stretched in Y-direction (as already mentioned in my report). You can enable debugging this way: SANE_DEBUG_GENESYS=255 SANE_DEBUG_GENESYS_GL841=255 xsane 2>log The logs may be to big to be send to this list, however so please try to compress them or place them on a website. The limit is 50 KB. > gray/16bit: > 75: ok > 150: ok > 300: ok > 600: backtracking. horizontal lines I only get backtracking here with high load of the computer. However I can confirm the horizontal lines. Looks like something connected to backtracking at 16 bit doesn't fully work yet. I don't have these lines in 8 bit mode. This also happens with the Canon LiDE 50. Here is a sample image of such a scan with forced backtracking (4.2 MB): http://www.meier-geinitz.de/sane/tmp/lide50/stripes-16bit-gray-0600.png > 1200: backtracking. Error during read: error during device I/O No error here. I get some backtracking and one or several strange horizontal lines when the scanner does backtracking. These lines contain data from the scanned image but are horizontally moved somehow. Data corruption? > 2400: backtracking. horizontal lines - picture is unusable Same here as for 1200 dpi. > color/8bit: > Segmentation fault at any resolution Works for me. Backtracking in high resolutions, but no stripes. Please create a log file and run the frontend in gdb and do a backtrace there (bt) when the error occurs. > color/16bit: > 600: Failed to start scanner: invalid argument > other resolutions: segmentation fault Works for me. No stripes even when backtracking with the Canon LiDE 60. However, I do get some stripes with the Canon LiDE 50. So there is a backtracking problem in 16 bit mode (3.5 MB): http://www.meier-geinitz.de/sane/tmp/lide50/stripes-16bit-color-0300.png Bye, Henning
[sane-devel] Re: Epson Perfection 3490 PHOTO
On Sun, 2005-12-04 at 22:54 +0100, Oliver Schwartz wrote: > Hi, > > > Is there anything I can do to help get the Transparency unit to > > work? > > As far as I know the transparency unit of the 3490 works ok. The only > thing not supported is the automatic film feeder of the 3590. Please > make sure you use the latest version of the snapscan backend from > CVS. The Epson Perfection 3490 I own works flawlessly (including the TPU). Levente
[sane-devel] Epson Perfection 3490 on Ubuntu Breezy 5.10?
Imar -- I will try this, thanks. dwh Imar van Erven Dorens wrote: > Hello Denis, > > I'm new to these mailing lists, so I hope I mail this alright. > I had the same problem like you, though before my 3490 I was > struggling to make an old canon scanner working with Xsane and learned > a bit.. > > 1: look into /etc/sane.d/dll.conf > Mine missed an entry to epkowa.conf which is essential for the 3490 > according to the iscan installation manual. > http://www.avasys.jp/english/linux_e/dl_scan.html (get the pdf) > So insert 'epkowa' into dll.conf > 2: restart saned: # saned restart > > 3: now try # scanimage -L > > I bet it works. > > Greetings,Imar. > ICQ: 11555901
