primax: Thread: Final note on Primax problem on Mandrake 9 SOLVED !!!

On Fri, 15 Nov 2002 ####@####.#### wrote:

> Pity the image is absolutely disgusting ... but I think there is a weird 
> default colour correction to correct, I'll tell you as soon as I 
> understand more about this.

I solved that one by deleting a primax calibration file in /tmp.

Why doesn't warm-up time appear any longer ?
It is possible to activate the scanner too soon, and that makes for bad 
calibration and disgusting images.

However, if scanner (colorado direct 300) is activated after correct warm 
up time the image is now very close to that obtained under windows.

EXCELLENT !!!!

Just a last mournful note: I have activated ppdev by adding 'modprobe
ppdev' at the end of rc.local .... and the scanner's lamp comes on during
init process and stays on. Guess that takes care of the warmup time
problem, but perhaps uses the lamp a bit too much ?

-- 
Michele Alzetta

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hallo,

>
> I solved that one by deleting a primax calibration file in /tmp.

You have to wait for the lamp. At least 1 minute is a good time. Otherwise the 
calibration makes wrong assumptions on the brightness of the lamp.

> Why doesn't warm-up time appear any longer ?
> It is possible to activate the scanner too soon, and that makes for bad
> calibration and disgusting images.

Yes - this is a problem. This is mainly because of the SANE architecture. The 
sane driver is loaded with the Frontend( XSane ) and closed with the 
frontend. If the driver wants to switch off the lamp, it has to do this when 
the frontend is shut down. So every time you close XSane, the lamp is turned 
off. This would mean warmup cycles with every new start of XSane. The Windows 
driver behaves this way and you have alsway to wait before scanning. 
In order to avoid this, you would need a persistent program that handles the 
timeout and warmup of the lamp. I think this is the next thing I will do.
For so long I use the same way primax_scan does: Manual lamp control.

> Just a last mournful note: I have activated ppdev by adding 'modprobe
> ppdev' at the end of rc.local .... and the scanner's lamp comes on during
> init process and stays on. Guess that takes care of the warmup time
> problem, but perhaps uses the lamp a bit too much ?

Do you mean that loading the ppdev driver switches your lamp on? Or did you 
add "primax_scan -l on" to your startup script?

Gruss,

Andre

- -- 
Andre Herms                   ####@####.####
                              http://www.cs.uni-magdeburg.de/~aherms
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE91NtMK/HaDUFBducRAp5XAJ4t2P+T+Fko1T9B4p265cPmB3dOzgCeP6Zk
9oOUJOMfIsNg6++YFIrhURo=
=2JqQ
-----END PGP SIGNATURE-----