NOTE: Images with an icon next to them have been artificially shrunk to better fit your screen; click the icon to restore them, in place, to their regular size.

A bit more than a year and a half after releasing Lightroom 3, Adobe today has released (the first?) public beta for Lightroom 4.

Lightroom 4 has lots of new big-ticket goodies, including a book module, map module (with geoencoding!), soft proofing, more video support, and a new render engine that takes the dramatic improvements in raw image conversion seen in the Lr2→Lr3 to the next leap. There are also many small improvements sprinkled about.

Adobe's Lightroom-Journal announcement gives some details, but for a comprehensive list of changes, see Victoria Bampton's always-excellent “What's New” post. For tutorials, walkthroughs, and other coverage, see this long list of links maintained by Sean McCormack

Important note: the Lr4 public beta is a “beta” in the true sense: take care to have a backup of any images you apply it to, and don't expect that any work you do with it will carry forward to the real Lr4 when it comes out. Use it to play around with and as a basis to provide feedback (at Adobe's Lr4 beta forums), but it's not intended to be used (or ready to be used) in a production environment.

Lr4 and Plugins

Modern versions of my plugins should work just fine in the Lr4 public beta.

Unlike the last major upgrade (Lr2→Lr3), there's not much new (yet?) for a plugin developer like me. There was a ton of new stuff in Lr3 to occupy my time (most of it came in Lr3's second public beta), and the stress of it eventually overwhelmed me, but in the end it caused me to make beneficial changes to my habits. I'm still developing every day, but with more balance. That, combined with a recent willingness to walk instead of take the car and I'm in pretty good shape, at my lowest weight in a decade (88kg · 195lb · on my 6'4" frame), but you don't want to hear about that, you want to hear about Lightroom...

Lr4 and Geoencoding

The only Lr4-specific change in my plugins so far is in my Geoencoding-support plugin: the silly kludge of “shadow data” that I had to come up with in Lr1 is now gone because Lightroom's plugin infrastructure finally allows me to update the “real” location data.

The Lr4 public beta does not allow you to upgrade an old catalog to Lr4, so there's not yet a need to migrate old shadow data to real data, but I'll build something to handle that before Lr4 proper is out.

I'm absolutely thrilled that Lr4's new Map Module allows geoencoding, in a variety of ways no less (drop-n-drag on a map!), but I'm not partial to how GPS-unit tracklogs are handled, so I'll probably continue to use my plugin to geoencode with them. My plugin also includes a bunch of other geoencoding-related support functions (enhanced reverse geocoding, view locations in KML, etc.) so I expect the plugin to become even more popular: the ease of the Map Module will bring more Lr users to the geoencoding fold.

Lr4 and Plugin Registration

My plugins are free for everyone to use forever, without payment to me or anyone else. However, I do encourage optional registration, which generally costs 1 cent in a PayPal fee. (If you choose to register and choose to include more than PayPal's minimum as a gift to me, PayPal will take its larger cut in fees, and if there's anything left over for me, you have my gratitude.)

However, none of this has anything to do with the Lr4 public beta, since registration is disabled in the public beta. But it does bring up a point that will matter when Lr4.0 proper is released: the plugin registration system that I came up with ties a registration to a Lightroom serial number, but since a major-version upgrade of Lightroom involves a new Lightroom serial number for Adobe, such an upgrade renders all my plugin registrations invalid. That means that folks who want to register my plugins must re-register them after an upgrade.

The hassle factor makes this really unfortunate, but in the end I hope it's not too burdensome, with registrations being optional and 1-cent and all. I'm sure I'll get flooded with messages by folks not understanding what went wrong with their plugin registration, or those who do understand it but don't like it. Let me offer my apologies up front.

Continued here...

NOTE: Images with an icon next to them have been artificially shrunk to better fit your screen; click the icon to restore them, in place, to their regular size.

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/500 sec, f/2.5, ISO 6400 — map & image data — nearby photos
Chopping Block
at Pierre Nadeau's Japanese Sword Smithy in Wakayama, Japan

Desktop-Background Versions
1280×800  ·  1680×1050  ·  1920×1200  ·  2560×1600

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/40 sec, f/5.6, ISO 6400 — map & image data — nearby photos
Charcoal
in all its full-color glory

Desktop-Background Versions
1280×800  ·  1680×1050  ·  1920×1200  ·  2560×1600

This year has gotten off slowly for me, having woken up January 1st with a cold and all, but with “Inspired Artistic Temple Shot” and its followup, “Simple Temple Sliding Wall”, I seem to have a black-and-white theme going, so I'll continue that today with a post about charcoal, from last year's visit to Japanese swordsmith Pierre Nadaeu (the swords are Japanese; Pierre is Canadian).

All the photos on today's post are shown in full color, but the subject matter's lack of chromatic variety makes them feel more monochrome than not.

A swordsmith can use various things to heat the forge — such as gas, coke, and coal — but the most predictable (and hence “best”) results are when using charcoal. Charcoal is much safer than coal (breathing its dust doesn't cause cancer, for example), but it's a lot of work to prepare, so when I gave it a try, Pierre opted to have me use coke (a product of burning coal) rather than deplete his stock of carefully-prepared charcoal.

Visiting his smithy, you couldn't imagine that there could be a place even more dirty, but he prepares the charcoal in an attached shed that vies for that honor.

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/320 sec, f/2.5, ISO 6400 — map & image data — nearby photos
Fruits of One's Labors
big pile of black messiness

Vertical Desktop-Background Versions
1050×1680  ·  1200×1920  ·  1600×2560

On his blog he has a whole post about the preparation of charcoal, at first citing the phrase “sumi-kiri san'nen” which means “cutting charcoal, three years”, apparently implying that it takes three years of experience to get good at it. Pierre, in his characteristic self deprecation says that he's still really bad at it after five years of practice.

You can see the various stages of preparation in a video at the end of his post, replete with impressive clouds of billowing charcoal dust towards the end.

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/320 sec, f/2.5, ISO 6400 — map & image data — nearby photos
Love, Friend, Cute Teddy Bears
Pierre Nadeau summarized in a stool cushion

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/400 sec, f/2.5, ISO 5600 — map & image data — nearby photos
Raw Materials

Nikon D700 + Nikkor 300mm f/2 — ¹/1250 sec, f/2, ISO 6400 — map & image data — nearby photos
View from Outside
handheld, with my Nikkor 300mm f/2 on my second outing with it

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/400 sec, f/2.5, ISO 6400 — map & image data — nearby photos
More Charcoal Detail

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/200 sec, f/2.5, ISO 6400 — map & image data — nearby photos
Further Back in the Shed
Charcoal, Straw, Sifting Pans

The charcoal and sifting pans are seen in Pierre's video, but he has a different blog post about the straw, which is used to make small whisk brooms that he uses while forging swords. The photo above is a mild transition from the black-n-white vibe, so let me continue adding color in showing the straw in use, as a bundled whisk broom just behind his hand in this photo:

Nikon D700 + Nikkor 24-70mm f/2.8 @ 40mm — ¹/40 sec, f/2.8, ISO 6400 — map & image data — nearby photos

He uses it to clean carbon(?) buildup from the steel, as seen in this photo from my original post about him:

Nikon D700 + Nikkor 24-70mm f/2.8 @ 42mm — ¹/80 sec, f/2.8, ISO 6400 — map & image data — nearby photos

After so much color at the end of last year (such as last year's final post or any of the bazillion fall-foliage posts like this), it was perhaps nice to have a few B&W posts, but I think I'm ready to get back to color again...

NOTE: Images with an icon next to them have been artificially shrunk to better fit your screen; click the icon to restore them, in place, to their regular size.

Now that Nikon has announced its next flagship pro SLR, the Nikon D4, with much flowery prose but few hard details, discussion and debate and speculation and flames and praise have filled camera circles.

This post is long, but here's the two-sentence summary for the “tl;dr” crowd:

As with most any technology release (hardware or software), folks tend to frame their personal whims and desires as “absolutely required!”, while features that they don't personally care about become unneeded fluff. Photographers who don't care about video, for example, lament the assumed cost of all the new video features.

This is human nature, and in this respect I am human (why on earth doesn't Lightroom have geoencoding built in!?), but my moral outrage at the omission of personally-desired features is tempered by many years of experience with product design, and a long-learned understanding that in practice things are much more complex than they might seem from the outside.

A feature not included in the D4 is built-in geoencoding, an omission that some people find unfathomable, as evidenced by a thread at DPReview started with this message:

This rant is clearly emotional, by someone who doesn't realize that it's emotional, nor that others may not share their particular emotions on this issue, so it's easy to dismiss. However, it started a long thread — one of many, I'm sure — where people debated the usefulness of having a GPS receiver in camera, and the business decision of having omitted it.

Of course, the responses included equally emotional rants on the other side of the aisle, such as this gem from Curtis Smith:

Personally, I've been geoencoding my photos for the better part of a decade (the ones I've posted, mostly in Kyoto, are mapped here) and would love to have it built into the camera.... but only if done well. I understand enough to know that it's not necessarily easy to do well, so I followed up the initial message with one of my own about some of the likely costs that came to mind — costs such as the physical space the GPS unit would add to an already bulky camera body, and how it would lower the value/cost benefit ratio (that is, the marktability) for those not interested in geoencoding their photos.

Each specific “cost” has its own level of impact, but the manufacture must weigh them as a whole against their benefits, and at this point in Nikon's product roadmap (at this point in the economy, at this point in their market research, perhaps in light of Mother Nature's harshness in 2011), built-in geoencoding didn't make the cut. Maybe it will when they reevaluated everything for the next camera. Or maybe not.

Anyway, as is common on faceless online discussions, some folks mix in a healthy dose of ignorance and antagonism with their emotion, such as this bit of arm-chair logic from Robin Casady replying to a “there are costs” post similar to my own:

Here, Robin is referring to a small add-on product that Nikon sells that includes a GPS antenna; when you plugin it in to the camera and it has any kind of satellite fix, photos are geoencoded automatically. This has been available for years, and if I were to use it with my current camera, it would replace what I actually do (which is carry a separate GPS receiver while out with the camera, then sync its tracklog to the photos in Lightroom, with my geoencoding-support plugin).

I don't choose to use Nikon's add-on because I feel it's an ugly wart on the camera, I worry about its speed and accuracy, and it lacks the ability to display its status beyond more detail than a blinking light. And even if I did use it, I'd still need a way to geoencode after the fact, for locations where I didn't have it with me, to geoencode the photos I get from others on the same outing with me, for locations it couldn't get a good signal, and for times where a depleting battery prompted me to turn it off.

Anyway, at first blush Robin's logic may seem reasonable... Nikon already has the hardware as a separate product, and the cameras have had for years the firmware needed to geoencode the photos, so the simple step to include the hardware inside the camera takes almost no work, so citing “engineering costs” seems unreasonable, Robin concludes.

But that's an exceptionally naïve, ignorant point of view, even when limiting the scope of “engineering costs” to the “software aspect” that Robin brings up. (Update: In light up the updates noted below, “exceptionally naïve, ignorant point of view” is a perhaps harsher characterization than Robin's statement merits. See more below...)

For example...

• If you move it from an external dongle to an internal component, you've lost all UI (“user interface”), so now you've got to come up with a way to interact with the user. You have to come up with a way for the user to turn the GPS feature on and off, and you have to come up with a way to indicate to the user whether the unit is on or off.

• Let's look at just that latter point for a moment, the oh-so-simple “indicate to the user whether the unit is on or off”. That might naturally go into the viewfinder display, but since that very-limited real estate has been staked out by other UI needs for years, you're forced to change or remove things that until now were considered critical. Maybe just make everything else slightly smaller to squeeze in one more indicator, but geez, that was done the last several iterations and now things are starting to get way too small....

  So that's not straightforward, and the same angst applies to the LCD displays.

  Update: In a touche!-worthy reply, Robin points out that there's already a GPS-related indicator in both the viewfinder and LCD-body displays, which flashes to indicate that it's on but has no position fix, and is solid if it has any kind of fix. This clearly makes this bullet point of mine completely moot and I have learned something, but I don't think removing one or two points removes the idea that there's a cost/benefit balance that most of us don't fully understand.

• Then you're faced with the fact that “on” and “off” are not really sufficient... you need to be able to communicate to the user whether the unit is actually getting a signal, and if so, how accurate. If I recall correctly, the hardware dongle uses a bi-color LED to indicate the difference between “on with good signal” or “on but no good signal”, and this is really very minimal because “good signal” means different things to different people (100m accuracy vs. 3m accuracy, for example). Also, “Not good signal” may really mean “warming up” or “can't see satellites”. So if you're going to bring it in house, you'll naturally want to tackle that issue to provide the user with a more-usable level of information, but maybe all of that doesn't need to go into the viewfinder, so now you've bifurcated the information (some in the viewfinder, and some somewhere else... likely in the menu system), so finding the balance there is another issue.

• Then you've got to consider the situation of when the battery is getting low... it makes no sense to run the battery into the ground just so the GPS receiver can keep its fix while the camera is idle.... what good is it to have had a good fix for the last hour if you now don't have enough battery to take a shot? So you've got to come up with some measures to handle this situation (perhaps GPS auto shutoff when battery is below X% full), and this means that you have to have a whole new UI to communicate to the user when this has happened, what the current status is, and perhaps to allow the user to make adjustments to the heuristics for their specific needs.

  Update: In the same reply noted above, Robin cites that there is already an option just as I postulated, that turns off the GPS receiver when the exposure meter turns off, some user-selected time (default: six seconds) after the shutter button is released. I offered the idea merely as an example of something that might be done, but I'm quite dismayed to find it's actually there in that form because one would generally want the GPS receiver to be active a lot longer than the exposure meter; the exposure meter comes back on instantly when you press the shutter button half way, but Nikon's GPS receiver takes a minimum of five seconds to get a fix when already hot, but is rated at 45 seconds when warm (unused for more than 15 minutes, I think). I'd like to the GPS unit remain on much longer than the exposure meter, and would like the ability to have it wake up every 14 minutes or so to keep itself “hot”...

• But we've forgotten the more common situation of power management... should the unit be on all the time, or should it auto-shutoff in the same way the image review shuts off, coming back up when the shutter button is half depressed? (I'm half depressed just thinking about this.) Both make a lot of sense, each applied to its own situation, but no one solution makes sense for everyone, so again you need to add UI to allow the user to indicate their wishes, and more UI to communicate to the user this additional status of the settings chosen and the current state within the context of those settings.

Notice how the “simple software aspect” immediately turned into a hardware aspect: both the viewfinder display and the LCD display require physical hardware manufacturing changes to update. There are other hardware aspects one could turn to (such as the LED seen in the external GPS unit), or one could keep it all software by burying everything into the menu system, but these are substantially less desirable.

Update: So, with my first viewfinder/LCD point having been completely wrong, the previous paragraph is pretty clearly unreasonable. You do still need to handle on/off for the GPS unit, but in my experience as a geoencoder I think it'd be sufficient to have it in the menu system.

All features have costs. The ones above are just what came to my imagination at first blush, but because I have no experience with embedding GPS receivers inside cameras, I'm sure there's a whole litany of additional problems I've neglected to consider.

Update: And it's because of this ignorance that we all have (at least those of us who are not camera-design engineers) that I characterized Robin's curt conclusion of “Bogus!” as I did. In light of my own ignorance on the viewfinder/LCD issue when I wrote it, my use of “exceptionally” seems overdramatic. Sorry about that, Robin.

Then there are the followup costs, such as the need to document all this in the user's manual, and translate that to all the languages that Nikon supports. (Of course, they'll have had to translate all the related UI in the camera menus.) Then there's the recurring need to provide support: more features mean more support calls, etc.

None of this is unsurmountable, and it's all certainly trivial compared to all the video features that did get added, so it wouldn't have surprised me in the least to have seen Nikon include this in the D4. But to do that they would have had to shift resources from something else, and if they had done that, we'd see these same online flamefests about whatever that “something else” was that got the short stick.

We'd also see additional flamefests about whatever GPS support did get built in and how lame it is...

This applies to pretty much every new hardware and software product you'll come across (I see it every time Adobe releases a new version of Lightroom, or Apple releases a new phone), so the next time something near and dear to your heart is released, realize that like everyone else you're talking to, you don't know it all, and take care to frame your wishes and opinions as just that, wishes and opinions.

(And as a matter of courtesy, don't point out my own advice to me when I don't follow it. :-))

By the way, several years ago I read an excellent writeup from a software developer about the extensive ripple of high-impact ramifications that he came across while trying to implement a “trivial” feature request from his users. I think it was about some kind of email-notification aspect of an online forum of some sort. My web-search kung-fu is weak on this one.... does anyone have a link for this article?

NOTE: Images with an icon next to them have been artificially shrunk to better fit your screen; click the icon to restore them, in place, to their regular size.

Nikon announced their new flagship SLR, the Nikon D4, to much anticipation made long unfulfilled by last year's tragedies (Japan earthquake, Thailand flooding). I would, of course, love one, but with a price in Japan close to US$8,000 and Santa not scheduled for another 11.5 months, it looks doubtful.

Anyway, I'm in the process of reading the D4 press release and am left in wonder by the ultra thick spread of marketing fluff that I don't recall in earlier Nikon releases. For example, talking about the low-light ability, they say:

which is just fine — the use of phrases like “sovereign” is strong when used in limited doses — but then they continue with:

“Excel in any situation”... what does that even mean? The entire sentence could have been replaced with “Pixel size is 7.3µ.” and it would have retained exactly the same information, while shedding the smarmy, fake feeling that makes me want to shower before moving on to the next paragraph.

I'd really love to chat with the person who wrote/approved this, to find out what beneficial effect they actually envision this kind of prose has on what kind of people? To me it's the textual equivalent of Tammy Fay Baker makeup.... I just don't see this kind of writing as anything other than a total failure in every respect. I'm not even half way through the press release, but already this kind of crap has been laid on so thick in paragraph after paragraph that my desire to vent about it actually eclipses my desire to know more about the camera (and hence I'm here writing this post instead of reading further). Bravo, Nikon Marketing, bravo... that's an amazing feat.

I'm excited to go on to find out more about the camera, but all I can do is hope that camera was designed by brighter minds than Nikon has in their marketing department.

NOTE: Images with an icon next to them have been artificially shrunk to better fit your screen; click the icon to restore them, in place, to their regular size.

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/400 sec, f/5.6, ISO 6400 — map & image data — nearby photos
Sliding Walls
minor outlying building of the Jingoji Temple (神護寺), Kyoto Japan

Vertical Desktop-Background Versions
1050×1680  ·  1200×1920  ·  1600×2560

I've been taking it easy this year because I'm still recovering from the cold I woke up with on 1/1, but after posting Paul Barr's inspired creation yesterday, I thought I'd look into my own photo archive to see what I was doing when he took that photo. I was standing next to Paul, but aiming my camera at a the sliding walls of a nearby building, with the thought that it might make a nice desktop background.

One thing I like about it is that even though it's full of detail, it's not necessarily clear right away what you're looking at, so you really need to engage with the photo to understand the setting. The bit of confusion followed by an understanding is somehow interesting to me.

Nikon D700 + Voigtländer 125mm f/2.5 — ¹/400 sec, f/2.5, ISO 1250 — map & image data — nearby photos
Wider View

This is the same temple complex we were heading to in last month's colorful “On The Path To Kyoto's Jingoji Temple”, but this particular scene is decidingly bland, which is why I went with a slightly edgy B&W version to open this post, and is perhaps also why Paul went with the pencil-drawing look seen yesterday.

For reference, here's the bland out-of-the-camera version of this post's lead photo: