-
From: Alan Womack [EMAIL PROTECTED]
To: Majordomo leben.com [EMAIL PROTECTED]
Sent: Wednesday, September 26, 2001 4:34 AM
Subject: re: filmscanners: Nikon Scan VS Negative dynamic
range
BUFFER on one of the tabs, crop on the right hand side
of the controls. Vuescan defaults to 2.0, I move
In a message dated 9/26/2001 2:40:53 AM EST, [EMAIL PROTECTED]
writes:
However, I've never got round to asking Ed whether the
buffer value is b% or 2b% of the linear dimensions or b% of
the frame area.
For instance, if the width is 36mm and the percent is 10%, then
there is a buffer of
Julian,
About the combing, are you using 12-bit?
I'm stuck with the 8 bits of my LS-30 :-(
I could try Vuescan and see if the white/black point settings actually work
at scan phase, looking at the raw file (if this worked, it would also give
me the benefit of 10 bits). I haven't had much luck
Alessandro wrote:
I'm stuck with the 8 bits of my LS-30 :-(
I could try Vuescan and see if the white/black point settings actually
work
at scan phase, looking at the raw file (if this worked, it would also give
me the benefit of 10 bits). I haven't had much luck with Vuescan until
now,
but the
Alex
At 23:01 25/09/01, you wrote:
I could try Vuescan and see if the white/black point settings actually work
at scan phase, looking at the raw file (if this worked, it would also give
me the benefit of 10 bits). I haven't had much luck with Vuescan until now,
but the latest release, which
Julian,
as is with most things that vuescan does, there is a setting for the BUFFER on one of
the tabs, crop on the right hand side of the controls. Vuescan defaults to 2.0, I
move mine up to 5%.
alan
I think Ed would make it much more user friendly if the exposure algorithm
.
Maris
- Original Message -
From: Julian Robinson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 25, 2001 9:26 PM
Subject: RE: filmscanners: Nikon Scan VS Negative dynamic range
| Alex
|
| At 23:01 25/09/01, you wrote:
| I could try Vuescan and see if the white/black
Julian wrote:
I think Ed would make it much more user friendly if the
exposure algorithm automatically applied a buffer which
blanks out the outer 10% of the image from exposure
calculations.
That's what the border and buffer settings are for. But as mentioned recently
there are some cases
On Sat, 8 Sep 2001 13:43:22 -0400 Austin Franklin ([EMAIL PROTECTED])
wrote:
That is just not true. F-stops are relative to the film, NOT to the
scanner. You can expand the exposure range on the film through exposure
and
development.
PLEASE read the archives. You can express the range
from
your post that this is just another post-scan tool, and therefore not as
effective.
Alex Pardi
-Original Message-
From: Julian Robinson [mailto:[EMAIL PROTECTED]]
Sent: venerdì 7 settembre 2001 06.44
To: [EMAIL PROTECTED]
Subject: RE: filmscanners: Nikon Scan VS Negative dynamic range
-Original Message-
From: Julian Robinson [mailto:[EMAIL PROTECTED]]
Sent: venerdì 7 settembre 2001 06.44
To: [EMAIL PROTECTED]
Subject: RE: filmscanners: Nikon Scan VS Negative dynamic range
OK mystery solved at last. I looked at the manual for the first time
(which must say something about ease
On Fri, 7 Sep 2001 14:46:46 -0400 Austin Franklin ([EMAIL PROTECTED])
wrote:
Well, technically, there is no reason that has to match either...it's by
someone's choice (or pure dumb luck) that it does. I've given the two
bit/three state example that holds perfectly true.
I ain't doing this
Mike writes ...
...
... Nikon Scan and VueScan apply different mappings
depending on settings (slide, negative, ...
Yes ... but they do this after acquiring the raw RGB, both of which are
very similar and which is a linear CCD acquisition ... anything non-linear
can be applied after that,
... but you better have all the RGB data ... and 12bits is necessary to
capture 11 f-stops.
That is just not true. F-stops are relative to the film, NOT to the
scanner. You can expand the exposure range on the film through exposure and
development.
Tony writes ...
On Wed, 5 Sep 2001 23:29:34 -0400 Austin Franklin
([EMAIL PROTECTED]) wrote:
Mapping the input data into 8 bit values has nothing to do with the
dynamic range of the A/D data
Arrgh... not this again! :-)
Actually it does, ...
...
Correct!!! ... linearity is the
Tony writes ...
On Wed, 5 Sep 2001 23:29:34 -0400 Austin Franklin
([EMAIL PROTECTED]) wrote:
Mapping the input data into 8 bit values has nothing to do with the
dynamic range of the A/D data
Arrgh... not this again! :-)
Actually it does, ...
...
Correct!!! ...
This
The 8 bit data represents only a dynamic range for THAT scan, not a
specific dynamic range. That is why a slide scan that has a dynamic
range
of say 3.6 can map into 8 bit data, as well as a BW negative that has a
dynamic range of 2.2 can map into 8 bit data.
Ah right, sorry, I
linearity is the keyword, that is, the scanner's driver
cannot map the CCD to RGB data non-linearily without losing information.
Do you think slide film is linear? Definitely not.
The trick is to compress the data in a way that artifacts aren't
noticable;,i.e., so that the desired input OD
= Original Message From Austin Franklin [EMAIL PROTECTED] =
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike Duncan
Sent: Wednesday, September 05, 2001 11:20 PM
To: [EMAIL PROTECTED]
Subject: RE: filmscanners: Nikon Scan VS Negative
Have you tried Scanner Extras / Prescan mode / low cont neutral?
Julian
At 09:44 06/09/01, you wrote:
It is very simple: NS decides to clip a neg scan if the dynamic range
encoded in the neg is more than a certain amount. I don't know what this
amount is, but I can demonstrate a very strong
I've never seen these options in Nikon Scan 3.0/3.1. Where should I be
looking (I can be blind like this sometimes)?
Jawed
= Original Message From Julian Robinson [EMAIL PROTECTED] =
Have you tried Scanner Extras / Prescan mode / low cont neutral?
Julian
At 09:44 06/09/01, you
In fact, three bits can represent any dynamic range at all.
That should have been three STATES not bits, can represent... Two bits can
be used represent three states...
Jawed Ashraf [EMAIL PROTECTED] wrote:
I've never seen these options in Nikon Scan 3.0/3.1. Where should I be
looking (I can be blind like this sometimes)?
= Original Message From Julian Robinson [EMAIL PROTECTED] =
Have you tried Scanner Extras / Prescan mode / low cont neutral?
September 2001 14:29
To: [EMAIL PROTECTED]
Subject: Re: filmscanners: Nikon Scan VS Negative dynamic range
Jawed Ashraf [EMAIL PROTECTED] wrote:
I've never seen these options in Nikon Scan 3.0/3.1. Where should I be
looking (I can be blind like this sometimes)?
= Original Message From
I have NS 3.1, and on my system there is a tool palette called Scanner
Extras. If you open this, there is a setting called Prescan Mode which you
can set to Low cont neutral (or hi key or lo key). But note that this
setting only appears if you have Negative selected rather than Positive
for
Hmm - maybe this is one of those things that Nikon withheld from LS30 /
LS40 (I have the LS2000).
I dunno, if this is the case it is unnecessary, but a good reason to buy
the more expensive scanner versions, or alternatively to buy
Vuescan. Surprise Surprise!
If I didn't have this
15:15
To: [EMAIL PROTECTED]
Subject: RE: filmscanners: Nikon Scan VS Negative dynamic range
I have NS 3.1, and on my system there is a tool palette called Scanner
Extras. If you open this, there is a setting called Prescan Mode
which you
can set to Low cont neutral (or hi key or lo key
On Wed, 5 Sep 2001 23:29:34 -0400 Austin Franklin ([EMAIL PROTECTED])
wrote:
Mapping the input data into 8 bit values has nothing to do with the
dynamic
range of the A/D data
Arrgh... not this again! :-)
Actually it does, because analogue voltages are mapped linearly by the ADC,
so with
Julian wrote:
Hmm - maybe this is one of those things that Nikon withheld from LS30 /
LS40 (I have the LS2000).
You may be right, but I thought you were still using 2.51. I never looked
for the settings you described when I was still running that version - because
I used Vuescan instead.
Julian wrote:
setting only appears if you have Negative selected rather
than Positive for your film type - IOW it is not available
for slides. Maybe you were set to slides the day you looked
in there.
Sorry Julian - when I looked last night I had the slide adapter in the LS30
so that's
Jawed,
You using a Mac? You really using 3.1? It doesn't appear in the manual -
dare I say it! Care to send a screen dump? Maybe it understands older
scanners - maybe older scanners don't have Analog Gain so the contrast
thingie is exclusively for them.
Maybe Nikon thought that the Analog
Mapping the input data into 8 bit values has nothing to do with the
dynamic
range of the A/D data
Arrgh... not this again! :-)
And that's because it's a misunderstanding of how the system works!
Actually it does, because analogue voltages are mapped linearly
by the ADC,
so with 8bits
I just scanned the Stouffer and a Max400 dupe of the Stouffer. There was a
light leak in my homemade film holder so the results won't be 100%
accurate. If I could only find my film duplicator.
Direct BW scans of the Stouffer target were made in BW negative mode.
Note that VS kept changing to
Comparing NS3.1 with the Kodak print of the Max400 Stouffer dupe,
NS3.1 has
more dynamic range by at least two stops. The print compresses the
brightest 2 stops and the darkest step is compressed.
Mike Duncan
What does the scanning software have to do with the dynamic range of the
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike Duncan
Sent: Wednesday, September 05, 2001 11:20 PM
To: [EMAIL PROTECTED]
Subject: RE: filmscanners: Nikon Scan VS Negative dynamic range
Comparing NS3.1 with the Kodak print of the Max400
35 matches
Mail list logo
