Ed Hamrick writes ...
> In a message dated 11/29/2000 1:39:44 PM EST,
> [EMAIL PROTECTED] writes:
>
> > I was playing with the newest distribution of Vuescan last night,
> > trying to determine how and when VS determined the
> exposure. I had a
> > difficult time with consistent determinations ... it
> would seemingly
> > determine the exposure (RGB and IR) only if I asked for
> 'scan|device'.
>
> Yes, that's correct. The reason for this is that doing
> batch scanning
> doesn't do the color correction for the preview (to save time). In
> addition, sometimes people move the crop box, but don't do a
> "Preview|Memory" command to refresh the preview. It was easier
> to implement (and more reliable) the way it is now.
> ...
In one sense, this philosophy accommodates users who "forget" how
Vuescan works, and heavily weights Vuescan's common usage towards
"automatic" and "batch" scanning. If I want to experiment, and
accommodate individual exposures for particular film frames, I seem to
be left with changing 'scan|device' parameters from being quick enough
for "sampling" (... e.g, single pass, low res, low depth, no crop file
...), to "careful" (... e.g, multiple pass, high res, highbits, crop
file ...).
Why not allow "determine exposure" settings similar to how you allow
"determine focus". Is there something which doesn't allow Vuescan to
disable reading for exposure ("manual" mode), and putting it with
'focus' in the "device" menu list(?) In addition to the "modes"
Vuescan allows for 'exposure' and 'focus', you could add a "batch"
mode, which does both during the scan automatically ... and disables
preview.
Don't let me to appear ungrateful ... au contraire ... it's just that
if I'm going to dedicate 15minutes to a highbit scan and archiving
50Mbs of RGB, I'd like something to say about the exposure (... altho
an automatic determination by Vuescan is not a bad way to go
...*smile*...)
shAf :o)
