Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: [Digital BW] Film scanning and scratches

2001-08-29 by wparsons@evergreen-funds.com

Two suggestions:
1.  (The least helpful, perhaps).  I use a Nikon scanner and find it useful
for dust, but not particularly for scratches.
2.  Just as I did in the darkroom, I wipe nose oil on the back (NOT the
emulsion side) of the negative to remove scratches.  Works like a charm.
Bill






tynmansystems@... on 08/28/2001 03:32:49 PM

Please respond to DigitalBlackandWhiteThePrint@yahoogroups.com

To:   DigitalBlackandWhiteThePrint@yahoogroups.com
cc:
Subject:  [Digital BW] Film scanning and scratches


I tried to find a group that is focused on film scanning, but
couldn't find one; hope this isn't too far off topic for this group.

Over the past two year, I have been scanning 35mm negative film (both
color and B&W) using a Canon 2710 film scanner. I notice that I spend
a tremendous amount of time retouching film scratches on over half of
the images that I have scanned. These are very fine scratches on the
film base, that would typically not be visible in an enlargement made
in an enlarger, but which are very visible when scanned and enlarged
in Photoshop.

My question is: is there something inherent in film scanners that
magnifies film scratches? I have seen the dust and scratch removal
software (e.g. Nikon's Ice software) touted in scanner
advertisements, but assumed these would be necessary only for old,
mis-handled, damaged film. Is this scratch magnification an attribute
of film scanning that we just don't talk about in public, or is it
just me?

Comments?

Thanks, Ben Tyndall.



Please visit the Group Homepage to check the Files, Bookmarks, Polls and
other resources as they are often being updated. The page is at:

http://groups.yahoo.com/group/DigitalBlackandWhiteThePrint




Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.