ðòïåëôù 


  áòèé÷ 


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]

[filmscanners] RE: Vuescan Color Tab



Laurie writes ...

> >   I say it's "alright" because there's nothing wrong with it.
> > However, if you did decide to convert from "device space" to another
> > space before archiving, and then wanted to convert again later to a
> > "better space" (for whatever reason), then you need accept the
> > additional quantization errors and extra dithering ... i.e., two
> > conversions rather than one.
>
> This may be a language problem; but by device space, I assumed that you
> meant the native color space profile of the device (scanner or camera).
> This native space is often smaller than most traditional working spaces
> (e.g., Adobe RGB 1998 or Color Match) resulting in a loss of raw data
> unless - ...

  There should be no loss of data ... unless Vs does something unjustified
(by anyone's understanding of "device space") if "device RGB" is selected
... I don't use it, and archive the raw scan.  In any case, the way device
space should work is, ... no data is lost because the RGB data is not
converted ... it is still the device RGB, as scanned, and the device space
is assigned.

  It seems to me you may be correct about Vs's definition of "device RGB",
especially for scans of negatives.

cheerios ... shAf  :o)
Avalon Peninsula, Newfoundland
www.micro-investigations.com (in progress)


----------------------------------------------------------------------------------------
Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe 
filmscanners'
or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or 
body



 




Copyright © Lexa Software, 1996-2009.