Lightroom 2.0 beta Released
Adobe Lightroom 2.0 beta Screenshot showing some new features in action (in this case, selective-area desaturation and a post-crop vignette)
Adobe Lightroom 2.0 beta
Screenshot showing some new features in action
(in this case, selective-area desaturation and a post-crop vignette)

I like to post right away when there's a new release of Adobe Lightroom, but alas, I've been on vacation for the last few days, and I was at the car-rental return at the Amami Ooshima Island airport when Lightroom 2.0 beta was released earlier this afternoon.

The 2.0 beta has a lot of exciting new features you can read about elsewhere (links below), but the ones I'm most excited about are localized corrections (you can “paint” exposure, saturation, tint, etc.) and multi-monitor / multi-window support. Now you know why I finally succumbed and added a second monitor a few months ago.

For details:

· John Nack's Blog (overview, lots of details, lots of links)
· Official announcement
· The download page

I'll repeat the main points you need to understand before using it:

  • Adobe is making it available so that you can kick the tires; it's not recommended for production work. By design, you can't work with your Lightroom 1.x catalogs in the 2.0 beta. Furthermore, you can't be sure that the 2.0 beta catalogs will be completely usable in the “real” 2.0 (which will be released, presumably, some time during the summer).

  • It's free for Lightroom 1.x customers (the beta expires August 31st, by which one presumes the real Lightroom 2.0 will have been released). Anyone else can try it freely for 30 days, just as with the currently-latest production version, Lightroom 1.3.

  • You can install and use both Lightroom 1.x and the 2.0 beta side-by-side on the same computer.

My existing Lightroom export plugins (for: Zenfolio,  ·  SmugMug  ·  Flickr  ·  Picasa Web) should work fine in the beta. Plugins are much easier to install in 2.0: you place them anywhere on your system you like, then point to them via the new File > Plugin Manager dialog.

Over the last few months that I've been working with Lightroom 2.0 development, I've been rearchitecting my plugins to both take advantage of new plugin support in 2.0, and to make it easier for me to add features across all my plugins (and to add new plugin destinations). Unfortunately, I've had a cold for so long that I'm not ready to release them yet, so it'll still be a while. But as I said, my original plugins for Lightroom 1.x should work fine in the 2.0 beta.


All 10 comments so far, oldest first...

Aperture 2.1 has a plug-in based architecture which allows localized, “pixel-level” editing as well.

Description here: http://www.robgalbraith.com/bins/content_page.asp?cid=7-9308-9356

I wonder how close the functionality is between the two.

One disadvantage with the way Aperture handles this is that the program basically hands off the original RAW file to the plug-in, and after the adjustments are made it is “re-imported” from the plug-in, so changes made by the plug-in are not non-destructive, ie they ARE destructive and are not undo-able. It’s almost exactly like exporting to Photoshop and then re-importing, but it all happens within Aperture.

How does LR 2 handle this?

Lightroom’s local corrections are all completely non-destructive. I’ve never used Aperture, although I’ve heard it questioned whether its plugin architecture is as you described, or merely whether the currently-available plugins work that way. I don’t know. Apple is pretty smart, so either way, I’m sure it’s a stepping stone to greater things. —Jeffrey

— comment by Zak on April 2nd, 2008 at 10:33pm JST (9 years, 9 months ago) comment permalink

What about soft proofing in the print module? Nothing?

Jeffrey, with all your great articles about color management, I’m surprised you’d let this one slip past 🙂

I’ve got to admit that I don’t know exactly what the term “soft proofing” means. I don’t do all that much actual printing, and when I do, it’s just with a cheap consumer printer, so I guess I’ve never had the motivation to pay attention. Perhaps there’s a cyclical cause/effect loop going on here…. —Jeffrey

— comment by Peter Davis on April 3rd, 2008 at 1:56am JST (9 years, 9 months ago) comment permalink

I don’t know, Apple hasn’t seen fit to give me a prototype iPhone capable of working in Japan, or a Macbook Air to review for my extremely influential blog. How smart could they be?

— comment by Zak on April 3rd, 2008 at 7:25am JST (9 years, 9 months ago) comment permalink

I love you exporter to Zenfolio, but I am getting an “Internal Plugin Error” after clicking on login to Zenfolio. Followed by the message saying “logon aborted” and then something about a global all_id.

Any thoughts on how to get around this?

I am using LR Beta 2.0, Mac OS 10.5.2 on a Macbook Pro.

Thanks in advance!

Oops, this was due to a touch of stupidity on my part. I’ve pushed a new version that fixes it. Thanks for the heads up. —Jeffrey

— comment by Chris Pal-Freeman on April 4th, 2008 at 9:36am JST (9 years, 8 months ago) comment permalink

I am trying to upload photos from lightroom 1.4.1 to smugmug and it uploads about 12/44 pictures and then gets and error code () saying that it had to abort. what can be wrong?

— comment by Jill Yablon on April 27th, 2008 at 9:31pm JST (9 years, 8 months ago) comment permalink

I am still using LR 1.3 and I am also getting mysteriously aborted uploads to SmugMug. I fixed one issue by turning off the screen saver, and thought I was OK. But I have always been uploading medium res files (6 MP). Last night I attempted 166 Hi Res (12.1 MP) files and the system stalled at 77. However, all backup .jpgs were written to backup USB hdd. This makes me think it’s either a SmugMug issue, or a plug-in issue. Any ideas?

— comment by Gary Salles on April 29th, 2008 at 1:32am JST (9 years, 8 months ago) comment permalink

Wondering if we will have to pay for the LR2 (once released) after purchasing 1.4? Sorry if this is off topic. Btw, I lived in Jpn for many years (from pre-bubble) before returning to Australia.

— comment by Rudi on May 15th, 2008 at 7:34am JST (9 years, 7 months ago) comment permalink

I need your help. Again. You were kind to us a few months ago, when I was trying to configure Lightroom for our New England conservation center’s treatment studio. Now for the sequel…

We need to apply a custom camera profile, made with a device-level target. I want to assign the profile to the raw file, then convert it to either Profoto or AdobeRGB. I know that a characterization can be achieved using the ACR/raw adjustment tools found in the develop module. However, these don’t provide nearly enough accuracy. The profile we’ve generated does. Using it in our workflow would also offer less opportunity for error and inconsistency. Our focus is accuracy, consistency and workflow. How can I modify Lightroom to incorporate our custom profile (we’re ony using one)? Or can Lightroom be altered to allow me to add the profile as an option?

We’re determined to use ony Lightroom; adding more steps and applications to our workflow is highly undesirable (few of our staff are comfortable with Photoshop).

Thanks, Matt

— comment by Matt Pearson on May 29th, 2008 at 5:06am JST (9 years, 7 months ago) comment permalink

I’ve downloaded the trial and I really love it. My big problem now is trying to work out what to do until release – is it really sensible to purchase Lightroom 1 so that I can play with Lightroom 2.0 until the end of August? I’d happily preorder Lightroom 2.0 instead if that were an option…

If you’re happy using the 2.0Beta a bit longer, I can send you a serial number you can use to extend the 30-day trial (anyone with Lightroom 1.x can do this for up to five different people, as per this page). —Jeffrey

— comment by Sylvia on June 29th, 2008 at 8:21pm JST (9 years, 6 months ago) comment permalink

Can you send me the code? I heart lightbox 2.0 and would love to extend my trial period …

— comment by Mimi on October 1st, 2008 at 3:08pm JST (9 years, 3 months ago) comment permalink
Leave a comment...


All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.


You can use basic HTML; be sure to close tags properly.

Subscribe without commenting