"Warmup" of Canon CanoScan LiDE 400 scanner
Hey simple-scan folks.
This issue may have to do more with the underlying sane-parts, but nonetheless I would like to explain it here, largely because simple-scan is really nifty and simple to use.
My Canon CanoScan LiDE 400 scanner works both on windows and Linux. On windows it works better, largely because there is some additional "warm-up" stage that windows does before doing the scan.
On Linux I often get error message about USB stuff not initialized and what not.
I do not know what windows exactly is doing but I know that on Linux this works as well in principle; I noticed that via xsane and then hearing how the moving parts in the canon scanner move, before the scanning part begins. I assume this is the same "warm-up", but I don't seem to have a manual way to force such a warm-up.
Would it be possible that simple-scan also gets this as an option? This could be a separate entry somewhere in the preferences part, so this does not have to be a main UI change. But in particular with my LiDE 400 scanner model, I am almost 100% sure that there needs to be some "warm-up" step because windows is doing this automatically, whereas on linux this unfortunately does not seem to be the case (and I don't seem to have an option to do so via xsane either, so this means I have to scan on windows mostly; it does work on linux but it seems random to me WHEN it works; and often it does not work and I don't really get any cue or hints from linux on what to do different, so to me this is currently a "black box" system in general).
I am not certain whether this is relevant for GNOME in particular, but it may be that I am not the only user who may run into that issue, so perhaps if enough people have some oddities with scanners here and there, there could be some unified solution to such problems. Unfortunately I do not know the internals, e. g. how the C code works that determines all of this. What I can say is that I have fewer issues on windows than on linux with the scanner, even though it works on both; just not that reliable on linux, due to issues that are not really visible to me. Thank you for reading this issue tracker at the least!