[sane-devel] cdrecord fails if SANE is running
Hi, As the title says, cdrecord (even the prodvd-version) fails if xsane is=20 running. I mailed a bug-report to the maintainer of cdrecord, but I thou= ght=20 it would be nice if this mailinglist knew about it too. J=F6rg Schilling=20 probably will not respond. A small log is below. As far as I can see, SANE holds the sg-device open, even when it doesn't = scan.=20 On the other hand, cdrecord fails if it cannot open a device, instead of = just=20 skipping it. By the way: not only with -scanbus, also when it is used fo= r=20 recording. ljm [root@Ronsard ljm]# cdrecord -scanbus Cdrecord-Clone 2.01a19 (i686-redhat-linux-gnu) Copyright (C) 1995-2003 J=F6= rg=20 Schilling Linux sg driver version: 3.1.24 Using libscg version 'schily-0.7' cdrecord: Warning: using inofficial libscg transport code version (schily= -=20 Red Hat-scsi-linux-sg.c-1.75-RH '@(#)scsi-linux-sg.c 1.75 02/10/21=20 Copyright 1997 J. Schilling'). scsibus0: 0,0,0 0) 'IBM ' 'IC35L018UWD210-0' 'S5BS' Disk 0,1,0 1) 'NEC ' 'CD-ROM DRIVE:466' '1.26' Removable CD-RO= M 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) 'QUANTUM ' 'ATLAS_V_18_WLS ' '0230' Disk 0,7,0 7) * 0,9,0 9) 'QUANTUM ' 'ATLAS10K3_36_WLS' '020W' Disk scsibus1: 1,0,0 100) * 1,1,0 101) * 1,2,0 102) 'Nikon ' 'LS-2000 ' '1.31' Removable Scann= er 1,3,0 103) * 1,4,0 104) * 1,5,0 105) 'UMAX' 'Astra 1220S ' 'V1.3' Scanner 1,6,0 106) * 1,7,0 107) * scsibus2: 2,0,0 200) * 2,1,0 201) * 2,2,0 202) * 2,3,0 203) * 2,4,0 204) * 2,5,0 205) * 2,6,0 206) 'IOMEGA ' 'ZIP 100 ' 'P.04' Removable Disk 2,7,0 207) * scsibus3: 3,0,0 300) 'SAMSUNG ' 'DVD R/RW SH-W08A' '1S30' Removable CD-RO= M 3,1,0 301) * 3,2,0 302) * 3,3,0 303) * 3,4,0 304) * 3,5,0 305) * 3,6,0 306) * 3,7,0 307) * [root@Ronsard ljm]# xsane & [1] 26430 (windows open, first complaining about root, then for choosing the=20 Nikon-scanner, then the XSane user-interface) [root@Ronsard ljm]# cdrecord -scanbus Cdrecord-Clone 2.01a19 (i686-redhat-linux-gnu) Copyright (C) 1995-2003 J=F6= rg=20 Schilling Linux sg driver version: 3.1.24 cdrecord: Device or resource busy. Cannot open '/dev/sg4'. Cannot open SC= SI=20 driver. cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are= =20 root. cdrecord: For possible transport specifiers try 'cdrecord dev=3Dhelp'. [root@Ronsard ljm]# --=20 (c) ljm ( xs4all)No part of this copyright message may be=20 reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Announcing: Coolscan2 and the dust-off plug-in fot GIMP2
Hi, We proudly present: The dirty-duster plugin for GIMP2 version 3 I have tested it under GIMP 1.2 and that works. Julien Blache ported the C-code to GIMP-2. I have not been able to test the script-fu part, so please send some feedback about it. It can be foud on my home-page: www.xs4all.nl/~ljm (look for the SANE-logo) ljm -- (c) ljm ( xs4all)No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] sane-coolscan2.
On Wednesday 15 December 2004 06:34, Hubert Figuiere wrote: > On Wed, 2004-12-15 at 00:05 +0100, Laurent-jan Dullaart wrote: > > > There is a script-fu/gimp1-plugin for the coolscan2-backend available at: > > > > www.xs4all.nl/~ljm/dirtyduster.tar > > > > Works quite well for small scratches or dust. You'll need some experimenting > > with enhancing the contrast in the infra-red image. Also, see > > > > http://andreas.rick.free.fr/sane/ > > > > for the original plugin. The plug-in part from my tar is practically an > > unchanged copy of this. Andreas also explains a bit how it works. > > At one time I did port it to Gimp-1.2. Patch available there: > > http://www.figuiere.net/projects/dustrm/ > > Perhaps should I port it to 2.0 ? > > Cheers > > Hub > -- Julien Blache promissed to have a look at it and help port it to GIMP2. I am still running GIMP1.2, so I have no experience writing plug-ins for GIMP2 and I cannot test it. Of course, if you'd port it, you'd save him some work :-) Just wondering: how many scanners are there (apart from the coolscan series) that support an infra-red channel? And how do the backends for those scanners handle this channel; how do you get it in the GIMP? As an alpha chanel (like the coolscan) or as an additional picture (like the coolscan2)? From previous discussions about the coolscan, I remember that the SANE-standard does not really cover this. -- (c) ljm ( xs4all)No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] sane-coolscan2.
On Tuesday 14 December 2004 10:47, Johannes Berg wrote: > Hi, > > >What do you mean? I need it? :P But do you know another tool for removing > >dust and scratches? I use compressed air and a very soft brush. :-) > > > > > There's a recent message giving a hint that someone has implemented this > in gimp-fu (and you can google for that relatively easily) > > johannes > > There is a script-fu/gimp1-plugin for the coolscan2-backend available at: www.xs4all.nl/~ljm/dirtyduster.tar Works quite well for small scratches or dust. You'll need some experimenting with enhancing the contrast in the infra-red image. Also, see http://andreas.rick.free.fr/sane/ for the original plugin. The plug-in part from my tar is practically an unchanged copy of this. Andreas also explains a bit how it works. -- (c) ljm ( xs4all)No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Coolscan Dust-off plugin under GIMP2
Hi, Has anyone got the dust-off plugin as made by Andeas Rick working under GIMP2? Either directely or via my little script-fu? I got some reports that the plug-in hangs under GIMP2. As I am still under GIMP1 and as yet have no plans to upgrade in the near future, I would be gratefull for some help, hints or reports. ljm -- (c) ljm ( xs4all)No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Problems compiling on RH9 with gimp2
Hi, I am trying to upgrade to gimp2. I installed everything from RPM's, except sane and xsane. On a clean RH9 installation (workstation), I had to install the following to get GIMP2 working: aalib-1.4.0-5.1.fc1.fr.i386.rpm atk-devel-1.2.0-2.i386.rpm exif-0.5-1.i386.rpm fontconfig-2.2.1-6.1.i386.rpm fontconfig-devel-2.2.1-6.1.i386.rpm freetype-devel-2.1.3-6.i386.rpm freetype-utils-2.1.3-6.i386.rpm gimp-2.0.1-1.i386.rpm gimp-devel-2.0.1-1.i386.rpm glib2-devel-2.2.1-1.i386.rpm gtk2-2.2.4-5.1.i386.rpm gtk2-devel-2.2.4-5.1.i386.rpm gtk+-devel-1.2.10-25.i386.rpm lcms-1.10-1.i386.rpm libcroco-0.3.0-1.i386.rpm libexif-0.5.12-1.fr.i386.rpm libexif-0.5.8-1.i386.rpm libexif-devel-0.5.12-1.fr.i386.rpm liblcms-1.12-2.i386.rpm pango-devel-1.2.1-3.i386.rpm pkgconfig-0.14.0-3.i386.rpm XFree86-devel-4.3.0-2.i386.rpm This should give sufficient version-information . Sane-backends: no problems. sane-frontends cannot be compiled; configure complains: gimp.h not found. The RPM from Gimp.org puts it in: /usr/include/gimp-2.0/libgimp/gimp.h As a quick & dirty solution, I tried: ln -s /usr/include/gimp-2.0/libgimp/ /usr/include/libgimp/ did not help: configure complains a lot about syntax-errors and othe includes are not found (libgimpcolor/gimpcolor.h, libgimpmath/gimpmath.h, libgimpbase/gimpbase.h) checking for GTK+ - version >= 2.0.0 /usr/lib/libfontconfig.so.1: undefined reference to `FT_Get_BDF_Property' This could be a fontconfig-problem, but all he RPM's installed without problem. Xsane: Same GTK-problem. Xsane, however compiles, but not as GIMP-plugin. Starting xsane gives the license-agreement (which I accepted). Next is the small window "Scanning for devices". Xsane hangs. Next I commented out all the unused backends (i.e. everything but coolscan2 and umax). That worked. Xsane still refuses to save as jpeg, tiff and others. The gtk-errors may be a problem with incorrect RPM's that have nothing to do with SANE. I'm looking into that. Still: the combination with gimp2 is not as smooth as it should be. ljm -- (c) ljm ( xs4all)No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Xsane 0.92: make fails with /bin/sh: no: command not found
On Sunday 25 April 2004 13:41, Henning Meier-Geinitz wrote: > Hi, > > On Sun, Apr 25, 2004 at 10:50:48AM +0200, Laurent-jan Dullaart wrote: > > As a part of rejuvenating the FAQ, I went through rhe installation process > > again. My first dissapointment was the need to upgrade GIMP if I wanted to > > compile the sane-frontends as GIMP plug-in. Oh, well... > > Which version of gimp did you want to use? 1.2.0 > I tested 1.2.0 and 2.0 and both > worked. Older versions should also work but I didn't test them. > That surprises me a bit. Reading the config-log, I'd think 1.3.23 was the minimum version: configure:8004: checking for GIMP - version >= 1.3.23 configure:8166: gcc -o conftest -g -O2 -Wall -D_GNU_SOURCE conftest.c -lm >&5 conftest.c:10:1: warning: "PACKAGE_VERSION" redefined conftest.c:5:1: warning: this is the location of the previous definition In file included from conftest.c:53: On the other hand, the SANE-API is sufficiently well designed to be able to use the older frontends(1.0.9) with the new backends (1.0.13) without recompiling the oldones. > > But more seriously: when compiling the xsane 0.92, I got the message: > > > > file=./`echo cs | sed 's,.*/,,'`.gmo \ > > && rm -f $file && PATH=../src:$PATH no -o $file cs.po > > /bin/sh: no: command not found > > make: *** [cs.gmo] Error 127 > > > > Browsing through the mailinglist, I found that a > > ./configure --disable-nls > > avoided this errormessage. So I got xsane compiled and running. But it is > > a nasty errormessage that should get fixed. > > Looks like a real bug in xsane: While the configure script tests for > msgformat, it still tries to run that program if it's not present. It > doesn't help to use the internal NLS in that case as it doesn't > provide msgformat either. xsane should disable NLS in that case > automatically. > > xsane comes with .gmo files bu they are older then the .po files so > the Makefile rebuilds them. > From: http://lists.alioth.debian.org/pipermail/sane-devel/2003-June/008196.html and some mails on the 0.80-version I understand that the problem has been there before. -- (c) ljm ( xs4all)No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Xsane 0.92: make fails with /bin/sh: no: command not found
Hi, As a part of rejuvenating the FAQ, I went through rhe installation process again. My first dissapointment was the need to upgrade GIMP if I wanted to compile the sane-frontends as GIMP plug-in. Oh, well... But more seriously: when compiling the xsane 0.92, I got the message: file=./`echo cs | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=../src:$PATH no -o $file cs.po /bin/sh: no: command not found make: *** [cs.gmo] Error 127 Browsing through the mailinglist, I found that a ./configure --disable-nls avoided this errormessage. So I got xsane compiled and running. But it is a nasty errormessage that should get fixed. -- (c) ljm ( xs4all)No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Digital ICE support
Sorry for the late reaction, but: On Monday 01 December 2003 15:29, Major A wrote: > > I think that IR cleaning is a front end task personally. For starters > > you can tweek the IR cleaning parameters after the image has been > > scanned if you are not happy with the default ones, without having > > to scan the image again. > > Agreed. I think there should be a sanei_* library that allows the code > to be used in frontends or meta-backends, whichever solution is > best. (Just think of a network scanner that is accessed by a handheld > device -- you don't want the IR cleaning to be done on the handheld.) I recall that someone suggested that there should be something like a "mid-end" (like saned) that does the correction. This would keep front-ends simple and provide a moer uniform way to access features like IR-correction. > > > Which is why IR cleaning should be a front end operation, with a set of > > default parameters for the most common scenario. I note that Vuescan > > only provides light, medium and heavy options in the front end for > > this. Clearly there is not a lot of need to twiddle parameters. I do not agree that there is little need for correction. When I try to correct using the simple GIMP-plugin, I find that both brightness and contrast of the IR-chanel are critcal and they must be set for each image separately. Also, the exposure for the IR-chanel seems important. <...> Another reason why a mid-end could be better than the front-end is, that the mid-end can scan always at full bit-resolution (12 bits on my LS-2000), do the calculations and then round to 8 bits. hm... maybe it's time for me to pick-up programming again... ljm -- (c) ljm ( xs4all)No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author.
[sane-devel] Translation status
On Tuesday 26 August 2003 01:04, Till Kamppeter wrote:
> Yann E. MORIN wrote:
> > Good {evening,morning,afternoon} all!
> >
> > (Sorry Henning for the private mail... Still not used to the reply policy!
;-/)
> >
> > Once upon a time (on Friday 22 August 2003 20:05), Henning Meier-Geinitz
wrote :
> > > fr Translated : 579 (92.3%)
> >
> > Here I am again, with an updated .fr.po translation :
> > Translated : 619 (98.7%)
> > of which :0 fuzzy ( 0.0%)
> > Not translated :8 ( 1.3%)
> > Total : 627
> >
> > French-aware readers, would some one comment on those
> > translations (not yet
> > included in the above result), before I submit the file :
> >
> > "Bayer Dither {16,64}" -> "Bayer entrelaçé {16,64}"
> > "Dithemap {1,2}" -> "Table d'entrelçage {1,2}"
> >
> > To me, dithering is the same for color-space as halftone is for B&W-space.
> > Am I right? And does that make sense to translate 'dither' (and dithering,
> > ...) as 'entrelaçé'?
> >
>
> Salut,
>
> I am not perfect in french, but 'entrelaçé' is "interlaced" for me, in
> printing also "weaving". This means that on one sweep of the print head
> not all pixels of the covered area are printed, the next sweep goes over
> this area (or a part of it again) to print pixels which were left out
> the first time. This is done to get a resolution higher than the
> distance between the nozzles, or to make the paper less wet on high ink
> densities, or also to reduce stripes of the print head sweeps.
>
> Dithering is something completely different, which is also done by laser
> printers. One does dithering to raise the colour depth on the cost of
> resolution. A laser has only one bit of native colour depth, inkjets 1
> or 2 bits (always per ink/toner colour, usually CMYK or CMYmyK). As
> photos have 8 bits of colour depth per colour component of RGB but often
> a lower resolution than the printer, one takes a matrix of printer
> pixels, for example 4x4, and makes up one photo pixel of them. By
> combining different dot patterns in such a matrix the avarage colour
> impression of the matrix can have many more different color tones then a
> printer pixel.
>
> Unfortunately, I do not know the french word for dithering. Perhaps you
> should have a look at the translations of the GIMP-Print package
> (http://gimp-print.sf.net/).
>
> Till
>
I would suggest "pointillage" or "tramage". Tramage is used by some printer
manufacturers.
ljm
>
> ___
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel
>
[sane-devel] Re: Coolscan 2 and autofocus
On Wednesday 13 August 2003 13:31, Major A wrote: > [I'm also replying to the SANE mailing list, please send questions > like this to that list in the first place.] <...> > > That's weird. I've had reports from at least one LS-2000 user who says > the scanner works fine, including AF, so this is interesting. Maybe to add to your list of statisfied users: my autofocus (LS2000) is also working fine. <...> ljm
