Simple Scan

resolution selection ignored when source is set afterwards

Bug #983441 reported by DemoFreak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Simple Scan
Fix Released
High
Unassigned

Bug Description

As suggested by Michael Nagel, i splitted this issue from https://bugs.launchpad.net/simple-scan/+bug/891586 as it seems to be a different problem.

----

Canon CanoScan 9000F
sane-backends 1.0.23
simple-scan 3.2.1/3.4.0

- scanning a document in several resolutions (300, 600, 1200dpi) results in output files of same size, all seems to be scanned at 600dpi
- scanner noise sounds equal (while normally sounds "faster" at 300dpi and much "slowlier" at 1200dpi)
- when saved as PDF, only the 600dpi scan has the correct screen size at 100% scale
- "crop to A4 size" from menu only works correct at 600dpi, when scanning at other resolutions the cropped area is too small/too big

Scanning with xsane and skanlite works correct on all resolutions, so it seems to be a simple-scan problem.

---

Revision history for this message
DemoFreak (demofreak-9) wrote :

---

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).

---

Revision history for this message
DemoFreak (demofreak-9) wrote :

---

Rolf Bensch from Sane devel mailing list worked out, that the parameter order is important to scanimage.

dont work: scanimage --resolution 300 --source Flatbed
works: scanimage --source Flatbed --resolution 300

So maybe simple-scan uses scanimage with the "dont work" parameter order as well?

---

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Great debugging work DemoFreak! Simple Scan now sets the resolution after the mode.

Changed in simple-scan:
status: New → Fix Committed
importance: Undecided → High
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Fixed in 3.4.1

Changed in simple-scan:
status: Fix Committed → Fix Released
Michael Nagel (nailor)
summary: - Simple-scan ignores resolution selection
+ resolution selection ignored when source is set afterwards
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.