Lightroom CC 2015.3 / 6.3 now available

Lightroom CC 2015.3 and Lightroom 6.3 are now available on Adobe.com.  The goal of this release is to provide additional camera raw support, lens profile support and address bugs that were introduced in previous releases of Lightroom.  This release also restores the Import experience available prior to Lightroom 6.2.

Thank you for all your feedback and passion for Lightroom.

New Camera Support in Lightroom CC 2015.3 / 6.3

  • Canon EOS M10
  • Canon PowerShot G5 X
  • Canon PowerShot G9 X
  • Fujifilm X-T1 IR
  • Leica SL (Typ 601)
  • Sony RX1R II (DSC-RX1RM2)

New Tethered Camera Support in Lightroom CC 2015.3 / 6.3

  • Canon EOS 5DS
  • Canon EOS 5DS R
  • Canon EOS T6i / 750D
  • Canon EOS T6s / 760D

New Lens Profile Support in Lightroom CC 2015.3 / 6.3

Mount Name
Apple iPhone 6s back camera 4.15mm f/2.2
Apple iPhone 6s front camera 2.65mm f/2.2
Apple iPhone 6s Plus back camera 4.15mm f/2.2
Apple iPhone 6s Plus front camera 2.65mm f/2.2
Canon EF Canon EF 35mm f/1.4L II USM
Canon EF Canon EF 300mm f/2.8L IS II USM
Canon EF Canon EF 300mm f/2.8L IS II USM +1.4x
Canon EF Canon EF 300mm f/2.8L IS II USM +2.0x
Canon EF Canon EF 400mm f/2.8L IS II USM
Canon EF Canon EF 400mm f/2.8L IS II USM +1.4x
Canon EF Canon EF 400mm f/2.8L IS II USM +2.0x
Canon EF Canon EF 400mm f/4 DO IS II USM +1.4x
Canon EF Canon EF 400mm f/4 DO IS II USM +2.0x
Canon EF Canon EF 400mm f/5.6L USM
Canon EF Canon EF 400mm f/5.6L USM +1.4x
Canon EF Canon EF 400mm f/5.6L USM +2.0x
Canon EF Canon EF 500mm f/4L IS II USM
Canon EF Canon EF 500mm f/4L IS II USM +1.4x
Canon EF Canon EF 500mm f/4L IS II USM +2.0x
Canon EF Canon MP-E 65mm f/2.8 1-5x Macro Photo
Canon EF SIGMA 20mm F1.4 DG HSM A015
Canon EF Zeiss Milvus 1.4/50 ZE
Canon EF Zeiss Milvus 1.4/85 ZE
Canon EF Zeiss Milvus 2/35 ZE
Canon EF Zeiss Milvus 2/50M ZE
Canon EF Zeiss Milvus 2/100M ZE
Canon EF Zeiss Milvus 2.8/21 ZE
Canon EF Zeiss Otus 1.4/28 ZE
Canon EF-M Canon EF-M 15-45mm f/3.5-6.3 IS STM
DJI ZENMUSE X3 HG310 (RAW + JPEG)
DXO DxO ONE
Leica M Voigtlander VM 35mm f/1.7 Ultron
Nikon F Nikon AF NIKKOR 24-85mm f/2.8-4D IF
Nikon F SIGMA 20mm F1.4 DG HSM A015
Nikon F Zeiss Milvus 1.4/50 ZF.2
Nikon F Zeiss Milvus 1.4/85 ZF.2
Nikon F Zeiss Milvus 2/35 ZF.2
Nikon F Zeiss Milvus 2/50M ZF.2
Nikon F Zeiss Milvus 2/100M ZF.2
Nikon F Zeiss Milvus 2.8/21 ZF.2
Nikon F Zeiss Otus 1.4/28 ZF.2
PENTAX Asahi PENTAX Super-Takumar 28mm f/3.5 M42
PENTAX Asahi PENTAX Super-Takumar 50mm f/1.4 M42
PENTAX SIGMA 18-300mm F3.5-6.3 DC MACRO OS HSM C014
SONY A SIGMA 18-300mm F3.5-6.3 DC MACRO OS HSM C014
SONY Sony DSC-RX1RM2
SONY FE Zeiss Loxia 2.8/21
SIGMA SIGMA 20mm F1.4 DG HSM A015

Fixed Bugs:

Installation Instructions

Please select Help > Updates to use the update mechanism in the Creative Cloud app.

For customers that started using Lightroom in 6.2, please click here for an orientation to Import.

Direct Download:  Windows | Mac

Give us feedback

Once you’ve updated to the latest version of Lightroom, don’t forget to leave us feedback about your experiences. Lightroom wouldn’t be what it is today without our passionate and loyal customers around the world. Giving us regular feedback helps us to find and fix issues that we may otherwise not know about. We are listening.

Here are a few ways that you can send us feedback:

Report bugs and suggest features

Discuss workflow and get help with how-to questions or basic troubleshooting 

Thanks!

141 Responses to Lightroom CC 2015.3 / 6.3 now available

  1. Cool cool. Is the lens profile for Tamron 15-30 fixed? LR doesn’t recognize it when choosing auto in the lens correction. So I have to manually choose the tamron profile.

  2. Thanks for restoring some of the functionality (and there are improvements like being able to pick up keywording (I don’t think that was there before. However, I find the shaded previews with the big tick completely unhelpful. Is there a way of turning this off so that NEW photos are as before (bright) and PREVIOUSLY imported are the ones that are shaded. This works SO much better for me.
    Best
    Chris Tribble

    • They didn’t restore that? Yeesh.

      Yes. Having a Grid of HUGE checkmarks instead of being able to see, oh, I don’t know… Maybe the actual images you want to import makes SO much sense.

      End sarcasm.

    • Emile says:

      Huh? I’m totally underwhelmed by 6.3 seeing the amount of time they took and especially the amount of time we, the end-users, spent living through this mess, but at least they completely restored the import dialog in 6.3 for Mac – no big tick marks here.

    • Simon King says:

      Agh! I thought they were bringing that back!!

      why not , the new tick not only stops you seeing what the image is it is ambiguous and utterly unhelpful. Please restore (or make prefs to be able to) just as Chris says

      thanks

    • David Madison says:

      My Windows version has the old style check marks restored

  3. Bill Simmons says:

    Once again, my Adobe Application Manager just has a spinning wheel when I search for this update for my Mac. For the last update, I had to remove some file from a hidden library. It looks like I will have to look up and re-do that process just to get the update manager to function. This is a major PITA. As part of my CC subscription, Adobe should be reliably informing me of available updates, not pushing out this buggy interface. Unbelievable.

  4. Jerry says:

    My CC menubar drop down shows no update for Lightroom CC (2015).
    Btw, my Lightroom app’s About Adobe Photoshop Lightroom CC… shows I’m using 2015 2.1 Release

  5. Tobias says:

    if you now could fix the speed issue that would be great

  6. I think I will wait some weeks before installing any updates from Adobe.

  7. Any idea when will it be available for CC subscribers in Saudi Arabia? I can’t wait to get the memory card auto-eject back.

  8. lordmac says:

    but …… the new Nikon D7200 ??????

  9. Steve Miller says:

    I liked the new import. I guess I was one of the few. The old one is not as good.

    • Jake says:

      I agree, the new import feature was way better than the old one. I am disappointed they changed it… It looks like they are easy to manipulate. I feel sorry for the people at adobe who can’t handle pressure. I am not happy with their decision to revert back to the old method. They should have a way to interchange between the two if that is possible.

  10. Joe Louis says:

    Well it’s about time

  11. Jake says:

    I am disappointed you guys caved to people who can’t handle change. Is there a way to use the New and better import feature that you guys disappointingly removed? If so then I am happy, if not I remain deeply disappointed.

    • BK says:

      Jake, it’s far from being an inability to handle change – valuable functionality was removed on the 6.2 import dialog (auto-eject card, move images, preview of filename, visibility of filenames, and much more) which seriously affected the workflow of established users who had been using these options since the very early versions of LR.

      While it’s understandable that Adobe would want to try and simplify certain aspects, in this instance they went too far.
      Perhaps you’ve not seen the main thread on this issue?
      http://feedback.photoshop.com/photoshop_family/topics/new-update-6-2

      Far from being “easy to manipulate”, I applaud Adobe’s decision to undo their previous work and revert to the original dialog.
      There are surely few corporations of comparable size who will listen and act on their customers’ complaints – this is a Very Good Thing and a welcome move away from the “you’ll have what we give you” approach of others – Mozilla (Australis interface on Firefox) and MS (ribbon interface), I’m scowling at you…

  12. Gordon Brice says:

    Just wondering when you will include lens profiles for other mobile phones? I have the LG G4 H815 which has a very good F1.8 lens and what test that have been done by various magazines rate the LG4 camera lense to be better than iPhone6!!!!

  13. Örjan says:

    Nothing to fix the “Server busy” problem at start?
    I have never seen this problem before, not until LR 6.
    Now “Server busy” every 3 start or so. Have to start other program or alt/tab other program to make the pictures to load. Like some type of workaround.

  14. Still no update to restore tethered capture for Nikon SLRs on Mac OS X El Capitan? Weak.

  15. B. Jefferson Le Blanc says:

    Lightroom 6.3 is off to a great start—not. The downloaded patch installer won’t work with my copy of Lightroom 6.1.1. I downgraded from 6.2 because it was so yucky. Do I have to upgrade to 6.2 again in order to get the 6.3 patch to work? It would be nice if they told us such things. Better would be a complete install of 6.3 instead of a patch. But, obviously that’s too much to ask. So, Adobe, add insult to injury while you’re at it. The bad PR rolls on as the development team still can’t seem to get out of it’s own way.

    • David Miller says:

      I am at a loss on how to update perpetual LR 6.0 to perpetual LR 6.3.

      On Adobe site, I go in circles and circles, getting nowhere. Or, know where
      Frustrating ! !

      Just to get perpetual LR 6,0 in the first place was a nightmare.

      A friend and colleague of mine tried, and succeeded, after several hours, working with Adobe chat. Me….I cannot even find Adobe chat for this issue.

  16. B. Jefferson Le Blanc says:

    P.S. I get the error message, “Update is not applicable. Error Code: U44M2P28.”

    • Hi Jefferson,

      It looks like this forum thread addresses the issue you’re having, with a proposed solution:

      I have Lightroom 6.0 and can not upgrade to 6.01 or 6.1.

      • B. Jefferson Le Blanc says:

        @ ProDesignTools: One of the recommendations worked for me, though the thread was a bit confusing. I uninstalled Lightroom 6.1.1—fortunately Lightroom comes with an uninstaller. Though the uninstaller did not actually remove the app. I had to do that manually. Anyway, after reinstalling Lightroom 6, I was able to apply the Lightroom 6.3 patch. Thanks for the tip.

        And, voila!, the old import dialog has returned, complete with the small check marks we never knew we loved until they were replaced with that hideously large, image obscuring version. I don’t know what other people are talking about here—why they still appear to see them. Likewise the old Copy as DNG, Copy, Move, Add import options have been restored, as have the File Handling choices like Don’t Import Suspected Duplicates.

        Unfortunately, one thing that remains from the 6.2.x version is the instability. The import dialog has frozen on me twice now in the space of half an hour of testing. This is not cool. There is still work to do, then, before the engineers—or management—even think about more feature enhancements. We deserve to have the bugs worked out of products we’ve paid for first. Perhaps the Creative Cloud model has made them careless because it makes it so easy to introduce new features without fixing the old ones. Think again people. In fact, if this instability persists, I will again revert to Lightroom 6.1.1. I don’t know what changes in version 6.3 make it worth living with that instability for any length of time.

        Nor does withholding features from the stand-alone version of Lightroom endear them to users. If CC does not have sufficient appeal without such ill humored gimmicks, that should tell Adobe something about their software leasing scheme. In fact, this latest cock-up with version 6.2 is more than enough reason for anyone to avoid Lightroom CC if they haven’t bought into it yet, and to abandon it at the end of this year’s lease if they have one. These, along with other problems, were foreseen by critics when Adobe introduced the Creative Cloud. That so many of the dire predictions have proven to be valid should be a warning to users if not to Adobe itself. Adobe should be rethinking more than a few things, as should their customers.

        • KC says:

          Try Capture One Pro…

          • B. Jefferson Le Blanc says:

            Can’t afford it.

          • Boris says:

            I’ve tried it (http://foto.nsonic.de/capture-one-pro-8-lokale-anpassungen-fazit/) and unfortunatly it’s not working for me. Features are missing or worse than in Lightroom. (My Blog is in german – maybe you can get the idea with a translation tool.)

            @B. Jeffersion Le Blanc “Can’t affor it”?!? WHAT? It’s somewhere around 250 Bucks w/taxes and i would LOVE to pay that if it works better for me than Lightroom.
            If you cannot afford that, then i assume you are not earning money with photography? Maybe put aside some money for a little longer and consider higher Software-Prices

            Adobe Lightroom was once more expensive too – And it was fast and solid. Now it’s relative cheap … in price and stability 🙁

          • B. Jefferson Le Blanc says:

            @ Boris: My income and my budget are none of your business. Capture One Pro is $299 in the States. That said, it’s interesting to read that you find it inadequate, even at that price. What I know of the app is that it is more complex than Lightroom and takes a technical, even scientific approach to Photo processing. In my experience Lightroom has always been (the import dialog excepted) relatively easy to use, no doubt because I spent years with Photoshop before starting up with Lightroom. I’ve also taken the trouble to read Scott Kelby’s books on the program, which have been no end of helpful.

            I’ve had no reason to even consider an alternative to Lightroom until recently. And for that I would be more likely to try Affinity Photo (https://affinity.serif.com/en-gb/photo/), which is far less expensive than even Capture One Express. At my age, however, I’m less inclined to take up a new application than I once was, so I’ve been waiting and hoping for Adobe to restore Lightroom to it’s past utility and stability. At this point they have the utility back; stability, unfortunately, remains a problem.

  17. Thank you for bringing back the old import dialog, and it reads and transfers much faster in this version as well. Glad to continue using it for my work!

  18. René Zuch says:

    Thanks for restoring the old import dialog.
    Also I see serious speed improvements on my iMac 5K, eventhough there is no enhancement mentioned in the release notes.
    I was able to switch GPU on without the bad effects it had before. Switching between pics in the library module is very fast now and the White Balance is working now as well without lags.
    For me this is a good update. Please continue like this.
    Regards
    René

  19. Peter says:

    Could you add the white balance tool to the selections? I shoot a lot of interior scenes where light from different light sources shows up in the final pictures. I know how to work with this in PS, but having that tool available in selections would save me a lot of time.
    PS. Many thanks for getting rid of that 6.2 import dialogue.

  20. lordmac says:

    OK, but don’t work in tethering on a Mac with Yosemite and EL capitan. Why ?

  21. Steffen says:

    Still no anti-haze filter in the standalone version? Adobe, how come you dislike your royal customers (in my case since version 1.0 beta) so much? What have we done to deserve such special treatment?

  22. Uli says:

    Thanks for listening to an overwelming majority of customers and for reverting back to the old import dialog .
    Maybe for the future – if you want to simplify things for novice users – be sure to have it customizable for advanced users .
    Uli

  23. Brian Fleming says:

    Thanks for listening Adobe re the import module in Lightroom, what I call a result.
    I hope all of us who were quick to point out our dislike of the change will be as quick to thank you for listening to our concerns and the restoration of the better import module.

  24. Is the overall speed improved?

  25. Simon Thomas says:

    Thank you, thank you, thank you Adobe for seeing sense and bringing back the old import process. Lightroom is, without doubt, an amazing product and I just hope that in future Adobe will consult widely, perhaps by beta testing, before embarking on any major changes.

    Just one change I would like to see in respect of importing: is there any chance you could enable me to import by file type? That would be really useful.

    Thanks again

    • Simon: I’m assuming you’re shooting RAW +JPG? What you can do is, in the Import module when you’re looking at the grid of images, first hit the uncheck all button, sort by file type (at the bottom), select the first image of the type you want, hold down the shift key and click the last one. Import.

      NB: If you’re shooting RAW + JPG you can tell Lr to treat the jpg files as separate images – or not – in the Preferences.

      Mike.

      • Simon Thomas says:

        Hi Mike.
        Yes I am shooting RAW + JPEG (have no choice with Leica Q at the moment)
        Many thanks for advice. I will try it.
        Simon.

  26. Dave Merrow says:

    Update good but still no fix for Nikon (D4/D800) tethering problem. Really causing problems for my business!!

  27. Florian says:

    Thank you Adobe, for bringing the “classic” import back and returning the functions that were removed. I see no problem with melding the new import set up in 2105.2/6.2 as an option with the classic in a future update. Choices for potential users are always good, Removing choices, as you found out, is bad. So very glad you owned up to this and corrected it. Kudos to you!

  28. Boris says:

    I have LR 6.1.1 on Mac, it is showing that there are no updates available. Trying to instal 6.3 patch will tell me that it failed with U44M2P28. According https://forums.adobe.com/thread/1873397 I have to reinstall LR. Dear Adobe guys, I am using Mac to not face the same crappy issue as on Windows and I will not reinstall LR every time there is an update. If you are not able to fix your update mechanism, then sorry, I will stick with LR 6.1.1 and will not buy any upgrade anymore. It is annoying how the quality of the LR is going down with each release.

    • Peter says:

      Hi Boris,

      on Windows those ” crappy issues” didn’t come up. Perhaps you should rething your decision using Apple-Products; or your decision using Adobe-Software.

      • Diego Cuoghi says:

        I just installed the 6.3 patch over Lightroom 6.1.1 in two MacPro (2009 and 2013), both with OSX 10.11.1 (El Capitan) without issues.
        And I am very satisfied because, apart the return of the import dialogue and some useful functions, it seems fast and stable,

      • Boris says:

        Hi Peter,

        having Windows does not work for me. Too many issues compared with Mac. The only software I am getting always upset about is LR and its updates. Yes, I do not use the CC but a standalone version, so maybe I am a second class customer. But as said, if Adobe is not able to pay good developers/testers, then sorry, I will not pay for LR7 (and I will not move to CC).

        • Boris: When Lr6 came out Adobe was quite clear that it would be the last standalone version and would not be updated along with LrCC. Take it or leave ut Unless there’s a major shakeup at Adobe headquarters there will never be a Lr7.

          Mike.

    • B. Jefferson Le Blanc says:

      Boris, I had the same issue. Reinstalling Lightroom 6 was not a problem, however—there is even an uninstaller in the Lightroom folder, though you may have to remove the app manually even after running the uninstaller, as I had to do. You can find every version of Lightroom 6 at http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015—I suggest everyone bookmark that page. Finding updates or even upgrades for the standalone version of Lightroom on the Adobe site is a pain and a half. All they care about is pushing the Creative Cloud. If you don’t use it, to Adobe you’re less than a second class citizen. Download Lightroom 6 and the 6.3 patch. You can skip the intervening updates. The whole process will take you little more than half an hour. That said, Lightroom 6.3 is most notable for restoring the import dialog. However, I find it to be more unstable than Lightroom 6.1.1. Unless there are other features or fixes in the update that address issues you’ve been having, sticking with 6.1.1 should not be a problem for the time being. Depending on how much more trouble I have with 6.3 going forward, I may revert again myself.

      By the way, when running the uninstaller it will offer to remove your Lightroom preferences. I have a lot of setting I did not want to risk losing, so I chose not to remove the preferences. The reinstall and the update went just fine anyway, so unless things are really corrupt, you shouldn’t need to delete the preferences either.

      • Ronald says:

        Are any of the ‘freezes or crashes’ repeatable? I had no difficulty going from 6.1.1 to 6.3 on my ‘test’ system. Also, in limited testing so far, have not experienced issues you indicate, but wary after reading of your experience. Anyone else having stability issues with LR 6.3?

      • Boris says:

        Thanks for the help, but as said, I do not want to uninstall and install. I can backup my preferences, sure, but why should I spent at each LR update 1 hour reinstalling? I have a nice example for how I would imagine LR updates – I am using Crashplan – each time there is a new update, the software will download it, install it and do not need to care about any uninstall/install stuff. The same works for 20 different apps on my computer, just the Adobe LR does not work that way.

        • B. Jefferson Le Blanc says:

          It won’t take an hour to do the un-istall/reinstall/update. As I said, it’s about half-an-hour’s work. But if there’s nothing in Lightroom 6.3 that you need, sticking with 6.1.1 will do for awhile—until Adobe gets the app stabilized. At that point you may need to uninstall Lightroom as whatever it is that is blocking the update to 6.3 is likely to do the same for any subsequent updates. Adobe installers have always been finicky; this current instance is nothing new. It seems to be a company policy of long standing. If they wanted to fix it they almost certainly would have done so by now. They obviously don’t want to explain it, either.

          On the other hand, if you stick with your refusal to uninstall Lightroom after the program has been reliably fixed, you’re hurting no one but yourself—cutting off you nose to spite your face, as the saying goes. Your hostility to Adobe doesn’t hurt Adobe in the least.

  29. Tommy Høyland says:

    Thank you for restoring the old import function. It’s much more practical. I wonder how you (Adobe) come up with such ideas. Don’t do things the Flickr way. Why not do beta testing?
    Anyway, is there a way to get rid of the mobile sync warning at startup? It’s a minor but irritating feature

    Thx

  30. Maciej says:

    Hmm… Adobe deletes uncomfortable comments. I haven’t expected that on such a company.

    So I’ll repeat: is the profile for Canon 16-35mm f/4 L IS USM fixed? It has incorrect distortion data. Problem reported to Adobe almost a year ago.

    Regards,
    Maciek

  31. B. Jefferson Le Blanc says:

    I’ve been doing a lot of griping, so at this point I should add my thanks as well for the engineers who responded relatively quickly to user feedback and restored the import dialog to all it’s complex utility. If anyone has a problem with it, I suggest they read a book. There’s a lot to Lightroom besides the import dialog that needs explaining if you expect to discover the full potential of the app.

    Still, guys, you need to stabilize Lightroom before moving on to any further development. Frequent crashes and freezes are not acceptable behavior in a professional app as seasoned as Lightroom.

  32. Piet says:

    I just updated to lightroom 2015.3 after having lots of performance issues with 2015.2 on my macbook pro. I hoped everything would be better, but after opening Lightroom I was greeted with the following error: “Error changing modules”. I googled and tried all of these ‘fixes’: https://helpx.adobe.com/lightroom/kb/error-changing-modules-lightroom.html, but to no avail. Has anyone had the same problem? and or a solution? I am now trying to reinstall Lightroom.

  33. David W. Hewitt says:

    Thanks. I am glad to have the update.

  34. Clark Kranz says:

    Still having problems in Develop module in seeing changes when editing in 3rd party software when using tiff images. That bug did not get fixed

  35. DocD says:

    Well, my wife’s iMac (El Capitan) showed an update from LR 6.2.1 was available so used the application manager to update (214 MB download) to LR 6.3 and message said update was successful. ‘Great’ I thought, started LR and after the initial splash screen confirming 6.3 was loading (why same image as 6.2 & 6.2.1, you changed it at 6 and again 6.1 & 6.2?) got an error pop-up saying ‘error switching modules’? Looking for help online via Adobe shows this error for 2014 versions and earlier. I had to roll-back to 6.2.1 using time machine (remarkably painless) to at least see the expected library images again. Is this yet another bug, have others experienced this. By contrast, updating from LR 6.2.1 to 6.3 on my Win 10 Pro x64 machine worked fine yesterday. Did the iMac download get corrupted (if so, why the successful update message). I’ll leave off trying again until I know more from Adobe about 6.3. Also, why no dehaze tool for us loyal (since LR 3) repeat users to make up for the 6.2/6.2.1 fiasco?
    Regards

    • Pete Green says:

      For the Error changing modules error has been resolved by some by Uninstalling Lightroom, rebooting, then reinstalling Lightroom. See if that works for you as well!

      Regarding Dehaze, there are a couple solutions out there to get Dehaze working in Lightroom 6 — here’s one – http://prolost.com/blog/dehaze

      • B. Jefferson Le Blanc says:

        Thanks Pete for the referral to the Prolost Dehaze presets package. The referenced page also includes an explanation of why Dehaze was not included in the licensed version of Lightroom and a link to an authorized Adobe explanation. Incredibly, there is a law that prevents adding features to already purchased versions of software. CC isn’t affected because it involves renting or leasing the software, where payments are ongoing. So I must take back my remarks about Adobe’s dubious motives here. Unfortunately, they haven’t made the explanation widely available so that most of us have been left to speculate—and suspect nefarious motives.

        This raises the question, though, given the law, how could they justify that new import dialog? That was a significant feature change to an already purchased product in that it applied to licensed as well as CC versions of Lightroom.

        The author generously makes his Dehaze presets available for free—though you have to penetrate an overly fancy web form to get them. He has other presets for sale that are worth a look. Compared to Photoshop plug-ins his package is reasonably priced, in my opinion.

  36. DocD says:

    to roll-back to 6.2.1 using time machine (remarkably painless) to at least see the expected library images again. Is this yet another bug, have others experienced this. By contrast, updating from LR 6.2.1 to 6.3 on my Win 10 Pro x64 machine worked fine yesterday. Did the iMac download get corrupted (if so, why the successful update message). I’ll leave off trying again until I know more from Adobe about 6.3. Also, why no dehaze tool for us loyal (since LR 3) repeat users to make up for the 6.2/6.2.1 fiasco?
    Regards

    • Using Time Machine to do roll-backs is not a safe practice. I can damage the installation such that new patches leave a broken install.

      To fix this, fully uninstall Lightroom using the uninstaller and reinstall using an installer.

  37. DocD says:

    Sorry for partial repeat post above – wifi went down mid-send!

  38. Doodles Weaver says:

    …and, it’s still broken. This is unbelievable!

    The old import dialog is back, ’tis true, but did anyone think of testing it before releasing?

    Pre-6.2 import worked fine with thousands of photos and videos, including detecting and ignoring malformed files; 6.2 import ‘worked’ though the dumbed-down process was painful; 6.3 import finds the files and populates the grid with filenames, but if there are any videos in the folder you get no previews (photos or videos), the import hangs without ever importing anything, and the Lightroom process still runs even after you exit.

    Could we have more testers and less product managers fixing things what aren’t broke? Please?

    • Are you on Mac or Windows?

      • Doodles Weaver says:

        Windows, 64 bit.

        If the selected import location contains any movie files (mine are .MP4s from mobile phones and .MOVs from Canon point-and-shoots), Lightroom is broken forevermore — it doesn’t populate the file selection grid with thumbnail images, clicking ‘import’ closes the dialog but the progress bar never moves, and regardless of whether I click ‘cancel’ after or instead of ‘import’ the program hangs on exit and has to be killed through Task Manager.

        One step forward, two steps back…

  39. JasonNOVA says:

    Thanks for bringing back the import! It was the lack of file path that was killing me, where I imported 200 GB to a wrong drive before noticing it, that never happened with the old (and new again!) import. So thanks!

  40. Bruce H says:

    Will there ever be lens correction for olympus cameras and lens?

  41. B. Jefferson Le Blanc says:

    I tried to report the instability in Lightroom since version 6.2 on the Photoshop Family blog following the report a bug link at the top of this page, but my comment won’t post. So I’ll put it here in hopes that responsible parties will see it (and yes, I have an active account on that blog and was logged in; no error message appeared but nothing happened when I hit Continue—there’s no Captcha requirement as there is here).

    I upgraded to Lightroom 6.3 yesterday. While I appreciate the restoration of the full featured import dialog, this update preserves the instability I found in versions 6.2 and 6.2.1. The app freezes frequently in the import dialog. And it often freezes if I switch to another application and then return to Lightroom. Previously, in version 5, the app only froze after many hours of use. This was annoying, but tolerable. Version 6 and 6.1.1 behavior was similar. But 6.2, 6.2.1 and 6.3 are, in my experience, more unstable than any pervious version of Lightroom—and I’ve been using it since the beta, and have paid for every upgrade since, including Lightroom 1. That’s eight years, now.

    I don’t know what’s going on with Lightroom development. Perhaps the same boneheads in management who thought up the simplified import dialog are not allocating enough time for the engineers to solve extant problems. I know from extensive correspondence with Lightroom staff on this blog that this was the case with some problems in Lightroom 4. It took many months and an inordinate amount of hectoring from me and other dissatisfied users before our issues were addressed. But this instability is worse than any bug I’ve ever experience with Lightroom before; I don’t know why it’s not a priority. It’s persisted through three updates, now, while a variety of less significant issues have been addressed. If I don’t find a solution for this persistent instability, I will once again have to revert to Lightroom 6.1.1 and wait for you guys to figure it out—to put it more politely than I’m inclined to do. But being rude doesn’t help, so I’ll forebear.

    By the way, from reading the hundreds of posts about Lightroom 6.2 and 6.2.1 I know I’m not the only one to experience this instability. It suggests to me that a serious flaw was introduced at some point and that you have not yet figured out what it is. This is the sort of thing that happens when people try to do too much on too short a deadline—as a result of poor leadership from ill informed managers with impaired judgment. This is particularly obvious in light of the simplified import dialog fiasco, but the consequences seem to extend beyond that particular situation. Here’s hoping you can convince the powers that be to give you the time needed to fix this stability problem once and for all. Otherwise, Lightroom’s reputation, and by extension that of Adobe, will continue to be tarnished. This is all the more unfortunate because until recently Lightroom was one of Adobe’s most solid products.

  42. Eddie W. says:

    Cannot run slideshows with LR 6.3. Received “error in changing module” when trying to move to Slideshow.
    Any idea how to fix this anyone ?

  43. Thor Egil says:

    Thanks, looking good so far.

  44. Machiel Bos says:

    Thank you for restoring the old import dialogue and fixing the bugs!

    Greetings,

    A happy Lightroom user

  45. Robert Kelly says:

    After all the waiting, I am disappointed and saddened to say, It still crashes with this new update.
    I get a pop up
    LoadLibrary failed with error 1114: A dynamic link library (DLL) nitialization routine failed.
    There is no way I can trust this software is saving my changes, A real shame.

  46. David Miller says:

    This worked. Uninstall and all

    Thank you ! ! !

    B. Jefferson Le Blanc says:
    November 19, 2015 at 2:34 am
    Boris, I had the same issue. Reinstalling Lightroom 6 was not a problem, however—there is even an uninstaller in the Lightroom folder, though you may have to remove the app manually even after running the uninstaller, as I had to do. You can find every version of Lightroom 6 at http://blogs.adobe.com/lightroomjournal/2013/06/keeping-lightroom-up-to-date.html#lrcc2015—I suggest everyone bookmark that page. Finding updates or even upgrades for the standalone version of Lightroom on the Adobe site is a pain and a half. All they care about is pushing the Creative Cloud. If you don’t use it, to Adobe you’re less than a second class citizen. Download Lightroom 6 and the 6.3 patch. You can skip the intervening updates. The whole process will take you little more than half an hour. That said, Lightroom 6.3 is most notable for restoring the import dialog. However, I find it to be more unstable than Lightroom 6.1.1. Unless there are other features or fixes in the update that address issues you’ve been having, sticking with 6.1.1 should not be a problem for the time being. Depending on how much more trouble I have with 6.3 going forward, I may revert again myself.

    By the way, when running the uninstaller it will offer to remove your Lightroom preferences. I have a lot of setting I did not want to risk losing, so I chose not to remove the preferences. The reinstall and the update went just fine anyway, so unless things are really corrupt, you shouldn’t need to delete the preferences either.

    Reply
    Boris says:
    November 19, 2015 at 7:27 am
    Thanks for the help, but as said, I do not want to uninstall and install. I can backup my preferences, sure, but why should I spent at each LR update 1 hour reinstalling? I have a nice example for how I would imagine LR updates – I am using Crashplan – each time there is a new update, the software will download it, install it and do not need to care about any uninstall/install stuff. The same works for 20 different apps on my computer, just the Adobe LR does not work that way.

    Reply
    B. Jefferson Le Blanc says:
    November 19, 2015 at 7:58 am
    It won’t take an hour to do the un-istall/reinstall/update. As I said, it’s about half-an-hour’s work. But if there’s nothing in Lightroom 6.3 that you need, sticking with 6.1.1 will do for awhile—until Adobe gets the app stabilized. At that point you may need to uninstall Lightroom as whatever it is that is blocking the update to 6.3 is likely to do the same for any subsequent updates. Adobe installers have always been finicky; this current instance is nothing new. It seems to be a company policy of long standing. If they wanted to fix it they almost certainly would have done so by now. They obviously don’t want to explain it, either.

    On the other hand, if you stick with your refusal to uninstall Lightroom after the program has been reliably fixed, you’re hurting no one but yourself—cutting off you nose to spite your face, as the saying goes. Your hostility to Adobe doesn’t hurt Adobe in the least.

    Reply
    B. Jefferson Le Blanc says:
    November 19, 2015 at 2:43 am
    I’ve been doing a lot of griping, so at this point I should add my thanks as well for the engineers who responded relatively quickly to user feedback and restored the import dialog to all it’s complex utility. If anyone has a problem with it, I suggest they read a book. There’s a lot to Lightroom besides the import dialog that needs explaining if you expect to discover the full potential of the app.

    Still, guys, you need to stabilize Lightroom before moving on to any further development. Frequent crashes and freezes are not acceptable behavior in a professional app as seasoned as Lightroom.

    Reply

  47. pedro alfaro says:

    thetering Nikon D800 in OS X EL CAPITAN is good now with this update?

  48. stephen bruhn says:

    I have a CC account with Adobe. I cannot get LR to appear in the CC App menu as an update. It’s just not there. I opened LR and it says the version I have is ‘2015 release’. When I check the updates in the Help menu it switches to the CC App but does not list any LR updates. I also get a pop up message for the CC App on my desktop which tells me there is 3 apps to update. When I open the CC App, there is only Photoshop and Indesign. Two, not three??? It now seems that it is impossible, for reasons that I don’t understand, to update LR. I also logged out of the CC App, quit it, started it again and logged back in. No change.
    So, how can I update my version of LR? Please. Any help would be useful and appreciated.
    Regards

  49. Achim Kleiner says:

    6.3 still not working. Video Modul without funktion, no playback.
    (Mac Os 10.11.1 on iMac)
    🙁

  50. Achim Kleiner says:

    i am back on 6.1.1, waiting for …?

  51. Following my initial gratitude, I’m now feeling disappointed as I note that although sort by capture date is still there, it’s not possible to select on a day by day basis – as was the case in the earlier capture dialogue. This can be REALLY helpful if you’ve not wiped a card following an earlier shoot and ONLY want to import a more recent set of images. Being able to clear all and then select day by day is an ESSENTIAL function for my workflow. PLEASE restore!
    In hope
    Chris

    • Chris, in previous versions at least there was an option to create subfolders for each date on import (right panel, bottom). Is that no longer there?

      Mike.

      • Mike – for the life of me I can’t find it there. Things have gone from bad to worse. I’d love to find an alternatifve to LR but I’ve got SO much time and effort invested in using the program and it’s central to my work flow. Feeling VERY let down.
        Chris

      • Mike – thanks for the thought. Of course you’re right about being able to create subfolders – this I do as a default – I keyword and import on the basis of date. What I WANT is the old way of being able to select a day’s worth of images for import. I could then do rough keywording for a day’s work and repeat the process for the next day that had been saved to card. IMPOSSIBLE to do this now.
        Best
        Chris

  52. David Madison says:

    Eject card feature not restored on my Windows 7 64 bit version. Please restore this, it is something that is very useful for multiple card ingests, it saves time, it makes the user’s life a wee bit easier.

    Is there a reason this was not restored?

    • David Madison says:

      further Eject card comment — this does not eject when an import is cancelled. It does when an import completes.

    • Richard Kramer says:

      I upgraded to lr CC 2015.3 on my Win10 PC and the eject check box is back. It’s in exactly the same place as in 1.1. If this is what you are talking about, you have to have a card inserted to see it.

    • Thor Egil says:

      I don’t get this moaning about this eject card “feature”. It does nothing useful at all. When you are done copying, just pull out the card from the reader – it won’t kill neither you nor the card.

  53. Malcolm Kantzler says:

    I have Lightroom 4.4 and it has no support for newer cameras. Do I have upgrade options outside of CC? Thanks.

    • If you just need Lightroom, you can get an Lightroom 6 upgrade on Adobe.com: https://www.adobe.com/products/catalog/software._sl_id-contentfilter_sl_catalog_sl_software_sl_mostpopular.html

      If you use Photoshop and Lightroom, this is the best way to keep on top of native raw camera support and keep PS/LR converters in sync with features: https://creative.adobe.com/plans/photography

      Please note, you don’t need to upgrade to get the the latest camera support. You can get the latest camera support for older versions of our software through the free Adobe DNG Converter. Details here: http://adobe.ly/ACRandDNG

      • Malcolm Kantzler says:

        I use Lightroom 4 with Photoshop CS5. Your second option looks like CC, so I’m limited to the DNG converter. I really wish Adobe would just provide LR and CS5 updates, even if only to conform them to new camera file formats. That would be courteous.

        Thanks for your reply.

        • B. Jefferson Le Blanc says:

          @ Malcolm Kantzler: I don’t know Adobe’s official reason(s) for not providing camera compatibility updates for older versions of Photoshop and Lightroom, and it’s certainly a sore point with many users who don’t like feeling coerced into paying for upgrades. But the reason could be that it would simply create too many branches of Adobe Camera RAW to be manageable. For one thing, when ACR is upgraded with Photoshop, new features are added along with the additional camera support, in conjunction with new versions of Lightroom. Adobe put ACR and Lightroom development on parallel tracks some years ago. In the case of Lightroom, camera compatibility is integral with the program and updates for older versions are probably infeasible for one reason or another.

          While it can slow down your workflow to use it, an up-to-date version of the DNG Converter can handle any RAW format that the latest versions of ACR and Lightroom can process. So, if you don’t care to upgrade, you can use the freely available DNG Converter to pre-process your images, which can them be used in older versions of Photoshop and Lightroom that otherwise do not support your camera.

          There is a related issue that recently came to light regarding features showing up in LIghtroom CC that are not available for the current stand-alone version of the program. That is, it’s actually illegal to add features to an app that has already been paid for. Since CC is paid for continuously, this limitation does not apply. So Lightroom users will have to wait for the next paid upgrade to catch up with Lightroom CC. This rule may also apply to adding features to Adobe Camera RAW for older versions of Photoshop.

          So, though Adobe obviously considers adding features to their CC apps in between upgrades to be an incentive to rent their software, it may also be the case that they have little discretion in the matter.

          Be that as it may, the question of whether or not one wants or needs the new features in an application upgrade remains as material as it ever was. It’s not a new problem. And it is probably why many people have habitually skipped upgrades over the years, getting every second or third one as suits their needs. This issue remains for Adobe Lightroom. Unfortunately for users, the Creative Cloud has removed that option for most of the rest of Adobe’s apps. Which has led many old hands to look for alternatives to Adobe’s leasing scheme, and it has undoubtedly encouraged other developers, like Affinity, to create competing products. And I can’t help thinking that it’s a good thing in the long run. Adobe’s near monopoly has always created skepticism among some users and often outright hostility. If there are viable options to Adobe’s products there will be less cause for resentment. It may also be hoped that such competition will have a benignant affect on Adobe as well.

  54. Peter says:

    Just updated to 6.3. Beside the disappointment there is absolutly no excuse and compensation for hours spend with uninstall/reinstall, each Version of Lightroom is getting worse.
    Lightroom now hangs forever if I go to the Web-Module. No Response, nothing. Have to kill it through Task-Manager.

  55. Rune Engebo says:

    Adobe finally took responsibility for their scandalous 6.2 release.
    Today I got an email confirming they will credit me 3 months subscription fee because of the instability problems I have experienced with the software after updating to 6.2. It did however take me several complaints to support before they acted on the matter.

    If all LR subscription users are credited the same way this must be a significant hit to Adobes finances for 2015. Anyway, will I update to 6.3? No way! Did a roll back to 6.1 a few weeks ago and do not plan to update again unless new cameras or lenses “force” me to do so somewhere in the distant future.

  56. Adrian Kaminski says:

    Thank you Adobe for restoring the old import dialog. Now I can import again without double and triple checking everything again.

  57. Hi – I owe Adobe an apology! I think I must have missed an update in the process of sorting out various computers with different versions installed, and now find I have the proper, latest CC LR 2015.3 and indeed, Destination Folders and all the other goodness of the “proper” import screen are all there. Many thanks – and sorry if I bad-mouthed anyone in my confusion.
    THANKS for restoring this.
    Best
    Chris

  58. Axel says:

    Coming back to the ‘streamlined’ import of LR6.2 and in case some Adobe folk happen to read this:

    I actually came across one of the people who have difficulty dealing with the old-school import dialog! He’s a semi-pro photog with mild PS experience, though he was confused where his shots end up after import and how the whole copy/move thing is supposed to work. So +1 for diagnosing some problems there…

    … but (BUT!) after I explained the import dialog to him, it was no good anyway! He didn’t get the whole LR concept with immutable source files and ‘exporting’ the processed shots, unlike a straight PS open-edit-save. Plus the whole plethora of ACR options is beyond him, he didn’t use most of them in PS so why would he want to use LR.

    So tl;dr: People who are unable to import there files with the current LR and aren’t willing to read up won’t be happy with the rest of the current LR anyway. For those folks, create a nice, streamlined ‘LR Elements’ and stop dumbing down the original.

  59. Aidan says:

    Looking forward to Adobe making changes to LR that are actually WANTED by users.
    They could start by going through some of the old requests on Get Satisfaction – a place where LR users don’t seem to be getting any.

    For example here’s a 5 year old request, with users so passionate about it that a number of users (including myself) have mocked up screenshots of how it could look:
    http://feedback.photoshop.com/photoshop_family/topics/colour_coding_folders_and_collections_to_simplify_navigation_cataloguing

    Here’s hoping. And there’s plenty of other old requests with more votes by users too.

  60. jim says:

    Has any one gotten tethering to work with the Canon t6s and lightroom 6.3? It does not work for me although my older canon cameras do work.

  61. Jeffrey says:

    My Lightroom CC just updated and everything looks fine in the Library mode. However, in the Develop mode everything is multicolored and looks like a painting. I have rebooted my machine and looked for any new updates and I don’t see anything.

  62. Susan says:

    I do a lot of projects using scans of images on paper that need to be enlarged and printed on paper again, big papers, which means they must be scanned at high resolution. Which I’ve been doing for years. But now the Lightroom 2015.3 edition, in a Mac computer with its recently updated OS, fails to import anything scanned at more than 1600 dpi. Why? Is that a Lightroom error or a Mac error? I don’t know. This edition of Lightroom manages previously scanned and imported big files with no problem. Chucking all my Lightroom images into any mobile system would be totally inappropriate and unfeasible: the Lightroom Mobile system is unwanted, and that constantly presented option is annoying, not an asset. Being able to click a NO button so nothing about Lightroom related to automatically spewing images into a Mobile system continues, would be better. I suspect that changing priorities to focus on automatically sending all images into some mobile system meant you decided Lightroom should stop importing high resolution scans because such files won’t fit in your mobile system. Whatever you do with the Mobile options, you need update the Lightroom CC application so it can import high resolution scans while being used on an iMac again, or it will no longer be very useful for me.

  63. And not listed in the 6.3 list of fixes; the soft proof bug reported last April is now, finally fixed.

    [TH: It’s on the fixed list for 6.4. Sincere apologies for the delay.]

  64. Bob Port says:

    The Adobe Creative Cloud update system for Mac is an abysmal failure. I pay for this software. I pay every month. Every single update that has been issued for months fails to instant normally. Every single one. This is unacceptable. Why subscribe if your subscription deliveries don’t arrive.

    Fix this, Adobe!

  65. the dude says:

    Live Photos support?

  66. Bill Higgins says:

    My Lightroom CC app says it’s up to date. However there is no De Haze slider showing under Effects tab

    • Rikk Flohr says:

      You must be using the Creative Cloud Subscription version in order to have access to Dehaze. Go to your Help>System Info… and verify that you are running CC2015.1 or later.

  67. Bill Higgins says:

    Many thanks Rikk. I’ll try that, Cheers, Bill

  68. Sharon Stefaniuk says:

    I have a friend who is a photographer who is experiencing a problem with his iMac OS El Capitan 10.11.5 & Lightroom 6.3 that is causing it to freeze.
    He’s already brought his computer to Apple; they wouldn’t deal with it & referred him to Lightroom.
    For some reason, the Lightroom catalog is contained in the disk “Macintosh HD.”
    When Lightroom does its backups, it also stores them in the “Macintosh HD.”
    This causes it to be critically low on space, and to freeze.
    Is it possible for either or both the Lightroom catalog and the Lightroom backup files to be moved from their current locations, and automatically sent to & stored in different external hard drives?
    When he imports his photos, they appear in Lightroom & the Lightroom catalog & a second copy is sent to a portable external hard drive. After editing the photos, he exports the final edit to his portable external drive; deletes them from his Lightroom, sends them to the trash & empties the trash.
    After he finishes editing his photos, he exports the final edit to his external hard drive, & deletes them from his Lightroom, trashes them, and empties the trash frequently.
    How can this problem be fixed, please?

    • Rikk Flohr says:

      The Lightroom catalog files must be on a locally attached drive for Lightroom to open the catalog. That can be an internal drive or a drive physically attached to the computer (not a networked drive). For performance reasons, it makes the most sense to keep this on a primary internal drive where ever possible.

      The Backups can be placed in any location – either by changing the location in the Backup dialog or moving them after the fact. There is no harm in moving them. Good backup practices would dictate that your backups be on a different drive than the live catalog in any case. That way, a drive failure doesn’t take out your live catalog and the backups. The number of backups you keep is entirely based upon comfort level. However you do have to manage the removal of no-longer-needed backups manually through the file system. Lightroom doesn’t have a mechanism for managing backup files after they are created.

Leave a Reply

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