photoblogography - Just some stuff about photography

Negative Lab Pro

Auf Wiedersehen, Silverfast

in Film , Friday, October 16, 2020

This is a quick review of Negative Lab Pro, a piece of software I’ve been aware of for some time, but only just now got around to trying.

Upfront, the website claims “NEGATIVE LAB PRO brings impossibly good color negative conversions right into your Lightroom workflow”. And it does exactly this. And it’s a really big deal.

I’m a long term user of Silverfast, and have defended it more than once, despite its insistence on ignoring all conventions, and the total deafness of its developers and managers to any kind of feedback or dialog. Despite all this, it’s pretty good. But the workflow is stuck in the 1990s, even if some minor concessions to openness have been added. Sadly for Silverfast, I think that Negative Lab Pro (NLP) is a major nail in the coffin.

NLP provides conversions which are at least as good, provides a totally non-destructive workflow in Lightroom, enabling easy creation of multiple versions of the same source scan, all fully re-editable.  On top of this it taps into Lightroom’s Profile mechanism to enable devastatingly accurate emulations of the rendition of standard scanners such as Fuji Frontier and Noritsu.

Of course, negative conversion is a very subjective thing, but the respective look of basic Frontier and Noritsu output is quite objective.  Generally I do all my own scanning, but some time ago I did have some lab scans done, just to get a reference point. For for now I’ve just take a recent XPan shot as a test.

NLP test

The top version is Silverfast’s Kodak Portra 400 NegaFix profile at default settings.  The lower is NLP at default settings. Again, colour negative conversion is a very subjective thing, but frankly, the NLP version to me looks like what Portra 400 is supposed to look like. The greens are more natural (although the Silverfast version may just possibly be more accurate, the grass was very green), and the NLP sky is complete free of the cyan tinge given by Silverfast, the shadows are better balanced. Game over, basically.

Of course, Silverfast provides a wide range of tools to tune profiles, to make colour adjustments way beyond what Lightroom alone can do, but all of this is destructive, sits within a clunky application framework, requires multiple steps and multiple file generations, and is generally slow.  NLP also has a wide range of adjustment tools, which are easier to understand and much faster to apply, making far more fun to experiment.

I’m sold on NLP. Silverfast will now be restricted, in most cases, to Raw scanning. Of course, by generating a Raw scan, in theory I can still process it through Siverfast HDR, but it gets very fussy if any other application has so much looked at one its DNG files.

There is only one drawback (and it could be major in some cases): NLP cannot remove dust and scratches using the infrared channel.  But on balance I guess I can live with that.

Posted in Film on Friday, October 16, 2020 at 07:31 PM • PermalinkComments ()

6000 sow’s ears

...and not a silk purse in sight

in Post-processing , Monday, October 05, 2020

I enjoy taking photos. Seeing the world through a viewfinder, and cutting out pieces of it to copy and keep gives me a sense of accomplishment. Maybe it even makes me happy (my default state being “miserable old git”).

The rest of it… I don’t know. The long, long process of trawling through memory card contents, discovering that expected gems are out of focus junk, and the possibly good stuff I can’t even remember taking, the endless work of turning a Raw file into an actual finished photo, the doubts about my aesthetic choices, about my software choices, about comparing my flaccid shots with others’ effortless contest-winning masterpieces, this is not so much fun.

I actually prefer editing and working up film photography - with film, especially slide film, it is what it is, the choices were made when the shutter was pressed, and I find scanning film to be somehow more of a tangible activity than importing a memory card.

This pressures me to try to reduce the amount of photos I take in the field, but in some situations, not taking the shot isn’t really an easy option. A case in point, and the point of this post, is my most recent trip to Antarctica. Ok, it was actually 2 weeks in-situ, which is a long time, and the conditions were largely pretty good. The opportunities were endless, and to my horror I came back with about 6300 shots. Ouch.

If I have any wish to share anything of this harvest, even if it just to post a few galleries here, clearly I need to narrow things down. Quite a lot. This already presents a problem, because often the real quality of a photo cannot be told from a quick look at the default representation of the Raw file in Lightroom (in the old days, I could use Aperture’s much more elegant handling of Raw-JPEG pairs for a first pass - Lightroom doesn’t provide any help there).  But anyway, I managed select 1376 potential candidates without doing any kind of adjustment.  I then settled into the long process of examining and adjusting each and every one of these, finally, after months, ending up with 573 second round candidates.

From these I should now make a final selection, and start to do productive things like post subsets online. I might even make a book.  But for now I am so sick of ice and penguins…

Drm 20200128 P1286011

Me, after dredging through over 6000 self-indulgent snaps

There’s got to be a better way.

Posted in Post-processing on Monday, October 05, 2020 at 04:20 PM • PermalinkComments ()

Why I still miss Aperture

whine, fanboy, whine

in Apple Aperture , Friday, April 17, 2020

It seems weird to be writing about Apple Aperture in 2020, some 5 years since its nominal demise. It does still work on MacOS Mojave, although it seems to make the OS crash if it is left running for too long (several days). I still lament its passing, while acknowledging that the stable door has been open so long that this particular horse has not only bolted into the next hemisphere but has been rendered down for glue.

But there is one feature of Aperture which I still use, and which I’ve never seen before our since its murder by Time “Bean Counter” Cook, and that is the Light Table.

I realise that for the vast majority of camera owners, Light Table is at best puzzling, but more generally a target of scorn. It has little to do with demonstrating that cats photographed with THEIR Superpixelmuncher X100X ProX are better than those of the next DPReview forum rodent.  That’s because it is a feature for photographers, not camera owners. And it’s brilliant.

A Light Table can be added to a Project, and can be used to arrange, lay out and edit (in the true sense of the word) a set of photos contained in that project. And I’ll say it again, it’s brilliant. Under peer pressure to do something useful with my COVID-19 confinement, I’m embarking on a couple of long, long overdue publication projects. One of these is to create a book. The big challenges in book creation are the selection and ordering of photos in a way which is coherent and conducive to the aims of the project.  The other is layout. Aperture’s Light Table can pretty much solve the first, and can help to get started with the second.

IMG 6463

The view above shows Aperture displaying a Light Table, with the pool of photos shown below in a browser strip (when added to the Light Table they gain a red counter icon). On the right I have an iPad acting as a second screen - this shows the photo selected, either on the Light Table, or in the browser strip.  So, simultaneously I have a freeform selection and layout, a means to browse and select photos out of my initial edit, and a full screen view so I can check sharpness or whatever.  When I place or move photos on the Light Table, automatic alignment and placing guides appear, like in InDesign or something. I know of no other application which can do this. Whichever unsung hero came up with this concept, (s)he deserves a mega award.

And it doesn’t end there. You might say that the Light Table seems a little constrained. No problem, drag a photo or photos off of the area in any direction, and the light Table expands to accommodate them.  There may be a limit, but I’ve never encountered it. Of course, you can also have any number of Light Tables you want under a Project, so you could even dedicate one to each spread.  Then again, Aperture also had a superb Book tool, so really you’d just progress from a rough mockup using Light Table to Book.

And there’s more: using the sort-of gadgety (only it isn’t) Loupe, you can examine any part of any photo, at your chosen magnification, in-situ.  And, thanks to Aperture’s unparalleled integration, using the HUD panels, you can pretty much do anything to any photo, also in situ, be it add keywords, check metadata, or even fully edit (in the Photoshop sense) the photo (of course all this worked in Books too).

ApertureLoupe

The much-maligned but actually very slick Loupe

ApertureHUD

The Light Table with adjustment tools HUD

Ok, it took a few versions for Aperture to fully deliver on its lofty ambitions, but once its got there (let’s say v2.5) it was humming.  Everything fit together like a well engineered Swiss watch. Unfortunately, the Apple dumbing-down disease struck a glancing blow to v3, but it was only superficial.

So given all this, why did it ultimately fail? Well, setting aside the fact that such an application just did not fit into Apple’s consumer disposables vision, and indeed probably only ever got approval because of Steve Job’s antipathy towards Adobe, it did suffer in detailed comparison in some areas to the far less ambitious Adobe Lightroom. For example, the pixel peepers and forum rodents could point at minute and adjustable differences in initial rendering - usually of noise at 1’986’543’200 ISO, or sharpness of Your Cat’s whisker at 500% magnification. Also Apple was pretty sluggish at keeping up to date with new camera releases, which Adobe correctly saw as an absolute priority.

What sunk Aperture was essentially Apple corporate culture.  It was overcome by a brilliantly conceived and ruthlessly executed social marketing campaign by Adobe, playing on all of Apple’s corporate weaknesses (obsession with secrecy, no interaction with customers, etc).  Aperture was different to Lightroom, and in many ways.  But Adobe managed to ensure that the competition was judged by one facet only, the pixel-peeping level characteristics of its image adjustment toolset. And actually even here Aperture had some unique and very powerful features (the implementation of the curve tool, for example), but nothing was going to save it against the massed ranks of photo-influencers like Jeff Schewe, Scott Kelby, Michael Reichmann and legions of others.  Apple just could not bring themselves to put the spotlight on others. Or, of course, horror of horrors, release a Windows version. No, people had to buy Macs to use Aperture.

Had Aperture been developed by an independent company, free of the clutches of Jobs, Cook, et al, I’m pretty confident it would have flourished. It was aimed at a market segment which is still not served today - it’s a pity the marketers never realised that.

I’m still happily using the Light Table, and it integrates pretty well with a Lightroom-centered workflow. But I’m on the last version of MacOS where this is possible.

Posted in Apple Aperture on Friday, April 17, 2020 at 05:00 PM • PermalinkComments ()

(I don’t need no) education ?

or maybe I do

in Post-processing , Wednesday, September 14, 2016
I've been quite prolific this year in photo-education consumerism. I've been fortunate to be able to participate in workshops with, and receive direct advice from, in Ragnar Axelsson (in Hamburg), Daniel Bergmann and David Ward (in Iceland), and Rafael Rojas (in Switzerland). All four are exceptional photographers, and really nice people, and all four have taken the time to give me feedback.

They've also shared with me techniques for post-processing files from camera in order to turn them into something meaningful. This part I find the most interesting, because it's an area in which if I'm honest I'm totally adrift. A lot of this education just goes straight into one ear and out of the other, but enough sticks around for me to get a feeling that some of it is totally contradictory. Two acclaimed, successful landscape photographers express pretty much exactly the same objectives, but give pretty much diametrically opposed ways to reach them. I'm not talking about "there's a million ways to do the same thing in Photoshop", but rather something like one person advocating increasing detail, and the other decreasing it, to achieve the same look. Which rather makes my brain explode.

drm_E-P5_20160416_P4164216.jpg

Hamburg. Probably should be in monochrome and cropped a bit



I'm not sure if it's a result of this, or some basic lack of vision, or something else, but quite often when I'm reviewing recently imported images in Lightroom, if I'm honest I can't actually see anything I should change. They look fine to me. One of the above-mentioned experts may well take a photo of mine and apply layer upon layer of intricate changes, which, probably, improve the photo, and certainly make it look different. But then when I'm back home, sitting in front of the same photo, I don't even have a clue where to start. Should I take the David Ward approach, or the Rafael Rojas path ? Should I first consider framing, and cropping, as both Ragnar and Daniel appear to do? Should I immediately consider monochrome, like Rafael and Ragnar would propose, or should I flip it upside down to check the balance in the composition, as David does ?

Or should I just sit there staring at it for a bit, and then wander off to the web in search of new software or cameras to buy ?

drm__20160722_DP0Q0428.jpg

Iceland. Um. Looks better upside down. And, er, the white balance ?



After (large number) of years and (much larger number) of money spent, I should have a better idea, but I haven't. I had been drifting towards a sort of aesthetic borrowed from the film using, portrait/travelogue loose community, larger revolving around the look of Kodak Porta 400, and applying that to my vaguely defined landscape/architecture/travel genre. And before that, I had gradually evolved a process of enhancing images by manipulating texture using progressive, graduated micro-contrast ("clarity", or "detail"), which was quite natural to do in Apple Aperture (less so in Lightroom). But then, I've learned, recently, that touching the Clarity slider, at least to push in a positive direction, is A Bad Idea, and Contrast is my friend. Except that I learned 2 months ago that a giving Clarity a hefty upwards shove in sky areas can be very rewarding, and keep your hands off Contrast.

Of course, I probably got most of that wrong anyway.

drm_E-M1_20160903_P9033209.jpg

Well, I could spend hours on this if only I knew where to start!



So now what ? I basically haven't got a clue. Then again, I'm no worse off than when I started, and it was all quite good fun. Perhaps the style and methods I'd evolved myself were not so bad. Certainly, any four of the above could take any one of my images, and enhance it, arguably make it better. But then it would be theirs, not mine. It's a comforting though to fall back on, except of course when I'm back sitting in front oaf a recently shot photo, and I still have no idea what to do with it.
Posted in Post-processing on Wednesday, September 14, 2016 at 03:14 PM • PermalinkComments (2)