ðòïåëôù 


  áòèé÷ 


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: Re:24bit vs more



Rob,
One of the problems with raw scans of negative film is that they are
unreversed and do not have the orange masking removed, which is one of the
reasons that most people use the scanner software to do this prior to
sending the output to an image editor.  Typically, by calling the scanner
software into play, the file gets converted to 24 bit so that the scanner
software can perform the functions.  This is why I also do not send raw
scanner data (high bit or otherwise) from the scanner directly to an image
editor when working with negative color film stock.  Instead, I send a
reversed and mask removed 24-bit image file to the image editor using the
default scanner set points (unless they are way out of wack for the image)
and tonal curves, where I do a more refined set of enhancement and
correction adjustments to the set points and tonal curves with respect to my
working file.  For my purposes, I call the data I export to the image editor
in such cases a "low bit raw file;" but it is not what is technically
considered a raw file.

-----Original Message-----
From: filmscanners_owner@halftone.co.uk
[mailto:filmscanners_owner@halftone.co.uk]On Behalf Of Rob Geraghty
Sent: Monday, September 15, 2003 4:30 AM
To: laurie@advancenet.net
Subject: [filmscanners] Re:24bit vs more


"Austin Franklin" <austin@darkroom.com> wrote:
> You should either get raw data from the scanner, or do the setpoints/tonal
> curves "correctly" in the scanner software.  Keep in mind, every time you
> re-do setpoints/tonal curves, you are degrading the data.  It's just a
fact
> of how setpoints/tonal curves work.  What the significance of that
> degradation is, will vary greatly, so it may not be *that* bad...but why
do
> things twice when you can do them right the first time?

Are you saying this applies when using Vuescan - especially with negs?  Or
are you assuming the sort of interface that Nikonscan provides?

> > Getting the *right* 24
> > bits can sometimes better be done with an image editing program than the
> > scanner's interface.
> I understand that some scanner software is lacking, and that is where you
> simply should get raw data from the scanner, and learn how to do a better
> job of setpoints and tonal curves in PS.

OK, then I think we agree?  Other than what you mean by "raw data".  I
wouldn't ever attempt to use an editor (I don't own PS by the way) to do
what Vuescan does to go from the raw scanner output from a neg to produce a
positive image.

Rob

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


----------------------------------------------------------------------------------------
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.