Comment 1 for bug 983441

---

As I figured out just now, the sane tools behave different regarding the resolution:

- xsane respects the selected resolution (tested with 300, 600 and 1200dpi). The output files differs in size by factor 4, as expected.

-rw-r----- 1 hannes users 25658079 14. Apr 19:36 test0001.pnm
-rw-r----- 1 hannes users 102666906 14. Apr 19:37 test0002.pnm
-rw-r----- 1 hannes users 410624709 14. Apr 19:38 test0003.pnm

- scanimage always scans with 600dpi (like simple-scan does), regardless what's given by --resolution parameter. The output files are similar in size.

hannes@gurkenkiste:~> scanimage -d pixma:04A91908 --resolution 300 --mode Color --source Flatbed >test1
hannes@gurkenkiste:~> scanimage -d pixma:04A91908 --resolution 600 --mode Color --source Flatbed >test2
hannes@gurkenkiste:~> scanimage -d pixma:04A91908 --resolution 1200 --mode Color --source Flatbed >test3

-rw-r--r-- 1 hannes users 107429029 14. Apr 19:51 test1
-rw-r--r-- 1 hannes users 107429029 14. Apr 19:51 test2
-rw-r--r-- 1 hannes users 107429029 14. Apr 19:51 test3

So it seems the problem is located in an interaction of the scan frontend and the sane backend (as scanimage/simple-scan are able to scan with the configured resolution when using other devices, and on the other hand xsane is able to scan the desired resolution with _this_ specific device).

---