Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 




      :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: filmscanners: OK, Vuescan is driving me nuts

>From: "shAf" <michael@shaffer.net>
>Reply-To: filmscanners@halftone.co.uk
>To: <filmscanners@halftone.co.uk>
>Subject: Re: filmscanners: OK, Vuescan is driving me nuts
>Date: Sat, 19 May 2001 11:43:30 -0700
>Jeffrey writes ...
> > >I suppose I am with Lynn ... afterall, whether you use Vuescan to
> > >crop, or not, it still scans the entire frame, simply delivering
> > >what's within the area to the "cropped" file.
> >
> > The problem is the little slivers of black border that are left
>cause it to
> > calculate the scan exposure incorrectly.  To avoid this, I have to
>crop the
> > image ever so slightly and Vuescan's cropping tool makes this
>     Wouldn't the Vuescan "buffer" variable solve this problem ...
>leastwize, I thought that it was its purpose ... set it once ... don't
>worry about the exposure again(?)
>shAf  :o)

Yup, works for me. My Crop|Buffer setting is 2% (I think the default) and 
that seems to work well for my full frame crops.  A person could probably 
increase this to 10% to make sure the black can't influence the auto values.

Joel W.
Get your FREE download of MSN Explorer at http://explorer.msn.com


Copyright © Lexa Software, 1996-2009.