Lightroom 1.3 on Leopard

by James Duncan Davidson

Compatibility with Mac OS X Leopard is one of the bullet points of the recent Lightroom 1.3 release. Now that I've had a few days to work with the release, I can indeed confirm that Lightroom 1.3 gets along with Leopard, at least for the most part. There are, however, a few small issues I've run into.

lightroomleopard.png

The first of these issues appeared for me when importing files directly from a compact flash card. I've seen some spurious error messages on a few of my imports, including an odd message indicating that there was a problem with 0 of the images imported. Also, on one occasion, an image wasn't copied as part of the import process. For the time being, I may start copying images over to my local drive in the Finder and then import them. I did this with a previous version of Lightroom to work around import problems. This would be a real drag, but incomplete imports are also a drag.

lr_close_preview.png

Second, I've seen Lightroom crash a few times while working with the Print module. This was reported in a few places on the first day of release. The workaround talked about on the net is to minimize the print preview window, as shown to the right. I can report that this seems to work for me so far.

And last, as you've probably heard, there have been warnings concerning Lightroom's database and Time Machine. For the time being, I've followed the recommendations to exclude my Lightroom catalog from Time Machine backups. I've also excluded the preview folder as well, since it only includes data that can be easily rebuilt from my image library.

lr_timemachine_exclusions.png

This doesn't mean you have to skip backups of your Lightroom database, however. If you make backups of your catalog from within Lightroom—I have mine set to make a backup every time I run Lightroom—those backups will be nicely stashed away for you by Time Machine. Also, if you have Lightroom automatically write XMP data, those XMP sidecar files will be faithfully backed up by Time Machine as well, providing a fairly complete backup solution.


6 Comments

Richard Caccavale
2007-11-21 12:57:26
James:


I have had import issues with every version of Lightroom on both Tiger and Leopard, so I just don't trust it. Even with the previous version on Tiger, I would sometimes know I shot more than showed up in LR, and sure enough they would be in my backup that I copied in the finder even though LR claimed to have succeeded. I tested import under Leopard and got the error you saw on an 8GB chip. I think it is wise to always copy your photos in the finder and then do a LR import from their final location. That way you can confirm that everything looks good at a file-level before worrying about catalogs and metadata.


cheers


Rich
http://herodot.us

random bob, a.r.c.
2007-11-21 16:00:05
I'm an Aperture User (Don't hate me!), but until I recently got newer hardware had been d/l'ing and trying the latest builds of Lightroom, as my old rig just couldn't handle AP well enough...


Anyway, I wanted to throw this out there: I seem to remember that the 1.2 iteration at least had an option that during import it'd ignore "possible" duplicates... I wonder if the problems you're experiencing are related to this function? Note that it's "possible" duplicates, indicating that LR isn't positive it is, but it's going to ignore it anyway.


Perhaps this function isn't working quite up to snuff, huh? Have you tried making sure this option is unchecked and seeing if these problems still persist?

Richard Caccavale
2007-11-21 23:34:10
random bob,


I am not sure about James, but I have tried with, and without that option checked. Nevertheless, I have my D200 set to number continuously, so there should be no duplicates on a card, even 8GB, when shooting RAW. I just find it safer to copy in the finder and then import.


Don't feel bad about being an Aperture user. I still have 10k images in Aperture and I miss it sometimes. I think the workflow is better, but I switched to LR for the RAW conversion, which I deemed better, and that is what it is all about for me.

Skip Harris
2007-11-23 20:28:07
There are also printing issues, at least there is for me. Have Leopard 10.5.1, Lightroom 1.3 with an Epson 2200. Color management is not working with this combination. Prints have a color cast and are dark. I have seen posts in various other forums from others with the same hardware/software combination as mine that describe the same issues. But I have not seen anything definitive from Adobe, Epson, or Apple that state this is a problem and it will be resolved. Have no issues printing from Photoshop or other programs, it is just a Lightroom issue ... Skip
dion
2007-12-04 16:47:48
Leopard 10.5.1, LR 1.3, Epson R2400. I found that in print settings that if I use Colorsync as apposed to no color management when using printer profiles my prints look fine. Anyone try that yet?
Walter
2007-12-07 08:23:04
I recently upgraded to Apple’s Leopard OS for my Mac Pro. I also updated to Lightroom 1.3. I waited until 1.3 was available before upgrading the Mac OS. Since upgrading, printing to my Epson Stylus Pro 3800 has been a problem. I updated the printer driver to the latest 10.5 compatible driver from Epson’s website but I still have problems. Prints no longer match what I see on my monitor. Colors are weak and washed out, lacking all saturation. I have tried increasing saturation via Lightroom’s saturation control but it has no effect on the printer’s output. I am using ICC profiles for my paper/printer combination and set printer color control off. I have tried exporting images to Photoshop and printing from Photoshop with the same results—unsaturated, washed-out prints.


Has anyone else encountered printing problems with these latest updates and does anyone have a clue as what is going on?