The "Art" of NEF Conversion
by Uwe Steinmueller (last updated 10/06/2000)
NEF Conversion Forum
NEF Test File
If you click on the photo you can download this photo in NEF format.
I (Uwe Steinmueller) keep all copyright on this picture but also grant
to everyone to play with it and get used to NEF conversion processI think
the photo is technically quite ok to get you a fist NEF experience.
Why NEF files?
With the popular professional SLR "Nikon D1" Nikon
introduced a proprietary RAW file format NEF (Nikon Electronic Image Format)
with about 4MB filesize.
Why did Nikon not stick to standards like JPG or TIF?
-
JPG is a lossy format with the only purpose to save space while to
lose as little as possible image quality relative to the compression
ratio. If space and speed would not be in issue JPGs would not exist.
But space and speed are very important factors in real life computing
(the D1 is quite a powerful computer) and that is why JPG are so important.
-
TIF produce large files. The D1 creates images with 2000x1312 pixels
and has a potential color depth of 12bit. As TIF only supports 8 or
16 bit this would get one 16 bit TIF file to 15MB of file size. Here
the write speed of D1/CF cards and the capacity of todays CF cards
or even Microdrives set the limit
That is why Nikon decided to have either JPGs (FINE mode needs about
1.1 MB of size) or RAW files which are just a "dump" of the
CCD content. The concept of RAW files is not new for digital cameras (used
by the Kodak professional line) and is also used by scanning software
like Silverfast (you capture a raw scan and the software decodes and interpretes
it later). The NEF files should contain all image content captured by
the CCD and thus get you theortically to the optimal possible results
for the D1.
Here is a description of NEFs and TIFs for the D1 by Richard Parkinson
"..., the TIFF is bigger so it has more information, right? No!
The NEF format is propriatory and is, in effect, a raw dump of the CDD
information, it has 12 bits of data per pixel. So (12 * 2008 * 1320)/8
= 3,975,840 bytes of data in the image. Now a NEF also has a crude thumbnail
and some extra info, so the file size is actually 4,063,232 bytes. The
TIFF format stores the data in a different way, the one that comes from
the D1 is an 8 bit TIFF, that means that each pixel contains 8 bits (1
byte) for each color (Red, Green and Blue), this gives 3 * 2000 * 1320
= 7,920,000 bytes for the image. Again some extra info is stored with
the TIFF so they end up at 7,938,048 bytes. Now comes the complex part,
the 12 bits used in the NEF is actually more information than the 24 bits
stored in the TIFF because of the way the CCD works, basically each pixel
in the D1 only gives 1 color, the others are interpreted from the pixels
of those colors nearby.
So the NEF which is smaller contains more information, but in addition
to that it has had less processing, so it gives you more scope for improvement
later to correct any problems of color balance, exposure etc. Think of
it this way, if you want the maximum detail do you keep the original or
a copy? Obviously the down side of the NEF is that you need a program
to read it, fortunatally for us users the likes of Mike (QImage) and Eric
(Bibble) have alowed us to use this format without the need for the expensive
and clumsy Nikon Capture.
At the end of the day you have to decide:
TIFF = big, good qualility, standard format JPEG = Small, lossy compression,
standard format NEF = Medium Size, best quality potential, propriatory
format
You pays your money and takes your choice, but in my book the NEF wins
hands down! Only use JPEG if you are short on storage or you need the
speed of storage for rapid shots, I never use TIFF."
Here is Daniel Stephens "Decoding
NEF" article.
The buyers of the D1 (myself included) were not too happy that when they
buy the D1 they can capture NEF files but NIKON only provides the software
to decode for additional $500. Most people see this as a hidden price
tag (Kodak includes the software with the camera to decode its RAW files).
Because of this price tag for the software some shareware authors managed
to write software which can decode these NEF files. That is why D1 users
have the choice among three different software packages.
NEF Converters
|
|
|
|
|
|
Nikon Capture
|
|
$500
|
Qimage
V9.1
|
Qimage is actually a print processor which can perform NEF conversion
in batch. That is why the user interface is very different to NC
and Bibble. Not available for the Mac.
|
$30
|
Bibble
2.0 (PC) and
1.0b(Mac)
|
Bibble is more like NC and is also available as Photoshop plug-in
and for the Mac.
|
$99
|
|
|
|
Related Tools
|
|
|
|
|
|
Band Aid
|
Noise filter for D1 by Camera Bits
|
$149
|
Quantum Mechanic
Pro
|
General Noise filter by Camera Bits (beta for Windows)
|
$189
|
CimageD1 V2.2
|
High ISO filter for D1
|
free
|
|
|
|
Literature
|
|
|
|
|
|
The
Digital Photojournalist's Guide, 4th Edition
|
Although this book does not cover the D1 this of use for a better
understanding of digital cameras and their strengths and shortcommings
|
|
DeNEF |
Nikon D1 NEF image file decoder for Unix |
open source |
I believe one needs all three programs (on the Mac only NC and MacBibble)
as there is not one best solution. On the downside I find more and more
that the optimal solution is somewhere in the middle (nowhere) of all
these programs. Here is a feature list of the available programs (I use
all three and all findings are bases on my own experience)
NEF Converter Feature Chart
Feature
|
Nikon Capture 1.1.2
|
Bibble 2.0
|
Qimage 9.1
|
|
|
|
|
Colormanagement
|
yes
|
yes (JPG files are not tagged)
|
not really (Files are not tagged)
|
Monitor calibration using color profiles
|
yes
|
yes
|
yes
|
|
|
|
|
Batch conversion
|
not really
|
yes
|
yes
|
|
|
|
|
Levels
|
no
|
yes
|
no
|
Color correction
|
yes
|
yes
|
yes
|
Can save/restore settings for color correction
|
yes
|
no
|
can save filters
|
Can set settings for color correction as default
|
yes
|
no
|
can save filters
|
Curves
|
yes
|
yes
|
no
|
Can save/restore settings for Curves
|
yes
|
no
|
no
|
Can set settings for curves as default
|
yes
|
no
|
no
|
Sharpening (Unsharp Mask)
|
yes
|
yes
|
yes (not WYSIWYG)
|
Can save/restore settings for Sharpening
|
yes
|
no
|
can save filters
|
Can set settings for Sharpening as default
|
yes
|
no
|
can save filters
|
Can adjust Curves and Sharpening at the same time (no new modal
dialog needed)
|
yes
|
yes
|
Yes but is not WYSIWYG
|
Change saturation (HSV)
|
no
|
yes
|
yes
|
Autolevels
|
yes
|
yes
|
yes
|
|
|
|
|
Crop images
|
yes
|
no
|
yes
|
Rotate images
|
yes
|
yes
|
yes
|
|
|
|
|
Can create 16bit TIF files
|
yes
|
yes
|
no
|
Photoshop Plug-In
|
no
|
yes
|
no
|
Can be used in Photoshop actions
|
no
|
yes
|
no
|
|
|
|
|
Noise filter
|
no
|
yes
|
yes
|
Color fringe correction
|
no
|
???
|
yes
|
Exposure correction
|
no
|
yes
|
yes
|
White balance correction by finding white area
|
yes
|
yes
|
yes
|
White balance correction by color temperature selection
|
no
|
yes
|
no
|
|
|
|
|
Camera control
|
yes (can capture via Firewire directly to PC/Mac)
|
no
|
no
|
|
|
|
|
Printing
|
no
|
no
|
yes, Here is where Qimage comes from
|
|
|
|
|
Uwe's Nikon Capture Defect List
Slow
|
Yes it is slow, but I got used to it
|
tone setting execution (custom setting 24)
|
The different values of tone settings are interpreted by NC before
the image gets displayed. Although this flag does not influence
the actual image (NEF) data I cannot find any way in NC to overwrite
this settings (e.g. for false settings)
|
White balance
|
There is no easy way to correct white balance by setting a different
color temperature (like in Bibble)
|
Crash in White Balance
|
Sometimes NC crashes when I perform the white balance function
|
No automated workflow
|
There is no support for an easy automated workflow (I need that
for the many photos I have to work with)
|
No exposure compensation
|
There is no easy exposure compensation possible like in Bibble
|
Bad usage of temporary disk space
|
Load Images from card need a lot of temporary file overhead and
leaves most cleanup to the user
|
|
|
|
|
Price Tag
|
An improved version of Nikon Capture should be part of the D1 delivery
|
Glossery
slow
|
This is relative to how Photoshop 5.5 performs on a Windows NT4.0,
PII 300, 320MB Memory machine
|
colore fringe correction
|
In some situations the color of some color pixels influence incorrectly
the neighboring colors
|
|
|
|