Photographs, Photographers and Photography

September 22, 2009

Lightroom wins

Filed under: Lightroom — Thomas Pindelski @ 11:22 am

Aperture is dead in the water.

Having started serious volume digital photo processing with Apple’s Aperture and finally made the switch to Lightroom almost two years ago, the following data recently released by Adobe hardly surprise me:

Clearly, I’m not the only one making the move, especially if you take into account the large increase in Mac sales in the past few quarters. Forget the upper table – Aperture does not run on Windows so it’s not a fair comparison. The lower table is.

When did you last hear of a meaningful update to Aperture or see any advertising for the product?

Those still using Aperture should be getting worried and would do well to consult my earlier piece on abandoning that major stress source for Mac performance. Aperture is another orphan application which couldn’t handle the heat in the kitchen. It’s future is …. well, what future? Have you noticed how Aperture does not even support Panasonic G1/GH1/GF1 RAW file import – maybe the most signifiant camera design to hot the market in the past year? That makes me think it’s a dying application, starved of capital as Apple concentrates on making …. cell phones.

It bears repeating – the user interface in Lightroom is not only logical and linear, it actually makes photo processing fun. That’s not something I thought I would ever write. And you don’t lose track of originals or accidentally erase them, either.

December 18, 2008

Lightroom 2 on an older Mac

Filed under: Lightroom — Thomas Pindelski @ 8:31 am

Useable.

I mentioned a while back that I would comment on how Lightroom 2 runs on an older Mac. I had tried LR 2.1 on my 6 years old iMac (IBM G4 1.25gHz CPU, 1 mB of RAM) and it was not useable for localized adjustments such as the adjustment brush. You would paint something on the screen and many seconds later the effect was visible. Not useable.

Well, Adobe released Lightroom 2.2 the other day so I loaded this up on both the MacBook (Intel C2D 2.1gHz, 4 gB RAM) and the iMac. First, on the modern machine the adjustment brush is now fully useable. Changes occur almost in real time – say a fraction of a second delay as you ‘paint’. In this comparison, the MacBook is running OS Leopard 10.5.5 whereas the iMac is on OS Tiger 10.4.11.

Moving over to the iMac things are quite encouraging.

For purposes of what follows I was using a RAW file from my Canon 5D, so both machines had to perform RAW decoding prior to display of the picture. A RAW file from the 5D is some 12 mB but once converted comes to some 60gB. Not small, in other words. As usual, I let LR generate full-sized previews on import – it takes longer but the payback when processing is immediate. Images pop on the screen far faster this way.


LR 2.2 on an old iMac

Loading LR takes 20 seconds (versus 7 on the MacBook) and the first switch from the Library to the Develop module takes a long 30-35 seconds (MB – 7 seconds). Thereafter, switching between the Library and Develop modules takes 3 seconds (MB – near instantaneous). But, most importantly, the greatest advance in LR2 compared with LR1, localized adjustments, is now quite useable in LR 2.2. I can ‘paint’ on the screen using the mouse and see the adjustment within a second or so – made even easier by using the mask-display routine outlined here.

This little test discloses just how much faster the Core 2 Duo architecture of the Intel chip is over the IBM G4, but also shows the fine job Adobe has done of keeping those older machines in service. If you cannot afford the latest Mac, $300 for a nice 15-17″ display on an older G4 iMac will serve you just fine and there are lots of these older machines around going for a song. While I sold my G5 iMac a while back when the MacBook came along, I would guess that the G5 CPU will be speedier than the G4, much as it was using Photoshop CS2 when I first got the G5. The G5 iMac routinely sells for $350 – $400. A spectacular bargain with clean looks and a nice big screen.

If JPGs are your thing, then a G4 or G5 Mac should just fly. And they sell for a lot less than a new Mac when the current bottom-of-the-line MacBook (mine!) sells for a very overpriced $900 and iMacs start at $1,200. That money saved gets you a another lens for your DSLR and a great computer for Lightroom 2.2.

December 14, 2008

Tethered photography with Lightroom 2

Filed under: Lightroom — Thomas Pindelski @ 9:05 am

A bit tricky.

The idea of tethered photography with a digital camera is that what you snap appears shortly thereafter in Lightroom on a screen size of your choice.

Practically, this translates into controlled conditions where the camera and a computer can remain close together, so think studio photography. No matter whether your subject is a flower or a person.

The opportunity of immediately seeing your pictures in Lightroom, with default import processing (camera profile, sharpness, etc.) applied, all viewed on a large, properly profiled screen will take you as close to visualizing the finished thing as you can get. Indeed, if computer display is your goal you will see what you are getting; those who print and have a properly profiled screen/printer will be just as happy.

In a perfect world you should be able to attach your camera to your computer, open Lightroom and bang away. In real life the process is two stage. First, you have to tell Canon’s software (ugh!) to deposit pictures in a named location. Second, you then tell LR2 the name of this folder which it will monitor, transferring any new content to a different folder seen by LR2. Thus the first folder is emptied by LR2 and the second is transferred by you, the user, within LR, with contents either moved to your LR catalog or bad snaps moved to Trash. So you start and finish with these two empty ‘transit’ folders but they must not be removed for everything to work. That’s for the neatniks amongst us!

What follows applies to Canon DSLRs but doubtless similar steps apply with others.

With most modern Canon DSLRs (5D, 40D, whatever) you will need current versions of Canon’s Digital Photo Professional (I am using DPP 3.5.1) and Canon’s EOS Utility (2.40). You tether your camera to a USB connection on your computer (laptops are ideal for this) and the camera end is connected with a miniature USB plug. As the one supplied with the camera is short, you can either buy a USB-A to USB-A extension cable, or simply get a longer USB-A to USB-Mini cable. Radio Shack or whatever. There’s no brand value here.

Plug in your camera, switch it on and fire up DPP, then click on Tools->Start EOS Utility. Go to EOS Utility->Preferences and check the box shown below:

This makes sure that what is transmitted to your laptop is also saved on the card in the camera. A useful safety precaution.

Now using Finder, create a unique folder you want monitored. I call mine ‘Canon EOS 5D Capture’ in my user directory.

Back in EOS Utility, go to the Destination drop-down box and enter that destination:

Before even getting into Lightroom 2, check this setup. Take a test picture and it should appear in a few seconds in DPP. With my 5D on a MacBook it pops up in DPP in 4 seconds – that’s for a RAW original.

Now Lightroom 2 has to be told where to look for the picture you have just taken.

Go to File->Auto Import and check ‘Enable Auto Import’ thus:

The click on ‘Auto Import Settings’ and enter the exact folder name under ‘Watched Folder:’ you just created in EOS Capture as shown:

Any typos here and nothing will work.

Back in Finder, create a new folder for the destination of your pictures as seen by LR. I have used the default name of ‘Auto Imported Photos’ which LR2 suggests, above.

Now take a test snap and the left panel of LR2 will show the following:

The new folder you designated appears in LR2. Click on it, hit F5, F6, F7, F8 and L and you will see this and all future pictures presented in their full glory, filling the screen. It takes 7 seconds from click to view with my 5D and modest MacBook (2.1 gHz C2D CPU, 4 gB RAM) with RAW originals. Doubtless JPG would be faster as less processing is involved, but JPG so compromises quality I do not bother with it.

If you like what you see, remember to drag-and-drop (move) the keepers to your permanent Lightroom catalog. Then, still in LR, delete the losers.

If you power down your camera or the battery fails or you disconnect the cord, you will need to go back into DPP and reload EOS Utility from the Tools menu. Other than that, it’s plain sailing. I’m using OS 10.5.5 Leopard and LR 2.1; earlier versions of Leopard seem to have had issues with the Canon software but now all is well. You can check Canon’s site for free upgrades to the latest DPP and EOS Utility software. (The older Capture application refuses to work with Leopard on my MacBook, so don’t bother with it if you are using like tools).

If you read that tethered photography was only fixed by Canon in the 5D Mark II, save yourself the upgrade money. My 5D Mark I works fine with this technique.

There’s no better way to preview studio snaps even if they involve moving subjects. You can check light and color balance from just a few test snaps. Very handy when you are using studio flash where its virtually impossible to ’see’ how your lighting has turned out on the camera’s miniscule LCD screen.

Once you have made the settings above, tethered photography involves the following simple steps:

  • Switch on camera
  • Connect to computer
  • Load Canon DPP and EOS Utility
  • Load Lightroom
  • Take a test snap
  • Navigate to the folder in LR and expand the test snap to full screen
  • Bang away

Your camera will use up its battery faster this way as it’s saving both a card image and transmitting a copy to your computer, so come prepared with spares!

Come to think of it, a battery powered netbook computer and a tethered camera would be more than useable in the field. An ideal combination, perhaps, for those who like to take their studio with portable strobes with them. Of course, you would have to convert the netbook to running OS X to use your time effectively ….

November 24, 2008

HP Designjet paper profiles in Lightroom 2

Filed under: Lightroom, Printing — Thomas Pindelski @ 8:44 am

Trust HP to design this for engineers, not humans

In yesterday’s column I mentioned the existence of aftermarket profiles for some interesting papers made by the likes of Hahnemühle and Arches. These are swellable papers designed to absorb the ink dyes used in the HP DJ 30/90/130 printers. That’s all well and good, but how on earth do you get these to show up as choices in Lightroom when you are in the Print module? Especially as the instructions from HP for the right place to install these simply do not work.

Well, HP is first and foremost an engineering company which means that things obvious to engineering graduates are gobbledeegook to regular humans. Mercifully, your instructor, Dr. Pindelski, happens to have an engineering degree, so if you use an HP Designjet 30, 90 or 130 printer, follow the instructions below and all will be well …. so long as you have the good sense to get a life and use a Mac. PC users can probably figure things out from what follows, but please do not ask as I neither use nor propose to ever use a PC again.

Here’s the Print module in LR2:

Click on ‘Managed by Printer’ then click ‘Other’ and you get a listing of the standard HP paper profiles:

Now go to Finder and click on the Library (this is the Mac’s library on the root of your internal hard drive, not the one under your name in Users) and navigate to the directory show – navigation is from bottom to top:

Your Finder screen now looks like this:

Now Control-Click on the file named ‘hp_designjet_pm.plugin’ then click on ‘Show Package Contents’:

Now drag and drop the downloaded package of profiles (see yesterday’s entry for the download link) onto the directory named ‘ICCProfiles’:

The ‘designjet’ directory is the one with the new profiles, which you just dragged and dropped.

Click on the ‘designjet’ directory in ‘ICCProfiles’ and you will see all the additional profiles, thus:

The remaining task is to edit the ICC profiles of your choice so that they will show up in the LR2 drop-down box. The snag is that you have to use one of the tailored HP name strings to force the choice to show. This means two things:

1 – You must use a file name identical to one of the existing ones used by HP for their papers
2 – You will have to embed your profile description of choice in the replacement new paper profile for it to display meaningfully in the LR2 drop-down box.

First, then, we have to determine which of HP’s standard paper choices we can dispense with. That’s easy, because you didn’t buy this fabulous printer to use Brochure or Proofing paper or for that matter generic Coated paper, so that means at least nine of HP’s file names can be reused. Further, if you stick with the ‘Max Detail’ drivers, you get even more redundant file names to use – and why would you want anything but maximum detail in your display prints?

First, determine the new papers for which you would like to install profiles – here’s the list from the file downloaded from HP:

I’m intrigued by the Arches, Hahnemuhle and Ilford papers. so in the following screen snap I have erased those imported profiles which are not wanted and also erased all the clutter from the inclusion of the HP Z2100/Z3100 profiles which are for HP’s latest – and very expensive – wide carriage pigment printer, thus:

As I am adding nine new profiles I will need to reuse nine of HP’s file names to make these show up – here’s the ‘conversion’ table:

To embed these paper names in the new profile ICC files we have to edit the profiles, rename them using HP’s cryptic file naming convention, rename the original files rather than erase them, in case they are needed in future, then move the new files down one level in the directory so that LR2 can read them.

Double-click on the first new file, the one for Arches Infinity Smooth 230 paper. You will see this as Colorsync opens:

Click on ‘Localized description strings’ and enter the name you want for the paper of choice – the default looks like this:

Those names are awful (this is the text which will show up in LR2) so I make them more user friendly, like so:

Now save the file in Colorsync (Command-S) and move on to the next one, repeating as necessary with descriptive names for each paper.

Next we have to rename the original files which are no longer needed; I do this by simply appending the text “.old” to the name of the original file; use the conversion table you created above to determine which files need to have ‘.old’ appended to their names:

Next, rename the new paper profile files using the old HP file names – the same ones where you just added the “.old” extension, like so, repeating for each new profile and making sure to use unique HP file names from the original files, with no duplications:

Here all all the name changes on the new files:

Finally, drag these renamed .icc files down one level to where the “.old” files reside, thus:

Load LR2 and click on Profile->Other in the Print module and this is what you will see:

To further clarify matters, I then add the text “HP” to the HP paper profiles, using Colorsync as before, with the following result – compare with the previous screen snap:

Now check all the boxes thus to make these properly named profiles show up in future when you click in LR2 and hit ‘OK’:

Next time you click profiles in the LR2 Print module you will see this:

Select the profile of your choice, load the appropriate paper in the printer and off you go! But do first make sure your display is profiled properly and, of course, I highly recommend Dr. P’s free screen profiling approach which will not only save you money on the colorimeter you do not need, but will get you more accurate colors to boot.

I took the additional precaution of making the new, renamed .icc files ‘read only’ to make sure that any new profile or application updates do not overwrite the files created above. You can do this by control-clicking the .icc file, clicking on ‘Get Info’ and making it ‘read only’ in the dialog box that pops up.

Why use printer-managed profiles rather than application managed colors? For the simple – and vital – reason that when you hit Print->Preview in LR2, Apple’s Preview application will display a Preview; at the lower left you will see a box for previewing the print on the screen using the color profile you have chosen – so much for all the ‘experts’ who maintain that you cannot soft proof with applied paper profiles in Lightroom:

You are now viewing a Print Preview of your picture with the paper profile of choice applied to the image. And you can use a selection of non-HP branded printing papers. What’s not to like?

And I can think of no better time to buy one of the truly great wide carriage printer bargains – HP still lists the Designjet 90 (18″) for $995 and the Designjet 130 for $1,295 (24″). I would not hesitate to buy another today and do, on rare occasions, rue the fact that I did not buy the 24″ model as the form factor is much the same with six inches added to the width. Either takes up little room for such a large format printer. OK, so they go ‘clankity-clank’ when they print, but you can afford ear plugs from the $2,000 saved on not buying their latest Z series machines. And ink use is so frugal, even a Scot would approve.

November 19, 2008

Camera profiles in Lightroom

Filed under: Lightroom — Thomas Pindelski @ 8:27 am

Now you can match the manufacturer’s intent.

I have generally avoided using Canon’s DPP Professional software which comes with the 5D. Clunky, slow, limited in application and not integrated with my man processing ‘engine’ – Lightroom – plus all those comedic spelling errors, well, it’s all just too much. Or too little.

Now Adobe has made it possible to view your RAW imports in Lightroom (and this only works for RAW images) emulating the manufacturer’s software. So instead of viewing your images in the latest Adobe Camera Raw profile, you can get to look at them in what DPP Professional would do. The differences are easily seen on the screen.

Point your browser to this address and download the profile package:

Now when you next start Lightroom 2 you will see the following in the Develop panel:

Click the drop down box and the camera specific profiles appear:

So if you are still using DPP, forget about it, download the profiles into LR2 and you have all you need in one place.

Here’s a snap processed using the Camera Landscape Beta 2 profile – note the warmth in the rose:


5D, 400mm ‘L’, 1/500, f/5.6, ISO 250

November 16, 2008

Lightroom 2 Upgrade

Filed under: Lightroom — Thomas Pindelski @ 8:34 am

Painless, amazingly.

My extensive tests with the free trial version of Lightroom 2 confirmed that the product is stable and debugged and I now find I cannot live without the localized adjustment features LR2 added. Not to mention enhanced keywording and search functions. Hopefully Adobe will add keystone/perspective correction in the next version and I will be able to bid a not-so-fond farewell to Photoshop CS2 (and its many predecessors), that user interface nightmare of a product.

Having had nothing but trouble upgrading Adobe products in the past I approached the idea of an online upgrade of Lightroom 1.4.1 to Lightroom 2 ($99) with trepidation.

Mercifully all went well.

Pay your $99 – assuming you have a version of LR1 on your computer – and off you go:


Download in progress – you have to elect either the Mac or Winblows version.


The new serial number is provided for input.


Old and new numbers input and she’s ready to go! I have blurred out the last four digits for security – you have twenty thousand guesses!

Even though I had the trial version already loaded, Adobe insisted on uploading the whole thing again – no big deal as it only took a minute or two.

My only complaint so far is that the auto-masking feature, when applied to large areas, is very sluggish. Now I must try the application on our old iMac G4 (PPC, 1.25gHz) and see how well it works on a relatively ancient machine.

If you do not have LR1 then LR2 will run you $299 – $100 more than Apple’s Aperture. Adobe has no earthly reason to drop the price to compete with Apple’s offering. If you elect the latter, be prepared to blow another $2-3,000 on a machine which might actually run it at something approaching reasonable speed. If you don’t believe me, stop by an Apple Store with your favorite RAW file and load it in Aperture on a MacBook. Then try the crop tool. Convinced?

November 14, 2008

Lightroom 2 – Keywording

Filed under: Lightroom — Thomas Pindelski @ 8:44 am

I have been putting this off for too long.

I have been putting off adding keywords to the pictures in my Lightroom database in much the same way as stock market investors prefer denial to fact. Open that statement in the mailbox and, yes, you too will be apprised of this year’s 40% drop in value. That’s the result of the foolish “stay fully invested” mantra of the past two bull decades which has been brainwashed into your psyche by amoral advisers seeking only to maximize their fees. This is by no stretch of the imagination a financial blog – though I do like to point out photography equipment bargains when I see them – but suffice it to say that after the 1929 crash the Dow index did not return to pre-1929 levels until …. 1954. So the ‘fully invested’ bunch, or what was left of it, had to wait out a war and 25 years later they had devalued dollars equal in amount to their 1929 investment.

But, like that reluctant letter opener, I have preferred to fool myself that my Lightroom cataloging system, which heretofore has avoided the use of keywords, would serve me well, added by a solid dose of good memory to help find things in a trice.

Wrong.

I am now finding that it’s getting increasingly difficult to locate a treasured snap in short order. Was that snap of the wife in Bermuda in ‘Cityscapes’ or under ‘Wife’? Was that picture of our sweet little boy, Winston, under ‘Playground’ or ‘Winston’ or ‘Birthdays’?

Here’s how I have ordered my folders:


In LR2, the green light refers to the active drive. The numbers indicate that I have 207gB left on a 465gB drive

Click on, say, the ‘Beach and Sea’ containing folder and you get:

Well, you get the idea. As long as you remember that the snap you want is in ‘Beach and Sea’ the rest is plain sailing. Snag is, sometimes it’s simply not where you would logically place it today and memory tends to fade.

Now that Lightroom 2 has made key wording easier and faster, if no less tedious, I have resolved to add keywords to as many of my pictures as makes sense and I am disciplining myself to do a hundred or so a day. Rather than doing this one by one, I assemble those that need generic keywords – ‘monochrome’ or ‘grain effect’ for example – and do a batch add of the relevant words. In a final pass I will add image specific keywords where warranted, the goal being that a keyword search renders a handful of results.

A related motivating factor is that my catalog of images (the keepers, that is) is growing faster than in days past, owing to the higher success rate of digital technology and greater availability of time for my hobby compared with those days when I was putting in 60+ hour weeks on Wall Street.

Here are some of the keywords I have added – note that I have replicated the folder names in case I ever decide to scrap or revise the folder structure. I have then started adding new keywords like ‘Red’ which identify pictures with strong red content:

LR2 allows you to drag and drop keywords onto image(s) so the process is fairly fast. The tricky bit is coming up with image specific words that make sense. “How would I think of this image were I looking for it?” is the recurring question.

Now when I wish to locate all files matching a specific keyword, I go to the right hand panel of LR2, highlight the word and click the arrow to the right – here’s the result of clicking on ‘Cemeteries’:

Keywords can be stacked for compound searches, though the technology in LR2 still trails Aperture’s where you can select a filter with boolean keyword input, using ‘if’, ‘and’ and ‘or’ logic. I have no doubt that this will eventually come to Lightroom.

So far I have encountered one snag. If you stack images of like kind (I stack composite HDR images for example as all go towards one result once merged) and leave the stack closed when keywording, only the top picture in the stack will be keyworded. If you subsequently change the top picture in the stack you will not be able to find the new one if you forgot to keyword it. To work around this I simply open all the stacks in the Library before keywording, so that all pictures in a stack have the keyword applied.

I have been banging away at LR2, moving files and folders, stacking, copying, processing, exporting and adding keywords for a while now and have had no lock-ups. The only time the application really bogged down was when I tried using the adjustment brush with auto-masking switched on to paint in a large, irregular sky area. I got the spinning beach ball while the overtaxed, modest GPU (Intel GMA 3100) in my MacBook did the data crunching. Mercifully, this is not something I expect to do often. At 4 megabytes of RAM it’s not like I’m hurting for CPU memory so I’m blaming the graphics processor for this one!

If I decide to upgrade to LR2 (I’m using the 30 day free trial which comes fully featured) I’ll give it a run on our old iMac G4 ’screen on a stick’ which continues to soldier away as a great Internet browser. That will answer the question of how well LR2 runs on older PPC CPU Macs. I can confirm that LR 1.4.1 runs well on this computer if nowhere as fast as on the MacBook. It remains more than useable for those looking for a low entry price to the world of Lightroom processing. The latest version of Aperture does not run at acceptable speeds on older machines like this one, whose G4 CPU runs at 1.25gHz and has just one core compared to the Intel’s two. One of the most distinguishing features of LR 1.4.1 is its speed on these old but still useful machines. Let’s hope that has been retained in LR2.

By the way, for those readers into this sort of thing, here are some interesting statistics on LR vs Aperture users from the Adobe blog. Probably self-serving given that this is Adobe’s data, but interesting all the same. Sample sizes are not stated in this survey:

I have questioned Apple’s commitment to Aperture before (no critical mass, no significant profit) and have little reason to change that opinion. And as I can testify, the conversion process from Aperture to Lightroom is not pretty. So the sooner you switch, the better. Adobe does this for a living; to Apple it’s a rounding error.

Enough talk. Here’s a snap from the beach, a composite of four images combined using Helicon Focus:


Kelp. 5D, 100mm macro and ring flash, 1/100, f/22, ISO400. Composite of four images using Helicon Focus.

November 9, 2008

Lightroom 2 Trial

Filed under: Lightroom — Thomas Pindelski @ 9:00 am

Trying it out.

I continue to watch the excellent tutorials to be found here and have now downloaded the 30 day free trial of Lightroom 2.1 from the Adobe web site. I delayed doing this as the predicatble raft of bugs in 2.0 has now been largely resolved and discussion boards suggest the application is stable. Never buy Version 1 of anything ….

My first focus is on the graduated density filter and adjustment brush, which are new features of the localized adjustments added in Version 2 of Lightroom.

While I have for ever toyed with the idea of using those slip-on graduated density filters for landscape work, the whole thing has always seemed too clunky. Further, interposing yet another easily scratched surface between object and image has never much appealed to me and the thought of carrying dozens of those filters and all the related gadgetry to attach them to my lens has left me cold.

Well, with Lightroom 2 there is no more need for external filters. Not only can you add a graduated density filter of your choice to selected areas of an image, you can also tilt the horizon for these where necessary, elect the level of graduation and change color, brightness, clarity, contrast, saturation and sharpness in your area(s) of choice. Try that with mechanical attachments!

Here’s a case in point of a landscape with a sloping horizon taken from my front door yesterday. As the original discloses, the lighting was flat, the scene less than interesting and the sky horribly bland.

A few moments work, applying graduated sloping colored filtration to the sky area and selectively darkening the foreground using the new adjustment brush feature (look at the road at the bottom), plus an overall tweak for saturation and clarity, and upping the reds and oranges, and you get a nice Old Master look, like this:


From my front door – the beauty of central California. 5D, 200mm ‘L’, 1/1000, f/4, ISO 400

The ability to make localized graduated adjustments is powerful and Adobe’s implementation superb. It bears watching those videos as there are so few adjustment buttons that you have to learn how they work, but the engineering and user interface are remarkably elegant. Indeed, it was Lightroom’s far more intuitive user interface and logical work flow that made me abandon Aperture. Not to mention the general slugishness of the Apple application regardless, it seems, of how current or fast your computer is. Lightroom flies, the slowest step being localized adjustment brush operations which take a second or so to register on my MacBook (4gB RAM, 2.1gHz C2D CPU).

By the way, when you first fire up Lightroom 2 it will convert your Lightroom 1 catalog for use with the new version, but it also leaves the original Version 1 catalog untouched in the event you decide not to upgrade. (The on screen narrative does not make this clear, implying that your original files are lost). Nice – no need for yet another back-up, though I made one just in case. You should too.

Finally, this screen snap shows the area to which I have applied the graduated effect – the dot is the center point above which things darken. You can also see that I have sloped the graduated density area to replicate the natural slope of the horizon – just drag up or down on one side to slope the area affected.

Lightroom 2 is beginning to look like a keeper.

As for these guys, well, I would be looking for a new day job in their place:


Yesterday’s hardware. Yesterday’s concept.

And if you have a big investment in these, well, sell them in a yard sale and the proceeds may just pay for the upgrade to Lightroom 2!

November 7, 2008

Lightroom 2 tutorials

Filed under: Lightroom — Thomas Pindelski @ 8:40 am

Assessing whether to upgrade.

Now that Lightroom 2.0 has come and gone, with the usual fixes for basic bugs which should never have left Adobe’s labs (Americans always prefer garbage today to quality tomorrow), Lightroom 2.1 is beginning to intrigue me. I’m still using 1.4.1 because it’s stable and does what I need, but one of the appeals of 2.1 is the ability to do localized adjustments without hopping over to Photoshop. That’s something I tend to avoid like the plague.

The other evening as I was flipping though photography podcasts on the Apple TV – you can do the same on your computer (Mac or the other kind) using iTunes – I came across a counterintuitively named one going by the title Photowalkthrough.

Here’s the download page in iTunes – just search in iTunes on ‘Photowalkthrough’.

The podcasts of interest are the ones on Lightroom 2. I have watched a couple and there are really nice on screen demos of the use of the local adjustment brush which seems to be the key feature added in LR2. I was especially impressed by the auto masking feature which restricts edits to, say, backgrounds or foregrounds, based on the outline of the object concerned. No need to outline the item in advance, as you might in Photoshop.

I seem to recall reading that the upgrade from LR 1 is some $100 and after watching a few more of these I may well spring for the cost. There’s a 30 day free trial version available, of which more here.

July 30, 2008

Lightroom 2

Filed under: Lightroom — Thomas Pindelski @ 10:02 am

A feature comparison.

With the release of Lightroom 2, Adobe has published a useful feature comparison to Version 1 – click here.

I’m not upgrading right now, respecting my ‘Never Buy Version 1.0 of anything’ rule. Further, as I do not do a lot of image processing, the enhanced controls in v2 don’t do that much for me. 64 bit support? Meaningless to me from a practical perspective.

As for Lightroom 1.4.1, which is what I currently use, I couldn’t be happier. It’s fast, doesn’t lose images and printing is a dream. I’m beginning to wonder whether Aperture will be orphaned soon – a small user base (Mac only), a bog slow application unless you spend $$$ on hardware and very buggy implementation will not see me back with that flawed product.

May 5, 2008

Enjoying processing

Filed under: Lightroom — Thomas Pindelski @ 8:00 am

Hard to believe, really.

I confess that the two words in the title of this piece are ones I would never have seen writing together. To me processing is simply a mechanical step that stands between the snap and its realization. A necessary if boring interlude which should be made as fast and automated as possible to let the picture show itself to the world.

If the increasingly rapacious hardware needs of every latest version of Aperture saw me abandon the product rather than spend more money on newer, faster computers seemingly every six months, then I can only report that my first few months with Lightroom have been nothing short of bliss. Relatively speaking, that is. I still hate to process but now I don’t have the endless frustrations of spinning beach balls and lost originals that were becoming Aperture’s specialty.

First, Lightroom runs happily even on our ancient G4 iMac and second, it simply cooks on my current bottom-of-the-line MacBook (1.83gHz C2D, 2gB RAM). Second, while the interface may lack the polish of Aperture’s, who cares? You no longer need Aperture’s pretty screens to distract you while you wait for the beach ball to disappear. In Lightroom you are already three snaps down the road of production and output. In other words, Lightroom is an industrial grade tool for users who need fast, reliable throughput.

Even round trips to Photoshop are not that bad. Once CS2 is loaded (it takes 30 seconds on the MacBook as it’s running in Rosetta PPC emulation mode) a round trip to take advantage of special features not currently available in Lightroom takes a minute or so. Mostly this is to use ImageAlign or the Transform function to correct skewed and leaning verticals. Other than that, pretty much everything I need to fix a picture is in Lightroom, and I would hope that distortion correction will be added to the next full version of Lightroom in a few months.


Hearst pool cloister ceiling. 5D, fish eye, 1/1500, f/8, ISO 400, Image Align

A related benefit is the easy ability to craft import and processing presets – nothing more than one click settings which confer a bunch of preferred adjustments on your image, with full preview and undo abilities. I should add that I use RAW exclusively for my source images, whether from the 5D or LX-1.


Lone diner. One click to monochrome in Lightroom. Lumix LX-1, RAW original, ISO 80

So I’m not about to say processing is fun, but Lightroom simply makes this step as painless as anything since Polaroid gave the world instant snaps.

April 2, 2008

Lightroom 2.0

Filed under: Lightroom — Thomas Pindelski @ 7:43 am

Beta testing is the way to go.

Adobe has just released Lightroom 2.0 Beta allowing all and sundry to bang away at it in a sort of group grope-wiki software development approach which I can only applaud.

Why?

Well look at the catastrophe that resulted when they decided to go it alone. Alternatively, compare this to arrogant Apple’s approach with Aperture 2.0 whose first 2.1 update seems to have more error fixes than 2.0 had new features. That’s what you get when you restrict testing to an insider elite comprised of wedding photographers. Apple needs to learn that the real tinkerers who are going to find stuff do not do weddings ….

Localized corrections in the Develop module and multiple monitor use seem to be the most useful enhancements – this is enough to call it 2.0 or are earnings hurting? Still, Adobe is adopting the right development approach. A discussion forum can be found here.

There’s no soft proofing support yet, but read this for a workaround.

Interestingly, the ‘10,000 pixels a side’ import file size limit (meaning files cannot be over 10k pixels on either dimension or more than 100mB in total) has been increased to 30,000. I actually ran into the 10,000 pixel limit when migrating from Aperture to Lightroom on some big scans of 4″x5″ originals, so this is not as odd as it at first sounds.

Anyone can use the 2.0 Beta but to extend the trial past 30 days you either have to be a registered 1.x user or ask Adobe nicely. There’s a neat tutorial here. In a related tutorial an easy way of exporting, say, multiple images to Photoshop, such as in HDR photography is explained. The enhancements allowing multiple image printing on one page are nothing short of superb – some 5 minutes into this tutorial.

Is Adobe trying too hard? With 2.0 Beta newly out and 1.4.1 still in need of repair, is Adobe unnecessarily rushing things?

While I have no access to current data, assuming that PC users outnumber Mac zealots by 4:1, it’s not like Aperture is a competitor. Add the fact that Aperture 2.0 seems to require the costliest Mac to run half decently (if then), whereas Lightroom potters along nicely on an ancient G4 Mac, I somehow doubt there are going to be too many users switching from Lightroom to Aperture. In fact, I would guess they are about as common as people looking for permanent resident status in North Korea. Trust me, Abobe, I only want to go through this hell once, so there’s no way you are about to lose me as a user unless something better comes along and it uses LR’s catalogs without need for conversion.

However, given how few people use Macs, I wonder whether Adobe would be better off canning half the Lightroom development team and spending the savings on properly marketing 1.4. Lightroom 2.0 is nice but, let’s face it, it can wait and you are not going to dump Aperture just because of this Lightroom Beta upgrade which isn’t even ready for prime time.

And, please, no comments about how photographers are disproportionately users of Macs. The sole reason you visit this blog is to read about photography and 80% of you, according to my statistics, use Internet Explorer. Last I checked, that piece of garbage doesn’t even run on a Mac …. and anyone using IE with Parallels on a Mac truly needs a lobotomy. And I’ll bet that of the 20% using Safari, some are running it on Windows and many don’t use Aperture in any case. So the 4:1 LR:Aperture user ratio is probably understated.

Sure, all the toadies, sycophants, commercial flacks and those otherwise in the pay of Adobe will extol the virtues of 2.0 and praise Adobe for its community spirit. Utter nonsense. Adobe is a stockholder-owned public company. It’s primary duty, as with any public company, it to maximize the wealth of its shareholders, not tell us about its great good heart and wonderful social policies.

So, Abode, fire a dozen developers (starting with the fellow who approved 1.4.1 for release) – $1-2mm saved – and roll something like this out.

“Aperture users! Make Lightroom run twice as fast. On your ten year old Mac. Invest the hardware savings in a new Nikon D3 instead”.

And let’s face it, Adobe, your stock is nothing to write home about.

Or, better still Adobe, write a proper converter for Aperture to Lightroom catalogs and sell Lightroom at 50% of retail to anyone downloading it and sending in the box top from their Aperture software. Now that’s something that might make me show some interest in your stock and it would pay for itself with the first few conversions. It might even preclude an imminent hostile takeover though I’m conflicted here as I would far rather own the stock is someone wants to acquire you for a premium to the quoted price.

March 13, 2008

Importing into Lightroom

Filed under: Lightroom, Software — Thomas Pindelski @ 4:54 am

Automating sharpening on import.

One of the first things I have to do when processing images imported from my Canon 5D (or the Lumix LX1 for that matter) is to sharpen the RAW image. This is standard operating procedure for digital cameras and has nothing to do with poor native image quality. The process simply negates the effect of the anti-aliasing filter, used in nearly every digital camera. Apple’s Aperture is really smart about this and does it automatically, detecting the camera used and applying Apple’s pre-set adjustments. Lightroom is less smart but can be taught to make the adjustment automatically on import.

Here’s the process – I have enlarged the screen shots for legibility, hence the poor definition – if you want to see aliasing take a look at the ‘jaggies’ in the pointers!

Here are the Lightroom defaults for sharpening in the Develop module.

Leave them like this and you will have to sharpen every picture once imported. A waste of time.

Here are the settings that work best for me – and I have large prints made on an HP Designjet 90 printer as my goal. For the small images used for the web it really does not matter what you do. A large print, on the other hand, is the most demanding output there is.

Having made those adjustments in the Develop panel I then create a new User Preset by clicking on the ‘+’ sign in the Preset area in the left panel and naming the current settings Canon 5D. No other defaults have been changed in the Develop module at this time nor do you want to make any changes:

Then when prompted which settings to save with this new User Preset, I choose ‘Check None’ then check only the Sharpening box. This will limited changes made whenever this User Preset is chosen to Sharpening only. Were I importing from a small sensor camera with inherent image noise (not an issue with the 5D) I would consider including Noise Reduction when creating the User Preset and would check the related box, below.

Next I insert a CF card containing images to be imported into the card reader and the import Dialog pops up. Under information to Apply: Develop Settings I click the drop down box and point to the Canon 5D preset just created:

Now my preferred sharpening settings will be applied as the pictures are imported and 1:1 Previews are generated. As is always the case with RAW files, the original file is never changed – it’s just the Previews that are managed.

You can make User Presets which are specific to a camera serial number, if you want, but as Your Truly owns just one 5D (a status unlikely to change) and one Lumix LX1, that’s a luxury I do not need.

One size does not fit all:

Now the above approach is camera specific, not lens specific.

It doesn’t mean that you just merrily import every image without the need for any additional sharpening adjustments.

Even in my small set of Canon lenses there are noticeable variations. The 85mm, 200mm’L’ and 400mm ‘L’ optics are pretty constant when it comes to sharpness at all apertures. Indeed, the 200mm generally needs a small reduction, it’s that good. On the other hand, the 24-105mm ‘L’ and the 50mm f/1.4 at full aperture both need a little more and the 20mm needs more all the time. It’s a mediocre piece of glass at best.

And it’s not just sharpening you have to worry about. There are other lens aberrations.

It would be pretty neat to be able to automatically adjust for Chromatic Aberration (color fringing), Distortion based on the lens used and Vignetting, but that feature is not available, yet. CA and Vignetting would be especially tricky as they vary with aperture. Distortion is no walk in the park either as the distortion levels in zooms vary with focal length. That’s not to say that Adobe couldn’t do it (we are talking simple look-up tables here, although a lot of them, and a presumption of low sample variation) and I, for one, would love to be able to have the fairly pronounced barrel distortion in the 24-105mm ‘L’ zoom automatically removed when this otherwise fine optic is used at its wide end.

DxO Optics adopts this exact approach in a plug-in for Lightroom. They should be applauded for their efforts. The list of cameras and lenses they automatically adjust for is set forth here. I have not tried the product and, at $300, I’m not about too, but it may make sense to some. It looks like the latest Mac version is not yet available so I could not try it even if I wanted to blow the coin. Their video suggests the product is bog slow (a couple of minutes to adjust just five images), and you can bet they are using the fastest possible hardware to put a gloss on things, so a pinch of salt is recommended before you lay out your hard earned cash.

Does any of this really matter with small images – like those reproduced on the web or in snapshot prints? No. But once your prints sizes get large, it can make a significant difference to the appearance of the picture. And a little bit of automation to reduce the drudge of processing is always a good thing.

March 12, 2008

More on Lightroom printing

Filed under: Lightroom — Thomas Pindelski @ 7:17 am

Some convenient enhancements.

Since publishing my first piece on how to profile monitors and printers for use with Lightroom, I have made a couple of interesting discoveries.

First, I listened to Adobe Podcast#1 (with Mark Hamburg, Kevin Tieskoetter and Jeff Schewe) from Apple’s iTunes store (search podcasts on “Lightroom”) which speaks to profiling (they are speaking about Lightroom Beta Release #4 for the Mac) and was intrigued to note that that we shared the same approach. The development team (a lot of very smart, well informed, outspoken engineers – highly recommended listening) does exactly what I published with regard to the use of Colorsync, letting the printer manage colors, not Lightroom. This philospohy is printer agnostic. Epson, HP, Canon, you name it.

My approach requires making Lightroom use Apple’s Colorsync utility to manage colors. You need a properly profiled screen and I describe in that earlier piece a very accurate way of doing that which does not even require a colorimeter, provided you follow certain disciplines regarding ambient lighting.

I suggest you give this method a try. Your maximum cost is a few minutes, a couple of pieces of paper and some ink. And the money saved on a Colorimeter (wish I had been that smart when I bought mine) will pay for a lot of paper and ink. It does not matter who makes your printer for this screen profiling approach to work.

The other thing I discovered is that it is possible to save the Colorsync setting in the Printer Profile – something I stated frustration at not being able to do.

I had forgotten that there is a ‘Save’ setting in the print dialog box. So elect Colorsync in Print Settings->PaperType/Quality then Save the setting with a meaningful name. I have named my saved file “HP Photo Satin – Colorsync” which states the paper type I chose before saving and obviously uses the Colorsync utility. Note that this named setting is independent of Lightroom’s Print templates – you choose it at print time after selecting a Print template. The printer dialog box dictates color management, the Lightroom Print template controls the paper size, margins and picture layout on the page.

Then, when it’s time to Print, I simple choose this drop down menu option in the Print dialog box (I have not yet figured out how to make it the default, something I would like to do as that’s what I use nearly all the time – what I need to do is work out how to delete the ‘Standard’ setting, I’m guessing, at the OS file level). A quick check – see the following screen picture – confirms that the Colorsync setting has, indeed, been saved and will be used when printing.

Now I am assured that both the right paper profile and the correct Colorsync setting is made without having to check yet another layer of menus in the print dialog box. So printing really is a breeze. I have created three templates – for three different paper sizes. That’s all I need, as I always use the same HP paper.

* * * * *

I learned an interesting thing from this podcast – what do you think Adobe did for the Lightroom development team for Christmas of 2005? They gave each member a digital camera and encouraged them to take lots of pictures. Maybe the resulting stress testing has something to do with the application’s speed? I wonder whether Apple ever considered doing that for its Aperture developers? Or do they simply get a $7,000 Mac Pro and 30″ screen which will run anything well ….

March 9, 2008

Lightroom and round trips

Filed under: Lightroom — Thomas Pindelski @ 8:34 am

To Photoshop, that is.

While the slightly up-tilted camera distortion is not that bad here, a quick round trip (Command-E on a Mac) from Lightroom to Photoshop CS2 and a few seconds with the ImageAlign plug-in sets things dead straight. Command-S in CS2 saves the corrected version as a TIFF file in Lightroom. ImageAlign is not just for de-fishing fisheye snaps!


Cropping of the perspective-corrected result in Lightroom – a superbly implemented tool.

Here’s the before and after – a subtle change but worthwhile:

Here’s the final result. Magical late sunlight. California sky.


Tough neighborhood. 5D, 20mm, 1/750, f/11. ISO 250.

You can see some lens vignetting but I left it uncorrected as it heightens the center of interest. My shadow works – at least for me!

The power of RAW

Filed under: Lightroom — Thomas Pindelski @ 8:03 am

Two stops under does the trick.

Because very high dynamic range pictures will result in burned out highlights, notwithstanding the fine CMOS sensor in the Canon 5D, I underexposed this one two stops (spot metered on the sky) then brought the detail in the foreground back with the processing controls in Lightroom. Here’s the Before and After – a very well engineered function in Lightroom allowing all sorts of comparisons.


Lone oak. 5D, 20mm. 1/4000, f/8, ISO 250. RAW.

As the controls in Lightroom indicate, I had to add substantial noise reduction and sharpening. As the sun was directly behind the tree, regular exposure would have made the branches unrecoverable – sort of like halation in films of days past. This magnitude of correction could not possibly be done in a Jpg file. The histogram testifies to the complete absence of burned out highlights – there’s no crowding at the right end.


Adjustments made in Lightroom.

I also boosted the Tone Curve substantially in the shadows – this control is perfectly implemented in Lightroom – I used the small pointer tool, which you can see at the top left of the following screen picture,allowed me to see the tone curve in the shadow range by placing the pointer in the foreground of the picture. This helped me determine where to adjust. The dotted line shows the reference starting point.

Here’s the final result after slight straightening of the horizon – the sunlight was quite blinding and it was not easy to see much in the viewfinder!

Once stopped down the rather ‘iffy’ Canon 20mm lens is free from color fringing, so no lens corrections were needed.

March 6, 2008

Lightroom defaults

Filed under: Lightroom — Thomas Pindelski @ 8:31 am

Don’t forget to set these correctly.

One slightly frustrating thing about Lightroom’s menu structure is that preferred settings for how the application looks and behaves are all over the place. You would expect to see everything under Lightroom->Preferences, but that is far from the case. A last vestige of the truly frightful user interface enjoyed by Photoshop users for years.

I tend to prefer a really stripped down, minimalist look to the screen interface, opting for a minimum of distractions on the screen. Once you learn some of the most useful one-key short-cuts, then you will no longer need the top Apple menu or much of what clutters the side panels.

In the Develop module I right click on the left sidebar and choose to show only the Library and Folders. I have little use for Find, Collections, Keywords or Metadata Tags, so these are switched off. You cannot get rid of the Navigator selection at the top, but the very irritating flashing of the small picture preview as you go through pictures in the Grid view can be hidden by clicking on the small arrow to the left of the word ‘Navigator’. Because my photography is thematic, I do use Folders and sub-Folders named after the theme in question which, with my limited volume of pictures, works for me when trying to find something. Others will opt for keywording and dated folders. Here’s how my left panel looks in the Develop module:

The right panel is similarly stripped down – I have little use for Keywording or Metadata:

Like ’switching’ can be accomplished in the other modules.

Much as I laud and respect the team which authored Lightroom, I do not need to be reminded of their names each time I boot the product, so I switch the display panel off by unchecking the first box under Lightroom->Preferences->General, like so:

In Lightroom->Preferences->Interface I get rid of the bizarre antique ‘Panel End Mark’ which Lightroom shows by default at the base of each panel, thus:

Now in File->Catalog Settings on the General tab, Lightroom comes with automatic file back-ups every thirty days switched on. First, 30 days makes no sense if you use the application more frequently. Your failing hard disk will not conveniently wait until your last back-up before blowing up. Second, if you are not making daily back-ups to a secure external drive, you are simply living dangerously. So I use SuperDuper! to make a daily bootable clone on an external Firewire disk and switch off this (now useless) choice, electing ‘Never’:

Still in the File->Catalog Settings menu choice in the Library (Grid) view, this time under the File Handling tab, Lightroom comes preset to discard 1:1 Previews after 30 days. Odd. It takes for ever to generate these when you import a lot of pictures and with the small increase in storage (my 40gB picture catalog creates a 6gB preview catalog) and given the vast increase in speed that 1:1 Previews add to the Develop process, you most certainly want to keep these. The third drop-down box is set to ‘Never’:

Next in File->Catalog Settings under the Metadata tab I leave the factory defaults for Metadata alone:

However, were I in the habit of frequent round trips to Photoshop and if I wanted my Lightroom edits to be automatically reflected in the Photoshop image, I would check the third box (’Automatically write changes into XMP’) above. Otherwise, Photoshop will simply show the RAW unprocessed image in the database or the image as it was last saved. On those (rare) occasions where I do round trip to Photoshop I will do a file save (Command-S on a Mac) before round tripping, thus forcing Photoshop to show any Lightroom edits in its displayed image. If you check this box as a default, Lightroom will slow down as every change gets saved to disk. You don’t want that unless you are running on a Cray mainframe and work at Lawrence Livermore Labs. Meaning you have a super fast machine.

Finally, to get rid of the top white menu, I switch it off as explained here.

Now I have the lean and mean user interface I prefer.

March 5, 2008

Lightroom Tutorials

Filed under: Lightroom — Thomas Pindelski @ 1:03 pm

Go to the source.

I came across some outstanding tutorials on Lightroom in video format, authored by George Jardine, a member of the Lightroom development team at Adobe.

Click here for an index.

If you do nothing else, download and watch the one titled The Lightroom Catalog – Part 1, or “Where Are My Pictures?” which is definitive on how Lightroom stores files. Without a proper understanding of this you risk loss of files which are stored in disparate Lightroom catalogs.

There are also a lot of useful Podcasts from the Adobe team in the iTunes store, all free. Many are in video format and feature interviews with famous photographers like Peter Turner, Eric Meola, Jay Maisel and Jerry Uelsmann.

While we are at it, I have found an even simpler way of switching off all the panels that Lightroom displays to allow uncluttered picture preview. Simply hit the Tab key on a Mac. Tab again to restore. Finally, to remove the menu bar at the top, go into this menu selection and, henceforth, the menu bar will only appear on a mouse-over:

There does not appear to be a way of doing this from the keyboard. (A reader has corrected me – refer to Comment #1 – the ‘F’ key does this – thank you, Alastair).

Here is the result:

February 28, 2008

Lightroom soft proofing and printing

Filed under: Lightroom, Printing, Software — Thomas Pindelski @ 8:23 am

Soft proofing in Lightroom is easy.

I do not propose to address image cataloging and developing in Lightroom at any length in this journal as there are lots of tutorials and blogs out there that know a thousand times more than I ever will. Adobe even has a couple of video tutorials out there though they are really poor compared to Aperture’s slick offerings. While presented by real photographers, rather than blackshirts, Adobe opts for a folksy, joking style. The last thing I need in technical instruction materials, Adobe, is someone’s idea of what passes for humor. Just the facts, ma’am. You want humor, you read my blog, OK?

What I want to address here is soft proofing of your Developed Lightroom picture.

You do not need Photoshop for soft proofing if you use a Mac.

‘Experts’ will tell you that Lightroom does not offer soft proofing of the image, meaning the ability to preview the photograph on the screen with the relevant printer drivers invoked to show how the printed picture will look. (Aperture has soft-proofing built in, as does Photoshop).

A soft proof can look quite a bit different from the regular screen image as a print has a much narrower dynamic range than the regular screen image and also has its own color characteristics conferred by your printer and paper of choice.

If you are taking studio portraits then you really must use soft proofing as the eye is especially critical of accurate skin tones. The color differences are significant and easily noticed when switching between regular and soft-proofs.

Profiling your monitor:

The first problem is that monitors are rarely properly profiled – do this right and what you see in Lightroom is what the printer will print, allowing for the lower dynamic range of a print compared to a monitor.

Here’s how to properly profile your monitor:

1. If you can afford one, get a really good colorimeter like the Eye-One Display 2. If not, go to Apple System Preferences->Displays->Color->Calibrate. You must profile the monitor in the same light as you use to compare it to the print. Use daylight – artificial light will give erroneous results as it is missing many colors in the natural light spectrum.

2. In Lightroom, make your adjustments to the image and make a test print. While there are two ways to work with printer profiles – Lightroom Managed or Printer Managed – I find that Printer Managed gives marginally truer colors – there’s little in it. So when in the Print module of Lightroom, you need to set the program up for Printer Managed colors, like so:

3. When you click on Print, set up the printer to use Colorsync, Apple’s color management utility.

Make your test print (use a familiar person as a subject with flesh tones) after checking that you have chosen the printing paper you are using – this forces the application to use the relevant printer driver. The printer cannot know which paper profile to use if you do not tell it. That is what Lightroom means in the previous picture when it states “When selecting ‘Managed By Printer’ remember to turn on the printer’s color management in the Print dialog box before printing”. (Frustratingly, Lightroom defaults to ColorSmart/sRGB and I can find no way to permanently save the Colorsync choice in a Print Template – meaning you have to choose Colorsync every time you want to print).

4. Now compare your test print to the image in the Lightroom Print module. They will not match.

5. You must now fine tune your monitor color profile. The printer is doing what Lightroom is telling it, but the monitor is not properly profiled for your environment. It is still not displaying colors correctly. Go back into the Apple System Preferences->Displays->Color->Calibrate tool, making sure to choose the display profile you saved in step 1, above, while keeping the Lightroom screen display unchanged. Now work through the Apple software again until what you see on the screen matches the print you just made, wrong as it is – hold the print up to the screen. Doing this at night with incandescent lighting is a complete waste of time.

The key adjustments are Target White Point and Target Gamma. Forget everything you have read about setting your screen to a specific color temperature or to a gamma dictated by some academic. Academics do not make prints. Use your eyes to get the best color match. I ended up with a Target Gamma=1.75 and a Target White Point =6707K. Whatever. Meaningless numbers.

Save the revised profile – you have now matched the monitor profile to the test print.

6. We are done with the test print. Discard it.

Soft proofing:

a. Now go back to Lightroom, choose the Develop module, and adjust the tones to your satisfaction.

b. In the Print module choose Print->Preview. Check the Soft Proof box at the lower left of Preview. This refreshes the display in Preview, forcing the image to use the printer paper profile you elected earlier (see #3, above). To confirm you are using the right paper profile, hover the mouse cursor over the words “Soft Proof” and the driver will be disclosed as in the following screen picture.

You are previewing a soft proof of your photograph which shows what the printer will print.

c. If you don’t like what you see, re-Develop the picture and try again. Do not even think of changing your monitor profile.

d. Make the final print. No need to return to Lightroom – just click on ‘Print’ at the lower right of the picture in Preview.

* * * * *

I get a ner perfect match using this technique, and have no need of a colorimeter to effect proper display profiling – my eyes and Apple’s built in tools tell me what I see. In fact, I have found this method to be so powerful that I am going back and reprinting several 18″ x 24″ prints hanging on the wall which simply were not quite right with regard to color fidelity, contrast and brightness. Spot on results every time from originals of widely differing tonal and contrast ranges.

The monitor I use with my MacBook? No, not a mega-bucks Apple Cinema Display – a dirt cheap ($235 at the time of writing) Samsung 216BW, 21.6″ diagonally and with 1680 x 1050 pixel definition. Heck, the articulated wall arm I use to mount this on the wall ran me almost half the cost of the monitor.

Want to read more? Check this excellent document by Apple on how Colorsync works in Tiger (OS 10.4.xx). Migrated to Leopard? Revert to Tiger – Leopard (10.5.2) is still messed up in this regard. And you thought Microsoft’s Vista was bad?

The print module in Lightroom is really well implemented in most other respects, not least in its ability to support multiple disparate pictures on one sheet of paper (Command-click non-contiguous images to select them in grid view, then go into Print view, electing, say, the 2×2 template).

Bear in mind that Lightroom is just one year old and is still in its first commercial iteration at v1.3.1. And it’s not as if I am the first person to note the absence of soft proofing within Lightroom, so you can bet Adobe knows of the issue. I would expect them to offer soft proofing within the application in the next major release. But it is not essential if you adopt the approach above and it’s not like it’s a big deal if you use Colorsync.

Now all I will need PS for is to correct lens distortion (Adobe may even add that in Lightroom) and for de-fishing fish eye snaps – though Comment #8 here suggests CS3 can do this. As I use the ImageAlign plug-in in CS2, I’m happy to save my money. A round trip to PS CS2 from Lightroom takes 60 seconds.

And if you think Adobe will cut the price of Lightroom by $100 to $200 like Apple did with Aperture, don’t hold your breath. Apple’s move smacks of desperation. Adobe has no need to cannibalize its pricing if it’s the only game in town and selling like hot cakes, though if they do drop the price all photographers will cheer. Investors may not.

February 25, 2008

Lightroom on an older Mac

Filed under: Lightroom — Thomas Pindelski @ 6:07 am

It still cooks!

You can read about how to migrate from Aperture to Lightroom here.

Given the great speed and smoothness of Lightroom on my MacBook (1.83gHz Intel Core2Duo, 2gB RAM, Intel GMA950 graphics card, OS 10.4.11) I thought it might be fun to try it on my old iMac (1.25gHz IBM G4 PPC, 1gB of RAM, OS 10.4.11). This is the elegant ’screen-on-a-stick’ design after which the iMac’s ergonomics went downhill – the poorly thought out stands on the current crop (G5 and later) need a couple of thick books to raise the screen to the right height. We keep that old Mac around in the living room primarily as an email and Internet browser for guests. The screen is superior too – far less color change occurs as you move your head. Needless to add, Aperture will not even run on this machine which uses a GeoForce FX5200 graphics card. Finally, it’s further distinguished by having a proper, horizontal disk drive which not only accepts 3″ discs (put one of those in your MacBook and it’s toast) but also burns DVDs (an option I avoided, to save money, on my MacBook). Unlike the disc slot in my MacBook, which refuses to read discs 50% of the time, this one really works. So much for progress.

Therefore I loaded Lightroom on the old Mac and tried to access my library of pictures by neworking the two. Well, Lightroom reported that it does not support networked volumes, meaning the drive has to be hard wired to the computer running Lightroom. No problem. I plugged the hard drive with the Lightroom database into the old Mac and fired her up. Loading the largest picture in the database – a 100mB TIFF file – was a snap. It takes a few seconds longer than with the MacBook but thereafter the processing controls that so dog Aperture – spot retouching, cropping, horizon levelling – were every bit as smooth as on the MacBook. The dead reliable iMac is some five years old, the MacBook has but a few months (and one repair already) on it.


The wonderful G4 iMac

So anyone running a machine of this vintage and thinking of using Lightroom should be just fine. If your Mac is even older and you are running Lightroom on it, I would be interested in your comments. There are many fine G3 Powerbooks still in daily use out there.

So, finally, a proper break with the incessant, money wasting, perennial hardware upgrade cycle dictated by Apple’s software design. And now I have total redundancy (hardware and data back-up) if my MacBook breaks down again – I wouldn’t be betting against that given my recent experience with Apple’s poor quality control.

Note that both machines are running the last version of OS Tiger (10.4.11). I have not upgraded to OS X Leopard (10.5) as I try never to buy ‘first of breed’, preferring to let others act as Apple’s unpaid guinea pigs. Indeed, there are many comments out there on chat boards that suggest that Adobe (or Apple – much finger pointing here) has work to do to make Lightroom render colors properly with Leopard. Additionally, all this user sees in Leopard is glitz and gloss, with little improvement in the way of function. Just like Aperture 2.0, in fact.

Aperture on a G4 machine? Fugghedaboutit! Neither that graphics card or the G4 CPU are even supported.

For those photographers out there looking to migrate their Lightroom application from Windows to a Mac (a trivial process requiring copying of your picture files and installation of the Mac version that came on your disc), there are some superb, lightly used, bargains to be had out there in G5 iMacs, Powerbooks and MacPros. A great way of fighting back against hardware upgrade tyranny. The LCD screens are reputed to be better than those on many current models (my G4 iMac testifies to that) into the bargain.

Older Posts »

Powered by WordPress