David Heinrich <dh003i at gmail.com> writes:
> On Mon, Nov 16, 2009 at 4:13 AM, Alessandro Zummo <azummo-lists at
> towertech.it>
> wrote:
>
> On Mon, 16 Nov 2009 00:14:34 -0500
> David Heinrich <dh003i at gmail.com> wrote:
>
> > How do I do that? From the command line, I see the following sane
> commands:
> >
> > sane-config
> > saned
> > sane-find-scanner
>
> ?try using scanimage -d yourdevice --help
>
> ?It should how you a list of ptions, one of which is the
> ?resulution list
>
> Ok, a detailed response to this.
>
> [snip]
> Thus, I followed your advice regarding the scanimage command, and got he
> results shown below:
> ?
> $ scanimage -d epkowa:usb:002:009 --help | grep resolution
> ??? --resolution 25..12800dpi (in steps of 1) [300]
> ??????? Sets the resolution of the scanned image.
> ??? --x-resolution 25..12800dpi (in steps of 1) [300]
> ??????? Sets the horizontal resolution of the scanned image.
> ??? --y-resolution 25..12800dpi (in steps of 1) [300]
> ??????? Sets the vertical resolution of the scanned image.
These are the resolutions supported with the extended command set.
Also, you can specify horizontal and vertical resolutions independently
(although this has not been tested extensively and you should probably
not try thing like 25 x 12800 ;-).
> $ scanimage -d epson2:libusb:002:009 --help | grep resolution
> ??? --resolution
> 50|60|72|75|80|90|100|120|133|144|150|160|175|180|200|216|240|
> 266|300|320|350|360|400|480|600|720|800|900|1200|1600|1800|2400|3200dpi [25]
These are the resolutions supported with the standard command set.
> It seems the epkowa backend supports more resolutions than he epson2 backend.
> So I guess I can just try epkowa in xsane.
Looks like the epson2 backend does not take full advantage of the
extended commands.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962 Help support software freedom
http://www.fsf.org/jf?referrer=1962
