Mike wrote:
> Thanks for the kind words. Sorry about the flaky web hosting. I
> appreciate the critique Moose. Above and beyond as usual. What you did
> to 13a is about the same as the print the Fuji Frontier at Costco spit
> out.
I guess I'm in good company. :-)
> The blown highlights are partly processing and partly me pulling
> the slider a little too far left. This computer is so glacially slow
> that I run out of time and patience. When I get the chance I'll scan a
> few more. The lake in the rain and clouds was quite magical.
>
Sure looks like it!
> ps; any suggestions for reading up on how to correctly use the
> white/black point controls (VueScan) would be appreciated. At this point
> I'm really just flailing around with the sliders.
>
I don't use the sliders, the adjustment is too gross. For shots like the
lake, I would probably have the WP at .01 to start with, Sunlight shots
with sky and clouds rarely can take much more than that. Then I look at
the histogram at the bottom left (CTRL-4) to see if highlights are
piling up at the end or there's nothing out there and adjust
accordingly. In my recent scanning of Yosemite shots, I think I had
values from about .2 to .001. Working on any given general subject for
many frames, it gets pretty esy to ht most of them with one or two tries
after a while
Using discrete numbers should help with the speed problem. As a hint, if
say changing .01 to .02, don't backspace over the 1, then type in the 2.
VueScan will repaint the screen once for the backspace, then again for
the new value. Instead, highlight the 1 and type a 2 over it, only one
recalc and redraw that way. My computer is fast enough that's this is
just a silly momentary annoyance, but I notice it anyway. I suspect
dragging the pointer results in lots of recalcs/writes and really slows
things down.
You should also be able to deal with much of the flatness with the curve
adjustments (CTRL-3). Again, I've given up on the sliders and put
numbers directly into the boxes up above. A shot like the lake might be
something like Curve low of .3 to .4 and Curve high of .65 or so. Just a
guess. Again, a little practice makes it go easier.
You may not know, but VueScan can read most kinds of image files from
disk and "scan" them into altered output files. I read watson13a in and
altered the Curves adjustment. I don't claim this is the right
adjustment, in fact, I'm sure it isn't, so take the actual result as
just illustrative. I'm just showing how to use VueScan in one area. You
can see the Curve adjustment values. Also, notice the White Point is set
to 0. That's because I'm reading a file that already has lost
highlights, not an actual scan. I've also moved the preview image to the
left to save space and put the Curve and Histogram displays in one
screen image. I think VueScan should let you actually do that, it would
make working with it faster
<http://moosemystic.net/Gallery/Others/Mike/watson13V.htm>.
I'm not advocating VueScan as an editor. You can't generally do as much
as in a proper editor, just showing how you can come out of the scanning
process much closer to a finished product. Some scans I do don't need
anything further, other need quite a bit.
Moose
==============================================
List usage info: http://www.zuikoholic.com
List nannies: olympusadmin@xxxxxxxxxx
==============================================
|