Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Having probs with a couple of hangs, profiles; default contrast, brightness and resolution #19

Open
venividi opened this issue Dec 23, 2014 · 0 comments
Assignees
Labels

Comments

@venividi
Copy link

First of all, just wanted to congratulate you on your work. wiasane is showing a ton of promise.

My setup is as follows. Running saned on a router: TomatoUSB (Shibby version 1.23)
Canon MF4370DN (scanner works great thus far on sane, recognized immediately etc.)

I have installed wiasane 0.1.1.9 on two different windows 7 premium home x64 PC's. Install went great on both. My scanning/OCR software is Adobe Acrobat XI.

First thing, Acrobat tries to default first to its 5 'basic' profiles but wiasane doesn't respond appropriately. This forces "Custom Scan..." and use of your native driver interface, giving the options of Color Picture, Grayscale picture, Black and white picture or text and Custom Settings. The options all work, but default to very low resolutions; when I go to the Custom Settings, and adjust the quality, its' defaults are 75dpi, and -1000 for both brightness and contrast. Memory mode seems to be necessary vs native mode with regard to transfer.

A few times I've encountered scanning halting midway (on the progress bar, and in terms of actual scanning.) The cancel button changes to wait, but the process and scanner seem entirely hung. Terminating Acrobat closes the dialog, but the scanner driver disappears from the list of options, too. A restart fixes this.

Its only an annoyance, but the driver window seems to default opening BEHIND the app. This is a problem if Acrobat is full-screen, since then it no longer has focus. It would be awesome if the native driver window opened on top of the z-order.

Despite the alpha quirks, I've been using and will continue to use it, gratefully... it already does things that the actual network driver for my scanner can't do (600dpi and a much quicker transfer.)

Looking forward to future revisions. If there's any troubleshooting steps I can do or debug information I can furnish, let me know. I'll have plenty opportunity to be scanning for the foreseeable future.

Many thanks.

Update: after a reinstall and much more use...

The custom setting is persistent. The color, greyscale and black and white settings all default to the same 75 / -1000, though.

Hasn't hung midway yet, since, either. Have had a number of times either a "not available" (I'll grab the exact text next time) right at the start, or crashes the application. After a crash it won't reconnect normally. I "solved" this by resetting the device in the properties tab of the device driver.

@mback2k mback2k self-assigned this Oct 28, 2016
@mback2k mback2k added the bug label Oct 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants