Don’t worry, you didn’t miss a 5.1 release! ACR 8.1 was released a few weeks ago, and ACR 8.2 would usually be released with LR 5.2, so they’ve skipped a LR dot release number to avoid confusing us!
It is an RC at this stage – a release candidate – which means it has been tested, but they’ve got a little more work to do before the final release, so it’s not being sent out to everyone over the automatic updates quite yet. That said, it fixes a number of the really irritating bugs in 5.0, so it’s not a bad idea to upgrade early.
Here’s the download link you’ll need:
Lightroom 5.2 – Adobe Labs
So what’s new? Camera support, for a start:
- Canon EOS 70D (preliminary support)
- Casio Exilim EX-ZR800
- Fujifilm FinePix HS22EXR
- Fujifilm FinePix HS35EXR
- Fujifilm FinePix S205EXR
- Fujifilm FinePix F805EXR
- Fujifilm X-M1
- Phase One IQ260 (preliminary support)
- Sony DSC-RX1R (was already in 5.0, but the camera hadn’t been released, so they couldn’t announce it)
- Sony DSC-RX100 II (preliminary support)
And the good news is the most serious and widely discussed bugs have been fixed:
- Output Sharpening and Noise Reduction were not applied to exported images that were resized to less than 1/3 of the original image size.
- Catalog containing images processed with PV2003 were adding a post-crop vignette when catalog upgraded to Lightroom 5, which could result in the loss of Develop settings if an earlier history state was selected.
- Pressing the “Reset” button while holding down the Shift key (Adobe Reset) caused Lightroom to exit abruptly or show an error message.
- Incorrect photo was selected when trying to select a photo in segmented grid in Publish Services.
- The Esc key did not exit the slideshow after right clicking screen with mouse during slideshow playing.
- Import dialog remained blank for folders that contain PNG files with XMP sidecars.
- Metadata panel displayed incorrect information after modifying published photo. Please note that this only occurred when metadata was changed after the photo was published.
The first dot releases have historically had a few little extra features, and 5.2 is no exception:
- A Smoothness adjustment slider has been added to the Detail Panel under Color Noise Reduction. This helps to reduce low-frequency color mottling artifacts on some photos.
- Refinements to the Spot Healing Tool:
- New Feather control, by popular demand.
- Auto find source method now works better for images with textured areas like rocks, bark, and foliage
- Auto find source method now prefers source areas within the crop rectangle
- Smart Preview size has been updated to 2560 pixels on the long edge.
- Refinements to the Local Adjustment Brush:
- Right Click (Windows) / Control-click (Mac) on a brush adjustment pin to bring up a context menu to duplicate or delete
- Control+Alt+Drag (Windows) / Command+Option+Drag (Mac) on a brush adjustment pin to clone (duplicate) that adjustment
I look forward to hearing your comments! As with all release candidates, Adobe would appreciate your feedback at the Official Feature Request / Bug Report Forum. If you don’t already have an account, you can use Facebook, Twitter or Google details to log in.
Sometimes I’ve noticed that the develop module Navigator window is showing the wrong image, even if I’m not moving the mouse over photos in the bottom strip.. for example, it happens that I’m working on image A (removing spots, for example) and it keeps showing image B.. has this bug been solved?
BTW, great job for noise reduction and pulishing services bugfixes.. the second one was a hard one, from what I’ve understood..
I’ve seen that one before too Gianni. The occasions when I’ve been able to replicate it, it’s because I’ve floated over the filmstrip at the wrong moment. I haven’t run into it recently, but I’m not sure whether it’s actually been fixed.
Every time I move from one part of your website to another, I get a dialog popping up saying ‘blockUI requires jQuery 1.2.3 or later. You are using v1.10.2.’
Running Win8 with all updates.
Bob frost
Every time I move from one part of your website to another, I get a dialog popping up saying ‘blockUI requires jQuery 1.2.3 or later. You are using v1.10.2.’
Running Win8 with all updates.
Bob frost
Hmmmm, thanks Bob! I upgraded to WordPress 3.6 this morning, so maybe a plug-in’s conflicting. I’ll dig into it!
Found it, the currency converter plug-in needs to be updated (except it’s no longer being developed). I’ve turned it off for now so the issues should go away. Thanks for the heads-up.
I added some noise but it was still not applied to exported images as same as 5.0 dose.
Tell me more? When you say you added noise, I’m assuming you mean noise reduction, rather than grain? What size are you exporting to? What were the settings you used? Have you definitely got the RC version open?
I meant noise grain and exported to original size using 5.2 RC.
I think these two screenshots may help explain the problem I got.
I adjusted some settings and the image processed looks like #1 screenshot attached below.
Then I just exported it to original size. I opened the exported image and resized the image browser window to fit the Lightroom window so that you can easily find out a big difference between the two ones.
It seems that the Noise Recution and Sharpening functions didn’t work (at least didn’t work correctly), and the Noise Grain function didn’t work completely.
Grain is completely different to the noise reduction issue that was fixed in 5.2 RC. If you’re going to compare, you’ll need to use the same program and compare at 1:1 view. Try importing your exported photo into Lightroom and comparing it 1:1 with the original edited version to see if there’s really a difference.
I got it, thanks for your reply.
I just imported the exported photo and compared it with the raw version at 1:1 view, I found that there was no difference between the amounts of grain of them.
So the grain function works fine, and why I saw a difference is because of algorithm of resizing image. Maybe MassiGra (a photo browser) uses a different algorithm from Lightroom.
Then I changed to fit view to watch two photos (a raw and a jpg) separately. To my surprise, I saw a difference between amounts of grain of them. And I captured the screen.
Please click the photos below to see the full-version for easier comparing.
So, I think there maybe a problem of Lightroom when resizing raw photo, which confuses me when processing raw photo.
That’s as designed – you’ll find the same in most programs. Grain (and noise reduction and sharpening, for that matter) vary depending on the zoom, which is why you should always use 1:1 to get an accurate view. You’ll likely find that if you view them both in Library, after zooming into 1:1, that they’ll look more similar even in Fit view. That’s due to a difference in the way the preview is rendered. Library takes the highest resolution prerendered preview and downsizes that, whereas Develop downsizes the raw data on the fly.
I see. It’s designed for performance, right?
Yes, that’s right
Thank you! 🙂