kopia lustrzana https://gitlab.com/sane-project/website
95 wiersze
5.0 KiB
HTML
95 wiersze
5.0 KiB
HTML
<!-- received="Tue May 26 00:14:29 1998 PDT" -->
|
||
<!-- sent="Tue, 26 May 1998 09:13:51 +0200 (METDST)" -->
|
||
<!-- name="Andreas Tille" -->
|
||
<!-- email="tille@physik.uni-halle.de" -->
|
||
<!-- subject="Re: [long] Overall usage impressions" -->
|
||
<!-- id="" -->
|
||
<!-- inreplyto="Pine.LNX.3.91.980525163157.3632A-100000@gargoyle" -->
|
||
<title>sane-devel: Re: [long] Overall usage impressions</title>
|
||
<h1>Re: [long] Overall usage impressions</h1>
|
||
<b>Andreas Tille</b> (<a href="mailto:tille@physik.uni-halle.de"><i>tille@physik.uni-halle.de</i></a>)<br>
|
||
<i>Tue, 26 May 1998 09:13:51 +0200 (METDST)</i>
|
||
<p>
|
||
<ul>
|
||
<li> <b>Messages sorted by:</b> <a href="date.html#264">[ date ]</a><a href="index.html#264">[ thread ]</a><a href="subject.html#264">[ subject ]</a><a href="author.html#264">[ author ]</a>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0265.html">Stefan Jeske: "RE: Mustek ScanExpress backend"</a>
|
||
<li> <b>Previous message:</b> <a href="0263.html">John Labovitz: "Re: [long] Overall usage impressions"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|
||
<!-- body="start" -->
|
||
On Mon, 25 May 1998, Paul D. Robertson wrote:<br>
|
||
<p>
|
||
<i>> I think this is a more difficult task than it first seems. Ideally, </i><br>
|
||
Oh, I didn't remember that I've said that it is an easy task :).<br>
|
||
For sure, SANE isn't an easy task at all and so why to include a<br>
|
||
useful idea, easy or not?<br>
|
||
<p>
|
||
<i>> you'd have to figure out a good "test target" to take a picture of, then </i><br>
|
||
<i>> balance each color intensity to that of the target given the same </i><br>
|
||
<i>> exposure conditions for each film. While you don't have to be spot on, </i><br>
|
||
Yes that's the real problem. I see only two solutions:<br>
|
||
1) A single person takes a single testimage and all available films<br>
|
||
and make the work -- who should be that person??<br>
|
||
2) We collect data from several people (as many as possible) and try<br>
|
||
average values. People should only suply values for pictures that<br>
|
||
aren't shot under extreme light conditions and the image should look<br>
|
||
as realistic as possible. The scan should be made by the same person<br>
|
||
who did the shot.<br>
|
||
I didn't know if so many people are able to do such work -- as I said<br>
|
||
it was an idea.<br>
|
||
<p>
|
||
May be we can hack into the code of the Canoscan frontent (as I said<br>
|
||
it supports this feature). But I havn't such a scanner and the software<br>
|
||
from Nikon didn't support it.<br>
|
||
<p>
|
||
<i>> given the range of films, formats, and scanners, it would be less than </i><br>
|
||
<i>> trivial. However, the idea has a good deal of merit, and I'd think that </i><br>
|
||
<i>> saving and restoring intensity values by name would be an interesting </i><br>
|
||
<i>> start, then someone would only need to maintain a master file of common </i><br>
|
||
<i>> names and values for the "Restore settings" menu selection. </i><br>
|
||
Yes I think this is a good starting point.<br>
|
||
<br>
|
||
<i>> Also, I'm not sure if the image qualities need to be changed to print versus </i><br>
|
||
<i>> display, and as we see more people making prints at home from inkjets, that's </i><br>
|
||
<i>> going to become more important than ever. </i><br>
|
||
I think this should be adjusted in the ghostscript settings and is no<br>
|
||
task for SANE. I think if we could come close to a state, that the<br>
|
||
"same image" (whatever it means in terms of f-stop and speed) on different<br>
|
||
films and scanned with different scanners looks equal at the display<br>
|
||
(more precisely is represented by the same RGB values ... monitors can<br>
|
||
differ -- an additional risk for the idea!) we can be happy. The RGB-image<br>
|
||
has to be the reference point and not the image at the printer.<br>
|
||
<br>
|
||
<i>> Well, I'm not a developer on this project either, but I think having a </i><br>
|
||
<i>> "save/restore by name" configuration parameter set would be a great </i><br>
|
||
<i>> addition. If the database were done per scan device, with the option to </i><br>
|
||
<i>> add a generic device for all scan platforms, I think it would be very </i><br>
|
||
<i>> useful for both slide and negative scanning. </i><br>
|
||
May be a single generic database is half the work and for the different<br>
|
||
scanners values can be calculated from a scanner specific lookup table.<br>
|
||
Once more, if we could "steal" this generic database from Canoscan<br>
|
||
and could adapt it for other scanners it could be a good starting point.<br>
|
||
(I never heard something about the quality of the Canoscan table ...)<br>
|
||
<p>
|
||
Regards<br>
|
||
<p>
|
||
Andreas.<br>
|
||
<p>
|
||
<p>
|
||
<pre>
|
||
--
|
||
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
||
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
||
</pre>
|
||
<!-- body="end" -->
|
||
<p>
|
||
<ul>
|
||
<!-- next="start" -->
|
||
<li> <b>Next message:</b> <a href="0265.html">Stefan Jeske: "RE: Mustek ScanExpress backend"</a>
|
||
<li> <b>Previous message:</b> <a href="0263.html">John Labovitz: "Re: [long] Overall usage impressions"</a>
|
||
<!-- nextthread="start" -->
|
||
<!-- reply="end" -->
|
||
</ul>
|