I assume you are talking about a fujitsu (you never said)? The
'buffermode' option was added to fujitsu backend version 1.0.40 on
2006-08-26, try upgrading SANE to get that.
1. If you power cycle the scanner, and connect only to sane, does it
send BGR data?
2. if you connect to windows and back t
to how I might set the caching option in the
backend and ultimately with a scanimage parameter.
--
Viktor R. Ivanov
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080215/6c21/attachment.htm
===
== Neuer Eintrag
===
---
-- Formular: 'adddev'
---
1. Your email address:
'spanr at gmail.com'
2. Manufacturer (e.g. "Mus
On Fri, 15 Feb 2008 07:37:08 -0500
"m. allan noah" wrote:
> unfortunately, the DPI is not one of the parameters reported to the
> frontend via sane_get_parameters, so a backend that does not have
> resolution controls, or one that relies on the scanner to round the
> resolution will not report th
Pierre Willenbrock schrieb:
> Guillaume Gastebois schrieb:
>> Hello,
>>
>> You can find all of that on :
>> http://ggastebois.free.fr/lide90_snoop/no_shading.tar
>>
>> What seems strange in calibration ?
>>
>
> The minimum/maximum values retrieved from the scans do not scale with
> the offset val
On Fri, Feb 15, 2008 at 2:15 PM, m. allan noah wrote:
> your english is quite clear, and you certainly understand the
> mechanical aspect, but i think you give the scanner too much credit.
> they dont have the brains to oversample and then downsample. they move
> the motor faster and take fewer
On Fri, Feb 15, 2008 at 9:57 AM, m. allan noah wrote:
> so you want the backend to scan at 1200x2400 but return 2400x2400
> data?
No. I guess my english is not very clear :-(
> it would have to interpolate 50% of the data in the scan with
> 'made up' data. or do you want to scan at 1200x2400 a
, except that the only resolutions provided are 300, 2400
and 4800.
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080215/047b2f74/attachment.htm
On Fri, Feb 15, 2008 at 8:44 AM, m. allan noah wrote:
> you friend would be correct IF sane used a file format which allowed
> the storage of the dpi, or exposed this data through some external
> means. but, as i said before, sane does not. so, you are going to see
> a stretched image.
>
> all
On Friday 15 February 2008 00:44:27 m. allan noah wrote:
> you friend would be correct IF sane used a file format which allowed
> the storage of the dpi, or exposed this data through some external
> means. but, as i said before, sane does not. so, you are going to see
> a stretched image.
Of cours
I cannot find the thread where this was discussed before, but here the
answer I received from a friend of mine, hopefully it will be useful
to clear up the confusion surrounding the resolution of scanners!
- The lower figure (1200) is what is called True DPI. This is the more
important value. It s
unfortunately, the DPI is not one of the parameters reported to the
frontend via sane_get_parameters, so a backend that does not have
resolution controls, or one that relies on the scanner to round the
resolution will not report the right values.
allan
On 2/15/08, Ren? Rebe wrote:
> On Friday 15
your english is quite clear, and you certainly understand the
mechanical aspect, but i think you give the scanner too much credit.
they dont have the brains to oversample and then downsample. they move
the motor faster and take fewer readings. the end user would scream
about the speed at lower reso
13 matches
Mail list logo
