Re: [long] Overall usage impressions

Andreas Tille (tille@physik.uni-halle.de)
Tue, 26 May 1998 09:13:51 +0200 (METDST)

On Mon, 25 May 1998, Paul D. Robertson wrote:

> I think this is a more difficult task than it first seems. Ideally,
Oh, I didn't remember that I've said that it is an easy task :).
For sure, SANE isn't an easy task at all and so why to include a
useful idea, easy or not?

> you'd have to figure out a good "test target" to take a picture of, then
> balance each color intensity to that of the target given the same
> exposure conditions for each film. While you don't have to be spot on,
Yes that's the real problem. I see only two solutions:
1) A single person takes a single testimage and all available films
and make the work -- who should be that person??
2) We collect data from several people (as many as possible) and try
average values. People should only suply values for pictures that
aren't shot under extreme light conditions and the image should look
as realistic as possible. The scan should be made by the same person
who did the shot.
I didn't know if so many people are able to do such work -- as I said
it was an idea.

May be we can hack into the code of the Canoscan frontent (as I said
it supports this feature). But I havn't such a scanner and the software
from Nikon didn't support it.

> given the range of films, formats, and scanners, it would be less than
> trivial. However, the idea has a good deal of merit, and I'd think that
> saving and restoring intensity values by name would be an interesting
> start, then someone would only need to maintain a master file of common
> names and values for the "Restore settings" menu selection.
Yes I think this is a good starting point.

> Also, I'm not sure if the image qualities need to be changed to print versus
> display, and as we see more people making prints at home from inkjets, that's
> going to become more important than ever.
I think this should be adjusted in the ghostscript settings and is no
task for SANE. I think if we could come close to a state, that the
"same image" (whatever it means in terms of f-stop and speed) on different
films and scanned with different scanners looks equal at the display
(more precisely is represented by the same RGB values ... monitors can
differ -- an additional risk for the idea!) we can be happy. The RGB-image
has to be the reference point and not the image at the printer.

> Well, I'm not a developer on this project either, but I think having a
> "save/restore by name" configuration parameter set would be a great
> addition. If the database were done per scan device, with the option to
> add a generic device for all scan platforms, I think it would be very
> useful for both slide and negative scanning.
May be a single generic database is half the work and for the different
scanners values can be calculated from a scanner specific lookup table.
Once more, if we could "steal" this generic database from Canoscan
and could adapt it for other scanners it could be a good starting point.
(I never heard something about the quality of the Canoscan table ...)

Regards

Andreas.

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com