Adobe Photoshop Lightroom 5.2 and Camera RAW 8.2 Released

A while ago, Adobe has made the Lightroom 5.2 and Camera RAW 8.2 Release Candidate version update available. I restrained from updating my Lightroom 5 version to the RC update and decided to wait for the full release. Today, final Lightroom 5.2 and Camera RAW 8.2 updates are finally available for download and fix a number of bugs while also adding support for several newest cameras. New Camera RAW features are only available for Photoshop CC users. CS6 users are also eligible for the update, but Camera RAW 8.2 for Photoshop CS6 only adds new camera/lens support and fixes bugs. It does not add new features.

Adobe Photoshop CS6

As always, Lightroom 5.2 and Camera RAW 8.2 updates are very similar. Having said that, there are some differences. In this quick overview, I will provide you with information for both.

1) Corrected Bugs

Here is the list of bugs and issues addressed in the Lightroom 5.2 update (quoted from Adobe’s blog):

  • Output Sharpening and Noise Reduction were not applied to exported images that were resized to less than 1/3 of the original image size.
  • Slideshow Exporting process fails for time-lapse sequences.
  • Unable to export a Book. This only occurred after a customer deleted a background photo.
  • Catalog containing images processed with PV2003 were adding a post-crop vignette when catalog upgraded to Lightroom 5.
  • JPEG decoding produced a red color cast.
  • Unable to scroll through photos when in Full screen mode. This only occurs when more than 1 photo is selected.
  • “Store presets with this catalog” preference is not preserved when upgrading catalog from previous versions of Lightroom.
  • Crash when scrubbing Size slider with existing spot selected.
  • Landscape crop not maintained on portrait oriented photos.
  • Pressing the Reset button while holding the Shift key results in an internal error.
  • Crash when attempting to move brush spots.
  • Gray area is shown when zooming in/out after cropping image.
  • A row of vertical artifacts appears along bottom edge of photo when applying Grain.
  • Defringe Color Sampler is inaccurate on photos that have Upright applied.
  • All of the images on a Compact Flash card did not appear in the Import Dialogue.
  • Metadata panel displayed incorrect information after modifying published photo. Please note that this only occurred when metadata was changed after the photo was published.
  • Soundtrack does not fade at the end of a slideshow.
  • 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.

Several of these bugs and issues were criticized heavily by our team as well as our readers. It is nice to see Adobe finally got around to fixing them. The performance of Lightroom 5.2 update will be further tested in a dedicated section in our Lightroom 5 review as soon as I properly test it.

Here is the list of corrected bugs and issues in Camera RAW 8.2 update:

  • JPEG decoding produced a red color cast.
  • Bridge always recomputed cropped image thumbnails when lens profile corrections are enabled rather than when necessary.
  • Feathering for healing brush operations were not the same strength as feathering for circular spot removals.
  • When selecting and adjusting multiple images, the Crop adjustment was not applied to the most selected image.
  • Local adjustment brush pin were not redrawing properly after moving from one location to another.
  • When using Camera Raw as a Filter in Photoshop CC, pressing the “Cancel” button on a Smart Object would rest the Smart Object to default settings.
  • There was no visual for the Heads-Up Display when control-dragging to resize a healing brush. This only occurred when the “Show Overlay” option is turned off.

2) New Camera Support

The following cameras have gained tethering support in Lightroom 5.2:

  • Canon EOS 6D
  • Canon EOS Rebel T5i / EOS 700D / EOS Kiss X7i
  • Canon EOS Rebel SL1 / EOS 100D / EOS Kiss X7
  • Nikon D7100

RAW image files from the following cameras are now supported in both Lightroom 5.2 and Camera RAW 8.2 unless stated otherwise. Note the support for recently announced Fujifilm X-A1 (Lightroom 5.2 only) and Olympus OM-D E-M1 cameras.

  • Canon EOS 70D
  • Canon PowerShot G16
  • Canon PowerShot S120 (preliminary support)
  • Casio Exilim EX-ZR800
  • Fujifilm FinePix HS22EXR
  • Fujifilm FinePix HS35EXR
  • Fujifilm FinePix S205EXR
  • Fujifilm X-A1 (Lightroom 5.2 only)
  • Fujifilm X-M1
  • Leica C (Typ 112)
  • Olympus OM-D E-M1 (preliminary support)
  • Panasonic Lumix DMC-GX7
  • Panasonic Lumix DMC-FZ70
  • Panasonic Lumix DMC-FZ72
  • Pentax Q7
  • Pentax K-50
  • Pentax K-500
  • Sony DSC-RX100 II
  • Sony A3000
  • Sony NEX-5T

3) New Lens Profiles

Profiles for the following lenses have been added for both Lightroom 5.2 and Camera RAW 8.2:

  • Sony E 35mm F1.8 OSS
  • Hasselblad LF16mm F2.8
  • Hasselblad LF18-55mm F3.5-5.6 OSS
  • Hasselblad LF18-200mm F3.5-6.3 OSS
  • GoPro Hero 3 Black Edition
  • GoPro Hero 3 Silver Edition
  • GoPro Hero 3 White Edition
  • Leica TRI-ELMAR-M 16-18-21 mm f/4 ASPH
  • SIGMA 18-35mm F1.8 DC HSM (Canon EF mount)
  • SIGMA 120-300mm F2.8 DG OS HSM (Canon EF, Nikon F, Sigma mount)
  • SIGMA 30mm F1.4 DC HSM (Nikon F mount)
  • SIGMA 60mm F2.8 DN (Olympus m4/3, Sony E mount)
  • SIGMA 17-70mm F2.8-4 DC MACRO OS HSM (Pentax K, Sony A mount)
  • SIGMA 35mm F1.4 DG HSM (Pentax K, Sony A mount)
  • Nikon 1 NIKKOR 32mm f/1.2
  • Sony DSC-RX1R

4) New Features

    Here are the new features Lightroom 5.2 gains over version 5:

  • A Smoothness adjustment slider has been added to the Detail Panel under Color Noise Reduction. This helps to reduce low-frequency color mottling artifacts
  • Refinements to the Spot Healing Tool:
    1. New Feather control
    2. Auto find source method now works better for images with textured areas like rocks, bark, and foliage
    3. Auto find source method now prefers source areas within the crop rectangle
  • Auto Exposure has been improved to be more consistent across images and across different image sizes.
  • Smart Preview size has been updated to 2560 pixels on the long edge.
  • Refinements to the Local Adjustment Brush:
    1. Right Click (PC) / Control-click (Mac) on a brush adjustment pin to bring up a context menu to duplicate or delete
    2. Control+Alt+Drag (PC) / Command+Option+Drag (Mac) on a brush adjustment pin to clone (duplicate) that adjustment

Here are the new features found in Camera RAW 8.2 that can be accessed by Photoshop CC users only:

  • The Histogram is now interactive. This enables the ability to click and drag on the Histogram to adjust the Blacks, Shadows, Exposure, Highlights, and Whites sliders.
  • A Color Smoothness adjustment slider has been added to the Detail Panel. This helps to reduce low-frequency color mottling artifacts.
  • Added new “rectangle mode” to white balance eyedropper tool. Click-and-drag with the eyedropper tool to define a rectangular pixel area. Upon releasing mouse, Camera Raw will use all the pixels within the marked rectangle to set the global White Balance.
  • Workflow presets are now available and can be selected by context-clicking the workflow link.
  • Presets have been added to the Save dialog box.
  • Auto Exposure has been improved to be more consistent across images and across different image sizes.
  • Refinements to the Spot Healing Tool:
    1. New Feather control
    2. Auto find source method now works better for images with textured areas like rocks, bark, and foliage
    3. Auto find source method now prefers source areas within the crop rectangle
  • Refinements to the Local Adjustment Brush:
    1. Move brush adjustments by clicking and dragging on brush adjustment pins
    2. Right Click (PC) / Control-click (Mac) on a brush adjustment pin to bring up a context menu to duplicate or delete
    3. Control+Alt+Drag (PC) / Command+Option+Drag (Mac) on a brush adjustment pin to clone (duplicate) that adjustment o Alt+Click (PC) / Option+Click (Mac) on a brush adjustment pin to delete the adjustment

5) Download and Information Links

You can read more about Lightroom 5.2 update by following this link. More information about Camera RAW update can be found here.

To update Lightroom, you can either use the “Check for Updates…” function in the Help menu or click here to download version 5.2 manually. Mac OS users should click here to download the update. To update Camera RAW plug-in to 8.2, you must own Photoshop CS6 or CC and use the built-in update mechanism.


  1. 1) Chattanooga Charlie
    September 17, 2013 at 7:27 pm

    I got the upgrade notice as I was commenting on your post about the ever present LR bug that has never been present for me.

    Unfortunately the Loupe Info Overlay still has the same bug that it’s always had.

    • September 17, 2013 at 7:45 pm


      that ever present LR bug never happened to me – with Lightroom 3, 4 and 5 – until about a month ago, maybe less. It is now a huge pain to deal with, very annoying. Does not happen very often, but too often for me to simply disregard nonetheless.

  2. 2) Dan
    September 17, 2013 at 8:26 pm

    “Move brush adjustments by clicking and dragging on brush adjustment pins”


  3. 3) Marat Yeshtukov
    September 17, 2013 at 9:35 pm

    Surprisingly there is no iPhone 5s support in Camera RAW

  4. 4) Torsten
    September 18, 2013 at 12:32 am

    It seems to me the update has made Lightroom noticeably faster; changing to the develop module for instance or browsing photos seems to work better on my machine now. Is this just a placebo effect or have others noticed it too?

  5. 5) darrell
    September 18, 2013 at 1:14 am

    Can anyone advise why nikon raw files always seem to have skin tones too warm in lightroom

    • September 18, 2013 at 2:19 am

      the way you see skin tones in Lightroom depends on your monitor calibration, white balance, light and Lightroom’s camera calibration profile. It is also a matter of taste. If you are unhappy with how skin tones look with Adobe Standard profile in Camera Calibration tab (Develop Module, right-side panel), change it to something else, like Camera Portrait v4, and see if that makes the right difference for you.

      • 5.1.1) darrell
        September 18, 2013 at 6:52 am

        I was really wanting to find out if this is a common problem , I have a wide gamut monitor which is regularly color managed/profiled

        • September 18, 2013 at 6:55 am

          It is not a problem as such, Darrell – again, it depends on your taste. What’s too warm for you may be just perfect for someone else. Usually, I do my own color post-processing, so it has never been a problem for me. Again, try changing the profile in Lightroom. There are more than one way it can render RAW images by default. Adobe Standard profile is just one and you can easily use any other.

      • 5.1.2) Chris Zeller
        September 18, 2013 at 8:39 am

        I think the real problem with lightroom (and all ACR products) is that it ignores Nikon Picture Controls. I ‘m sure users of all other brands have the same issues. What is the point of applying any kind of default develop settings in camera if ACR is going to ignore them. My photos always look better in the preview image than after importing to LR.With work, I can get them looking alright–and wityh a lot of work get them even better but I’d rather start with the Nikon PCS and go from there.

        A lthough I apply presets upon import, I just can’t seem to find a preset (or make one) that comes anywhere near what Nikon does in camera. I know I can use Capture NX2 to import, but then I would loose the functionality of LR.


        • Sebastiano
          September 18, 2013 at 8:46 am

          Hi Chris ,

          had the same problem with D70s, but almost all changed with D300. Which camera do you use?

        • Chattanooga Charlie
          September 18, 2013 at 10:30 am

          Chris, thanks. Thought surely, someone would mention this. I am pretty sure this is true for most Nikon DSLRs. I’ve only had the D80, D300, D5100, D7000, & D7100.

          It would be great if Nikon (and others) added the camera’s picture control info in the raw file & that could be used as a preset to get the same results as the preview/jpg IF desired.

          • Sebastiano
            September 19, 2013 at 2:11 am


            The problem is, IMHO, that Adobe made a choice, and a reverse engineering process.
            Nikon’s way of rendering the NEF is a Nikon choice, and despite the matter this way is “optimized for Nikon DSLR … etc, etc ..” I think, most of all, the choice for Adobe to differentiate its camera profiles from Nikon’s is to have a different product on the RAW converter market.

            In any case, Nikon hadn’t supported Adobe to develop camera presets, so Adobe made a reverse process, trying to develop presets that “look like” Nikon way.

            In my opinion this is an opportunity, not a defect, since you can try opening your photos both with View NX and ACR, and then choose the rendering you like more.
            A mean to capture “true colors”, meaning an exact copy of the scene captured, never have existed, neither with films, so the way you render colors may be interpreted also as a creative opportunity.
            Of course, it’s a totally different matter in case you have to prepare something that represents exactly the tones and colors of the scene.
            For example, let’s think about a brochure for make up, or dresses.
            If the “red” of the nail polish you’re printing is not “the exact copy” of the reality this could be a problem.

            But we haven’t also to forget that the light under we watch any object can “cast” it. So, the cases when you’ve photographed pink and your render is “casted toward” violet apart, there are many ways to put control on the “color management” chain, from shooting to viewing via PC (may be the more critical), to printing (the final result).

            In my tests I’m seeing that if you get an accurate WB measurement the renders ACR 8.1 and VNX2 do of my 14bit NEF done by my D300 differ only a bit, or in a way you can manage.
            Totally different matter with D70s. So critical the only way “not to false” the colors I shooted was to opern first in VNX, then export as a 16bit TIFF Adobe RGB to Photoshop or Lightroom.


            • darrell
              September 19, 2013 at 4:05 am

              I understand what your saying but shouldn’t the prime objective of any photo editing software to be able to reproduce colour tones as seen by the camera with the minimum of adjustment. My thoughts are that Its not difficult for a software house to provide endless adjustments for the user but the real goal should be to produce software that gets great results with a minimum of human intervention. We can then all spend less time in front of our screens

  6. 6) Sebastiano
    September 18, 2013 at 1:47 am

    Hi Romanas,

    do you know if the “old CTRL Z” bug has been fixed to?
    I mean

    Thanks, S.

    • September 18, 2013 at 2:21 am


      here’s hoping that it has. In any case, the best way not to mess things up too much should this bug happen (and it tends to happen with the rest of the nasty things, too) is to, first, use History and restore the look of the image to how it is supposed to be and, second, get out of Lightroom as soon as you can and perhaps even restart your computer.

      • 6.1.1) Sebastiano
        September 18, 2013 at 2:41 am

        Thank you for this preciuos piece of advise!

        p.s. having followed the link for LR 5.2 download I haven’t found the one for the 30 days trial version.
        I should still install the 5.1 trial (30 days), but I have no time for my photos in these weeks .. too much at work ;)

        Bye, S.

  7. 7) mayank
    September 18, 2013 at 3:52 am

    Hello Every one,
    does any one has any new if nikon is getting D610 in near future

    pls advise ASAP


    • September 18, 2013 at 5:25 am

      Hey Mayank,
      I heard rumors about the D610 on nikonrumors
      They said it will be announced soon and they also think it is just a D610 without the oil problem. If that’s the case you could get the D600 for cheap. I think Nikon is not deliberately building false cameras.

    • 7.2) Chattanooga Charlie
      September 18, 2013 at 10:34 am


      I would hope that they would include the italics “i” button that the D7100 has. That is a really great tool. My improvement for this button would be the ability to customize what is included that can be controlled from there.

      If you shoot many different subjects, it’s almost worth the cost of the camera to get this control without having to access several menu screens.

  8. 8) dinpin
    September 18, 2013 at 10:21 am

    Hey Romanas,

    just to mention a typo. you must own (Lightroom) CS6 or CC and use the built-in update mechanism. You meant photoshop : )

    • September 18, 2013 at 10:22 am

      Thank you! Will fix it right away. Happens when I’m in a hurry. :)

      • 8.1.1) dinpin
        September 18, 2013 at 10:27 am

        you are welcome. By the way thank you for the information.

        Pitty that from all the updates the one I wanted the most is still not present. The lens correction profile for the Nikon 18-35g lens.

        • GaryK
          September 22, 2013 at 8:23 am

          I too am disappointed that the Nikon 18-35mm G lens still doesn’t have profile support. This is a popular lens which has been out for a while, now.

  9. September 18, 2013 at 6:41 pm


    I installed Lightroom 5.2 and when trying to use the Nik HDR Efex Pro plugg-in I get

    The application did crash. Crash info file was generated in ‘/Volumes/Macintosh HD/Users/arg/Library/Preferences/Nik Software/HDR Efex Pro 2/2013-09-18t203628_787’

    Any thoughts or advice?


    • September 18, 2013 at 7:39 pm


      There is some evidence that Lightroom 5.2 is not the problem. Nik HDR Efex Pro 2 crashes as a stand-alone also. This is old Nik code on an old machine: Mac OS 10.7.5. Either installing Lightroom 5.2 is the culprit or an OS update did the damage.


    • 9.2) Kevmo
      September 21, 2013 at 2:43 pm

      I am having the exact same problem with exactly the same crash message. It also appears to be since installing Lightroom 5.2. I have not found a solution yet.

  10. September 19, 2013 at 1:54 pm

    I can confirm that “Output Sharpening and Noise Reduction were not applied to exported images that were resized to less than 1/3 of the original image size.” Bug is not fixed.

  11. September 24, 2013 at 6:15 am

    having the same issues with my Nik products , someone tell Google how to run photographic software please !!!!!

    • 11.1) Bob
      September 24, 2013 at 8:58 am

      Google changed the way Nik is distributing updates. You need to get their new release that’s available for all registered users, that has an automatic update module which brings down a new version that fixes the problem. The updater checks periodically and will update as new releases are available. You have to send an e-mail to Nik support, and they send you a link to the tool.

      I’m not to fond of the new way that Google is making us jump through hoops to get stuff, but the new installer/updater is a big improvement over the old Nik installation method.

  12. 12) Michael
    September 25, 2013 at 12:38 pm

    Is anyone else suddenly having an issue with importing CR2 files into lightroom after the update? I can’t seem to get any of my photographs to import now with the update in place.

  13. September 25, 2013 at 4:50 pm

    For those who have trial version of LR 5 installed, can we upgrade it to 5.2 following the suggested link?


  14. 14) David
    September 30, 2013 at 5:22 pm

    As quite a long term and very happy Elements user I wanted a better raw editor and catalogue so I took the plunge and have just purchased Lightroom 5, plus Windows 7 upgrade plus an extra 2GB of RAM. Following installation I was immediately invited to update to version 5.2. OK so far, although the update process seemed to take forever. Very disappointingly I only managed to open the program once. It now throws up an error message saying there was an unexpected error opening the catalogue. Getting around this has so far proved impossible. It seems to go through the motions of allowing me to create a new catalogue but nothing is actually created and the I just get the same annoying error message. Seems Adobe has a strange attitude to support – seems like you have to post a forum message and just wait on the off chance some one will respond. So next step may have to be undelete and try a reinstall and long winded update process. Perhaps version 5.2 is not the bug fix that it was meant to be? The question is how much time should I waste on this before admitting defeat and just ask Amazon for a refund. Very disappointing and so far a great waste of time.

    • 14.1) david
      October 8, 2013 at 1:22 pm

      Fixed – a full reinstall of Lightroom V5.0 followed by the 5.2 update seemed to fix this issue. Happy now, but wasted 4 hours messing around first.

  15. 15) Mandy
    November 8, 2013 at 1:01 pm

    Hi, so I have the updated LR 5.2 and every time I go to edit in PS CC I get the pop up error “This version of lightroom may require the photoshop camera raw plug-in version 8.2 for full compatibility.”

    I can’t figure out why it is doing this if I have the updated version.

    Thank you, Mandy

    • November 9, 2013 at 12:03 pm


      that probably means your Adobe Camera RAW plug-in for Photoshop CC needs to be updated to v8.2

  16. 16) deepak parmar
    May 14, 2014 at 6:46 am

    You are really dong great work, Keep it up

    Having one small query, I am looking forward to buy creative cloud membership to use Photoshop and Lightroom, but not able to find answer that photoshop and lightroom will have RAW plugin already installed or will have to install seperately from somewhere else.

Comment Policy: Although our team at Photography Life encourages all readers to actively participate in discussions, we reserve the right to delete / modify any content that does not comply with our Code of Conduct, or do not meet the high editorial standards of the published material.

Leave a Comment

Your email address will not be published. Required fields are marked *