People following my blog can probably guess why I’m concerned with this just at the moment.
Where and Why
The formal purpose of the artist’s signature is to certify that particular print as meeting theirÂ artistic and technical standards.
My research strongly suggests that there is no consensus on what is expected by art buyers, collectors, or museum curators.Â They do all seem to like consistency, so you should decide early on what you’re going to do, and do that from then on. Or at least make rare changes, and make the changes cleanly and ideally document somewhere people can find that you have done so.
So far as I can tell, people do anything from nothing at all to using a stamp or “chop” on the back to signing the front (“recto”) or back (“verso”). They write anything from their initials to a regular signature, or print their name, or anything else. They often include a date or two (for photography, date of image and date of print are the two most often used). They sometimes include the title of the print. They use anything from metallic-ink sharpies to pencils. They write on the back, or in the margin on the front, or within the actual image.
The full form I like is to put the image title and year photographed in the bottom margin at the left, and the signature and year printed at the right. I will leave enough space so it can be either included in the mat opening, or matted out, at the owner’s choice.
However, when signing a batch of prints all at once, that’s too much to write (it is; I’m not lazy, I just have lousy handwriting, and if I tried to do that much on each of a pile of prints, it’d end up illegible on most of them). If I were clever and thought ahead more, I might print the image title and year photographed as part of the image (an image of my careful printing; I can do it once legibly if I get enough chances), and only do the actual signature and year printed by hand.
Specifically, with what?Â What writing instrument?
The requirements as I see them are:
Harmless (will not damage the image, either physically or chemically)
Permanent (will not fade, hard to remove, resistant to water and other hazards)
Suitable width (artist preference)
Suitable color / density (artist preference)
Hard to smear
Writes smoothly and without skipping on the particular paper
Those first two are sometimes lumped into “archival”. Given the complexity of the inkset-plus-paper chemistry encountered in modern digital inkjet prints, adding a third thing, the ink from the signing pen, to the equation is at best a wild gamble. Ink plus paper combinations get tested by various firms, but I’ve never heard of any of them adding signing pens into the mix.
Given this total lack of real information, I’m making a wild leap of faith: I’m accepting all writing implements that make claims of being permanent and (critically) neutral Ph (or acid-free). And I’m taking their word for it; I have no way to verify it much.Â Amateur testing is interesting as far as it goes, but accelerated testing is a black art, amateurs aren’t very good at it. And for art prints, I’m thinking in terms of the print lasting for centuries, not just years.
The totally conservative approach is to stick to pencil (graphite, not very reactive) or India ink (basically a carbon suspension in water, not very reactive).Â I find that too limiting, especially since pencil doesn’t write on the front of this paper.
I tried a bunch of pens I liked writing with and had sitting around on this paper. Surprisingly, everything with any sort of “ink” wrote beautifully on the particular paper I’m working with this time (Canson Baryta Photographique). One dry pencil also worked fine (the Schwan all-stabilo 8046); a mechanical pencil with HB lead and a charcoal marker didn’t mark at all. (Maybe it’s not that surprising; this paper has an ink-receptive surface layer after all.)
Even more surprisingly, every pen I looked up info on claimed to be archival and acid free; apparently all of these pens I grabbed meet my technical criteria. (Well, all but one; for total giggles I tried a Big Round Stic, a very cheap ballpoint.Â Surprisingly, it wrote on the paper perfectly well. It’s hard enough to damage the surface, and I have no reason to consider its ink suitably permanent, so I would strongly recommend against actually using it to sign artwork.)
Blaisdell Charcoal Pencil Medium 633Tâ€”did not write on this paper
Here are the various results. I’m not bothering to label individual trials, you’ll need to try your pens on your paper anyway, but this shows that a wide range of pens made good solid clean marks on this paper, at least.
I also tried a few of them on the back of the paper.
ADDED: I found the Sakura almost impossible to smear. The other roller pens could be smeared just slightly by running a finger over them immediately after writingâ€”not something I do frequently by accident, but it also indicates that stacking prints as I sign them might be a problem. The Stabilo pencil also smeared a tiny bit, interestingly.
I’ve been meaning to do an article on this for years.Â This week, this image is on sale through The Online Photographer, so I thought I’d better get around to it, in case I might be able to stir up an additional order or two.
I’m simultaneously rather excited and a bit scared about writing this. I’ve had great hopes for this photo since I shot it in 1975, but never got a satisfactory print until 2007 when I had
I thought the Lincoln Memorial shot had promise at once; it’s marked on the contact sheet with red grease pencil as I did then for things I wanted to try to print.Â I remember not being able to print it at various stages and with various technologies; but looking at the contact sheet and early scans now, I think at least the first scan is something I could work with.Â I suppose it’s possible that I’ve learned something about digital printing in the last two decades.Â Probably other people could have printed it at earlier stages, too.
Then, on top of that, I really wonder if maybe I should have paid for more bits of drum scan (16 bits or higher res?); maybe it could be even better.
Yeah, I’m all wrapped up in getting ready for the start of the sale, which means I’m questioning every decision that it’s too late to change.
However, what I’m actually going to write about here is printing this picture. I’m working largely from memory (Ctein doesn’t tend to create a layer structure that preserves every single decision made as a separate event), but I do have the contact sheet (and negative), Nikon scan, drum scan, and the 2007 and 2014 versions of the edited file, so I have at least some objective evidence of what was done to aid my memory.
How we accomplished things might be of some interest, but what we chose to accomplish, and why, are far more important. Of course I have even less evidence for those; that’s nearly entirely from my memory.
Â Which Version?
The problems actually start one step back from where you might think.Â You see, I have three exposures of the memorial from this trip.
This shows them in backwards order (note the negative numbers at the bottom). So, at the left there is the one I actually printed.Â In the middle is an even more underexposed version, of no particular interest.
And at the far right is what first caught my eye.Â It wasn’t just Lincoln and the park workers, it also included the family in the foreground at the left.Â Unfortunately, it was done in such a hurry that the exposure is awful, and the family is cut off too high (for no good reason, there’s free space at the top), and that guy on the right is a problem, and there’s a guy on the left between us and the family too (I suspect one or two of the spare guys walked into the frame between when I saw the possibility and when I was able to shoot).
So, in the end, there’s no choice, there’s only one version worth working with.Â You can’t obsess about the ones that got away, because if you shoot people living their lives, aÂ lot of things you see get away over the years.
I started with a scan I made myself (Nikon Coolscan LS-2000).
First, you may notice there’s an amount of crap on the negative. That’s easily fixed, if annoying.Â Also, it mostly looks pretty good; I think my saved file of this is significantly adjusted, not straight.
Also, that the cropping is somewhat different, and that there’s that ladder in the background, and that the perspective is also somewhat different.
I might have been able to make something of this, eventually, but I didn’t at the time.
So I went ahead and had a drum scan made (some years later).
Even at the small size it looks a bit more flavorful to me (remembering that we’re looking for information to work with in printing here, not finished art!).Â It’s smoother.Â Also they either cleaned the neg better than I did, or spotted it a bit.
First time I’d done this, so I probably didn’t give the lab the best instructions, either.Â What I’ve got is a 40 megabyte tiff file in 8-bit (per channel) RGB, which is a pretty strange choice for the lab to make when scanning a B&W negative.
When Ctein first got his large-format printer, I was out in California about a week every month for work, so I was visiting fairly frequently. He suggested I bring some image files that we could play with printing, so the next time I went out I did. Came back from that with four prints I believe (four that I still have on my walls, at least), and we worked on a couple of others a bit before moving on.Â We spent about a day and a half doing that and very little else, which was a blast.
(My usual readers mostly know who Ctein is, but for those who don’t: he is or has been a photographer; custom printer in dye transfer, B&W, and digital; author of two books on printing; and writer for many photo magazines.)
In case you’ve never tried it, I can tell you that you can learn quite a lot sitting for hours with a master printer working on getting photos ready to print. We’ve done this off and on at my computer and his over the years, sometimes just poking at ideas, this one time carrying several images all the way through to making actual large prints (24″ paper, the images are about 20″ wide and 30″ or so long).
Okay, so what all did we do, anyway?
I think of this as global contrast adjustments.Â Treating the picture as a whole, we’re putting the major parts into appropriate tonal relationships.
The Lincoln Memorial is a masterpiece of neo-classical design.Â I wanted to present it in the print with that kind of formality, both for its own sake, and because that increases the contrast with the workers standing casually on the statue.
In this case, a bit of straightening plus removing the vertical convergence were required.Â This is an area where digital printing has it all over darkroom printing; you can do a small amount of perspective correction in the darkroom, but most enlargers make it very annoying, and the physics limits pretty strongly how far you can take it.
If you’re doing this kind of work a lot, it can be worthwhile hauling a view camera around, or at least a perspective control lens, which lets you fix the convergence in the camera.Â On the other hand, that means you can’t get such shots of anything but static scenes (well, or scenes that can be predicted reliably).Â With digital, you can get the perspective you want in more dynamic situations.
Local contrast enhancement
Anything from large-radius unsharp masking (with a radius up in the 50-75 pixel range you’re changing the local contrast quite strikingly) to simple dodging and burning to fancier Photoshop tools to additional curves adjustment layers with individual layer masks.Â I believe we used some techniques to enhance contrast in both shadows and highlights without making the whole picture look flat
Noise (grain) reduction
Another place where digital printing has it all over the darkroom!Â I think Ctein hit this with Neat Image after playing with the settings a lot.Â Neat Image has a lot of settings, and I use Noise Ninja (which is simpler and quite effective) myself.Â Ctein uses both (and other newer things), choosing them for how well they work on the particular problems in a particular image.
Much simpler in digital than in the darkroom.Â I don’t have to manually spot each print with a palette of dyes and very very fine brushes, and yes, I’ve done that.Â (Yes, it’s so easy one can get lazy about cleaning negatives before scanning, which is not good.)
Remove stepladder from background
This level of retouching was done on darkroom prints for advertising photos sometimes (even in color), using air brushes and such, but I would certainly never have tried it.Â I’m glad to have the ladder gone, though.Â (I remember removing it was Ctein’s idea. I learned one Photoshop technique I hadn’t known previously watching how he did it, too.)
Dodge out faces of workers
That’s basically simple, though we pushed it to the limit I think. What’s harder is touching up the background so it doesn’t look like there’s a halo. I don’t mean avoiding an actual halo, that’s relatively easy in Photoshop. But even if you get it just right, your eye will create a halo that isn’t there, so you end up having to do some careful background burning to make it look right. Purists might argue that that’s wrong; I guess in some situations I’m not a purist.
Crop to eliminate distracting foreground steps, chain, pillars
The one thing that’s close to exactly equally easy in darkroom and digital!
Deciding how to crop is black art, mostly. In this picture it’s fairly simple, we’re trying to retain as much image as possible while eliminating a few distractions.Â Composition is always important, but this is a photo with a strong subject which draws the eye quite easily on its own, we don’t need to do a lot of work to get you to see the important bits here.
Adjust B&W tones in printer driver (somewhat colder black)
I always did prefer the cold-tone Agfa papers.Â With Epson Ultrachrome printers, in the B&W mode you can easily adjust the B&W image tone in the printer driver, and we turned it modestly to the cold side. I don’t remember numbers.
We re-worked the image when Mike Johnston of The Online Photographer decided (at Ctein’s urging) to offer this as their July print sale (TOP has done a couple of print sales a year for a long time, but is just starting to experiment with havingÂ print sale every month).
To really see the final outcome, you need to go over to The Online Photographer and buy a print, but, for purposes of this article, here’s the jpeg we’re using to represent the final print.
Memories of this are more recent, plus the discussion was conducted in email.Â So I know what we aimed to do better than above, but I’m not nearly as clear on how Ctein achieved the goals since I didn’t see that happen.
So, here are the additional changes we made for the final version.
Lightened much of the image
I think Ctein probably felt, now, that the original print was maybe too dark (though he didn’t have it in front of him when doing the new versions, just the file). But also, for a smaller print, the proper brightness range is different, usually lighter, than for a bigger one, and the print sale prints were going to be smaller than the first print we made in 2007.
Brought out the worker’s faces more
Even after lightening, Ctein could get some more there, so he did.
Eliminated some optical-illusion halo around the worker’s heads
But we got weird illusion halos.Â But Ctein killed them off.
Reduced spray mist around the feet
In the first proofs I saw, I felt that the side and toe of Lincoln’s shoe, the hose near it, and the left worker’s boots ended up looking funny, low-contrast and weird. I suspect it’s actual spray from a few seconds before still in the air, and hence completely “natural”, but it looked weird, and I think what matters in this kind of print is that it look believable, not necessarily that it be slavishly accurate (obviously for forensic or scientific photos, or even just photojournalism, the rules are different!).
Removed weird effects on the toe of the boot
After the above, it looked bizarre for other reasons, so Ctein messed about until it didn’t. I didn’t see the intermediate state so I can’t be too specific.
Darkened the pedestal
I felt that the big hulking pedestal was drawing too much attention to itself.Â I didn’t want to crop it out, I wanted Lincoln to be clearly above us and it contributes to that, but I wanted it to draw less attention.Â Again, we pushed this to the point where some artifacts appeared, which Ctein then had to eliminate.
Brought out the spray on the left side some
Didn’t want to darken the spray or make it less visible while darkening the side, so magic was done.
So, to make it easier to compare, here are the initial scan and the final image side by side.
The list of things done looks long, but I don’t consider this to be an example of “extensive” manipulation. We did take one thing out (the ladder), but it was a background element. Other than that, we did things that were basically “optical” in their results, all of which can be done in the darkroom. It’s just that, when you start writing down every little thing, it ends up being a long list.
I’m evaluating these raw processors for my own use in my own workflow. My primary use for raw processors is for processing bulk photos into “semi-custom” quality; vaguely like what a pro lab in the film era would produce as “video-analyzed proofs”, where a human had glanced at each photo for a second or two and made some very quick adjustments. I use this for batches of hundreds of photos from events ranging from science fiction conventions to roller derby bouts. Because most of my work is by available light when there isn’t much light available, noise reduction capabilities are important to me; if you shoot outside in the sun, or in a studio with all the lights you can fit, your needs will certainly differ. I use a different workflow for images that I’m taking the time to push to the “custom print” or higher levels; those go through Adobe Camera Raw and Photoshop CS6, and get a deal more work (usually multiple curves adjustment layers with layer masks, plus some bitmap layers with masks or unusual blending modes). That means I’m not looking at all at any issues with driving a printer in these raw processors, or doing very much with some of the fancier features, especially local adjustments. I am looking a lot at the ability to usefully copy settings from one photo to a group of others.Â So, I apologize to any products that are marvelous, but don’t fit my particular needs too well. I’m trying to be clear about the limits of my interests here, in hopes of not damaging anybody.
Since I’m learning most of these products for the first time, it’s inevitable that I’m not going to get the best out of each of them. I apologize in advance to anybody who gets poor ratings in some area because I didn’t figure out how to use it!Â (Email me, and if I agree I’ll fix my articles).
Finally, I have not tried to come up with objective measures for various characteristics.Â These reviews are, in the end, entirely subjective. I try to explain why I feel the way I do in ways that will help people decide if they care what I think, but it’s entirely possible that somebody will have very different views from mine even if their needs are very similar.
I’m making my work public because it seems a shame not to, and because I hope I may get feedback correcting any mistakes I make (before they lead me to choose the wrong product).
I’ve noted things I could improve here and there, rather than actually improving them. I’m afraid of the best becoming the enemy of the good, and my spending huge amounts of time on this project making it better and betterâ€”and never quite being ready to publish it.
Mostly, what I have here is the final images I produced from each of the images in each of the processors.Â Sometimes my ideas for the image may have evolved during the process, too, just to complicate things.Â And there are formatting issues, and the full-size images are pretty large.
(Because there was a checkbox, the galleries of results for each photo are presented in random order. This means you aren’t always viewing the products in the same order. This seems good for avoiding some small risk of bias.)
This photo was shot with a Nikon D700 and Sigma 120-400mm lens at 270mm, ISO 6400, 1/250 sec. at f/5.6 and saved as a NEF (raw) file.
I’ve chosen very similar croppings in each case, and at thumbnail size these look pretty similar.
Like many sports shots, especially below the top professional levels, this one has some technical flaws. The woman with the whit helmet cover isn’t actually quite sharp. I think this is an actual focus issue, not a shutter-speed issue, but it’s hard to be sure at this level. I was already shooting at ISO 6400 at f/5.6, which was wide open on this lens.Â Being able to stop down another stop would probably have helped, but I certainly couldn’t give up a stop of shutter speed.
Looked at full-size, they differ quite a lot, though.Â I think the key points are the white helmet cover the taller woman is wearing (degree of detail in the highlights), the texture of the flushed patch on the cheek of the woman, and the background texture (say just to the right of the taller woman).
Photo Ninja: noise maybe just a hair better controlled.Â Helmet cover highlight just a bit better.Â Color balance is either a question of my eye at the moment of processing (I’ve worked on these over two weeks).Â I seem to remember white-balancing on the same stripe of the referee at right in all cases, though.
Darktable: Noise remarkably well controlled, but maybe pushed too far; the near woman’s face is looking a bit plastic.Â Helmet cover highlights a bit missing (not really important in this image, but shows differences). I probably should have made it brighter here.
LightZone: Noise pretty bad. Helmet cover highlights not too good.Â I have made this one brighter, maybe a hair too much so.
Capture one: Noise kind of okay, helmet cover highlights bad, brightness about right maybe (but cover got away then).
Lightroom: Noise decent enough, highlights a bit gone.
DxO: Noise is a problem.Â Nothing really matches Noise Ninja (even 2, but 3 is better) in this test.
This photo was shot with a Fuji FinePix S2 Pro and a 70-200/2.8 lens at 115mm, ISO 1600, 1/60 sec., f/2.8.Â It was saved in JPEG mode.
This considerably older camera doesn’t have as good low-light performance as the D700, so ISO 1600 still requires considerable help with noise reduction. The lighting also isn’t very good.Â It’s room light, inÂ hotel function space, so the face turned down is rather shadowed.
(The subject is the late John M. Ford. This was from his “Ask Dr. Mike” show at Minicon in 2003.)
There’s more variation in cropping this time, though not massive. I did straighten the picture in all cases, anyway.Â Color balance also varies a lot, and I tend to prefer the middle positions.
Since this is from a JPEG file, we can’t do much about highlight recovery.Â The shoulder of the lab coat and some of the collar are definitely burned out. Doesn’t harm the picture that much, though.
The black shirt is horrible for noise (and needed considerable adjustment of the black point to make it look tolerable at all).Â The shadow above the right edge of his mouth is a particular problem, and below the chin.
Lightzone: Shirt has lots of big blobs.Â Forehead and cheek aren’t really too bad.Â Upper lip and shadows on chin are awful, though.Â I could pick settings that were less bad there, but they don’t do nearly as well on the forehead and cheek then.
Capture One: Shirt is cleaner, with less black point assist than LightZone. Cheek isn’t as nicely cleaned up but chin exhibits fewer noxious artifacts. Not bad really.
Aftershot: Nice noise cleanup (go Noise Ninja). Just a little cold on the white balance.
DarkTable: Overly smoothed but still didn’t reduce noise enough.Â Shirt isn’t showing nasty aftifacts so much though.
Lightroom: Maybe a bit cold. Shirt is both blobby and blue (but fixing white balance might fix that).Â Noise doesn’t really look that bad (because I chose to leave it being somewhat obtrusive rather than push until I got artifacts). Some might argue that I’m more bothered by noise than I should be, and shouldn’t work so hard to reduce it.
Photo Ninja: Face could be lighter I think. Shirt is reasonably clean and not blacked out.Â Noise reduction pretty decent leaving lots of skin texture.
DxO: seemed easy enough to get what I could fixed.Â Shooting jpeg is not a good idea :-).
This was shot with a Fuji Finepix S2 Pro at 28mm (I think the Tokina 28-70 ATX Pro), ISO 200, 1/250 sec. f/8, saved as a RAF (raw) file.
The conditions weren’t really very good for this photo, the direct sun on the water at the top of the falls with the rest of the face in fairly deep shade leads to distinct problems.Â There’s also a big magenta ghost reflection at upper right, demonstrating the nicely circular aperture on that lens.
Some of the processors didn’t get on with the Fuji raw file (which is admittedly one of the weirder ones).
Capture One: I let the sunlit water get a bit away in this version, to bring up the detail in the face some.Â I’m reasonably happy with this given the problems in the initial exposure.Â I did use masking to bring down the top water highlights some.
Darktable: although it got an image out of this file, there’s an obtrusive pattern over it. This is not a usable conversion (and I didn’t do much of any work to optimize it). Note that the water at the top is not really very burned out.
Lightroom: Not enough contrast, I lost the color in the ice on the face, and the face is too dark. This is all on me, though, there’s nothing I remember about Lightroom that made me do any of those.
Photo Ninja: Boy, look at that sunlit water!Â Now that’s highlight recovery.Â I did let the color balance go too yellow (and lost the cyan in the ice on the face mostly, though there are traces left especially on the left).
Shot with a Nikon D200, 50mm lens, ISO 800, 1/30 sec. f/2.8. I’m not sure if that “50mm” is that setting on the 28-80 Tokina zoom, or the Nikkor 17-55/2.8, or my old Nikkor 50/1.8 AIS. Saved as a JPEG file.
These are close to identical (by the standards of this comparison, where I processed them individually by eye and didn’t go back to bring them into convergence later). This turned out to be an uninteresting test photo.
Shot with an Olympus EPL-2 and 60mm f/2.8 macro lens. ISO 400, 1/500 sec., f/8 and saved as an ORF (raw) file.
None of these really quite works for me (there are other shots from that day that I like a lot, though). I don’t have the plane of focus quite where it needs to be I don’t think (there was too much wind to shoot on a tripod, and much of the focus plane placement is luck or at least selection from among a random assortment). And I haven’t made the colors do quite the right things in any of them.Â Which in some ways makes it an interesting test photo.
Lightzone: Colors do look mostly good in the flower.Â The background is just a bit olive. Capture One: Less red, background more olive.Â A bit darker.Â All that’s me, not a difference in the programs, though.
Aftershot: More red in this one.Â Definitely too dark.Â All me again.
Darktable: Local contrast in the flower is bad, and it’s too dark. I had trouble getting this any better in Dark Table, though.
Lightroom: Yeah, that’s about what I can do with this. Was quick and easy in Lightroom.
Photo Ninja: Colors look cleaner to me, and I see more definition in the flower sex bits inside there. That is the processor.
DxO: The micro-contrast tool was nice to work with here.
Doc Smith Books
This is the only artificial test shot included, and the only one I shot specifically for this test. This is intended only as a semi-objective (not quantitative) test of highlight recovery capability.Â There is a direct flash on the far side of the books, at about camera level, so that the light decreases with distance along the line of books.Â The book covers provide some fairly normal image content, and the brocade pattern in the tablecloth provides highlight detail. The exposure was set so that the near edge was several stops overexposed, to ensure that the limits of even exceptional highlight recovery would be visible.
(The one experiment where the brocade was much less recoverable was when I used Adobe Camera Raw and rendered into Adobe RGB 24-bit. That really lost me a lot. As I have found before, using a big space like ProPhoto RGB in 48-bit mode helps a lot.)
My reading of the test images is that there are clear differences in highlight recovery (though some of them could have been caused by other changes I also made; I tried to not do that, but I could have slipped).Â The order, from best to worst, of the processors for highlight recovery is:
DxO Optics Pro
Capture One Pro
Corel Aftershot Pro
It’s hard to see at all clearly with single images on the page, so I’ve made an animated GIF that flips through them in order, with each processor labeled.
Shot with a Fuji Finepix S2 Pro at Sigma 105mm macro lens. ISO 200, 1/60 sec., f/4.8, saved as an RAF (raw) file.
Lightzone: This is maybe a bit too muted in color, but not tinted. The white fur areas have held up very well.
Photo Ninja: right on in color, I think.Â And very quickly achieved. I like the white fur and the black both, too.
Capture One: I let the white leg in the foreground kind of get away from me; I pushed this for a bit more contrast in general, and I think I overdid it.
Lightroom: Nice detail and contrast, but I let the color get away just a bit, that carpet looks actively fake now.
This was fascinating, I’m very glad I took the trouble to tackle this project this seriously. While this won’t pass muster as a set of serious product reviews (I think I’ve been adequately careful to deny that intention), it records my reactions and opinions pretty well and shows some basis for them.
And I’ve learned a lot about raw processors I’d never used, in some cases never heard of, before.
First the good: The worst of them were somewhat better than I was afraid would be common.
Especially, the free software examples show a smoothness and sophistication of user interface, and a high level of capabilities, that I’m not used to finding in free photo software.Â (I’m quite familiar with free software and use it extensively and love the idea a lot; I use Linux and Solaris / Illumos regularly, and Emacs and Perl and MySql and Apache web server and PHP and GCC and the whole Gnu command line toolset. Its area of strength isn’t generally smooth and sophisticated GUI.)
And the bad: none of them are a good replacement for what I’ve been using.Â I can continue using Aftershot for the time being, until I get a new camera body my old version doesn’t support (new versions lack Noise Ninja integration), and by then things may have improved.Â But, right now, while the quality of many of them is quite good enough (and Photo Ninja seems clearly better to my eye), the responsiveness of the editing UI is not good enough in any of them except Lightroom.Â Lightroom has noise reduction problems (maybe spending more than the sale price of Lightroom on Topaz denoise, using it through their Lightroom integration interface, and learning to use it well would solve that).
The performance of all of these rendering files at various resolutions is also far slower than Aftershot (and Bibble before it) achieved, but that’s not tremendously important for my workflow.Â What’s an actual problem is UI responsiveness.
I think this is how about everybody works: I see something I think is not quite right, and set out to fix it. I pick a tool. Then what I do is adjust the slider (or whatever UI element) for that tool and watch what happens, and see if this is going to make the thing I’m fixing better.
For this to work well, the screen area being previewed needs to snap back and forth quite sharply between states as I adjust the control.Â In Photo Ninja, I can often see the tiles of image being updated individually; that’s far too slow.Â (For complex things, like noise reduction, really instantaneous response is no doubt technically impossible, and I’ll have to live with that of course.)
The way the human eye and brain process images, it’s really valuable to have sharp, clean switches between versions of the photo, and for exactly when that happened to be obvious (and quick).Â I have to switch back and forth a lot more times when the switch is sluggish.
So.Â Photo Ninja is the one that strikes my fancy best.Â The big flaw with it is UI responsiveness, and I hope that comes up reasonably soon on their worklist (I know it’s on their list). From the web site it looks like they have a very small development team, which sometimes makes things slow. It’s also more focused; it doesn’t try to own your photo catalog to, it just edits (it has a browser for finding photos in your filesystem, but it also integrates well with Photo Mechanic); that also fits my preferences very well, I prefer products that are really good at doing their core thing, and don’t try to do much else.Â I have hopes that they’ll do some work on editing responsiveness.Â I will say that I think I get the best results, most easily, out of Photo Ninja.Â This fits very well with my workflow, where getting semi-custom quality results quickly is the key.Â With the current level of responsiveness it’s still pretty usable, especially for smaller sets of photos.
DarkTable and LightZone are both free software (DarkTable does not run on Windows, LightZone does; they both run on Linux and FreeBSD and OS X).Â They’re quite sophisticated and do good workÂ The UI responsiveness isn’t very good with them, either.
Capture One Pro is the big dog in some sense (been around for a while, heavily used by professionals, now shipping with most medium-format digital gear).Â It works fine, is a bit sluggish in UI response still, and didn’t really capture my heart. It has considerable capability to do local adjustments, which mostly doesn’t matter to me, but makes it closer to a good complete replacement for Photoshop for those not trying to achieve “fine printing” levels. It’s also the most expensive by a lot.
Lightroom is the other big dog (must be many more copies out there than Capture One). Being annoyed with Adobe was part of why I started this (hoping to avoid being chased to Lightroom by the collapse of Bibble and Aftershot); it’s the default choice for DSLR photographers. UI responsiveness is good. Capabilities are generally good.Â Noise reduction, which I use pretty heavily, is a problem area, though.Â It has weird issues working with anything other than local disk drives, too, which I had to fake my way around and would be afraid might break at any future release of either Windows or Lightroom. And it tries to lock me in by making me use their “catalog”.
So, there you have it.Â Lots of highly capable products out there, none that I really fell in love with for immediate use.Â I have some hopes for the future, though, mostly centered on Photo Ninja.
Well, what the heck; somebody asked, and they do have a free 30-day trial.
They certainly talk a good game, including details about noise reduction that sound like they’ve worked on it hard.
Looks like I’d need their more expensive edition just because I have a semi-pro camera (the Nikon D700).Â Since I also get raw files from friends on occasion, it’d probably be a rude shock to discover I couldn’t process Oleg’s files in the future anyway. I do get a bit upset at such clear-cut price skimming, though.
What’s with going to separate images for “use tool in this image” vs. “correction preview”?Â This happens when I select the eyedropper tool for white balance. The effect is to make the targets I’m trying to hit half as big, and to cause me to have to look away from where I’m clicking to see the effect.Â Everybody else including free software packages is bright enough to understand clicking in the same image they’re previewing. The response is also pretty slow.
The big talking point seems to be doing noise reduction before de-mosaicing. In theory this does suggest some benefits, in that cleaning up the noise before you spread it around sounds simpler.
On initial experimentation, though, it’s not doing as well as Noise Ninja did historically.
Just conventional unsharp mask, it looks like, which they recommend against.Â Still needed for many of these images though.
Hey, you can undock the organizer!Â And put it on the secondary monitor, say. Thus getting back the scarce vertical screen real-estate. I just stumbled across a keyboard shortcut for doing this, dunno if there are other ways.
I can tear off individual tool palettes, too.Â Putting histogram on the other monitor is another good thing.
I seem to be losing on the Fuji S2 again.
And it doesn’t recognize DNG files as images at all. I confirmed this in the product forums, where it seems to be common knowledge. This really ought to be enough by itself to knock this product out of consideration; that’sÂ the standard strategy for dealing with unsupported and unusual cameras.Â (Sounds like it will accept DNGs that it converts itself, and DNGs that cameras write natively, but not those converted by Adobe DNG converter.Â Not acceptable, DxO!)
While single controls take too long to preview, there’s a very fast swap between corrected and raw. That gets less useful as the complexity of correction increases, but I use my raw processor more for bulk correction, so that’s not as much an issue as it would be for some users.
The automatic defaults did quite a nice job on contrast and brightness.Â That’s a big win for the way I use raw processors (on bulk photos, looking for semi-custom results).
Noise reduction not showing to great advantage. And clicking the color balance eye-dropper in the same place doesn’t produce very similar results to other products.
This is a camera JPEG, so many of the benefits don’t apply, notably in noise reduction.
And either it’s not working that well, or I’m not finding the right options. Selective tone looks useful, and I’m quite used to working with the tone curve tool, at least.
Uh oh; it can’t seem to open the Fuji S2 raw file (RAF) for this. And doesn’t even see the converted DNG file. Fail! (I noticed the S2 wasn’t on the list of cameras they had optics modules for, either). And I haven’t had that camera for years now, no way I can make any sort of calibrations myself.
I actually had some trouble getting the sharpening I’d used in other processors.
Had to play with contrast and micro-contrast to get this to come out okay.
Doc Smith Books
This looks pretty successful, and was easy.Â (There’s no explicit “recovery” control in this, as in many processors now.)
Also not processable, neither DNG nor RAF are supported.
I was already a Picturecode customer with their Noise Ninja application and Photoshop plugin, which I’ve been using for a long time now, and which is still arguably one of the leading noise reduction tools. Now they’ve released a raw processor (and organizer; more on that later) that I would call a direct competitor to Aftershot.
I’ve used Photo Ninja through Fourth Street Fantasy Convention weekend, for my lightning pictures, convention pictures, and a Minnehaha Falls trip the next Tuesday, in addition to the test photos I ran through everything.
I found Photo Ninja produced particularly good renderings of my images, with less effort than the other products. The “smart lighting” feature does a great job of making good-looking proofs nearly painlessly the vast majority of the time. And it’s easy to take control when the automation is going astray, as all automation does now and then.
While performance is good overall, and it makes good use of my four cores, it takes inconveniently long to update the image previews when I adjust some control. Since the normal workflow consists almost entirely of shoving controls around to see how I like the resulting look, this is a problem. I can generally see individual image tiles being updated, meaning I don’t get the quick snap from one version to another that’s needed to make it easy to decide which one looks better.
There doesn’t seem to be a way to use mouse roller or arrow keys to adjust a numeric box controlled by a slider (you can, at least, type in a value).Â Again, this is something I use all the time, and would miss really badly.
I can’t find a tool to give stepless image rotation dragging the image. There’s a slider that gives me Â±45Â°, and buttons for 90Âº increments (weirdly hidden in the “view” menu!), but no way to just turn the damned thing until it looks right.
I was able to get 3×3 and 5×5 grid lines in the crop tool easily enough, which I find very valuable.
It took me unreasonably long to finally recognize it, but the “constrain to original boundary” checkbox, clear by default, is how you make the cropping boxes stop at the image edges. I think this should be on by default.Â While you sometimes want to go beyond the edges, much more commonly you don’t.Â It does seem to retain the way I had last set it, at least.
Color Info Panel
I didn’t find any tool to report the color component values of the pixel at the cursor. I use this a lot in other products to evaluate color correction settings. I think every other product has this in some form.
There are something like 11 modes available, and they aren’t described anywhere. Only a few of them seem at all obvious, and the shapes they make differ considerably from each other.
Here are a few of the interesting examples:
The help does not seem to have any sort of help function, which has made it extremely annoying to try to figure a lot of things out.
That is, lack thereof.Â Often it’s really effective to use the visual curve editor to apportion the brightness range between the density ranges that have important content, and there’s no way to do that right now.
Changing rating, color, or selection in editor mode
You can change those things on the film strip, but you can’t change them on the actual editor screen, which is very annoying. I’m frequently making my final ratings, and using colors to sort out image sets, while also making adjustments (when I’m seeing close to the final forms of the photos), and I have to go down, wait for the filmstrip to auto-de-hide, and then find the thumbnail for the current photo, and verify I have the right one.Â And the absence of that information from the screen makes it easier for me to forget to think about it, too.
I can’t move things around the screen.Â I can make the film strip auto-hide in editor mode, and even the left panel, but I can’t move the film strip to the side.
With the triumph of the wide-screen monitor, it has become a capital offense to put anything permanently at the top or bottom of the screen. Vertical screen space is the scarcest resource on my computer, so anything that can possibly be moved to a secondary monitor or at least put to the sides, has been. But that film strip goes at the bottom, with the only option being to auto-hide it.
The really annoying issue is that you can’t pick the pixel dimensions to render in. PictureCode tells me they will of course have that eventually, at least. It’s a real pain now, though. When I need to render to given limits for a web gallery (or to arbitrary client requirements), I can’t in Photo Ninja.
Merging RAW and Jpeg
This is controlled by an option on the browser screen, rather than a central preference. That’s probably a good choice;Â I imagine some people would want to access the jpegs a lot more often than I do, and with merging selected they’re not very accessible.Â I got confused a few times, not thinking of the option being there, but that’s my learning curve issue.Â And a number of the other products don’t support it at all.
In the browser display, the thumbnails have neatly centered rows of round dots (not actual stars) representing the star ratings.Â Unfortunately, they’re not located at the spots where you click to change the star ratings.Â If you put your cursor near them, a red box appears delimiting the area the ratings levels appear in, and the ones currently set move over to the left.Â This strikes me as a triumph of design over user experienceâ€”it looks better with the ratings dots centered over each thumbnail, but it misdirects my aim each time I go to try to change one.
This is also true on the film-strip.
There’s no way to filter the images displayed in browser mode. I use this all the time, and no, sorting is not an alternative (it separates things that I need to compare to confirm that my ratings are correct, or to fix my ratings). I need to be able to filter by rating, color, and selection, in combinations. I would also like to have filename wildcard filtering in there too.
Come to think of it, I’d like to include the green dot (it means I’ve made adjustments to the image) in filtering as well.Â The green dot is more visible than many ways to flag that, and it’s a very good idea.
A roller derby action image, shot at a long focal length by available light and hence at high ISO (6400) to get the high shutter speed necessary.
Â Dr. Mike
Available light at Minicon in 2003. Shot with my Fuji Finepix S2, so even ISO 1600 was pretty serious.
The big challenge was noise reduction, especially since parts of the face are deeply enough shadowed to be pretty worst-case. And Photo Ninja really ought to have good noise reduction, so it was worth playing with.
I tried none, color noise only, and luminance plus color noise (plus played with the controls on each setup).Â Here are the screenshots of those:
Sun off the white water at the top of the falls, plus the face being in shadow, made this something of an exposure problem, meaning that the shadows got pulled forward a lot in processing.
Photo Ninja got strikingly better results with the sunlit water than I’ve managed elsewhere.
This one as mostly easy; just a little cropping, and increasing brightness in a picture where most of the colors are dark.
This is from an Olympus EPL-2 raw file (“.ORF”).
Doc Smith Books
This is an artificial highlight recovery test. Photo Ninja doesn’t seem to have done a lit better than other processors, which is interesting given how big a difference there is in the Minnehaha picture.
This started from a Fuji Finepix S2 raw file, so I had to rotate it 135Âº to get it to this orientation. The density and color correction were trivial.