|
Book Review: The Art of Raw Conversion, reviewed by Nick Latito |
|
Wednesday, September 20 2006 @ 05:24 PM EDT
|
Nick Latito (chiark on Groklaw -- he said I could tell you that) volunteered a while ago to review for us No Starch Press's "The Art of Raw Conversion," and here is his review. The book is more formally titled "The Art of Raw Conversion: How to Produce Art-Quality Photos with Adobe Photoshop and Leading Raw Converters", by Uwe Steinmueller and Jürgen Gulbins, ISBN 1-59327-067-4, published by No Starch Press and available from them and from the usual suspects, like Amazon and O'Reilly. You can view a sample chapter here. It's about how to get high quality results with your digital camera, specifically how to work with the RAW files your digital camera generates to filter out imperfections, how to understand color management, adjust exposure, etc., or as the opening sentence puts it: "Our goal in this book is to demonstrate a reliable workflow that will help you achieve optimal image quality from your digital camera using the RAW file format." I gather they call them RAW files because they are describing the raw data the digital camera takes in when you take a picture. I asked Nick to give me a sentence or two about him, and this is what he wrote:
Nick Latito confesses to being fascinated by digital imaging from the early days - remember Digiview on the Amiga in the 80s? Now using a Nikon D70, Photoshop CS2 and shooting RAW purely for pleasure, he's taken a look at "The Art of Raw Conversion" to see if it can improve his output and make his life easier. As you will see, he really enjoyed the book and learned from it. His main complaint is that he'd have liked it to be longer. Note the postscript also.
*********************************
Groklaw Book Review: The Art of Raw Conversion,
~ by Nick "chiark" Latito
First off, a slight caveat to Groklaw readers: this book, and therefore this review, really pays no attention to the Open Source marketplace. The only operating systems covered are Mac OS X and Windows, and the software covered is of a similar nature.
Introducing RAW
The audience of Groklaw is composed of geeks, law fans and parties with an interest in either or both topics. Some of you will have a better understanding of how digital cameras work than others -- some may have a much better understanding than I. If you already know what RAW is, skip on a few paragraphs, for I'm going to spend a while introducing what RAW actually is.
Digital cameras, in the vast majority, produce pretty decent JPEG images out of the box when you point them at something and press the shutter release button. What happens is that a shutter moves out of the way (in most cases), allowing the sensor to collect light at each pixel site (of which a 6 megapixel camera will have 6 million), which in turn produces a voltage at that pixel site. Things are complicated somewhat when you consider that each pixel site -- with the exception of Foveon sensor-equipped cameras -- only captures monochrome information, hence something else is needed to capture colour images: a colour filter is placed over each pixel site. Three primary colours can make up colours in the additive light model employed by computers, so three colour filters are used. That doesn't lend itself nicely to a repeatable (tessellated) pattern, so one red, one blue and two greens are used to make a two by two square. For the reasons why, Google "Bayer filter".
Your battery-powered camera's processor, tuned to give a compromise of size and battery life against performance and functionality, has to take the raw voltages from the sensor, apply correction curves, interpolate the data into a colour image, sharpen the image and generally work hard to produce an image prior to compressing the whole lot using cosine transformations and all sorts of gubbins to make a JPEG compressed image.
Many cameras now give the option to save the unmolested data from the sensor, or raw data, in place of or as well as the JPEG image and a handful don't even offer anything other than raw images out of the camera. The disadvantages of this are the size of the data -- as it's largely uncompressed data, it takes more space -- and that you have more control over the image which adds another decisive step requiring work into your current processing workflow.
The advantages are many: when you push that button on your camera and capture JPEG, your camera makes decisions which throw away information or make alterations difficult. Digital processing introduces the concept of adjustable white balance, which is something that film photographers have to understand but don't have much control over, other than changing film stock or applying filters to correct colour casts: to change white balance on a RAW image, just dial in appropriate settings on your converter. Your image is not subject to JPEG artefacts. Your sensor probably captures more than 255 levels of intensity at each site, but that's what JPEG is limited to, being an 8 bit per primary colour format: RAW will capture more, normally either 12 bits (4096 possible values) or 16 bit (65536 possible value) at each site.
Each different camera manufacturer has its own format for RAW images which often changes from model to model, so a RAW converter has to understand each manufacturer and each model to provide the best range of possibilities to the photographer.
On to the book!
So, with the understanding of what RAW can do for you, how can you use it? This book makes no apology for referencing the most popular image processing solution in its subtitle, that being Adobe Photoshop CS2, and if you're looking for help and advice using Linux, the GIMP or DCRaw, you'll not even find mention in this book.
The book looks and feels like a classy affair: it's a full-colour production on quality paper, and it appears that great care has been taken with the layout and design. It's bang up-to-date, and the bibliophiliac in me really appreciates it. Throughout the book, a fresh design has been used which works well with the subject matter. Callouts are used in the place of footnotes, keeping the feel modern. Illustrations are clean, clear and -- as they should be -- illustrative! The first page is a superb work of art beautifully presented that really does inspire, and each chapter starts in the same way. The quality of the included photographic work is very good. Coming in at just over 200 pages (240 to be exact), my impression is that the ethos is quality, not quantity.
The book starts by providing a detailed background to digital imagery and the tools you'll need. Even though I considered that I knew how things worked in some detail, there were still revelations in 7 pages: I'd rather that you took that as a comment on how rich the information is rather than a comment on my knowledge.
Following on from the basics are fourteen pages introducing colour management, hammering home its importance in getting the results that you want. This is an appropriate treatment of a potentially massive topic. Part of me would have liked more detail in here, and more concrete examples of how to get it right, but going deeper would take a lot more words backed with a lot more examples.
The book then opens up into the main objective: how to get the best out of your raw images now that you have the necessary background. Emphasis is placed that you should develop your taste and work according to what you feel is right, not necessarily what automated tools tell you that you want. Examples throughout the book show what is possible, and I'll reiterate that they're great but occasionally a bit more commentary or example would have been nice. The corollary is of course that others would find such commentary obvious, but I always like to understand what options someone had at steps to produce their final work.
Workflow is covered, and again I would expect that even seasoned professionals will find something in here, even if it's just affirmation that they're doing the right thing at the right time. The point that exposing correctly in camera will give you an easier path to perfection is well made. There are some assumptions on background made, and being honest I would have liked a bit more explanation here of some of the very basics to ensure that everyone's understanding is common.
We then come to the particulars of each software package covered, which takes 100 pages of the book. The author's aim is to show you that there's no one tool that does everything perfectly, and in that it succeeds. The largest section herein covers Adobe Camera Raw, followed up by Pixmantec Rawshooter, Apple Aperture, then a conglomerate of other raw converters. Adobe LightRoom is then given a fair crack of the whip, and the author's enthusiasm creeps through here: I sense that there might have been a struggle to fill the allocated pages, as a half-page picture illustrating no more than shortcut keys is included.
This was interesting for me, but it won't realistically mean I rush out and buy something else resulting from it. As an amateur, I can't justify spending more on another tool just to fill a specific gap that I haven't found by myself.
A brief chapter covering some image perfection techniques is next and, being frank, I believe that people reading this book will probably already know the content here in much more detail than presented. I also get the sense that this might have been added to bulk out the book: a page is apparently devoted to showing three screen grabs detailing the effect of the healing brush.
Back to the potential audience, batch processing is briefly but well illuminated which largely wraps up the main content. Chapters cover off the DNG format, how to use metadata, quality conversion to black and white, and how to profile your camera, which is a fascinating if very involving process.
As mentioned, the book does ooze quality -- it's beautifully laid out and produced. The language used is clear and appropriate for the topic, and there's only a couple of phrases that hint that authors are not native English speakers. That fact never once gets in the way of the book's ability to communicate, enlighten and entertain.
I did learn a lot from the book and enjoyed reading it. It's written with an easy and enthusiastic style by people who are passionate about their art. There are some topics which appear out of place in such a book and my honest feedback is that I'd drop some of these sections and expand on the core, or even just include more of the authors' superb examples of work, perhaps showing more of what they feel as right and wrong and the decisions they made at the various stages in their workflow to produce the finished articles.
It really does highlight that there is an art to this rather than a repeatable formula that gives perfect results every time, but at the same it time equips you with the background understanding, approach and tools needed to get the best. I liked the book, but I would have liked to have seen more of some bits and less of others. With that in mind, I'd recommend it to keen amateurs who own a DSLR and attach a caveat to check the content to ensure you're not, for example, expecting a manual of how to use Camera Raw in CS2 but rather a discussion on techniques and approaches to help achieve your own style and vision. As such, it succeeds but I'm left with a feeling of wanting a little more.
Postscript -- A note on open source
Whilst there are very capable image processing solutions, such as the GIMP, and raw interpreters such as dcraw it seems to me that open source has yet to address the needs of the professional or even keen amateur photographer. Photoshop is one major functional area keeping me on closed source, meaning that my next purchase will be a Mac as I now have a way out of Windows. When Linux gets great colour management as part of the OS, it will help. Adobe cannot be deaf to the fact that they have people clamouring for Photoshop on Linux. It was the most wanted application in a recent poll! I'd love to see this improve in the very, very near future, and it appears that people are actively working to crack this particular nut.
|
|
Authored by: MadScientist on Wednesday, September 20 2006 @ 05:31 PM EDT |
[ Reply to This | # ]
|
|
Authored by: MadScientist on Wednesday, September 20 2006 @ 05:32 PM EDT |
[ Reply to This | # ]
|
|
Authored by: Anonymous on Wednesday, September 20 2006 @ 06:16 PM EDT |
Speaking of Photo stuff (and guess what, there is no Photoshop
for
LINUX)...
GIMP is not close to being equal to
Photoshop?
When is GIMP going to be Photoshop replacement?
Or when is a version of Photoshop to be released for
Linux?
Why? Because, this past week we have been moving stuff
from
Windows to Linux, and we ran into an issue when we were building
a
brochure, where we need some photos for the brochure, and discovered
that GIMP
does not support CMYK. AND our printer (runs a printing press
and build plates
for the press process) said we must have all our
photos sent in the document as
CMYK (not RGB) ?
http://en.wikipedia.org/wik
i/CMYK_color_model
There is A
plugin
providing
rudimentary
CMYK support for The GIMP
http://www.blackfiveser
vices.co.uk/separate.shtml
"Background
One thing preventing The GIMP
from being useful in a pre-press
environment
is the lack of support for the CMYK
colour-space. This plug-in
goes
some small way towards rectifying the
situation, using a trick with
layers
to fake CMYK support. The plugin is
unfinished, but usable for its
primary purpose, and since
I'm
unlikely to have
time to develop it further in the near future, I'm
releasing
it as
is"
Hmmm, the plugin, is but only a lesser "work around" to get
to
something that is not pure CMYK (it seems)?
The folks who do the
printing know nothing about Linux, OpenOffice.org,
Scribus, or The GIMP!
Why would they when there is no LINUX tool
that will do the CMYK for them
easily?
FYI - The CMYK plugin is not installed with GIMP when you load
your
distro (Ubuntu, or others that I have been looking at)? Meaning,
that
newbie folks who want to learn to use Scribus for doing a
brochure, that they
will then want to take to the printer to have
printed, will have to hunt around
and install it (NOT, because this is
not a newbie thing finding the plugins,
etc)...! In the end
will they be forced back to using
Windows?
CMYK is already part of Photoshop, and the folks who are in
the
printing business that we talked to about printing the brochure, said
that
Photoshop has a really good version of CMYK... but, to run
Photoshop we gotta
buy photoshop and then we gotta buy Crossover office
to get it to runon LINUX
but at only a SILVER level and not GOLD?
When is GIMP going to do
CMYK? Anyone?
Those who are saying LINUX is ready to replace
Windows, well, I got a
couple of other reasons why we will have to keep Windows
on the desktop
for now, as Linux and the LINUX apps are not ready to do it all
for us!
CMYK - who would have thought... I like the GIMP. AND
would like
to use SCRIBUS (not a word processor just a layout app), but... how
do
we get the CMYK files from the digital photos, so that we can have
our
printer say no problem. We can send stuff to this printing shop
in
.PDF, but the photos need to be CMYK before we can do anything?
AND is
then SCRIBUS something that the print shop must know... or can
they take the
.pdf files with CMYK photos in them, and just use those?
[ Reply to This | # ]
|
- When is GIMP going to be Photoshop replacement? Or Photoshop be released for Linux? - Authored by: Anonymous on Wednesday, September 20 2006 @ 06:38 PM EDT
- Pagestream For Linux - Authored by: Anonymous on Wednesday, September 20 2006 @ 06:49 PM EDT
- When is GIMP going to be Photoshop replacement? Or Photoshop be released for Linux? - Authored by: Anonymous on Wednesday, September 20 2006 @ 07:39 PM EDT
- Patents? - Authored by: DebianUser on Wednesday, September 20 2006 @ 08:10 PM EDT
- GIMP Already has CMYK - Authored by: Anonymous on Wednesday, September 20 2006 @ 09:23 PM EDT
- Check out Krita - Authored by: Anonymous on Thursday, September 21 2006 @ 12:48 AM EDT
- Rawstudio - Authored by: IMANAL on Thursday, September 21 2006 @ 01:55 AM EDT
- Rawstudio - Authored by: chiark on Thursday, September 21 2006 @ 03:07 AM EDT
- Rawstudio - Authored by: Anonymous on Thursday, September 21 2006 @ 08:30 AM EDT
- Rawstudio - Authored by: Anonymous on Friday, September 22 2006 @ 05:59 PM EDT
- Rawstudio - Authored by: Anonymous on Thursday, September 21 2006 @ 11:20 PM EDT
- When is GIMP going to be Photoshop replacement? Or Photoshop be released for Linux? - Authored by: troll on Thursday, September 21 2006 @ 06:00 AM EDT
- gimpprint? - Authored by: LegalIdiot on Thursday, September 21 2006 @ 06:37 AM EDT
- Cause & Effect? (dog & tail) - Authored by: Anonymous on Thursday, September 21 2006 @ 12:50 PM EDT
- When is GIMP going to be Photoshop replacement? Or Photoshop be released for Linux? - Authored by: Anonymous on Sunday, September 24 2006 @ 07:40 PM EDT
|
Authored by: Anonymous on Wednesday, September 20 2006 @ 06:40 PM EDT |
This book looks as though it would be interesting, and my compliments for a nice
review. The explanation of the Bayer format was especially nice and to the
point. What I would like to do here, though is to address the problems in raw
data processing which exist for Linux developers who are working on these
problems.
First, there are many schemes for recovering a color image from data which has
been presented in Bayer format. Some of these schemes are very simple, and some
are very sophisticated. Some of them are even patented, and some are proprietary
secrets. New methods are being developed all the time, and I am aware of at
least one Ph.D. dissertation in electrical engineering which is being written on
this topic. Thus, looking for more clever ways to address this problem are
always welcome -- for use both in Linux and in commercial software.
Moreover, compressed raw formats also exist, and I suspect that the book says
little about them. Several camera manufacturers have introduced proprietary
compression algorithms. These algorithms are not publicly described, and the
information is not shared with developers of camera support for Linux. It is
often clear what kind of method is being used, but even in such situations
essential details are missing and can only be guessed at. Compression techniques
which I have seen used in cameras include ADPCM, ADPCM compression followed by
some other method (two stage compression), several variants of differential
Huffman encoding, and some cameras use a compression algorithm which is even
less obvious and remains completely unknown.
Similar problems exist with many commercial scanners, too.
In other words, these problems are sufficient to provide a challenge to many
clever people. [ Reply to This | # ]
|
|
Authored by: Anonymous on Wednesday, September 20 2006 @ 08:07 PM EDT |
If this interests you, take a look at Uwe Steinmuller's website at Digital Outback Photo [ Reply to This | # ]
|
|
Authored by: Anonymous on Wednesday, September 20 2006 @ 09:55 PM EDT |
A few quick points to make:
1) You'll normally find RAW format on a digital
SLR, and not a point-and-shoot. If you're not using an SLR, there is no point is
worrying about trying to get good enough pictures to make RAW worthwhile. If
you've ever used a digital SLR, you'll know the difference as it is
unmistakable.
2) If you're getting prints made of your photos, the prints
are not going to be any better than the person running the machine. If you don't
care too much how the prints look, you can get them done cheaply at the grocery
store while you do your shopping. There's no point however in going to great
lengths to get the best possible image files and then taking them to the
cheapest place to get them printed. The cheapest places simply run the machines
in auto. The better places look at each print and set the machine up manually
for what is best for that individual print.
[ Reply to This | # ]
|
|
Authored by: Anonymous on Wednesday, September 20 2006 @ 10:33 PM EDT |
We're just lucky that the major camera manufacturers, while not (for the most
part) embracing Adobe's generic DNG (digital negative) format, have not used
the DMCA or some such to prevent Adobe and others from supporting the
various proprietary RAW formats.
However, there was a case a year or so ago when Nikon, trying to make
money off their proprietary RAW-conversion s/w, considered encrypting part
of the RAW photos so that no s/w but their own could do the conversion, to
the point where Adobe claimed they might not be able to support Nikon's
format due to DMCA concerns. There was enough hullabaloo that Nikon
backed off -- after all, copyright on the images belongs to the
photographers, not the camera manufacturer.
In the short term, before we worry about getting OSS up to handling CMYK,
etc., we should at least keep pressure behind such initiatives as DNG to
ensure the images themselves remain open to third-party s/w, open or not.[ Reply to This | # ]
|
|
Authored by: Anonymous on Thursday, September 21 2006 @ 11:57 AM EDT |
dcraw used to be the basis for ACR. I went OSX purely because of Photoshop back
when the GIMP wasn't cutting it at all for RAF files out of an S2Pro. Nikon
Capture did better conversion than the base ACR software did a while ago, though
I don't know if that's still the case. NX certainly grew capture into a nice
application and I'm not sure if I'll use PS much at all anymore with my D2x.
Nikon probably won't do Capture for Linux though, so I'll stick with the OSX
platform, and having a color-managed OS is really good.[ Reply to This | # ]
|
|
Authored by: Anonymous on Friday, September 22 2006 @ 07:01 AM EDT |
The Gimp isn't the only game in town. Since version 1.5,
Krita has supported loading RAW images, 8 and 16 bit RGBA,
CMYK, Grayscale, Lab (16 bit only), YbCbR, HDR RGB images
in 16 and 32 bit floating point, 32 bit floating point LMS
colorspaces, full color management with icc profiles --
and lots of tools and filters that work with almost all
colorspaces. You can do your photo retouching in 16 bit
rgb without any problems. There are layer groups and
adjustment layers.
And 1.6 is in beta right now, and offers perspective
transform, magnetic lasso, curves and more. Oh, and you
can embed any other KOffice document as a layer in your
image.
Sure, there's a lot to do. Krita isn't as polished as the
Gimp, and not as fast as Photoshop. We've got lots of work
to do still, but fortunately, we love doing the work :-)
Boudewijn Rempt, Krita maintainer (who really should
update the website, but hacking is so much more fun)[ Reply to This | # ]
|
|
|
|
|