Invalid default brightness, contrast, and possibly resolution

[CMaiku]

Thank you for writing this driver. It's just what I needed to set up my scanner for the network.

However, I'm having an issue where in both the native wia scanning (reached with NAPS2) and the windows fax and scan dialogs the brightness, contrast, and I believe, but am not certain the resolution, have invalid default values.

On first run, in the native wia scanning dialog, the default brightness was -1000, contrast was -1000, and resolution was 12800. I'm not certain, but I doubt my scanner (an Epson Perfection 1660 Photo) supports that high of a resolution. In the windows fax and scan dialog, the resolution was sensible at 300, but brightness and contrast are maxed out at -100 each. On subsequent scans, the default brightness for the native wia scanning dialog is now -334 and for the windows fax and scan is -33.

I looked at the open issues and wonder if this might be related to issue #6.

Please let me know if I can provide any further information and thanks again for writing this.

[mback2k]

Thanks for reporting this issue. Please try to upgrade to the following development version: wiasane-v0.1.1.8-4-ga8d2f98.exe and try it again.
The detection of supported resolutions was changed in a8d2f98.
Regarding the brightness and contrast values, please run the following program with your SANEd server as parameters and post the sections about those options here:
C:\Program Files\SANE WIA Driver\winsane-dbg.exe <hostname> <port> (you don't need to scan something)

[CMaiku]

After upgrading, the resolution still shows 12800. A quick internet search tells me the scanner supports up to 1600x3200 dpi (12800 x 12800 interpolated). So I guess the resolution was right. Still I'd prefer something more sensible as a default. Is that a setting in saned or?

Here's the relevant command output:
https://gist.github.com/CMaiku/cdce53317284ad4f1d29

[mback2k]

WiaSane uses the current value of the SANE backend as the default, see https://github.com/mback2k/wiasane/blob/master/wiasane/wiasane_def.cpp#L227. Since it is shown as 300 on your output, I wonder why it shows up as 12800. This might actually be something caused by the native WIA dialog. Which Windows version are you using?

I will take a look at the brightness and contrast settings next weekend.

[CMaiku]

This is with windows 7 home premium. Thanks again for the help.

[mback2k]

Please try wiasane-v0.1.1.8-7-g7df4f61.exe for a possible fix of the default brightness and sharpness/contrast settings. Relevant commits are 79ae6f5 and 7242b89.

[CMaiku]

The new version seems to fix contrast in the native ui, but brightness is still weird. With this version, in the native ui, brightness starts out at 143, and after each scan it decreases by 286, but only after each scan. If I close the ui and open it again without scanning, it remains the same value it was after the last scan.

In the wizard (the one reached with windows fax and scan) contrast is still -100 and brightness is -33.

[mback2k]

Thanks for the feedback, could you please post the debug output of the relevant sections between individual scans here?

[CMaiku]

Sorry for the delay. Here's the information as requested: https://gist.github.com/CMaiku/a7187ad6390ea86591d1

[mback2k]

Please try this build wiasane-v0.1.1.8-14-geb52905-dbg.exe while catching the debug output with DebugView.

[CMaiku]

Here's the requested information: https://gist.github.com/CMaiku/5a3ceb329217b6a6196e

It is the same procedure as last time. 3 preview scans, each causing the brightness in the native ui to change as described above.

[mback2k]

It seems like your update of WiaSane went wrong. I don't see the debug output added in 3598bf8. Please try to uninstall, reboot and install the new version again.

[CMaiku]

I've tried as you suggested twice, including redownloading from the link above, and I don't see any output added by that commit :/

[mback2k]

Please check if an old version of the driver is still installed by opening the Device Manager, installing the device manually using the legacy hardware wizard and removing it, including the driver, afterwards.

[CMaiku]

Eventually got the debug output with wiasane-v0.1.1.8-15-g3598bf8-dbg.exe. Here's the output, this time with a preview scan and a full scan: https://gist.github.com/CMaiku/5a3ceb329217b6a6196e

[mback2k]

This should already have been fixed by https://github.com/mback2k/wiasane/releases/tag/v0.1.1.9.