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 halftonin
On Fri, 2005-11-18 at 00:11 +0100, Oliver Schwartz wrote:
>
> ah, ok. That makes more sense. I guess I'll disable 2400 dpi to make
> sure the error doesn't occur.
>
1600 dpi seems to work OK. Oliver, did you receive my previous post in
which I've tested almost all possible combinations of reso
On Fri, 18 Nov 2005 16:07:51 +0100
patrick deflandre wrote:
> Hum, I understand I've made a mistake. But which editor handle 16
> bits by color ?
> I've tried several graphics editor with no success.
Cinepaint, formerly called filmgimp.
Martin
Oliver Schwartz a ?crit :
>
>
>>But for me the 16 bit depth doesn't work. If I try to open the file
>>with gimp, the following message is displayed :
>>
>>PNM : invalid intensity maximum value
>
>
> That's a gimp problem. AFAIK gimp still can't handle more than 8
> bits/color.
>
> /Oliver
>
Hi,
> I confirm the 3200 dpi works well for me, and there isn't any
> interlacing problems. I apologise for my previous message which was
> not enough clear.
>
> In fact, it seem's that if I do a 2400 dpi scan which does not
> work, then the following 3200 dpi scan are bad. But it works again
> if
Levente Nov?k a ?crit :
> On Tue, 2005-11-15 at 21:13 +0100, Oliver Schwartz wrote:
>
>
>>I've now adapted the quality calibration code for the 2480 and enabled
>>it for the 3490. It's a pitty that you solved the problem already ;-)
>>otherwise it would be nice to know if quality calibration so
On Tue, 2005-11-15 at 21:13 +0100, Oliver Schwartz wrote:
>
> I've now adapted the quality calibration code for the 2480 and enabled
> it for the 3490. It's a pitty that you solved the problem already ;-)
> otherwise it would be nice to know if quality calibration solves it,
> too
>
> The co
Hi,
> - at 2400 dpi :
> I have done several try, at least a dozen.
> Sometimes it's all dark, sometimes all white, sometimes a
> succession of colored bands, and sometimes I have a good scanning,
> but at least it doesn't scale the entire selection I have made on
> the preview screen. And I have a
Oliver Schwartz a ?crit :
> Hi,
>
> I've now adapted the quality calibration code for the 2480 and enabled
> it for the 3490. It's a pitty that you solved the problem already ;-)
> otherwise it would be nice to know if quality calibration solves it,
> too
>
> The code is in CVS now, it should
Hi,
> I don't think the sensors is defective, because it works very well
> on Windows2000 with the Epson software. And I have try the quality
> calibration with no result.
Hm - I don't think so. Quality calibration (i.e. the option named
"Quality calibration", not "Quality scan") was disabled fo
Levente Nov?k a ?crit :
>>>- dirt on the calibration stripe or windows. Even a small dark spot on
>>> the area where shading correction is done could have a big impact, as
>>> it gets applied over and over for the whole scan height.
>>>
>>
>>This is a possibility. I will check this as soon as pos
Selon Levente Nov?k :
>
> Two vague ideas (if the green line is vertical):
>
> - defective sensors (maybe a quality calibration would help a bit)
I don't think the sensors is defective, because it works very well on
Windows2000 with the Epson software. And I have try the quality calibration with
Selon Oliver Schwartz :
> Thanks. Some more questions:
>
> - Is the green line always at the same place?
Yes, the green line is always at the same place.
> - Is it also present if you only select a small region in the middle
> of the preview?
The line is also visible on a preview. If I select o
m. allan noah a ?crit :
>
> Should it be due to my installation : I've make and installed the
> cvs code
> in /usr/local without uninstalling the debian version which is in /usr
>
In order to use Kooka (KDE scanner prog) I start it from a console with
LD_PRELOAD=/us
Should it be due to my installation : I've make and installed the cvs
code
in /usr/local without uninstalling the debian version which is in /usr
>>> In order to use Kooka (KDE scanner prog) I start it from a console with
>>>
>>> LD_PRELOAD=/usr/local/lib/libsane.so kooka
>>
On Mon, 14 Nov 2005 plum.pudd...@free.fr wrote:
> Selon Jim MacLeod :
>
>>> So we use the same backend and firmware with a different result.
>>>
>>> Should it be due to my installation : I've make and installed the cvs code
>>> in /usr/local without uninstalling the debian version which is in /usr
Selon Jim MacLeod :
> > So we use the same backend and firmware with a different result.
> >
> > Should it be due to my installation : I've make and installed the cvs code
> > in /usr/local without uninstalling the debian version which is in /usr
> >
> In order to use Kooka (KDE scanner prog) I st
plum.pudd...@free.fr wrote:
> So we use the same backend and firmware with a different result.
>
> Should it be due to my installation : I've make and installed the cvs code
> in /usr/local without uninstalling the debian version which is in /usr
>
In order to use Kooka (KDE scanner prog) I start
18 matches
Mail list logo
