There's an old saying...
"You can hit a nail with a sledgehammer..."
And another...
"There's no free lunch..."
Maybe Project ESE is entirely on-track and satisfied with the results? Not sure?
From what I can tell, there are other people who have done an enormous amount of experimentation to get to the point of minimizing the aberrations and stop-gaps. This includes disabling the scanner errors to allow an entirely different hardware application. My suggestion is to have a longer term approach that would allow optimizing the scanner hardware for a camera application.
Quote from Golembewski - "The true usefulness of the SANE drivers lies not in the front-end applications, but rather in the fact that the raw code for the back-end is open source. This means that the LIDE 20 driver itself can be modified and changed, allowing the scanner to perform functions that the manufacturer never intended.
Unfortunately, driver programming is a complex thing, and is an art in itself. Years of dedicated study are required before a programmer can successfully attempt to write a device driver from the ground up. However, those with a decent amount of programming skill can easily use a combination of detective work and intuitive guesswork in order to modify aspects of the SANE drivers.
I was able, with a bit of practice and programming study, to disable the calibration and error correction routines found in the driver for the Canon LIDE 20. This allowed me to use the more extensively modified scanners easily and effectively, and was vital in letting me create the higher quality photographs of the later-model scanner cameras."
Bookmarks