WEDDING SEASON SALE! 30% Off Training Systems!

Your content will be up shortly. Please allow up to 5 seconds
Gear & Apps

Adobe Issues Lightroom Statement | Bringing Back & Fixing Features

By Kishore Sawh on October 17th 2015


It’s been a particularly volatile few weeks for Adobe users given the flood of updates to its Creative Cloud suite of programmes that got us all excited, only to have that flood of excitement turn to an eruption of public outcry. It was Lightroom that’s really been the cause of much contention as they made some notable changes, additions, and omissions, some of which were just entirely disappointing or problematic.


Of course, I’m speaking of stability issues with LR, and the import dialogue problem that’s been on the tips of venomous tongues. Many users were unamused with the new dialogue and its performance and called for a return to the previous version. We featured a video not long ago that showed how slow LR’s import was of some RAW files compared to its contemporaries, which seemed to echo the problems of many. It does, however, warrant saying that the files were from a Fuji X-T1, which it seems LR has particular problems dealing with.


Regardless, that import issue, stability issues, and the removal of the auto-eject-card upon import option, were enough to overwhelm Adobe into issuing an apology, and in the face of rather overwhelming discontent it has released a statement saying that Lightroom will revert to the old import dialogue in the next update, as well as return some removed features. When is it happening? That there not yet an answer for, but to tide you over they have released instructions on how to a previous version devoid of these issues in the meantime. You can find those here.


Personally, I haven’t noticed any real stability issues with any of the new versions, and maybe I’m just lucky, but the one issue I’ve had and contacted Adobe about is I was noticing a peculiar difference in how images were looking in the Library and Develop modules. This is not something I’d experienced before, and it was consistent among various catalogues (I create a catalogue per shoot), though only affecting new catalogues that were created in LR post the updates. Curious indeed, and annoying, but was assured that what I was seeing in the Develop Module was, in fact, the proper profile. I hope this is fixed soon too.


Library Module Left | Develop Module Right (seems just a saturation difference)

In all of this, though, even given the annoying problems in their new releases, it’s just another reason I’ve got to love Creative Cloud because clearly it allows Adobe to field these complaints, but also to issue fixes somewhat on the fly.

Source: Adobe

This site contains affiliate links to products. We may receive a commission for purchases made through these links, however, this does not impact accuracy or integrity of our content.

A photographer and writer based in Miami, he can often be found at dog parks, and airports in London and Toronto. He is also a tremendous fan of flossing and the happiest guy around when the company’s good.

Q&A Discussions

Please or register to post a comment.

  1. Paul Empson

    performance when in use is fine… just the slow import for me..
    I unticked the use graphic card as I found it was causing exports to fail much more often… 10’s of failed file exports… now almost none..

    | |
  2. Mark Romine

    I now have a 5K iMac 4Ghz i7 that will Turbo Boost up to 4.2 Ghz, 32GB Ram and I’m so disappointed with LR 6 Desktop performance even with Smart Previews @ 1:1 running under OS 10.10.5 Yosemite. I have the ‘Use Graphics Processor’ checked and I have the ADM Radeon R9 M295x card installed. I have Standard Preview size set to auto.

    So in an attempt to try and get some help, I log onto the Adobe User forums and post the above about my machine specs and my frustration with the overall performance of LR on a brand new maxed out iMac. The only suggestion of help that I get from Adobe is that I need to upgrade my LR to 6.2.1CC. That was on Thursday of this week. Really!?

    | |
  3. Simon Grimley

    Personally I’m happy about the import system being rolled back but it also raised a worrying thought.

    Should Adobe release a change that is for the better in the future but a lot of people complain as they don’t like it will they roll that back too.

    It’s great they listen to customers but they should be wary of allowing those same customers to keep them stuck because they don’t like change and hold the product back from evolving.

    | |
    • Kishore Sawh

      This, this is a very good point Simon. A few complaints at the hands of some shouldn’t hold back the tide of progress. I think strategically it’s smart this time, to show they ARE listening. Also, it won’t hurt that the changes are largely aesthetic, and the rollback is optional until a more sturdy fix is made. Also, Adobe speaks to a host of photographers like myself, who give them feedback from a professional perspective, and less so, and pass on the concerns and thoughts of our audience. So it’s actually helpful for everyone when we get feedback like this.

      | |
  4. Austin Swenson

    In an effort to dumb Lightroom down and make it simple to use, Adobe underestimated how many people need and want something more complex, and now they fixed it.

    I think this is a lesson that when enough people outcry about performance issues, Adobe will change them. If more people made a bigger deal about the current version’s performance issues, I think they would get cracking just like they did here.

    | |
    • Kishore Sawh

      There’s certainly some truth there. When I speak to the Adobe LIghtroom team, however, I get the sense they think they are innovative and satisfy the wants of photographers. I don’t know if they’re just too close to it to see, or aren’t prolific shooters, or what, but the fact is, they aren’t immune to failure. The speed with which LR operates, and how it hogs system resources must be sorted out.

      | |
  5. Neu Porabno

    The difference is normal. What you are seeing in Library module is preview JPG your camera stores within the RAW file – same as it is displayed on the lcd on camera. This preview is edited with “in-camera” style chosen. What you are seeing in Develop module is just plain RAW. So therefore it is a big difference. Set the “in-camera” style to some extremes (saturation on full, contrast on full) and shoot some RAWs and import them. Library photos will look saturated and crappy as hell but same ones in Develop will be flat raws. Been like that from version 1 :)

    | |
    • Kishore Sawh

      Neu, that conclusion is what I figured, but I’ve been using LR for some time now, and the difference never as noticeable, if at all, as I’ve found it recently. On top of that, the image there has had a few global adjustments, which should reflect in both modules, wouldn’t you say?

      | |
  6. Jean-Francois Perreault

    We’ve all made mistakes and we’re all gonna make new mistakes. It’s not the mistake but what we do about it that counts.
    I think Adobe responded very well by apologizing and saying they are gonna fix this. Kudos!
    A few will still say that is release should never have happened but hey, at least they listened and are getting it fixed.

    Now Adobe, when are you gonna improve x-trans handling? Just sayin’ ;)

    | |