Upon closer use of vuescan 7.3.6:
When BP is set to 0 or at 0.0001 i get unexpected RGB=0 values in my scans.
The complete border area of the negative stays at RGB=0, likeways some very
dark points in the image. Before i had always some non rgb=0 values in this
area when i wanted.
I have to use a brightness of 1.5 till 2 to get some value other than 0
there, but this image needs a brightness of 0.75.....the negative is of
i see in the scanhistograms in vuescan at the dark end, near BP the
beginning of a sharp peak: that is where the negative border and some other
pixels are. But it is cutoff.
Nevertheless i expect if i set BP to 0 that there will be no pixels in the
resulting scan with rgb= 0. Like i achieved before (with vuescan 7.3.1, i
dont know when exactly it changed)
How is BP calculated? Was there a change ion vuescan? Setting BP stays a bit
like manipulating a blackbox, since there is no way to pinpoint specific
pixels to be black or just not black for now.
(data: normal exposed supra 100 negative, ss4000, 48 bit scan, 4000 dpi, BP
set to 0, WP set to 0.001, 48 bit output to adobe RGB 1998 space)
----- Original Message -----
Sent: Wednesday, December 19, 2001 1:43 PM
Subject: filmscanners: VueScan 7.3.6 Available
> I just released VueScan 7.3.6 for Windows, Mac OS 8/9/X
> and Linux. It can be downloaded from:
> What's new in version 7.3.6
> * Set the default monitor color space on Mac OS to Apple RGB
> * Enabled 14 bit scans on AGFA Arcus 1200
> * Increased range of focus values on LS-40, LS-4000, LS-8000
> to handle unusual slide mounts
> * Fixed problem when color space set to Adobe RGB or Apple RGB
> * Fixed problem with "Prefs|Release memory" option
> * Fixed problem scanning negatives on HP 7400C
> * Fixed problem with locking colors when scanning from disk
> Ed Hamrick