Category Archives: Software

DxO ViewPoint

A handy plug-in.

DxO is a Photoshop or Lightroom plugin whose purpose is twofold. Correcting keystoning from leaning verticals or slanting horizontals and removing volume anamorphosis, the elongation of objects near frame’s edge when very wide angle lenses are used. I have traditionally used PS CS5 to correct keystoning and believe that PS CS6 adds volume anamorphosis correction, but as DxO is running a $39 special offer – half off – through December 31, 2012, I purchased the Mac version on the recommendation of a friend.

DxO’s poky servers went down half way through my first download attempt but the second was successful. It’s a whopper at some 187MB, larger than Lightroom itself. You have the option of installing it as a PS and/or LR plugin in addition to the mandatory stand-alone version which is installed in the Applications folder.

The LR version integrates seamlessly, requiring the user to hit Photo->Edit in->DxO Viewpoint when in the Library or Develop module whereupon LR generates a lossless TIFF file which pops up in DxO ViewPoint. You have a choice of 32-bit or 64-bit versions. I went into Finder and erased the 32-bit one as it’s a distraction. If you can use 64-bit, why not?

The controls are intuitive. In the image below from the San Francisco Palace of Fine Arts, there is keystoning in two planes – vertical, obviously, and horizontal as I was not plane to the subject.

There are three keystoning icons in addition to traditional sliders. Icons are the way to go. First you dial in your preferred aspect ratio – 3:2 like the original in this case – then click on the double keystoning icon and align the guidelines with the two verticals and two horizootals that have to be straightened:


Guidelines aligned along two verticals and two horizontals.

Click Accept then File-Save and the corrected version is saved, stacked, along your original in LR:


Corrected version.

Here’s the result after using the Transform->Distort command in PS CS5 for comparison:


Corrected in Photoshop CS5.

Note the excessive elongation of the plinth compared with the DxO ViewPoint corrected version. I have left in a hint of keystoning in both versions to preserve the suggestion of great mass and height.

Either version is better than the rudimentary correction in Lightroom, which tends to remove far too much of the original.

I don’t know that I would pay $79 for this plugin but $39 seems fair. As I do a fair amount of architectural photogrtaphy, it fills a niche in the toolbox. Whenever taking pictures where keystoning is unavoidable, I make sure to include lots of space around the main subject, knowing that much of it will be lost in processing.

Original on the D700, 35-70mm f/2.8 AFD Nikkor.

Nikon voice memos

Smooth Lightroom integration.

One really handy feature in the Nikon D2/D3/D4 bodies is the ability to record a voice memo of up to sixty seconds in length for each image. After enabling the function in Settings, you hold the voice memo button down while speaking into the microphone on the rear of the body. If you are taking posed snaps of strangers and want to send them a copy as a courtesy, this is a great way of recording their email address for later retrieval.

At first I thought this to be a worthless gimmick but in practice am finding it to be a really useful feature on my D2x.


Recording button red circle; speaker and microphone – yellow and green arrows.

You can playback the voice memo using the camera’s small speaker to check it’s intelligible at the time of recording.It sounds far better over your computer’s speakers!

When it comes to processing, Lightroom fully accommodates this function. The WAV file recording has the same frame number as the image but with a ‘.wav’ file extension and is imported along with the image into LR 2, 3 and 4.

You can see the sound file in the Library module of Lightroom and you can play it back by clicking the arrowed icon:


LR’s Develop module and the playback icon.

A like feature is also available on some Canon DSLR bodies.

File sizes? A 10 second recording averages 75MB – not enough to worry about when it comes to consuming precious space on your camera’s CF or SD card. The D2 and D4 use one CF card, the D3 one or two CF cards.

Software of the Year

No contest.

By a country mile, Adobe’s Lightroom is my choice as Software of the Year.

While Lightroom has been around for quite a while, it has continually moved to strength and has never become a resource hog. It runs very fast on a capable machine, be it Mac or PC, yet will perform at quite usable speed on something more modest like my 2012 MacBook Air. Photoshop deserves like praise for speed; I’m still on CS5.

For cross-platform users, the LR catalog will load just fine in Windows and in OS X, and Adobe’s realistic licensing permits use on two machines. While it was hard to imagine any great improvements to LR3, LR4 surprised mightily with it’s greatly enhanced Highlights, Shadows, Clarity and Vibrance technologies, all materially improved from version 3. Used creatively, the first two begin to approximate the power of HDR with none of the complexity or garish results. Add a touch of noise suppression from the built-in controls and you have pretty much all you could wish for in day-to-day processing. With an outstanding database with easy keywording and filtered image retrieval, you are looking at a very powerful tool indeed. Aftermarket apps to load images to Shutterfly or to offer specialized processing needs are easily added. I find I rarely leave the confines of Lightroom for my processing needs, with round trips to Photoshop generally being restricted to perspective correction (PS’s tools are more powerful than LR’s) and, of course, to selectively blur backgrounds with the excellent Magic Lasso tool and Filter->Blur->Lens Blur. It would be great if Adobe was to add these functions in LR, but I suspect cannibalization of their PS cash cow is a key concern.


This merely scratches the surface of the metadata capabilities of Lightroom.

The one other external processing tool I use occasionally is Snapseed, which now accepts TIFF files generated from RAW originals, meaning no loss of quality. I use LR4 with two displays and it is beautifully engineered for this purpose.

Having chipped my many old MF Nikkors, I especially like how LR reads the EXIF data and automatically invokes the appropriate lens correction profile from the many I have created. It just takes one more bit of drudgery out of the processing step.

Best of all, LR is remarkably inexpensive for what you get, which includes Book, Map, Slideshow (really outstanding) and Print modules, all well integrated, for $115 at Amazon. The best book I have found is by Martin Evening who not only writes and illustrates his instructions well, but also takes great photographs. A $33 bargain which really should come with the software.

Update 12/17/2012:

This just hit my inbox. At $129 there are few better bargains in photographic software:

A fortnight with Mountain Lion

Robust and trouble free.

I published some early performance data for Mountain Lion on the Hackintosh a couple of weeks ago here, having earlier cautioned against early adoption owing to possible incompatibilities with older 32-bit applications.

Thus I determined to run Mountain Lion off back-up drives on three machines – the 2012 MacBook Air and my two Hackintoshes, HP100 and HP10. The latter pair use Gigabyte Z68X-UD2H-B3 motherboards, with Nvidia 9800GTX+ and GT430 twin monitor graphics cards, respectively. HP100 adds a third monitor via a DisplayLink USB dongle. The HP100 sports an i7 Sandy Bridge CPU, overclocked from 3.4GHZ to 4.4GHZ and the HP10 makes do with a modest i3 Sandy Bridge which cannot be overclocked, but serves just fine for streaming market data.

During the past two weeks I have used all three machines heavily at both my day job where I invest money and for processing my pictures using LR 4.1 and PS CS5.

It’s been pretty smooth sailing. All app vendors whom I favor have made sure their apps work with Mountain Lion with the natural exception of Xrite which prides itself on always being last, claiming they need to ‘test more’, even though Mountain Lion has gone through four Developer Previews in the six months before release. But that’s hardly news coming from a monopolist in the field of colorimeters – Huey, Eye1, Spyder – all Xrite, sadly. Still, while they screw around and generally act in their usual inept manner, you can be comforted with the knowledge that the Eye 1 display profiling app works perfectly fine with Mountain Lion, no thanks to Xrite, and likely unknown to them ….

As of today I am switching to Mountain Lion as the production OS on those three computers. It has proved bug free, robust and some of the enhancements are more than just eye candy. The addition of AirPlay, which permits anything on your screen to be routed to your TV to which an AppleTV is connected, is a tremendous value added and has all the TV companies searching for a change of underwear. Notifications and the ability to tailor these easily to your preference, are another great iOS feature which was overdue on the desktop. Safari is greatly improved, which probably says more about how dated it was with Lion, and installing Mountain Lion on a Hackintosh has never been easier. Overall speed may be a smidge slower than with the last version of Lion but it’s no big deal and my experience has shown that Apple generally speeds up a major OS as minor releases come along. CPU operating temperatures are unchanged from those seen in Lion.

I have had only one glitch and that was self-inflicted. The i7 Sandy Bridge overclocks easily up to 4.4GHz from 3.4GHz in stock form and when importing pictures and generating 1:1 previews in Lightroom on HP100, while simultaneously developing the early imports (hey, why wait?) I got a kernel panic. Turning down the CPU clock by some 2.5% to 4.3GHz solved the issue and while I could easily get to 4.5GHz or higher by messing with core voltages and a myriad of other variables in the BIOS, the return on effort and lower life span of the CPU mean I will not be going there. The machine is as fast as can be for my purposes.

So there are two messages from this experience:

  • Once you are satisfied that your favorite apps will work, it’s safe to upgrade
  • There has never been a better time to build a Hackintosh

Mountain Lion – don’t rush

Fools rush in ….

The recent history of OS X is as follows:

  • 10.5 Leopard – the last to run on G3/4/5 PPC machines as well as on Intel Macs. 32 bit.
  • 10.6 Snow Leopard – the last pre-‘dumb’ UI, 32 and 64 bit, Intel only, will run PPC apps using Rosetta
  • 10.7 Lion – the current OS with many iOS influences, such as touch gestures and the AppStore. Intel apps only, no PPC, no Rosetta. 32- and 64-bit.
  • 10.8 Mountain Lion – more dumbing down of the UI and 64 bit Intel only

On balance, I would have to say that OS X peaked with Snow Leopard. Robust, no nonsense, no frou frou. We are now in the land of chintz, bells and whistles. Faux chrome spokes will be next.

Before being a pioneer at the bleeding edge and upgrading your OS Lion Mac or Hack to OS Mountain Lion, due out any day now, stop and do this simple test first.

It’s the bold words above that should give you pause. If you recall losing the use of NikonScan or Quicken 2007 (both PPC apps requiring Rosetta in Snow Leopard) when you migrated to Lion, you run the same risk in migrating to Mountain Lion from Lion for all your non-64 bit apps. Indeed, as what follows shows, the risk is potentially far worse.

Apple continues to dumb down the UI of its desktop OS, making it more responsive to touch gestures, which sells more Magic TrackPads I suppose (Magic What? Gimme a break, Apple), while in reality the use of touch gestures with a desktop and traditional keyboard is simply poor design. It may work with a laptop but does not with a desktop, in my experience.

The quickest way to find out what will not run on Mountain Lion is to start up all the apps you use then go to Applications->Utilities->Activity Monitor and sort this screen by clicking on the ‘Kind’ column:

Activity Monitor sorted by 32- and 64-bit apps.

Anything that does not say ‘Intel (64 bit)’ in the ‘Kind’ column will not run with Mountain Lion until the application is updated by the maker. And, in my case, there are some real shockers here:

  • CrashPlan menu bar – cloud back-up. I have emailed the maker who replied “We plan to fully support Mountain Lion by the time it is publicly available.”
  • SteerMouse manager – confers enhanced functionality on my ancient Logitech mouse. I emailed the maker who responded: “ML supports 32 and 64 bit applications, but it does not support 32 bit kexts. SteerMouse consists of a 32 bit application and a 64 bit kext.” This means SteerMouse should work fine
  • LogMeIn – permits remote access and control of any computer. I have emailed the maker and they replied that LogMeIn will work fine with Mountain Lion
  • iPhoto – no problem – Apple has just updated to 10.6.3 which works with Mountain Lion
  • SMARTReporter – menu bar utility which provides early warning of imminent drive failure. I have emailed the maker who replied: “SMARTReporter works fine in 64 bit, and mostly fine under Mountain Lion. There is one issue related to Mountain Lion, the I/O error check doesn’t work there. i’ll provide an update for this in the next days and unless the Mac App Store delays things too long, the update should be released before Mountain Lion is publicly available.”
  • MacaroniTool – excellent UNIX utility which repairs permissions overnight with no attention. I have emailed the maker
  • growliChat helper – pops up a window when something important happens
  • i1ProfilerD2LionEditionTray – deal killer. App for running the i1Display2 colorimeter for profiling displays. I have emailed Xrite requesting an ETA. Don’t hold your breath on this one, as they just replied to me as follows: “We have not established final compatibility with Mountain Lion with any of our products. Apple reserves the right to change the OS up until the day of actual first customer shipment. Our software engineers are testing with pre-release copies of 10.8, but our final testing will only begin when the release version is available.” Meaning if you move to ML, be sure to profile your displays in Lion first as you will be waiting for the ML version for quite a while. Xrite did a similarly poor job of releasing the Lion version despite having 2 years notice that Apple was abandoning Rosetta and PPC CPUs. Bunch of amateurs who care little as they enjoy a monopoly in the colorimeter market – Huey, EyeOne, Spyder – yup, all Xrtite, unfortunately.
  • Dropbox – another deal killer. Replaces MobileMe for me and provides an easily accessed cloud storage space for frequently used files. There’s an experimental Mountain Lion version here of unknown stability
  • Bento – database app owned by Apple used for inventories
  • ccc_helper – used by CarbonCopyCloner – though I believe CCC is on top of 64 bit migration. Used for drive copying
  • Temperature Monitor – the maker has written in response to my question: “Yes, of course. There is no reason why Temperature Monitor should not work. The application also has 32 and 64 bit sensor drivers included to support monitoring of Intel’s “per core” temperature sensors.”

So several of these, once disabled, make my Macs and Hacks unusable. Mountain Lion will have to wait until apps are updated or alternatives become available. Running this simple check will warn you whether Mountain Lion is too early for prime time. I suspect that, for many photographers, the answer is a resounding ‘No thanks’ at this time. Better to stop and wait than to find you have just dropped the anchor through the keel of the boat and that you are out of lifejackets.

Some good news. PS CS5 and LR4 are fine – they have been 64-bit apps for quite a while. If you use three or more monitors with #3 and above powered from a USB2 port using a Newer Technology USB-DVI adapter (excellent) then I am glad to report that the maker has just updated the driver to 64-bit. I’m using the Moutain Lion version with Lion on my third display and it’s fine.

Will my Hackintosh or Mac run Mountain Lion?

You need to check if you are running in 64-bit mode. This is done in System profiler (‘About This Mac’) as follows:

If yours says ’32-bit’ you are SOL with Mountain Lion, arguably no bad thing. Mostly it’s the graphics card that is to blame. Good luck upgrading a Mac, but Hacks are easily upgraded to later cards. The Nvidia 9800GTX+ GPU I use is a 64-bit card. It is discontinued, outstanding and easily found used for $50 or less. Apple has published a list of Macs which will not run Mountain Lion and this is probably the issue. Just about any Mac over 3-4 years old will not run Mountain Lion. The list is somewhere on their site and I’m damned if I care to look for it. If you have to, your next desktop should be a Hackintosh.

Disclosure: Lomg January 2013 AAPL call options.