Lightroom 6.2 Release Update and Apology

Update #2: Lightroom 6.3/CC 2015.3 is now available which includes the previous import functionality, bug fixes and added camera/lens profile support.

Update: We plan to restore the old import experience in our next update. In the meantime, if you need to restore previous import functionality, or are experiencing other issues with Lightroom 2015.2.x/6.2.x, we recommend you roll back to the Lightroom 2015.1.1/6.1.1 update until things are reverted and corrected. See instructions here: https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html

I’d like to personally apologize for the quality of the Lightroom 6.2 release we shipped on Monday.  The team cares passionately about our product and our customers and we failed on multiple fronts with this release.  In our efforts to simplify the import experience we introduced instability that resulted in a significant crashing bug.  The scope of that bug was unclear and we made the incorrect decision to ship with the bug while we continued to search for a reproducible case(Reproducible cases are essential for allowing an engineer to solve a problem).   The bug has been fixed and today’s update addresses the stability of Lightroom 6.

The simplification of the import experience was also handled poorly.  Our customers, educators and research team have been clear on this topic: The import experience in Lightroom is daunting.  It’s a step that every customer must successfully take in order to use the product and overwhelming customers with every option in a single screen was not a tenable path forward.  We made decisions on sensible defaults and placed many of the controls behind a settings panel.  At the same time we removed some of our very low usage features to further reduce complexity and improve quality.  These changes were not communicated properly or openly before launch.  Lightroom was created in 2006 via a 14 month public beta in a dialog with the photography community.  In making these changes without a broader dialog I’ve failed the original core values of the product and the team.

The team will continue to work hard to earn your trust back in subsequent releases and I look forward to reigniting the type of dialog we started in 2006.

Sincerely,

Tom Hogarty and the Lightroom Management Team

Update October 12, 2015:  With 432 comments and counting I just wanted to let folks know that I’m reading all of the feedback and the team will provide an update this week.

769 Responses to Lightroom 6.2 Release Update and Apology

  1. David Madison says:

    Tom, your mea culpa is a step in the right direction, BUT…

    “very low usage features” ??? according to who??

    I used the feature to eject the card after import EVERY SINGLE TIME I IMPORTED IMAGES! I have over 300,000 images in my catalog. That represents a lot of imports.

    Have the LR team sit down with 8 cards after a shoot and force them to download them. Then tell me this feature is unneeded.

    [TH: David, we have in-product analytics that measures feature usage and we also reference that against the quality of any one feature and the effort required to bring it up to our standards.]

    • David Madison says:

      to TH: Since the feature worked perfectly and has for many versions, it seems really unlikely there was any current issue with quality of the feature or effort to bring it up to standards that would lead to dropping the feature.

      • Dennis Pritchett says:

        To TH: Well, that’s reason enough to not ujpdate Lightroom in the future, and I’m thankful I missed this one. Things work great for me. Instead of engineers, why not test stuff out with photographers, since that’s who’ll be using it?

    • Jason Dunn says:

      I’m genuinely curious because a lot of the comments here are mentioning the auto-eject feature: why would you use this feature? What’s the benefit? I purposefully don’t use it because after I import my photos, I open up the card via Explorer and delete everything on it. Formatting via the camera is much slower.

      I understand it’s upsetting when a feature you use gets removed, but most modern programs track which features get used, and which don’t, so the product managers can make informed decisions.

      • Jim says:

        Most camera manufacturers will advise that you format cards in camera rather than delete images on computer. Can lead to card failure and corruption

        • Lance Bates says:

          Entirely agree, Jim.

          • Kim says:

            Totally Agree with Jim too. I count on that feature and didn’t realize it wasn’t included in this new release. Ugh. It is just so slow. That is my major complaint.

          • marcos issa says:

            I am amazed with the removal of this tool. Always praised, talking to my students, this convenience that unfortunately now, we were hampered.

        • Tim Ashman says:

          I think many people over format their cards. I format mine about once a year on the computer and have never had a failure. I also just copy the files to my computer and then delete off of the card.

          • Jason Dunn says:

            Careful Tim! If you don’t do things exactly the same as the others here, they jump all over you, criticize you, and mock you for asking a polite question. There are some seriously rude, ignorant people here!

            First off, formatting in my Nikon D750 is very fast. But in my Sony RX100 Mark IV, it takes almost 60 seconds. So, yes, I do find that to be a little tiresome – especially since the Sony has pretty weak battery life. In general though, I don’t format in my cameras constantly. And, no, I haven’t ever had a problem. Maybe if some of you have had corrupt images, you’d feel more sensitive to this issue – that’s OK. But don’t slam me because I don’t do things the way you do.

            I am not a pro, so some of you are right, maybe if I was shooting for a living I’d have a different workflow. But do you all realize there’s an option to make a second copy upon import? When I import pictures, it automatically makes a second copy to my Synology NAS, which is protected with drive redundancy. So, no, I don’t care about keeping the photos on the cards. If you do, cool – do whatever works for you. But don’t trash me because I have a different workflow than you do.

            Lastly, now that I’ve seen the new importer (I hadn’t when I first posted here, which was why I asked about it), I agree its a disaster. For me, the loss of the auto-eject wasn’t personally a big deal. But the UI of the importer looks like something out of Elements. It’s garish, incredibly slow to draw on the screen of my new Dell XPS 13…it’s the most bloated, unstable piece of code I’ve seen in Lightroom in years (it’s crashed on me twice, bringing down Lightroom with it). So I’m very glad to hear that Adobe will be taking it out – that thing needed some serious beta testing and photographer feedback before being unleashed.

            Some people here really need to calm down and not be so hostile.

        • imajez says:

          I read a very interesting and quite technical explanation a while back on how deleting with computer works versus in-camera formatting. In camera formatting didn’t seem to be the sensible thing to do after knowing more about the processes involved and was indeed recommended against doing so as a matter of course.

          I’d link to it but it was on a FB pro-photography page and it’d be a challenge to find anyway.

      • C.A.M. Gerlach says:

        If that’s your reason for not using the feature, you might want to rethink your workflow.

        First, while chances for data corruption or problems on any one given shoot are low, if one goes long periods without formatting their cards, and also not ejecting them properly, there is a small but non-negligible chance that data corruption or other problems could occur over time. If you are just playing around with your camera for fun, then it probably doesn’t matter much to you, but as someone who depends on my cameras to deliver the goods for my clients, I format before every shoot–better to be safe then sorry..Same thing with auto-eject–unless something is writing to the card, the chances for data corruption are extremely slim, but I’ve had some times where Magic Lateran refused to boot after not ejecting a card properly.

        I’m not sure what camera system you are referring to, but every one I’ve used has taken less time (both for the user and the operation itself) to do so then manually opening them up in MultiCommander (not to mention Explorer) selecting everything, deleting it, and then emptying the trash. In fact, I’ve seen several users cite the increased speed/ease of this method as why they choose to format over delete, data integrity notwithstanding.

        Finally, as a good practice (and probably more important than always formatting or ejecting) I keep my photos on the cards until I’ve backed my ingested photos up at least 1-2 other places, using a fresh set in camera if needed. Deleting them right away, unless you back them up immediately via LR import as opposed to syncing everything after. is not a good practice. Doesn’t happen often but it’s saved my butt a couple of times, most recently when I had a bunch of DNGs for a major gig get mysteriously corrupted not too long after import and had to ingest them off the cards again–considering they were at dozens of the client’s properties all around a major city, this simple practice saved me hours upon hours of reshooting.

        And when it comes to analytics, all the experienced/pro users I know turn those off or block them via FW, so it could explain why the proportion of people who use certain features is drastically underrepresented, particularly among the core/dedicated userbase.

        • I am agreeing on all topics you covered and would like to hear an explanation why Adobe would remove any feature that is simply working. It cannot be the 100kb of file-size increase.
          Same annoying practice on removing filters in PS that have been around since the beginning and fell short due to some usability feedback I have not once allowed to submit data like any other pro I know. And since Adobe – at least in my mind – is a company which manufactures software for pros, I would love to them to ask the pro community before removing any working feature that might impact the workflow or result and therefore impact our income in one way or the other.

      • Gary says:

        Formatting in camera is quick and easy. Besides, you might not want to straight away. Ejecting the card is however vital and this was an excellent feature I used every time! What harm was it doing, that they would remove it?

      • Alan Kearney says:

        Jason, I guess besides not using the ONE feature of this software that kept you from accidentally corrupting a memory card by pulling it out too soon, you then show your ignorance by ignoring EVERY camera manufacturer’s statement about NEVER formatting a memory card EXCEPT in the CAMERA! You LIKE playing “Russian Roulette” don’t you!
        Oh yeah! Formatting is SO SLOW on my Nikon’s! I have to push two buttons – twice in q and 32 – 64GB cards are blanked in a “heart beat”.

      • Rick Popham says:

        @ Jason Dunn: Auto-eject benefits me because my workflow is different than yours. I import from the card via Lightroom, the card is ejected, the next card goes in, etc. The images stay on the cards until they’re backed up to other hard drives. Lightroom’s automatic ejection saves me time and helps prevent possible corruption of files if the card is removed without ejection. I never delete files from the card, either in camera or in the computer. Instead, the cards get formatted in the camera. With Nikon’s “two-button” format, it takes about 10 seconds per card, if that, and the card is properly formatted with any bad sectors written out.

        The modern program tracking is that thing I always disable, so the decisions that product managers make are not necessarily informed.

        • Jason Dunn says:

          Thank you for the rational, non-angry response Rick. Makes sense to me, and everyone’s workflow is different.

          For me though, when I import files into Lightroom, within a few seconds, Cubby starts copying over any new files to another computer on my network. And I also create a second copy upon import to my NAS. So my lack of using the eject feature is neither foolhardy nor reckless like some people here seem to think. I have three copies of the imported DNG files by the time the import is finished.

          I do think though that once a feature is introduced, and people rely upon it (especially pros) a company has to have a REALLY GREAT REASON for taking it out. Adobe clearly should have left it in based on the response here.

      • takes literally only 3 seconds to format cards in camera. you go ahead and delete images from explorer and eject the card in less 😉

      • Ed Knuff says:

        Formatting in the camera is not slow.
        Camera manufacturers emphatically recommend formatting the card in the camera to avoid corruption issues.
        Plus, why would you erase the card anyway before you know you have your images backed up?
        What planet are you living on?

        • Jason Dunn says:

          Well Ed, I’m glad you asked: when I import files into Lightroom, within a few seconds, a program called Cubby starts copying over any new files to another computer on my network. And I also create a second copy upon import to my NAS, which has full drive failure redundancy. So my lack of using the eject feature is neither foolhardy nor reckless like you here seem to think. I have three copies of the imported DNG files by the time the import is finished.

          If you’re not using tools to automate immediate replication of your images upon import, that’s your problem, not mine. If you like the auto-eject tool, great. Use it. But don’t trash someone else who doesn’t happen to use it. That’s rude.

    • Edgar Hugo says:

      Tom, maybe you should take into account that seasoned pros tend to turn off the phone home feature (aka “in-product analytics” so you don’t have such a clear picture)

      • bobfrost says:

        Just what I was going to say. I have turned off as much of the analytics in CC and Win10 as I can find. A friend even disconnects from the Internet while using CC – only connects now and again for email. We need to keep LR focussed on doing what we want, not wasting time doing what you want!

        So your analytics will be heavily biased in favour of those who don’t know what is going on in their computers.

        Bob Frost

        • Jason Dunn says:

          Respectfully Bob, by turning off telematics features in software, you’re opting out of having your feedback count toward the product future. I purposefully opt-in to every feedback option there is, because I know how that feedback gets used. And I most certainly know what’s going on with my computer, so please don’t generalize.

          If you chose to opt out, that’s fine, but it’s a lot like voting: you can’t complain about who gets elected if you didn’t vote. 🙂

      • James Hallows says:

        This!
        I’m particularly frustrated to see the “Move” option removed from the import process. I extract all my photos from the camera using Canon’s EOS Utility and then I use LR to add these images to my catalogue, moving them to the correct folder as part of the import workflow.
        I would like to see this reinstated please.
        Kind Regards,
        James

      • Rob Levandowski says:

        This, this, this. This is a huge takeaway from Adobe from this debacle.

        Thanks to the privacy-invasion excesses of major companies like Adobe, Facebook, and Google, plus the less-than-stellar history Adobe has with writing code that doesn’t have security issues, a lot of people will disable the “phone home” provisions of software right away. That’s especially true after the Snowden revelations.

        Your “in-product analytics” aren’t representative of your users. They’re representative of your most lazy and/or least security-conscious customers. For a technologically proficient clientele, that’s going to be a substantial difference.

    • Loh says:

      everyone i know uses the removed features.
      the feature to select a day to import the photos from is used by me every day.

      everyone and his grandma is complaining about the missing features.
      i don´t understand how adobes LR team could come to the impression these features are not used.

      sure they are not used by noobs. becasue they don´t KNOW them.
      once you know them you will probably use them.

      professional software should be made for professionals not the selfie crowd.

      • N/A says:

        Adobe in house testers and pet-testers like the likes ( 🙂 ) of Schewe are living in their own world far-far away from the real users and real world use cases…

        • TomFrerichs says:

          Jeff Schewe said on Luminous Landscape that this release “sucks.” And that he and other beta testers told Adobe that.

    • trevor h says:

      HAHAAA!!

      An apology and a commitment to listen.

      Then right out of the gate he replies and says they don’t care what you say. “We have in-product analytics that measures feature usage and blah blah blah” – NOT LISTENING. “Listen pal, we measure things ourselves and will tell you what is what” HOLY FAIL.

      Sad, pathetic, and true

      This is not a commitment to listen, it’s a PR stunt – users should shut up and take what the gods throw down – THEY HAVE SPOKEN.

      Commitment to listen, yeah ok.

    • Mathias says:

      I agree fully with David. And if it is true that the usage of eject the card after import is low, then it is because people haven’t found it. I’ve been using this for as long as I can remember. It is a time saver, and it makes sure you dont accidentally corrupt you card by removing without ejecting. Since the upgrade of lightroom I’ve been in several high-pace shooting situations, and it my heart jumps everytime I rip the card out without ejecting it because I forget that the feature is gone. And if I remember I still have to move from lightroom to a finder window, eject the card and then move back to lightroom. Who in their right mind would think this is simplifying?

    • John Tice says:

      We now have Lightroom for DUMMIES! You’ve taken away the functionality of IMPORT and now it is worthless. Whoever designed and whoever authorized this should be sent to Time Out.

      Give us some kind of an option to have the older, and superior, import dialog back. Are you trying to make it so simple that it’s worthless? You’ve done a good job. All of the functionality is now gone.

      There’s an old adage, “If it ain’t broke, don’t fix it.” Well, then geniuses at Adobe have really messed this one up!!!!

      • Ben Knecht says:

        Yes to your thought of LR for Dummies. I have worked hard to learn how to import my pics. I follow George Jardine’s method. It works great. I am an amateur photo guy.

    • OlMar says:

      To TH:
      How difficult is to add an option to eject the card after import and to “bring it up to the standards”? It’s not a complete rework of the software…

      And also consider that many people may not use the function because they don’t know about it or ever tried it, not because it doesn’t suit them.

    • Rick Mili says:

      We Adobe Lightroom users are in the position of drug users whose dealer has decided to “cut” the strength of his product. Over the years, we have become so addicted (invested time and effort) that we cannot go elsewhere (change products). And there is nothing that we can do about it!

      Hopefully, we will learn from this experience and try not to make the same mistake again (at least not with Adobe).

    • Stafford says:

      Getting in a pissing contest with a mad customer is a really bad idea. You guys messed up. Take the hit and move forward.

  2. Vicki Robinson says:

    Thank you for the apology, but I must concur with David Madison’s statement. Several of the things you moved had me scratching my head, but removing the option to automatically eject the card was one that just shocked me. It seems like such a silly move. Perhaps your data shows it to be an under-utilized feature, but that could well be because it is a feature that is not well-known. I discovered it by accident several versions ago and it’s been turned on – and a life-saver – ever since. I would say that those of us that know the feature exists, depend on it. I intend to hold off updating my LR CC2015 because of that feature alone. Please, please put it back – doing such a small thing will get you much more respect – – and appreciation – than you can possibly know.

    • Jason Dunn says:

      Hi Vicki! I’m curious – in what way is the auto eject a “life saver”?

      • David Grossklaus says:

        Jason – Auto Eject is a “Life Saver”. You can immediately take the ejected card and place back into the camera – and continue shooting if you choose to do so. You risk corrupting the card if not properly ejected. Ever take pictures of a wedding with a corrupted card? Formatting the card in the camera is much faster than via the computer in my house. Too many mouse clicks and every camera manufacture I know encourages/recommends that the card is formatted in the camera

        • jack zucker says:

          That’s incorrect.

          1) You can’t corrupt a card that hasn’t been written to.
          2) Even if it’s been written to, USB mass storage devices do not buffer writes unless you enable this in device manager and THERE IS NO USECASE FOR DOING THIS WITH A FlashDrive or SDCARD unless you are using it as a general purpose drive and then, only if you are editing files directly on the card.

          • Ryan Smith says:

            You must use a PC instead of a Mac. To Mac users this was a great feature.

          • David Grossklaus says:

            Check out Laura Shoe’s and others websites for their comments regarding damaging files without properly ejecting a memory card. Also personal experience validates my point – or were my corrupted files just a figment of my imagination? Please bring back the features/functionality that was removed. It took me less than 5 minutes to figure out the import dialog from scratch. What kind of monkeys do your testing?

          • Timothy Spear says:

            Jason,

            The default behavior of both Windows and Mac actually write information to the card every single time you open it. There is metadata stored in the file system directory which is updated, and because you are updating the directory data you actually have a significantly higher chance of data corruption.
            For this reason Mac and Windows both warn you of possible corruption if you remove the card without “ejecting” it.

            Tim

          • KC says:

            Just shaking my head…

      • Eric Dreczko says:

        Reason that auto eject is a “life saver” is a play on words but has merit as many a user has forgotten to properly eject the SD card… at least once – including you.

  3. Tom, thanks for your apology.
    The point is, I use every single step of the “old” Import panels, including “move” and the directory tree with the +(and italics) folder to be created. PLEASE give us back our so much used options on Import?

    Thanks, Clicio

    [TH: Thanks for the specifics, we’ve been gathering productive feedback all week.]

    • Mikhael LeMonde says:

      Tom,
      The import dialog was indeed complex but not dauntingly so. As others have pointed out, many of the removed features were an essential convenience which made the Lightroom workflow so useful for busy photographers.

      The new import dialog has inconsistent scaling on high-DPI displays (some text is almost too small to read, a problem which Photoshop recently fixed and Lightroom never used to have), perverts long-standing Lightroom conventions (‘dimmed’ means photos are selected, unlike elsewhere in Lightroom), hides important information about the photos to import (the ‘photo selected’ overlay obscures the central third of the photo) and about the outcome of the import (where the photos will be going after import), and requires me to do more work myself (without the ‘move’ option, I now have to open up a file window to delete photos after importing).

      Please, please, please, absorb some lessons from this mistake: that many people depend for their livelihood on the work you do, that in-software instrumentation is not the same as feedback, and that simpler is not always better.

      I shall look forward to your constructive improvements in 6.3!

      • Steve says:

        I agree with Mikhael. I prefer being able to navigate and create folders in the directory tree within LR, and to move files instead of copying. The new interface is clunky, lacks options, and is just plain dumb. What were you people thinking? Yes, people make mistakes. The true measure of character is how one rights their wrongs.

    • NilsWille says:

      I concur. I too use most of the “old” Import panels, and removing the directory tree on the right with the +(and italics) folder to be created was a major fault. Now it is a big hassle to import into the folder you like. We need a new update – and fast. People use Lightroom for work, it is not a leisure time app. 🙂

      Thanks, Nils

      • JoeT says:

        Same here… I was using most of the “old imports” too. I really dislike when I get in a flow and then something or someone (out of my control) changes what works… #justsaying

      • I agree completely. One of the absolutely most used features of the import was seeing the folders to be created. As I create subfolders by date, it was very helpful and easy to deselect certain date ranges that I didn’t want to import. This is especially helpful on my second machine, where I may only want to import shots from one day, but I have multiple days worth of photos on the card. That second machine doesn’t have my whole catalog, so I generally only deal with specific sessions of shots on it. Removing this feature is almost crippling to my workflow in these instances.

        This doesn’t even count the ridiculous extra step that now must be taken upon first launching the import dialog, where I have to select the card rather than having it auto select upon loading.

    • Rodolfo Giacco says:

      Clicio,
      Melhor voltar a versão 6.1.1 até tudo se resolver.
      Fiz a atualização e tudo começou a dar errado. Não pensei 2x. Voltei a versão.
      Qualquer coisa estou à disposição.
      – Clicio, better roolback to version 6.1.1 ’til everything gonna be right.
      I did the update and everything started get wrong. I did not think twice.
      Regards

    • I concur with the loss of this vital features being horrible, plus the auto eject…this was such a negative change in the interface…one of the things I had finally gotten used to was the old import interface…you can tell where things were going to go, how the folder structure would be set up, even before you did it. Why you took these things from us, without any warning is a serious concern I have, and I must admit, thought about switching to the Apple Photos program to store and catalogue my pics. Please change it back to the 6.1.1 interface and all will be forgiven, at least for me. A word of advice going forward, give your customers a way to keep the old import dialogue box, if they so choose. That way you can “experiment” all you want, but the customers won’t have to be held hostage to a lower caliber product than we are used to. Just my $0.02

    • Ray Brown says:

      While I don’t personally ever use move I valued all the easy ways to deal with photos from say a particular date by selecting or deselecting based on folders.

      I am one who always turns off analytics for any and all programs and operating systems. I like my privacy and don’t want to open any doors that might make my system less secure. Call me paranoid if you want but that is the way it will stay. Use you analytics to raise question but do not treat them as answers. Talk to real people who earn real money from photography before you make decisions like dumbing down that you have. I see some things that may take a while to get used to and I may eventually like and value just as many of the things you have removed took time to learn and appreciate. Auto eject is one that I always wondered why it have to be turned on as the default setting.

  4. Murashige Nakamura says:

    If I were you Tom, I would man up and hand in my resignation letter first thing in the morning for this failure. This is very intolerable. Failure and humiliation like this is not an option in my country.

    • Michael Watson says:

      No need for a moment like that and i’m glad your not from my country as it seems much more forgiving!

    • N/A says:

      nope, seppuku ! or sati … what do you think ?

    • Glad I do not live in your country. I fear many fine people loose their lives for nothing there.

    • John Waller says:

      Glad I don’t live in your country. Where I live there is room try different things, to make mistakes, learn from your mistakes and do your job better in future. Tom and Adobe tried to improve Lightroom. Good on them for trying. In this case, it was a high profile mis-step. They’ll fix it then we can all move on. No need to sack anyone for trying.

      • Blightroom says:

        Given that it is a monthly subscription there is a reason to ‘sack someone’. A monthly subscription (technically means it costs me something daily to use) had better work all the time. If it gets jacked up for a day, two days or a week there better be some refunds or credits.

      • LR user says:

        If they honestly were thinking of improving the product only they could have added this new easy-screen as an option that defaults to on. But given that they explicitly instructed a coder to remove the old dialog, and held to that even after their beta testers complained about it before release, they aren’t all that innocent as you make them out to be.
        This is a great example of a good product that suffers under a product management that fully grasp the entirety of its users… but thinks it does. (ooh shiny analytics!)

        Removing options is never a good thing. Especially not options that work well.
        If you think users can’t handle it, hide it deep in advanced settings.
        Also remember, analytics can be turned off. (And don’t even think about removing that option too!)

  5. Patrick McLeod says:

    Here’s the thing Tom, if people are paying for a product and then you remove features from said product that feels like stealing something from them. Also the “fix” did nothing for me and many others. Lightroom will not open for me at all.

    • Winni says:

      Also you are building a two-class society by adding features to the subscribed version of the same product that others have still paid for. I mean, the version numbers itself should tell you something. How can a version change from 6.0 to 6.1 to 6.2 be something different than 2015.0.0 to 2015.0.1 to 2015.0.2?

      You claim major new features (like the dehaze) have always been released with major releases and therefore the LR6 community will not get it, as they are stuck with their major 6.x release, but on the other hand the CC community gets it in a version, that has two minor version steps increased? This is hilarious!

      • Pieter Gellings says:

        Winni, I’m in the same boat but don’t agree with you. When I made the choice between a perpetual license for LR6 and going to CC it was clear from the website that with a perpetual license I would only get camera updates and bug fixes but no feature updates. Those would have to wait until LR7 (the next major release). So I think not getting dehaze is fair game. However I would have hoped we were also spared the new import feature, why we got that really beats me. I agree with Patrick that feels like stealing. Fortunately I don’t need any new camera support soon so I can safely stay on LR 6.1 until this mess is cleared and Adobe puts back the missing options.

      • Vic says:

        Yet they put the haze filter in PSE 14!!! So why not in LR6 ??

    • Loh says:

      yeah.
      and it´s NOT as if these features are not used.
      that is simply not true….. as the reaction of removing them proves.

      the LR team simply did this wrong….. there is no way around it.
      now bring the features back.

      maybe make a dumb import dialog and some instagram preset for the social media crowd when you think that´s the way.

      but give us, who make our living with photography, the option to enable the old import dialog that has powerfull features.

  6. Anne bury says:

    Although you may have analytics about who uses which features, I concur with the posters above about the auto-eject feature. It is perhaps not well known, but is very efficient for high volume users.

    • Loh says:

      analytics can be wrong.

      take win10 as example.
      most experienced user i know disable telemetrie…. so microsoft will think there are mostly noobs out there. 😉
      maybe that explains some of THEIR stupid decisions……

  7. Steve Dorman says:

    +1 for the eject card after import

  8. Doug Bulger says:

    For the import window. Offer a two tier approach. Basic with the features in the simplified window. Advanced with the features the pro needs like those in LR 4 an 5.

    • Stephen Starkman says:

      Totally agree with Doug, and hope this is the path the LR team will take.

    • Karen says:

      What Doug said. There are guided edits in Photoshop Elements. Included guided imports for people who need help, but don’t dumb it down for everybody.

    • John Ellison says:

      Here is the answer – put an advanced button on the import dialog or let us chose a default via preferences. Makes everyone happy

      • Patrick Corrigan says:

        I concur with John Ellison. There are many features that only some people use that are critical to those users. Give those features back to us, perhaps by including an “advanced button” (or some other mechanism). BTW, this feature should be a toggle that turns those features on until they are turned off. I personally import from disk, moving the images and converting them to DNG in the process. Without being able to move images while importing from disk I will have to completely change my workflow.

    • Rick Mili says:

      This is such an obvious solution to simplifying the interface and still maintaining the additional functionality that I cannot believe that Adobe did not think of this. What was your reason for rejecting this solution, particularly since you already have an “Advanced” button?

      Please give us back ALL the features that you took away in the latest “downdate”.

      As it is, I have to waste time uninstalling this abomination and re-installing an older version.

  9. Usage numbers or not, it still sucks for those of us who did use the feature(s) now removed. Consider this another vote to add the eject-after-import functionality back in.

  10. Tom says:

    Put back the import features.
    Staying with 6.1

    • David Grossklaus says:

      Me as well. Staying put with the product that works. Thank goodness I am not on the subscription model as my costs are already paid. I will not upgrade to newer versions until all removed items are restored. Time to look at the import feature of Capture One Pro – “professional features”.

      • Glenn says:

        I cancelled my CC subscription last year and switched from Lightroom to Capture One. Learning Capture One’s interface and converting my photos to the Capture One catalog was a non-trivial effort, but it was well worthwhile.

        Prior to my cancelling CC, I had spent many frustrating hours online with Adobe’s support folks, who were not equipped to resolve the numerous problems I encountered with many of the Adobe CC software updates.

        After reading the hundreds of comments related to this latest Lightroom update, I’m very glad I spent the time to convert from Lightroom to Capture One. As much as I liked the Lightroom application, I now realize that Adobe’s offerings are not the only option for serious photographers.

        I also recently started using Affinity Photo as a replacement for Photoshop and am blown away at the quality and depth of the Affinity Photo software. I am so glad to no longer be an Adobe customer.

        • Owen says:

          When I first heard about the creative cloud subscription model from Adobe two or three years ago I bought the last release of the creative suite that I could purchase outright, otherwise I would be forced into a monthly bill I did not want to have. I figured that by the time cs6 got long in the tooth some smart programmers would provide low cost alternatives to adobes products and thankfully I was correct. You guys at Adobe lost a customer in me when you went to the subscription model and nothing you can do will be able to win me back. Life goes on with or without the once incredible Adobe. This whole debacle over Lightroom confirms my decision. Sorry guys, but you are not the only horse in the stable any more, and your lack of caring for your loyal customers is going to cost you over and over and over in the years ahead in my humble opinion. I own a business and I care about my customers. It must be evident to them based on the high percentage of repeat customer orders I get. Read the book Purple Cow by Seth Godin to your team. Provide an excellent product or service. Take care of your customers. It really is that simple.

  11. Bill Tracy says:

    Your statement reeks of corporate BS.
    You’ve gotten fat and arrogant over the years.
    If you come to my house, do not expect to be invited in for tea.

  12. Kevin says:

    Not upgrading until you add the eject feature. Also, the AMD Radeon video card issue still exists months later. When are you going to fix that?

  13. The update released today does indeed now run on OS X El Capitan, however the first thing I got it to do was hang on generating Smart Previews. CPU / GPU ramped up, but nothing was happening, yet LR was not frozen – I could still perform tasks within LR. Restarting LR solved this, but I worry about this taking place on my larger shoots, like a wedding. After that, I tried exporting 4 JPEGs, 3 of which failed because “The file could not be written” and “No rendered photo exists on disk.” Restarting Lightroom again solved this and allowed me to export the images without problem.

    Something is still up with the new Lightroom. I am also not a fan of the new Import dialogue – why do we need to change screens several times to do the same thing one screen used to provide quite simply? The old dialogue was fine – Source on the left, Selected images in the middle, and Import preferences on the right. In what world is that difficult?

    • Butch_M says:

      “In what world is that difficult?”

      Yes, how did Lightroom ever reach it’s current level of adoption if the Import dialog was really such a detrimental hurdle to clear?

      If a pure novice would view any of the marvelous video tutorials by Julianne Kost on Lr importation and still have issues … there is no way ANY re-dsign of the dialog is going to help lower the bar …

      • Loh says:

        the problem is that adobe now focuses on user who know sh*t about computers. the selfie and social media crowd who never has to use a folders or navigate through a directory tree.

        these users dont know what a folder is.. because the software stores files for them.

        of course for them the import dialog is complicated.
        but you can´t make decisions for professional software on the sorry “dumbest users” (when it comes to computers).

  14. John Pane says:

    I hope you will also revisit your decision to make LR6 (not CC) a second-class citizen.

  15. Jared says:

    To avoid situations like this maybe set up some kind of poll and ask the users what they would like changed. From what I’ve heard everyone seems ok with the features they just want it to be more reliable and faster.

  16. Richard Waas says:

    I agree with all the above comments about the import screens and process as they were in the previous version. it was very easy to understand and the eject card feature was very important. Please put it back in the next upgrade!!

  17. Jack says:

    This is too little too late. What will Adobe do to restore confidence in what had been a great product? This part of the note, “…we introduced instability that resulted in a significant crashing bug. The scope of that bug was unclear and we made the incorrect decision to ship with the bug …” implies that developers knew the bug was there but released the update anyhow.

    Stripping out features combined with the practice of not making some features available to long time customers (dehaze) make me wonder about Adobe’s commitment to customers who want to purchase Adobe software.

    I am very disappointed in the way Adobe has handled the vers 6 releases.

  18. Dave Doeppel says:

    How about getting those of us who are ACE and speak and teach others more involved with your Beta program? That would be a step in the right direction.

    Dave Doeppel
    Adobe Certified Expert Lightroom and Photoshop

  19. Enoch says:

    While its good to hear an apology from Tom, and thanks, there’s been a lot of damage done by shipping this unusable product which has resulted in a lot of my time wasted and money lost in the past five days (I’m still having to deal with it). It’s stressful. I don’t know how trust can be restored in Lightroom, let alone Adobe as a whole. Unless the company regroups and stars focusing on unbloated programs which talk to each other in a far more seamless way, I just can’t see a future for them.

    The issue is partially the fault of the Lightroom team, however, it is the leadership from above, that is also responsible for guiding the team in this direction. Maybe Tom resigns, and he’s replaced, but the issue isn’t resolved unless the leadership the top decides to think through things differently.

  20. Paul Sumberg says:

    While I thankfully did not upgrade so I haven’t looked at the “new” import screen, I wish to say that I use nearly ALL of the features available in the current (6.0 and earlier) import process. To have to manually eject my memory cards after importing images is simply not acceptable. And most certainly it couldn’t have been all that confusing for your customers. I’ve grown accustomed to having Lightroom do exactly what I want to do with my images when I import them and I do not want to take a giant step backwards. I have been a Lightroom user since version 2.0 but by no stretch of the imagination am I married to using it.
    As for your allowing Lightroom to be released with a known bug (you always have bugs but until now I thought they accidentally slipped through), I feel it is absolutely NOT acceptable. This is not what I pay ADOBE for and if I can’t be certain that you have done your very best to release into production a reliable product than I must reconsider just what it is I am paying you for, and why.

  21. Savannah says:

    I am a relatively new user of LR and I adore the eject after import feature. I am with the seasoned users above and can’t justify upgrading until the feature is available.

  22. Richard Drdul says:

    All I heard in Tom’s apology regarding the import dialog is that they decided to make some changes but didn’t execute the roll-out very well. I didn’t hear that they understand why users are upset about the changes, and more importantly, I didn’t hear that they plan to bring back features that people want and need. In Tom’s responses to comments, I heard defences of the changes. Based on what I’ve read, I am not hopeful that we will see (something like) the original import dialog restored to Lightroom. I don’t understand why Adobe didn’t add a “streamlined” version of the import process for new users and others who don’t need extra features, while keeping the original “advanced” version, but maybe that would have displeased the gods of analytics.

    • Ray Brown says:

      Here here. Many Scanners have an easy mode and an advanced mode. It would make perfect sense here in the import module. Over time people who start with easy mode can explore the advanced features and learn them. Everyone wins.

  23. Jessica says:

    How about making a version that does not take up ALL my RAM? It is ridiculous how much memory LR and PS take up on a computer. Instead of removing useful tools and features make.it RUN BETTER! Also, how about a clone/healing brush that’s a little smarter when selecting content aware fill? Or better yet, make it like the PS version where you can select the area you want to clone first? These are useful improvements, not this BS you are doing now.

  24. Scott says:

    I appreciate the apology but it seems a bit calculated and disingenous. This is the worst screw-up that I recall, but certainly not the first. The last several major releases of Lightroom had bugs or performance issues that were show-stoppers for many users and could/should have been caught in testing. I am tired of beta testing Adobe software post-release. Adobe has demonstrated very little in the past 2-3 years to indicate that they understand the needs/frustrations of their devoted user base or care deeply enough to change course. Every release seems to add more features at the expense of stability, performance, or usability with little regard for the voice/experience of the customer.

    Well, today is the end of the line for me. I have no confidence that Adobe has a clear strategic direction for Lightroom, or that it will devote resources to fixing long-standing bugs. I cancelled my Photography Plan (early, so paid a penalty) and I am back to a perpetual license while I evaluate other options (which will most likely not include Lightroom 6.x or 7).

  25. Thanks for your apology. It is absolutely in its place, as I have been very frustrated for the last couple of days. bBt I am not convinced you care about me as a client before the old import is back with all its functions together with a stable version of LR.. I have downgraded LR to CC2015.1.1 and I am not upgrading anymore until I am 100 % sure that you can deliver a stable version that has the old import in it.

    If you still, after experiencing the massive protests from the professional LR-user community, want to keep the dumbified import, please make an option between the two import alternatives (dumbified/old import) when you import.

    I have now learnt that you (the company Adobe) do not care about your customers the way you I expect you to.
    Also, I would like to add that this whole mess has made me use the opportunity to look into other Raw-converters, like Capture One.

    -Karl.

    • Mihael says:

      … you’ve learned late. Lightroom is obviously tip of the iceberg. I stopped even posting feature requests for other apps, like Premiere. There are treat a paying customer like we would be obligated to pay and should be happy they are willing to give us permission to use their work-of-art-apps. It reminds me on communist regime, where people ought to be grateful for privilege to be citizen.

  26. Rick Weiss says:

    I agree with above comments. .I use the eject after import on every import. Also, I don’t allow any software to dictate the directory structure I use and specify it every time.

    I also never check a box to allow software to collect and upload statistics on usage. Therefore my usage patterns would not have been taken into account for the decisions in question.

  27. John says:

    Are you going to “work hard to earn your trust back” by restoring the features you removed, or is that just soothing talk?

  28. Jerry says:

    I am not a fan of changing the Lightroom Import interface to a more simplified model. However, if a simplified Import interface is truly necessary, then at least provide a user option to revert to the “Legacy Import Interface”. I’ve been a user of Lightroom since the release of version 1.0, and I hope that my recent decision to upgrade to LR 6 doesn’t prove to be something I regret.

    • Axel Krueger says:

      100% agree with that post. Really would like to have the old import back, but see the need to make lightroom easier to handle for new users.

  29. Butch_M says:

    Mr. Hogarty,

    I appreciate the apology, but it seems it is offered only half-heartedly. The use of the term: ‘very low usage features’ reveals you may still not fully grasp the seriousness of the situation.

    I mean, who informed you these were low usage features. If it was feedback from your private alpha and beta testing group, you either need to expand or diversify that pool because if the past four days or so on the feedback.photoshop.com discussion that recently moved into second place of all-time on that site is any indication … you are trying to make decisions on inaccurate and/or incomplete information.

    Nearly 500 users in unprecedented fashion found the time to make their feelings known on this issue and you still choose to label it as the ‘removal of low usage features?’ …

    That attitude really does make me doubt your sincerity … and I have been on this journey with you since the very first day of the very first public beta back in 2006.

    I just want to caution you, if you want to earn back my trust, and by all indications I am not alone in this sentiment, you and your team really do have a Herculean task ahead of you. We won’t be fooled twice.

    • Guy says:

      I wholeheartedly endorse your comments.

    • Joseph says:

      Well said, I appreciate the apology but he still gave a reason for such a bad move when he should have said “We were wrong, we will get LR back to where it was and make it better”.

      We all make mistakes, but Adobe has been making mistakes over and over again since LR6 came out. I started with LR4, and moved up to LR5 which basically was a better version of LR4. I installed LR6 on day one, and reverted back to LR5 within a couple hours, because I could immediately tell that it was a much slower, clunky program.

      I have a low tolerance for updates that take features away and don’t improve things. That is why I do not update my IOS or OS on my Mac products. The difference with Adobe is that I know that when I buy my next camera, I will NEED to use their updated products. If they keep making changes like this it leaves me no option but to find an alternative program.

      I’ve been waiting since the spring to LR6 to come together, and this update has proven that that may NEVER happen. Even in this apology, there was NO reassurance that they were going to put LR back to where it was, there was no concrete plan.

      So you are essentially saying “We are sorry you are mad, but…. kinda sucks for you because we decided on what’s important to your workflow”.

      Lightroom was SOOOOO amazing before, that I believe there is still a sliver of goodwill left between Adobe and the photographic community, but they need to be incredibly careful in how they proceed.

      While I appreciate the apology, this was not a whole hearted approach and did not alleviate my concerns.

      • Joseph says:

        I want to hear that you are putting LR back to how it was before, If that’s not on the table then there is no chance of your building any trust. If you are offering something less advanced than what you had, I am not interested in your products.

        I need to know now, because I need to start looking into other alternatives for my post processing if Adobe shows ANY signs of not rolling back these changes and actually making LR better.

  30. Florian says:

    Tom, First, your recognition of the problem you, Adobe, created by releasing this disastrous update prematurely and your apology is a step in the right direction. Every time I hear the word “analytics” applied to a business model, the hairs on the back of my head stand up. Analytics provide just numbers and percentages but have no soul, no feeling. It is obvious from the overwhelming cry of the photography community that the cold numbers missed the mark by a wide margin. Something as simple as ejecting the card after import was somehow lost in the numbers and graphs and pie charts. I like Dave Dieppe’s idea of some form of beta testing with the ACE community in future updates. I am still very much in favor of the option to go either with the simple import process and to have an advanced/pro level option for importing as well by bringing back the removed functions. Tom, your admission and apology was the first course of the meal, having the options for a simple and advanced import process would be a WIN-WIN for Adobe and the icing on the cake. This would really go a long way to bringing everyone back into the Adobe fold and regain your lost trust. Thank you.

  31. Paul Andrew White says:

    Hi Tom,

    I was quite shocked when i downloaded a minor update to LR that became totally unusable and had to do a quick switch to bridge to get a job out of the door.

    You have recognised it was an error in judgement, have responded quickly and normal service is resumed, thank you for that.

    Looking forward to more updates

    Regards, Paul

  32. Mick Brown says:

    I’m not allowing CC to upgrade until the import dialog is closer to what it was last week. Especially need eject after import. I also saw discussion elsewhere that there were problems with previously installed plug-ins. I’m not sure if it was in reference to the new PS LR or both

  33. Nick says:

    Tom,
    Trust is like a bucket with a slow leak. Sometimes that leak can be stopped, other times, it just pours out. Once that bucket of trust has been emptied, it can’t be refilled.

    The appalling changes to the import function have almost drained that bucket.

    Good luck.
    Nick

    P.S. My office has started to look for alternatives to LR.

  34. Give us the ability to return to the pre-existing import module..

  35. Guy says:

    Adobe is a business and is looking to make as much profit as it can by reaching the widest audience it can. Or, “let’s dumb things down to reach the broadest audience regardless of the needs of the people who bought and supported the product and made it successful”. While Adobe is entitled to a profit the people whose livelihood depend upon the functionality of the product are directly and significantly harmed by the pure greed exhibited by Adobe to reach “the masses”. If you want to be an “also ran”iPhoto type company, advise your customers in advance so they can make other arrangements to survive and support their business and family needs. This whole episode is tantamount to Coca Cola “reinventing” Coke. How’d that work for them? I would scrap this entire last release, got back to where things were and start over. I, for one am looking for acceptable alternates in the event Adobe doesn’t wholly fix this problem. This cannot happen quickly enough. And, some IDIOTS need to be fired.

    • YouControl says:

      If the removal of the auto-eject feature significantly harms you, your tolerance level for harm must be very low.

  36. Rory Hill says:

    Hi Tom

    If you really want to reignite the discussion like we had in 2006 you’re going to have to do better than your rather lame apology. You still make it sound like the problem was poor communication about why you were making the changes to the import module while 500+ users have told you you broke their workflows by removing functionality. You want to talk, how about announcing the return of the real import module while you decide what to do next. I suggest you add a mix of common sense to your “metrics”. By your logic I imagine the split tone should go in the develop module as I imagine it isn’t used much either.

    • YouControl says:

      Broke their workflow? How about: ‘Required them to slightly adjust their workflow’.

      • Brent Busch says:

        When it repeatedly crashes, corrupts your catalog, etc, that isn’t an adjustment of workflow, it’s a complete failure that costs people lots of time and money. Completely unacceptable.

  37. Jim Hughes says:

    Fortunately, I haven’t upgraded, and I won’t until this mess gets fixed. The apology is only a minor first step. And put the eject upon import back in. This is just crazy and reminds me of how Apple dumbed down their professional products and lost the confidence of their customers. You didn’t by chance hire some of those folks did you?

  38. Thom, it’s real simple.

    Don’t *remove* any features until you consult with Jeff Schewe, Seth Resnick and JP, at minimum.

    🙂

    Thank you for the apology. I believe you to be sincere.
    Stephen

    • Lance Keimig says:

      Tom-
      Thanks for starting addressing the issues with the latest release. Like most other commenters, I strongly prefer the old import process, and ALL of the features you removed. As someone who works with Lightroom users to help them clean up their catalogs, the MOVE option is essential. The eject or not eject card option is essential, and being able to easily navigate through where we will import to is even more essential. Please restore the import dialog.

    • Loh says:

      as a 3d max user this reminds me on a time when some important key people left the developing team and for a few years the new versions that came out where really dissapointing.

      the key peopel who left loved and used 3D max.
      the new people where coders but they had no real love for the product they did not even used it themself.

      adobe should not make the same mistake.
      there are enough ideas and bug reports in the community forum.
      ask professional and people who work with LR for years.

      don´t let people, who never used LR, decide how our software should look like!!!

  39. Warren Young says:

    Thank you for responding to the feedback quickly. I wish it didn’t take a user revolt to get you guys to respond so quickly all the time.

    For me, the big missing feature is the “move” option.

    But more broadly, the quality of Lightroom releases have been going down for years, starting from version 4, when you added the mapping module that you could — and still can! — crash within seconds, if you know how.

    Please, take my $10/month, aggregate it with some other peoples’ $10/month, and use it to pay software developers to fix bugs. There are many known but unfixed-for-years bugs in Lightroom. I’m happy with the features I have now. It’s past time to make them work 100% reliably.

    I’d be fine if you spent the balance of 2015 and the entirety of 2016 doing nothing but whittling your bug backlog down.

    I know, the old software model says that you need new features every 18 months, but isn’t this one of the attractions of the subscription model? The proposition is, “Here’s the product, just pay us a reasonable fee, and we will maintain and enhance it continually for as long as you keep your subscription current.” That gives you license to choose between features and maintenance; you are no longer forced to choose features.

    Want another example of the kind of unresponsiveness I’m talking about? Here’s a bug I filed with you guys a month ago, complete with a *reproducible test case*, which has had zero response:

    http://feedback.photoshop.com/photoshop_family/topics/buggy-interaction-between-write-keywords-as-lightroom-hierarchy-and-person-keywords-in-lr-cc-6?rfm=1

    It’s a bug introduced with the People feature, but here you are taking other features away to improve overall quality instead of fixing the features you just added in 2015.

  40. Ian says:

    It seems that Adobe have managed to upset a whole bunch of customers that use Lightroom in a commercial and professional capacity. photoshop.com is full of negative comments about the latest import process. I have to agree with every negative comment. We have a library of 2.8 million images and use the import feature everyday. Eject after import is vital, as is move (which we use all the time), we rename every file at import and the folder tree is vital to ensure we are putting in the correct folder.

    You really need to consider who your customers and bring back features that many use.

    Your team of researchers, educators and customers that say the import is daunting may be right (so is using parts of Photoshop and many other products in your stable) but that does not mean they should be removed. If you made Photoshop less daunting by removing features you would lose a whole wealth of customers. Lightroom is a professional product that you bundle with Photoshop and target professional photographers. . Listen to them admit you made a major cockup and roll back and incorporate the old import options that you have removed. Otherwise it has to be bye bye Adobe

    • YouControl says:

      You upset a whole bunch of customers already whenever you change as little as the colour of a button. It is as if your only option for not upsetting anybody, is to not change anything … ever. But that of course upsets people who demand certain changes.

  41. Neal Savage says:

    Did you talk to any real persons?

  42. I think there is some extreme over-reaction here. Yes, the LR team made a huge mistake on this release. Mr. Hogarty has owned up to it and apologized, and now the team should be given the chance to fix it. No-one needs to resign here.

    I have been a software designer for over 25yrs (not for Adobe), and I’m going to let the people who are not in the software industry in on our dirty little secret. Every piece of software gets released with known bugs. EVERY piece of software has known bugs. There are no exceptions. If a development team waited until every bug is fixed, nothing would ever get released. It’s just not possible to write a complex piece of software that is bug-free.

    It is the responsibility of the designers, the software architects and the product managers to understand the impact and severity of the known bugs and to make tough decisions about which bugs are severe enough to delay a release and which can wait to be fixed in the next release. In this case, the LR team made the wrong decision on at least one of these bugs. Hold your mouse up high if you’ve never made a decision that later proved to be wrong (if you’re currently holding you mouse up, you’re lying to yourself and you look foolish).

    I will concur with Mr. Hogarty that until a designer is able to reliably reproduce a bug it is EXTREMELY hard to fix it. Many times in my career I have been in the stressful position of having managers hounding me for dates to provide a fix for a bug that I don’t even know how to reproduce yet. It’s not a nice position to be in.

    So I will cut the team some slack on the bugs introduced and hope that the worst of them are fixed in 6.2.1.

    The bigger sin committed by the LR team IMO is to not consult and listen to the existing user base before making such sweeping changes to such an important function as the import.

    Removing functionality is always a dangerous thing as you can never have a 100% view of how the software is being used. As a software designer I understand that every line of code adds to the cost of maintaining the code overall, so I know it is important to remove unused code. But I also understand, as a user of software, how frustrating it is when functionality I’ve come to rely on is taken away.

    I was fortunate in that I watched Sean McCormack’s video (http://lightroom-blog.com/2015/10/05/lightroom-6-2/) comparing the old and new import windows and made the decision to not upgrade. I made that decision solely based on the removal of the eject-after-import option. I rely on that option on every single import, and I will add my name to the list of people asking for it back.

    I am also disappointed with the removal of the Destination Folder filter to select which photos to import. I find “Don’t import suspected duplicates” to be unreliable, especially when I don’t always import to the same drive (sometimes I import to my internal disk, sometimes to an external). When I travel I do not erase my cards until I get home, so I will have several days worth of shooting on each card and I usually only want to import the current or previous days photos since the older photos will have been imported already. The Destination Folder filter was perfect for this.

    The removal of the “Move” option is puzzling to me. While I never used it personally, it just seems like such an obvious and easily implemented option that I don’t understand why it was removed.

    I can understand how new users might find the destination folder tree daunting, but it is also a function that I have come to rely on and I am disappointed that it’s gone. I think hiding it under the advanced options, which is collapsed by default, would have been a better decision to avoid scaring the newbies while still providing this important functionality to the experienced users.

    This is just my (very long) 2¢ worth, but I do hope the LR team will listen to the current user base and bring back these features that we are asking for.

    …Mike

    • Rudi says:

      So you release software knowing it has errors? I know from theoretical computer science that you can’t prove for the physical absence of errors but you cat test every as Anyway, before starting photographing career I was in software development, too. We had release management and depending on it there have been several test stages. If you have new functions you depend on new use cases which flow into test cases. Several different groups tested using the test cases to make sure the software was tested as good as possible before it was released. And of course every other use cases that have been dependend on the new test cases!

      Adobe knows nothing about software quality of test methods. Seems like hacking some new functions into the the system and replacing well working functions with some odd ones which slows your workflow down.

      • “So you release software knowing it has errors?”

        Blunt answer, yes. I have never worked on a product team that did not operate this way.

        “Adobe knows nothing about software quality of test methods. Seems like hacking some new functions into the the system and replacing well working functions with some odd ones which slows your workflow down.”

        You’re confusing testing and quality with usability and functionality. The dumbing down of the import function is not due to lack of testing or poor quality, it’s due to a lack of understanding their users.

    • Zain says:

      Mike: very well stated. Totally agree

    • Chris says:

      Like!! Well said.

    • Warren Young says:

      I, too, am a professional software developer, with a similar span of experience. I must rebut several of your points:

      > Every piece of software gets released with known bugs.

      That’s a bit overstated. A lot of software is released without any *known* bugs, but has bugs anyway. Plus, there is at least one piece of production software, used every day by millions of users, which has no known bugs. (TeX).

      The real question is, what happens when it comes time to release version n+1, where you now know about the bugs in version n, and are choosing whether to spend finite development resources to fix the reproducible ones or to create new features instead. Adobe’s been releasing new versions of Lightroom containing known, reproducible bugs for *years*. Now they’re telling us that their intent is not to fix them, but to lop off the feature containing the bug? And we’re not talking about rarely used features here, but ones people have built everyday business workflows on top of.

      > until a designer is able to reliably reproduce a bug it is EXTREMELY hard to fix it.

      True, but Lr 6.2.1 contains many reproducible bugs. I gave a link above to one that goes back to Lr 6.0, and mentioned another that goes back to Lr 4.0. There are more, but I can’t be bothered to catalog them here. Adobe surely knows about those and more already.

      > not consult and listen to the existing user base before making such sweeping changes

      Agreed.

      After the CC change, Adobe stopped releasing public betas. I’ve been testing those betas since before 1.0 came out, and it’s always been one of the best reasons to use Lightroom: the perceived ability (though possibly a false one) to influence the direction of the product before it is released, rather than what we’re doing now, which is criticize it afterward.

      > you can never have a 100% view of how the software is being used

      Adobe baked telemetry into Lightroom. They knew full well they were removing features that people are using every day.

      > The removal of the “Move” option is puzzling to me.

      Lightroom has a tendency to nanny its users. There are many features the software should have, but doesn’t, because someone decided they could be dangerous. Observe how many Lr plugins depend on exiftool to get things done, for example, when the Lr SDK should have had these functions already, from the beginning.

      Move has always been disabled when the source is a camera card, on the theory that you’ll want to erase the card in the camera, and that it acts as a backup until you have backed up your LR catalog contents.

      That’s fine as far as it goes, but there are use cases where you don’t need or want that nannying. What if your photo source is an online photo sharing site, so that you can always just re-download the photos if something goes wrong on the import? Moving the photos from the download folder is exactly what you want here, to keep your download folder clean. I don’t *want* a copy of Uncle Bob’s photos sitting around in my Downloads folder after I’ve imported them.

      The question of Move vs Copy should be a *user* decision, the same way it is everywhere else in the system. I’m all for sensible defaults, but removing features because someone could possibly cause a problem with it is just mollycoddling.

  43. Gstark says:

    I have to say, I never expected from Adobe what many of us have experienced with this last upgrade… I’ve been using PS since version 4.5 and LR since its release in 2094…I can’t ever remember an upgrade that took away features I used so regularly… Yes, I want the eject card feature back and all the import options as before. This taught me one important lesson…. Normally when the creative cloud app alerted me to an upgrade I’d click the upgrade button without a thought … I got use to always getting an improvement to my workflow!
    You can bet I’ll use a lot more caution next time ! This was sad and scary… Makes me wonder where your steering LR…. I don’t want Adobe to steer LR down the same road as Aperature and Finalcut Pro ……

  44. Zain Willoughby says:

    Tom: I’m not a professional photographer but I could not agree more with all the many comments I have read on this issue. I too use every one of the functions that have been dropped in the new release. Please add my vote to call/plea to restore what to many of us is critical functionality. The suggestion of user selectable streamlined and advanced import interfaces seems most reasonable. A swift response along these lines will go a long way to retaining the loyalties of the customer base upon which Lightoom’s success has been built.

  45. Mark Hoyle says:

    I still don’t understand how an “upgrade” removes key features that many photographers rely on in their workflow.
    The import process was not broken obviously from the response you are getting on this issue. Maybe you should look at the quality of your tutorials if some individuals don’t understand the software. In fact you should reevaluate your support staff. I called about this upgrade and the person I was assigned did not know how to use the new features! Don’t remove features we have used for years or at least give us the option of keeping them.
    Thanks!

  46. The problem with analytics is that they don’t delve into the customer psyche and measure passion. Your customers aren’t passionate about the product; they’re passionate about the result! Please respect the passion and focus on making the result excellent for current as well as future customers. People and companies make mistakes. First comes recognition; seond comes an apology; third comes a fix. I hope you’re moving full speed ahead on a fix. No need to resign or fire anyone as long as you learn from the mistakes!

  47. Scot Hampton says:

    Kudos Tom for addressing the community so quickly and opening up the dialogue,
    but as far as the numbers go (re: “In-product analytics”), I would offer another gentleman’s advice:
    “Not everything that can be counted counts, and not everything that counts can be counted.”
    -Albert Einstein, Physicist

    “overwhelming customers with every option in a single screen was not a tenable path forward.”

    What I’m reading here is, and correct me if I’m wrong, is that you mean *new* customers. The current customers/users, I don’t think any of us are overwhelmed by the import dialog; most professionals have complex workflows that the many options help execute. This all would hint that perhaps Adobe is trying to create a more streamlined/amateur-friendly version of LR to increase new customer acquisition? If so, leaves me asking more questions…is LR having an identity crisis? Can Lightroom be all things to all people? Perhaps Adobe needs to make a separate Lightroom Elements version for the OTC consumer looking for a simple interface (on par with iPhotos/Photos), or somehow integrate the ability to choose your import interface (pro/simple)?

    LR room is a great tool, and I hope that you’ll consider restoring the previous import interface in the next update.

  48. Mihael says:

    Anyone read this apology carefully, could read he is NOT apologise for new import dialog, but ONLY for bug related. And they think the issue is bad communication. It’s like police in our country: There is no slight chance they made a mistake – the only possibe discussion is about way how we will pay the ticket.

    Look ADOBE: If you really care (If you are not like Animoto), and want our trust back than instantly revert old import dilaog back in full. No stupid play like we listened and we are giving “move” and “eject” ferature back on top of new import dialog and say “It’s there, see, there three levels deep in the menu under settings menu, under…” STOP IT! We do not want this new import dialog. Period. We were paying for product it was. When in the working mornig of monday we opened Lightroom we were shocked. No communication would change that.

    We want apples, give us apples. We do not want fancy potato, even if is golden metallic plated. We want our apple back. NOW! Any other is pure insult.

    Than when you knee down we can gain trust by asking if we want change, and what we want. Than we will discuss.

    And most important: I filled hundreds if not thousands feature requests and bug reposrt in last decade. Little to nothig in Adobe applications went good way in the real improvement direction. Good improvements were in era if CS1 to CS3 – later was unstable. CS4 brought some improvements (mostly real multicore support). CS5 and 5.5 was mist, CS6 is somehow latest good compromise. Than CC came and we are in toboggan slide of stupid unlogical changes toward more and more aukward and limited and constantly force user to new and new adaptation of workflow.

    What you want to achieve? North Korea style, where all are like one (same haircutt, same way of living life)?

    I know… you have your high time now and loosing 20% old users is like spit in the ocean, while youl gain other. Some will adapt (again), some will leave, some will come… So much you care.

    So this opology is NOT ACCEPTED, since it is dissembling.

    • Keith Reeder says:

      “Anyone who read that apology carefully, could read he is NOT apologize for new import dialog, but ONLY for bug which is related.”

      Of course it’s an apology for the whole mess:

      “The simplification of the import experience was also handled poorly”

      “In making these changes without a broader dialog I’ve failed the original core values of the product and the team.”

      “At the same time we removed some of our very low usage features to further reduce complexity and improve quality. These changes were not communicated properly or openly before launch”.

      What was that about “reading carefully”?

      • Colin Oatley says:

        Mihael is correct. “Poorly handled” refers to the manner in which the features were removed. It is not an apology for removing the features.

  49. Derek Helt says:

    I still have a sour taste in my mouth because of the lack of dehaze on the non CC version of LR. I’ve spent a lot of money on LR & upgrades over the years. I even bought LR back when it was still $300. So crap like this adds to my unhappiness with Adobe. Put the auto–eject back in, please. I used it on every import.

  50. Judy Tillson says:

    I haven’t upgraded yet, based on a few blogs that recommended waiting & so glad I waited.

    I’d like to request you put back the “eject card” feature. Why on earth was something like this taken out? Such a handy feature to use.

  51. Bob Ware says:

    Please do away with the silly, giant check marks that cover up the images that are to be imported. How on earth are we supposed to be able to see which images we do and do not want to import. I will grant you that most of the time I want to import all of the images on my card, but quite frequently there are large runs of images that I don’t want to bring into Lightroom. I was very happy with checkboxes and dimmed thumbnails for the files I wanted to skip.

  52. René says:

    With a kind of monopole in the image processing market Adobe became more and more arrogant profiting of his situation to impose all and anything to the users.
    It is inadmissible that users pay for features and that then Adobe removes these features without their consent.
    But take care Adobe Lightroom Photoshop, times change, you are a big dinosaur, old and inerte. Take care, other software houses (Capture One, Affinity) are developing excellent products, with modern and efficient concepts, and they will be (are) “dangerous” competitors and will very soon smash your arrogance!
    By the way you have lost one user for sure!

  53. Uli says:

    Tom – I appreciate your apology for the bugs – accepted. But regarding the UI and functionality change you don’t seem to have listend to the vast majority of the users – who don’t want this redesign and even more important need most of the features you took away in their workflow (won’t repeat them – they have been listed often enough)
    I have never been a fan of User Interface redesigns but can live with them as long as I have the functionality available I need. This is however no longer the case with the new Import dialog. Frankly – if turning LR into a “one size fits all” workflow “app” is the direction that Adobe continues and maybe even turns LR into a “one size fits all” raw processor I will be forced to go and look for an alternative. I would hate to do this but would take the trouble if I cannot find a reasonable workflow in LR any more.
    I’m only glad I didn’t jump on the subscription boat but bought LR6 . So I can continue to use LR6.1 for a while and if I need to move to other software I can still continue to work on my old photos with LR and don’t lose my development settings for the photos I put work into.

    Uli

  54. Erling C. Hollmann says:

    The new import window belongs in LR Elements, not in a professionel tool like LR6.

  55. Ryan Cutler says:

    The import screen is now a hot pile of garbage. I hope I never have to spend another moment on the phone with your terrible support team, also. Have you fixed the catalog syncing issues with collaboration over your servers?

    I much prefer spending my $10/month on Netflix, that at least works as advertised.

  56. Lorenzo Colloreta says:

    Hello there,

    quite happy to read an apology, it means when you want to listen you have plenty of feedback, but at the same time it shows you listened too late. I think we are not really talking about removing unnecessary options due to some user-collected data, please – stop lying. Having a simpler “newbie approved” import experience is what you (possibly) tried to do with the new “add photos” screen, which is actually a way to introduce an alternative workflow for beginners. Touching the standard “advanced” import panel makes no sense, especially removing options from there (was really the Eject Card so complicated to code and maintain?).

    My point is that truth is hidden in details: if you managed to put a huge round and opaque checkmark icon right IN THE MIDDLE of a photo thumbnail and also greying the selected photo (!!!) it just mean that the people who did that and the ones who were supposed to test and approve that had their brain switched off for some reason. Any mediocre UX expert would tell you this is insane for a photography workflow, let alone anyone who has been part of the Lightroom team – a software “designed by photographers for photographers” you said more than once – in the past greyed images were the unselected ones. Where are these people??

    This brings to another point which I’d just copy/paste from another comment of mine: Do you know what I really believe happened and you’ll never admit? This is the result of the new, distorted, “agile-like” coding workflows that allow something to ship even when still in development, just because you need to ship something. Something I’ve already seen elsewhere (Photoshop design space anyone?).

    You jumped on the CC wagon to be able to release new features as soon as there were developed.
    You failed because you’re still driven by release deadlines, possibly even more than before.

    Please ask for more user feedback in the proper place (beta program) and at the proper time (BEFORE releasing something).
    thanks

  57. KB says:

    The ghastly visual design of the new Import interface only adds insult to the injury—in the case of working pros, financial injury— resulting from removing features.
    If Adobe wants to turn Lightroom a crummy version of iPhoto, that’s their decision. As a Lightroom user since the beginning, I’ll be enjoying 6.1.1 for the foreseeable future, after which I’ll bid Adobe “adios!”
    I cannot support…or spend my time with… stupidity.

  58. Aidan says:

    Devil’s advocate opinion: Every extra feature Adobe keep in the software is so many more iterations of testing prior to release. This adds up because it is multiplied by every configuration to support, and yes there shold be automated builds etc etc, but even that takes time and resources to configure. There is no infinite budget.
    It is wise software release management to keep the number of features you support under check.
    Note, I’m not saying the features Adobe removed were correct in the slightest – I liked Eject Card on Import too. But I don’t believe having two Import screens is likely nor sustainable for Adobe’s Lightroom team to support and test every release. I hope there is a middle ground.

    • Loh says:

      polish existing features!!

      i don´t need new features with point releases.
      as a professional i would be happy when the EXISTING features would be polished and bugs fixed.

      sure i like new features…. but if i have the choice between buggy new features and polished old features… i take the later.

      take your time to test an PERFECT new features.

      there is so many in LR that is in need of improvement and nothing happens.
      instead they focus on REMOVING features…. how stupid is that?

      face recognition is not up to todays standard.
      ask google how to do it right.

      the map module gets no love at all and compared to sharware or even free apps is… well crap.

      demosaicing is getting old.
      not only does fujis x-trans files look terrible (still)… no, compared to the competition the whole demosaicing needs improvement to be class leading.

      sharpening in LR is terrible.
      i don´t use it at all.. many good photographers teach in their classes to NOT use LR´s sharpening.
      that should give you something to think!!

      i can go on for a while but i will stop here…..

  59. bernd says:

    From the beginning i worked with Aperture. But Apple recently forced me to change from Aperture to another software. Because Apple finished Aperture and published the new ultra super super duper app PHOTOS.
    It is a change from professionell to consumer needs. I was between Capture One and Lightroom. I chose Lightroom. After that i moved Terabytes of images. Work of weeks!

    And what happened now: Lightroom changed the import Dialog from professional to consumer! And i think we see only the starting point of this way. Don ́t use Apple as a role model anymore, please. it will be the worse scenario for professionell photographers.

    And the “funniest” thing is (as a LR 6 user), that I don´t get the dehaze function but instead i ve got the new import dialog…

    Maybe at first you should check up your analytics algorithms…

  60. Loh says:

    as a 3d max user this reminds me on a time when some important key people left the developing team and for a few years the new versions that came out where really dissapointing.

    the key peopel who left loved and used 3D max.
    the new people where coders but they had no real love for the product they did not even used it themself.

    adobe should not make the same mistake.
    there are enough ideas and bug reports in the community forum.
    ask professional and people who work with LR for years.

    don´t let people, who never used LR, decide how our software should look like!!!

  61. Loh says:

    “… It’s a step that every customer must successfully take in order to use the product and overwhelming customers with every option in a single screen was not a tenable path forward….. ”

    maybe people unable to use the “old” import dialog should stay on their smartphones?

    you want to make LR a dumb instagram like program or you want to make a program for professionals?

    if you want to make an apple like PHOTO app please let us know!
    i guess every professional will then look for alternatives.

    in case adobes wants to attract the smartphone zombies.. go for it…. make a simple app for them.
    call it “lightroom elements” or whatever.

    put as many ugly instagram effects in it and make it a “one click art solution”… but give professionals professional tools!!!

    maybe adobe does not care about the loyal professional crowd when it can get the billions of selfie addicts onboard. but it sure is no solution for me then……

    • Loh says:

      as another example… the node approach in NUKE is not simple but powerful.

      would pros be happy when digital domain removes this feature because it is to complicated for uncle tobby to cut and edit his vacation videos?

      i think everyone can guess the answer…. you don´t need analytics for that!

  62. Peter Voigt says:

    They have you hooked on their subscription service (which I would now label “pay more for less”) so now they arrogantly remove features that are important for professionals in order to boost sales for non-professionals. Not a very intelligent move, considering that it is the professionals that teach and write about their products – the result is an enormous loss of trust and goodwill in the community. If they wish to create a Lightroom Light for beginners, why don’t they just go ahead and offer that at a reduced price? Instead of removing useful professional features that we paid for? I am not updating anywhere soon – the removal of the auto-eject feature alone is reason enough for that.

  63. David Martin says:

    You made the “incorrect decision to ship with the bug” and you believe an apology is enough correction?
    Sorry. How about your resignation? Now that would be meaningful.
    As to the removal of “very low usage features”, exactly how did this improve the quality? And how stupid are your “…educators and research team…” to think that “The import experience in Lightroom is daunting”?
    Granted, it’s not the iPhone, but Lightroom is NOT supposed to be for the damn iPhone. It’s for working pros, semi-pros, and advanced amateurs who love digital photography—not the selfie crowd.
    Now matter how much one tries, you cannot “communicate[d] properly or openly before launch” a bad decision. A rapist explaining the act to his victim beforehand does not make the act correct. And from the tone of over 500 responses, I think many of us feel violated.
    You violated our trust. You violated our peace of mind and in many cases, our livelihood.
    You want our trust back?
    Fine. Immediately issue a new release that restores the Import dialogue exactly as it was before this unmitigated disaster. Then you can start a brand new dialogue in order to restore the “original core values of the product and the team.”
    To do anything else is, as another commentator wrote, pure corporate BS.

  64. René Zuch says:

    Hi Tom,
    this is a first step. I wonder how you measure how many people used the destination folder preview, as it is always there and was essential. I often used the checkboxes there to import just a certain day. This is impossible now.
    The date formats are not intuitve and that would have been a field of imporvement. So I need the destination folder preview to see whats happening. What about the possibility to customize the date formats. Maybe I just want do have month – day etc.

    Some things can be done differently (better) in a new import dialogue.
    A wish would be to have the Filter (Metadata) from the library module also in the import. There I could easily filter and select what days, what camera etc I´d like to import. The selection could then reflect the selection. This would be even more logic than the checkboxes in the destination folder preview. However the preview is still needed.

    What ever you do do it in dialogue with your customers and do it fast, as these “unimportant” removed features destroyed the workflow of so man of us.

  65. Al Birmingham says:

    1. How dare you try to force me down the CC route by making the standalone version less of a product?

    2. No way will I be making any upgrades or changes until auto eject returns and the bugs are fixed.

    3. May have to look at Corel for future editing software.

    • Yonnie R. says:

      My reply to your comment is a month late, but still honest. The only reason I subscribed to Adobe’s CC was to try Lightroom CC and PS CC on my Surface Pro 3. Not impressed enough to continue the subscription after my year is done.

      As a long-time Corel user, I’d heartily agree with opting to use Corel Draw’s Graphics Suite. Unfortunately, they, too, have implemented the subscription model to be able to use certain features. The good thing is that basic functionality is available in the traditional upgrade version. Either way, you’ll pay.

  66. Robert shami says:

    Hi Tom,

    Unfortunately Lr is used also by the pros, i don’t care if grandma at her house can’t import photos if that means i have to change my workflow.
    On larger analysis i think you guys @Adobe need to be respectful to the pro community, and this update is just lame, if that’s an indication on how you’re going towards a more amateurish user base i think i might unsubscribe and start looking elsewhere for a better DAM solution, C1 is already by far a better conversion software by the way.

    Sincerely

  67. David Ord says:

    Unfortunately the update has introduced a problem with my import operation, its taking over 40 seconds to import 1, 24 megapixel RAW file onto my computer ?, where as before this it was a few seconds.

    • Rikk Flohr says:

      David, have you performed a preference file reset? Close Lightroom, hold down [Alt/Opt]+[Shift] and relaunch Lightroom. Discard/Overwrite the preferences when prompted. After doing so is your import speed affected?

  68. Thor Egil says:

    Never used this Import window, but Synchronize Folder now seems to work again. Thank you.

    As for removing features – don’t do that. What I have learned after decades in software development is that some customers might drag you to court over such details.
    So we never remove anything, even though it might be meaningless or plain stupid functionality – there is always someone somewhere that is still using it.

    • Tanja Schulte says:

      not for me.
      unfortunately the bug is still there.

      win10 64 bit, LR 6.2.1

    • Thor Egil says:

      Sorry, I was overenthusiastic when reporting the Synchronize bug as fixed yesterday.
      The Synchronizze dialogue reports the number of photos correctly, but it then fails to synchronize any sub folders. It only includes photos in the current directory.

      Win 10 64 bit, LR CC 2015.2.1 latest version.

    • Thor Egil says:

      Aand the Photo Merge/Panorama function is broken. It fails to merge for the most part, sometimes producing something weird looking in the “Perspective” mode.
      Luckily I still have Photoshop for such thing.

  69. Tanja Schulte says:

    removing features because some users are unable to use them?

    what a great new concept adobe!!!

    i am not using dreamwaver, never learned it.
    but i would love to be a webdesigner.
    i don ́t know how to use 70% of it ́s features… it ́s intimidating.

    can i send you a list of features to remove?

    what is happening at adobe…. is this coding for kindergarten?

  70. Christian VERMEULEN says:

    Most of the things have already been said. But what makes me afraid, is not the fact that some major bugs ruined the 6.2 / 2015.2 versions, but the whole mind set which led to this catastrophy. As another reader stated, you are became fat and arrogant. This was already illustrated, at large, how you treat LR 6 users as second class citizens (I’m a CC subscriber). Please take action – meaning rethinking through the whole philosophy – and I’m afraid that it will take you a couple of white nights …..

  71. Chris Marquardt says:

    I don’t even know where to begin.

    So you’re seriously equating low usage of a feature with low importance of said feature to the individual user and then believe it’s a good idea to simply remove this feature that was present in your product for many years? Seriously?

    In my job I regularly have to import individual photos from 15 or more cards in succession. The “eject after import” feature is essential TO ME PERSONALLY and I don’t care if anybody else uses it. You’re making my work significantly harder with this decision and it’s a major mystery to me how this could have slipped through regression testing.

    Hide features behind a settings screen if you (falsely) believe that they are not important to your users.

    DO NOT STEAL LONG AVAILABLE FEATURES AWAY FRIM THOSE WHO BUILT THEIR WORKFLOWS ON THEM.

    Chris Marquardt
    http://www.tipsfromthetopfloor.com
    http://www.discoverlightroom.com

  72. Mark Payne says:

    Change can be difficult and some just don’t like change… It’s rare that I’ve seen good functionality removed from software, and the makers have considered it an improvement.

    Cleaning up the Import dialog is a great move, but if we could either have the option to switch back to the old version, or have more ‘advanced’ settings you could set which did the same things as old, some of the loyal supporters wouldn’t be up in arms…

  73. Steve B says:

    If your data showed that removing these essential features would not impact our workflows, then you are at fault for not ensuring that you are measuring the right data. Ask people to opt-in on the feedback and have them self-rate their LR experience level and Photography experience level.. Maybe then you’ll get useful metrics rather than metrics for metrics sake. Don’t go the high-handed MS route of deciding what’s best for the users.

  74. Ed Chatlos says:

    I don’t thank you for the supposed apology. Simple fact is the LR team has lost contact with its User Base.
    Those that have a problem with the original import dialog window don’t know how to use a computer, have never filed anything in either a filing cabinet or on a computer hard drive, have no real need to use a program like LR or PS and should stick to Apple’s Photo app or Googles Picasa or whatever they call it now.

    You Tom have ruined and otherwise great program. I agree with all of the above replies especially the one saying you should resign (maybe you can find a job with Apple. They just love to make all the decisions for their users) and the whole TEAM that thought up this new import dialog should be FIRED.

    I personally will be canceling my Photographers subscription plan if the old import dialog is not reinstated ASAP. Without it the program is useless for me so there is no need to keep paying Adobe for something I can use.

  75. Michael Watson says:

    This has Aperture to photos wrote all over it.
    Heres a quote from Tom on macrumers.
    “We’re seeing alot of people come in first on Lightroom mobile, so now we’re allowing people to use it locally on their local assets, their local photos and videos on their phone and tablet for as long as they like.

    More and more people are adopting the phone as their primary camera, taking the DSLR out less and less, and we’re seeing the same thing with the use of Lightroom. Some users are creative pros who are aiming for efficiency, but many others are just consumers who love photography.”

    Seen as Lightroom import is “no longer fit for purpose” i hope i can get out of my subscription under the sales of goods act uk.

    • Tim Ashman says:

      I too believe this is what is going on. There are many more consumers than pros, we will be out of luck very soon or be paying a lot more.

  76. PG says:

    Don’t know where to begin… there are so many people already expressing the same views as mine.

    Let me be constructive then: please bring the normal import features back. Hide them behind a UI if you need to to be enabled by those who understand what they are doing. Show the noob mode if you need to as default to be switched off by those who like, need and appreciate the functionality offered by the normal import UI you have removed.

    Really find the new import experience immature and half baked and as a paying customer it is frustrating to be forced to move from a feature rich process to a dumbed down one.

    Thanks.

  77. Vincent says:

    Analytics ? They’re very hard to do correctly, but most of all they’re useless.
    If ford did analytics, he would have created a faster horse.
    Designers THINK, they have vision, courage, they stand by it. They’re not cowardly covering their asses by lame analytics.
    They also have respect for their heritage, you’re here because of the 2006 14 months feedback and talented developper of back then. And you, armed with you incorrect analytics to back you unsure, untalented, ass, you thru that heritage of the giants you’re sat on, to the trash, thinking that your stupid numbers are better than you’re predecessors talent ! That’s arrogance.

    I’m pretty sure that the use of the eject feature, in the vast number of people that use Lightroom 12 times a year is very low, but I’m pretty sure it’s very high in those who use LR every day !

  78. Asbjørn says:

    I am by no means a professional photographer, but I will echo the others here: What was wrong with the old import dialog? I could of other areas of Lightroom that are far more intimidating than the import dialog, which I always considered very simple and logical. Choose your source on the left, select pictures in the middle, and change where the pictures go on the right. What could be simpler?
    The new import dialog doesn’t look like it is a part of Lightroom at all. It looks like it comes from a completely different application. Why split it up in two screens? This just makes it harder to use.
    You don’t make changes like that in a point release. You do it in a full release with the appropriate beta testing, so that you can get feedback.
    And please don’t go the Apple route and start dumbing down Lightroom. That’s not to say you shouldn’t make UI changes – I’m all for changes that improve things. But NEVER take features away!
    If your apology is sincere, you will reintroduce the old import dialog ASAP and than work out what changes to make in LR7 based on actual user feedback.

  79. OuiOuiPhoto says:

    Your are not making Beta anymore. So if you don’t increase the test scenarios of your test factory or what have just happen will happen again.

    If you don’t want to make beta anymore you should increase the number of people that have the version in advance. Today people that write books on Lightroom have the new version in advance. But those people follow the rules when they test.or use lightroom. You should include in your limited list of people that can use in advance a version more beginners.

    Beginners will do much more monkey testing than specialists

    Cheers

  80. Gert Kracht says:

    Dear Tom,

    I am so sorry to say this: The quality of the Lightroom 6.2 is not good.
    I tried everything this morning and it kept crashing with each import. (removed it and re-installed also)
    Please return the old import window and listen to your customers.
    I am back using 6.1. It has everything I really need for my workflow and is stable.

    I hope this lesson is learned. Change is good, but don’t take away the tools we all use on a daily base.
    My database is growing every day. I started to built up a new one with Lr6 and I am so happy with it. I need to see the drives, the folders, subfolders and the complete list of keywords. Guessing is not an option.

    Good luck,

    Gert

  81. Christian Scheer says:

    Thanks for the apology. But I am afraid, it won’t help. Coming reluctantly from Aperture to a company that tries to force down a subscription model down my throat, it seems I made the wrong decision to go with LR. No feature updates for a release that I paid for, but now you are dumbing down the software and take features away.
    Please rethink these bad practices.

  82. Will stay with 6.1 until the import window is sorted. an apology is one thing but the damage is done and once again the pro seems to be let down

  83. MD says:

    You have “in-product analytics that measures feature usage”? Great, then that must have told you, that for example the file names where displayed EVERY SINGLE TIME ANYBODY EXPORTED ANYTHING EVER.
    As well as other features that you stripped off. So, I wonder, how did you come to the conclusion that this was a feature that is not used much? Or do you also have “in-product eye tracking that measures what the users look at”?

  84. Simon says:

    I don’t understand how you could justify changing the import dialog to make things simpler when the entire program is rather complicated and daunting. Lightroom is not, and was never, meant for consumers or casual users. Photoshop has Elements to appeal to those who just want to do casual retouching, and if you want to expand Lightroom’s audience then perhaps you could use that as a similar model. Taking features away, no matter how little you think they are used, is not a good path forward when it comes to improving your product.

    I’m still on LR5 and have no plans to upgrade or move to CC precisely because of issues like this. It seems as though Adobe does not put the interests of their users first, and as such I don’t want to pay more money for upgrades that will remove features I use. If you think it’s a good idea to simplify the Import dialog and remove features like Eject After Import, what’s next? Dumbing down the Develop module to just one simple panel on the right-hand side? Removing Star Ratings or Color Ratings because they’re under-utilized? Ditching the Snapshots feature because your analytics indicate few people use it? If the poorly-handled 6.2 upgrade is any indication of where Adobe is going in the coming months and years of Lightroom development, I’ll keep my old version and start saving for Capture One or another program in the meantime.

  85. Walter Gladwin says:

    What can you possibly lose by putting back the missing import features under an ‘advanced’ heading?

  86. Mark Penny says:

    Well I’m delighted that because of my unresolved problem with CC updates (unable to update the applications and getting error update failed U44M1I210) despite two long online sessions with adobe, I was not able to upgrade to the latest LR fiasco. Adobe has still NOT addressed this problem so I’ll just stick with my older but functional versions.

    Tom, could the U44M1I210 problem please get fixed as well or will I wait even longer now that LR6.2 is a dud?

  87. Art Altman says:

    Tom, LRCC is much slower in D mode than LR 5.7 was. Even a simple crop suffers a long time lag in LR CC. It was snappy fast in LR 5.7.

    Can you fix this? Do you even acknowledge it?

    My machine does not have an external graphics processor. Even so, D mode was fast in LR 5.7.

    Yes I have tried checking and unchecking the graphics processor box in preferences.

    I had to switch to LRCC to import A7RII raw. Now I have a slow D mode.

    Why?

    Macbook pro 13″ 2015, 16g, 1tb ssd.

    Art

  88. Organized Records says:

    Hi Tom –
    Thank you very much for showing there are human behind the product. And since we are all human besides your Big Data machine reading stats, I understand that you sell because you work at Adobe. I can care less about Lr import workflow. Everybody has a different workflow. Sticking only with Lr, that’s everybody’s decision.

    I only the import to get images referenced into a catalog. I may not even need the preview option (I can always let that run later in the background).

    Power importing is mastered by PHOTO MECHANIC > triage > drag image you want in the catalog for post processing drag over the Lr icon, that’s it. Later for browsing I can use Bridge or Photo Mechanic. I don’t browse in Lr, I pick what to edit.

    So, a tiered import option panel would be great. And please do not forget to add the option: Just import – Do nothing, just get me in there. When I import, I know what I am importing already!

    Just a thought to pounder. I think I am not alone with this workflow.

    Keep up the good work and communication.

    Cheers.

  89. Robert Peters says:

    “Our customers, educators and research team have been clear on this topic: The import experience in Lightroom is daunting.”

    All it takes is a little work and the import process is easy to use. Somehow I’ve managed to survive the process since the late beta releases.

    ” It’s a step that every customer must successfully take in order to use the product and overwhelming customers with every option in a single screen was not a tenable path forward. We made decisions on sensible defaults and placed many of the controls behind a settings panel.”

    Fine. The problem is that Adobe REMOVED the options. Sensible defaults? Really?

    “At the same time we removed some of our very low usage features to further reduce complexity and improve quality.”

    Your usage information cannot possibly have come from any prudent user.
    The full destination path cannot be displayed.
    The renaming template is not visible during the import process.
    The filename only appears when the pointer hovers over the image.
    The images to be imported are dimmed.
    There is a monstrous check mark over images to be imported.
    What makes you think we want to see someone else’s image used as a background?

    All in all there were a lot of bonehead decisions made which screwed up the import process that has worked just fine.

    • Karen says:

      What Robert said:
      “The full destination path cannot be displayed.
      The renaming template is not visible during the import process.
      The filename only appears when the pointer hovers over the image.”
      (Hiding things does not make them simpler, it just makes me hunt for them).
      The images to be imported are dimmed.
      There is a monstrous check mark over images to be imported. (I’d add the checkmark is ambiguous. Does it mean the photo has already been imported? Or import this photo? You have to hover over an already imported photo to see “already imported”)
      What makes you think we want to see someone else’s image used as a background? (Yes!)

  90. LB says:

    I don’t mean to kick a man when he’s down, but this new import dialog is a big letdown to me. Navigating between its different “parts” is completely counter-intuitive (the tree on the left made so much more sense), and I do not get the point of this random selection of folders on the first screen (the one with the scenery). And I also used the “Eject after import” function.

    Thank you for reading me.

  91. Stuart Lurie says:

    Adobe management is no longer focusing on their customers, but some business model that makes no sense. I would fire all Lightroom managers for allowing an untested product to be released. And senior management should explain to the Board of Directiors how this product was allowed to go public without a formal Beta cycle.

  92. John B says:

    I too am disappointed with the changes in the Import dialogue. Simple things like ejecting a card after import saved steps in my workflow and made importing multiple cards much slower. I also see no need for the changes that were made. The do not add to the functionality but detract from the overall product.

    What is Adobe’s plan to restore the confidence of the photographic community? We each develop and optimize our own workflow and changes like this cost time and money.

  93. Joseph says:

    I think I speak for everyone when I say this: “Unless you put the Import back to where it was and improve on it rather than stripping away features, than the apology didn’t matter”.

  94. John Hooton says:

    I can only assume the latest Lightroom was driven by a corporate decision to sell to the technically inept, e.g. the masses, the smart phone selfie brigade. Lightroom has always been a program aimed at professionals who are technically savvy enough to figure out how it works, either by some of the excellent tutorials available (Laura Shoe) or by employing an assistant who is tech savvy.

    To dumb the import down at the expense of screwing up the stability is unacceptable and a betrayal to the professionals who have supported you since LR 1. I personally have bought every new version and upgrade and now subscribe to Adobe CC. Producing a program that constantly crashes is not what professionals want or expect.

    I have just installed your 6.2.2 fix and tried the first instance that I know produced a crash (LR not responding) . Namely just opening the program and then closing it. That simple request still produces the spinning ball and LR can only be closed by using ‘Force Quit’ on my Mac with the message ‘LR is not responding’.

    I don’t know who you employed to create this update – maybe it was the sort of people you are aiming to sell to as new LR users, in other words the technically inept.

    This is still no where good enough, especially when you consider that removing the automatic bug report is also a fix. It may fix your inbox overload but it sure as hell won’t fix the program. Get some seniors on this and stop messing with ‘newbie’ programmers who think they know it all.

  95. Mark says:

    Tom
    We appreciate the apology. How are we moving forward? Please now make some decisions and communicate them openly to the Lightroom community ASAP.
    1. Are you going to replace the missing features?
    2. Which features?
    3. When?

    I need to know so I can change my workflow and re-write my LR training curriculum and cancel one of my classes on file management. I’m waiting to upgrade but I doubt my students are so I’m in a pickle.

  96. David Martin says:

    After a days’ effort of attempting to use Lightroom 6.2.1 (patched), I’ve discovered that the patch does not work. Lightroom still crashes…now it simply waits until you’re performing a backup of the catalog before it trashes itself.

    Brilliant!

    I am moving back to 6.1.1 until Adobe gets its act together and Warnock & company decide to stop screwing their customers.

  97. TJ R says:

    An apology doesn’t help experienced users that make up the base of your subscribers. I updated not knowing about the change to import and I wish I could downgrade back to 6.1 I was hoping for an update to fix the GPU processing issues I’ve had that and the overall slowness and slug response lightroom has had since you’ve upped it to CC, but instead we get this crap. I have over 200k pictures in my catalog, the new import screen hampers my ability to tag and catalog according to my workflow and even deleted my damn import preset settings I needed. It’s been slow since LR5, but I’ve survived. Fix the memory and performance issues, put back in an advanced import feature for your experienced users that have been subscribing since day one that need it. And focus on what matters. Photo Mechanic is starting to look more and more popular.

  98. Robert Katz says:

    Quote: ” At the same time we removed some of our very low usage features to further reduce complexity and improve quality”
    Let’s see the actual data that you used to qualify a feature as “low usage”. I have been using LR since Version 1.0. The import process was simple and worked every time. Why did you ruin it?
    Robert

  99. David Martin says:

    “The bug has been fixed and today’s update addresses the stability of Lightroom 6.”

    Not really. Now Lightroom hangs up completely upon exit whether one backups or not. POS.

  100. Colin Oatley says:

    I can’t imagine why someone would not want to eject a card after importing files from the card. Ejecting should be the default. Users who don’t want to eject the card should be able to change the default to match their preference..

  101. Régis says:

    Tom,

    your apology is a step in the right direction. But I think you can feel the amount of frustration accumulated by your users in the last months, not only after this catastrophic release.
    The last releases have missed what your users are waiting for and the 6.2 release was the icing on the cake of non-sense.
    All the pro-photographers that I know just want SPEED.
    – We do not want you to make nice images appear on the back of the import dialog while removing half of the features it had.
    – We do not want you to nice checkmarks on the import images
    – We do not even want you to add an HDR option.

    We want the Develop module to be instantly available at full resolution.
    Why do we still have to wait 6 to 7 seconds on a 4K $ MacPro after pressing Q, A searching for sensor spots.
    We want to be able to import quickly. Why do we have to wait about 15 seconds (!!!) on a 4K $ MacPro to import a Fuji Raw file ???

  102. Advanced amateur here.
    Sure, the import screen was daunting in the beginning…but then I read a book and watched some tutorials.
    Please don’t treat all of us like idiots. This software is made for people that take photography seriously, and I have no problem putting in the extra time to learn it over a lack of options for the new digital shooters.

    Bring back the old panel.

  103. David Garth says:

    Bottom line this is a trust issue: when I subscribed to CC I was told I would get frequent updates with added features. What I got instead with this update was a dumbed-down product with essential features (at least to me) removed and bugs added. That appears to be indicative of a new mis-guided philosophy around Lightroom, that will eventually drive me away from a product I have truly loved. And then, on top of that, what utter disdain for your loyal customers to rush out a point release with known bugs. I am both angry and sad.

  104. Jim Harmer says:

    I’ve taught Lightroom to THOUSANDS of photographers over the last several years. Improve Photography is one of the largest photo blogs on the web, so I think I have a pretty good pulse on how photographers feel about this, AND what they struggle with in the import process.

    My students do NOT struggle to understand WHERE the photos are being imported from. The panel on the left on the previous import is really quite simple. We read left-to-right, so the left panel showing sources for the import was simple.

    The part my students DID struggle with–for years–is understanding WHERE on their computer the photos are being imported TO. I had to explain to them that it was in the right panel, but they still never quite grasped the destination.

    In the new design, the SOURCE is now it’s own page, which is useless. The thousands of people I’ve taught Lightroom to never struggled with that. The part they did struggle with, the DESTINATION, is now hidden behind a gear wheel and the drop down is even more confusing than before.

    • Jao says:

      This squares exactly with my experience. I teach Lightroom classes too and the import panel was only confusing because of the destination field. The rest was never a problem. Adobe fixed the part of it that was not confusing (the source) and made the problem actually worse while removing ESSENTIAL features that we depend upon. An unmitigated disaster.

  105. Karen says:

    As an Aperture Refugee, I’m concerned about the path Adobe is taking. Apple abandoned a program for advanced users in favor of “Photos”. “Photos” is a greatly simplified version lacking many editing features that worked just fine in Aperture. Fine, I’m not the target audience for that, I’ll switch to Lightroom. Then we get this new import dialog box, that is prettier, but takes away some features, hides others, and is more difficult for me to use. Again, I’m not the target audience for that, but I’ve got no where else to go! I’d ask you to please reconsider turning Lightroom into the Adobe version of “Photos” and keep it working for us hobbyists, enthusiasts and professionals rather than going for the camera phone crowd. I doubt that they’re going to pay for a subscription to CC. “Photos” is free after all.

  106. Jim Harmer says:

    If you regret not listening to your customers, then listen to us now and give us the import back! And while you’re at it, we’d like the stability and performance of Lightroom 5!

  107. George Coffey says:

    This is symptomatic of most software developers, they think that we want the new whiz band software engineering features that they want to install. Remember the old adage “If it ain’t broke don’t fix it”. Looking around for an alternative to LR that will care about the users.

  108. Nickt says:

    Rarely used? Ridiculous. I have a set of wrenches. I ‘rarely’ use 80% of them. Just because I don’t use most of the sizes on a daily basis doesn’t mean I want Snap-On to come to my house and remove my tools. They are TOOLS, I like having them when and if I need them.
    If you really feel a marketing need for this watered down import, let us turn it on or off and use what we are paying for. I believe PSE has optional interfaces. You rush out a horrible update that kills features and on top of that it does not work for so many. The followup fix doesn’t work either. I’m wondering what is really going on here.
    For now I am back to 6.1. I will stay there until this is straightened out.

  109. Bob Hawkins says:

    Unfortunately a post apocalypse apology doesn’t undo damage done. Since version 6.2 was knowingly released with bugs (“we made the incorrect decision to ship with the bug while…”), it is clear that profit is more important than service to Adobe. Now that I have 6.2(.1) off my computers, i will look at Lightroom and others for what I will need in the future.
    The changed Import routine lacks things I used in every Lightroom version (1,2,3,4,5,6.1). I have to go through the Preferences to switch off features I don’t need that didn’t exist in earlier versions (new features?-no, that is not allowed outside of CC). The lens profiles still don’t have some older lenses I have used for years. Lots of bugs still exist and thrive in 6.2.1 and El Capitan. I haven’t even tried 6.2.1 in Windows 10. I am still shutting off features that Microsoft uses for its marketing. No measurable metrics there…
    Lightroom 6.1 will suffice for a while. But if the new Import dialogue is the way of the future it is time I look for an alternate program.

  110. The key to good UI design is not to remove features. That just ensures that you are only selling your product to the lowest denominator. I doubt that Adobe see themselves as selling to that market. Even if they did, isn’t that what Photoshop Elements is for? Lightroom is supposed to be a professional-grade product. Dumbing down for “simplicity” in a professional-grade product is absolutely not acceptable.

    Good UI design is about making a feature rich set of functionality presented in a manner that is intuitive and quick to use. Unfortunately, this is a point that Adobe do continually appear to struggle with as that description couldn’t be used for many, if any, of their products.

    Removing functionality in a point release is also not acceptable. I’d even question whether it was legal. We’ve bought version X of the product based on an advertised set of features. We don’t buy version X.Y, although we need to be able to update to version X.Y to ensure that we get bug fixes and, in particular, any required security updates. If you want to make big changes like this, make them in Lightroom 7 so that we can all decide if that is a product that we want to purchase. And, when you do remove features, you need to be much more honest about it in advance. Discovering that a feature has been removed only once you’ve upgraded, as was the case with auto-eject for me, does not a happy customer make.

    As for the removal of the auto-eject feature, I am genuinely shocked that you saw this as candidate for removal. Any professional photographer I know wants that card ejected as soon as the import is complete because they will never re-format that card until it is next needed so that they have an extra level of back-up should anything go wrong. And it’s not as if there is a use case where a card will not be ejected…

    • KC says:

      Interesting point, we all paid for a feature that is heavily used by professionals utilizing a professional product. When Adobe forcefully removes features from a paid for product, I wonder if they have not committed fraud?

      Any lawyers care to chime in?

  111. Roger Walton says:

    Please put back “eject card”

    None of my clients had any problem importing in the old way once it was explained to them!

  112. Bob Ryden says:

    My two cents about auto-eject: I rename files as I import, and in a shoot there may be several different groups of photos that I want to give different names to. This means that I typically do several imports rather than the whole card at once, which would make auto-eject pretty inconvenient to have turned on. Judging from the other comments, however, most people don’t work this way so I’m in a minority on the issue.

  113. Rudi says:

    Hmm, my LR CC doesn’t recognize a new update from Creative Cloud. Even not if I use LR help->updates. When I read here that the hot fix doesn’t fix the problems I’m not keen to install the fix.

    I’m more interested in how to get back to at least 6.1!!

  114. carol carlaw says:

    I am yet to try lightroom and I would be a complete new user. I made a comment somewhere that my biggest concern was being controlled by a program. I have been watching and listening for a couple of yrs and use bridge. I am so glad I have not entered into this program. For now I will keep doing as I have been doing as things are straight forward and work with no issues at all. I prefer to take longer and to feel safer.Speed is ruining so many things these days. It’s such a shame as we live in times where too many things get changed too rapidly and often stupidly it’s no wonder people who rely on this program for their work are up in arms, I would be ropable. I think companies forget who made them successful and it’s their customers. I think a lot of damage has been done and the result will be people jumping ship as soon as something suitable comes along. I will now wait and watch. This has made me nervous and people never forget.

  115. imajez says:

    What Adobe’s testing of newbies missed was that the ‘concept of importing’ is a big stumbling block and not just the import dialogue.
    Also there’s this foolish assumption that EVERYONE regardless of ability/expereince should be able to quickly understand software without any instruction. Sometimes the best way of doing something may need an introduction/explanation, because the better method is different from a previous way that people are used to.
    What strikes me most of all is that LR would never even have got off the ground in the first place if the current mindset had been in place all those years back because LR’s way of working was radically different.

  116. Henk Plaggemars says:

    If you are going to be dumbing down Lightroom – and the import dialogue released earlier this week is a classic example, then consider a separate product – Lightroom Lite – for the touchscreen crowd.

    The original panel was full of useful information – and if your feedback is that folks are bewildered by this, then BUY the KelbyOne vid on using the import dialog and offer it as a freebie to the daunted. Scott does a great job of explaining the intricacies of the Import panel.

    Hiding stuff we use everyday behind an advanced panel is a retrograde step.

    Besides if the design of the Import panel is the sign of things to come for the other panels then I have one word for you to consider “Metro”.

    That having been said, I am really happy with Adobe’s LR and PS package (as they were a week ago) – keep up the good work, but take this feedback seriously.

  117. Patrick Corrigan says:

    There is a difference between cleaning up an interface and dumbing it down. You have apparently succeeded at the later by sacrificing features used by many of your advanced users. As a long-time Lightroom user, I have had no problems with the import dialog. All powerful software has a learning curve and Lightroom is no different, so please don’t remove features that we use to just make it simpler for new users.

  118. Richard Jones says:

    I’m still experiencing various significant issues even after this update which are making lightroom close to unusable. For example I launchany of the tools (brush, crop, retouch etc.) and their corresponding panels fail to load. The adjustment panels in general fail to intermittently load. The app has become slow and glitchy.
    This is unacceptable from adobe, where so many rely on the software for their business.

  119. Rudi says:

    Oh boy! Have two additional errors with import dialog:
    1. I use an import preset. It uses automatic develop, clarity, sharpening etc. Since 6.2 the automatic development preset does not work anymore. All other settings are applied. (I need the automatic value for 2nd sculling after doing a pre sculling in PM before setting my devel values)

    2. I use the automatic import from a certain directory when using Photo Mechanic. I set the metadata in PM. When LR imported the images it deletes parts of the metadata (descriptions etc.). To be honest it has been since Rel. 6. When importing directly out of the PM directory everything is OK, so the PM setting of metadata is correct.

  120. Rich Allaire says:

    I have no issues with new functionality or interface enhancements…

    Taking away functions was just DUMB! Please give us the choice or allow a configurable interface. The stability/crashing issues are ridiculous… How about some QA?

    I’ve loved Lightroom, but I’ve lost a LOT of confidence in it since this update was rush released (to show off at your MAX event, please don’t deny it.)

    Rich Allaire

  121. Christian says:

    Appreciate the difficulty of the situation you find yourself in.

    Do you have a site where you are collecting feedback about wanted features for possible re-inclusion into the experience?

    For me, I’d like more emphasis on the right pane – That’s where all of the work is done. Features I’d like re-added:

    + The ability to Move as well as copy/add
    + Displaying the resulting new filename when rename photos (I use multiple templates and the visual reminder of what the new filename will be is extremely helpful)

  122. John Lehet says:

    I imagine you are getting squeezed from above, and I’m sorry, Tom. You’ve done a fantastic job with Lightroom all along up to now.

    I’ve reverted to the previous version (I did that quickly, as even on Yosemite it was glacial and crashy), and I will stay here indefinitely and be very careful about clicking the update button.

    The main thing for me is that I was a hard-won subscriber to the CC model as a photoshop user since the mid 90s and a LR user since the first beta became available. I was very upset about CC, but eventually I subscribed. In the past I always paid for the updates anyway, CS and pre CS, though the not-photoshop, not-lightroom Adobe apps got updated less frequently. Now though, the model seems unpalatable once again. If I keep Lightroom un-updated because the updates are actually getting worse, I still have to keep paying for the updates and paying for the app perpetually, though I’ve got the old version. In the past it felt like, “Oh, they made it worse but I still own the good version and I’m not going to pay for this one, won’t update.” Now that situation is worse for us.

    As for the new version, it seems most of the focus went into Mobile and cloud features. I take photo editing very seriously, in fact doing most of that in Photoshop instead of Lightroom anyway. I want a real computer, with a real file system, and access to the files in a big external storage for editing. Lightroom for me is the best DAM for photography. I wouldn’t mind that moving to mobile — access to the whole catalog for browsing, keywording, rating. But instead it seems most of the focus on Mobile has gone into its weakest area — editing. As a photographer, I don’t get that at all. Personally I’d like it if LR kept focusing on what real photographers want and use. Make something else for the cell phone gang.

    It’s funny about the features that were removed. I think in some ways you were right about the import process being confusing, because the way I do it and the way I teach it is to do a very clunky-but-solid workaround. I manually copy the files to the folder where I know I want them, and then I drag those onto lightroom from the Mac Finder. But in reading the complaints about what was taken away, I wish I had used those features. I started this workaround during the first LR beta, way back, and I’ve been stuck in my ways ever since. When you remove features so they don’t confuse beginners, then they are not there as the beginners become ready for them. A shame to do.

  123. David Collison says:

    Very disappointing! I have a library of close to 300k images – mostly sports photography. The revamp of the import process is a complete disaster. It is not uncommon for me to have several cards to process after a weekend. The old import process/workflow easily allowed me to manipulate the directory, standard adjustments and allowing for the auto eject future. Auto eject is critical when managing the import process and being able to quickly swap cards out – additionally, to comments made previously, you shouldn’t format in the computer, camera manufacturers highly recommend formatting in the camera. Removing auto eject introduces several additional steps before removing the card and increases the chance that you’ll corrupt the images and/or file structure on the card. Quite simply, you’ve screwed up and made my workflow more difficult. Fix it – if you need to create a dummy mode for the noob, that’s fine, but don’t punish those of us using the product to manage a professional workflow.

  124. Sherri says:

    Please. I appreciate your ‘mea culpa’, but I get the clear picture that you’re sorry for the way you rolled out the changes on the import dialogue, not for making them, which pretty much negates your ‘mea culpa’ in my eyes. I have rolled back to 6.1.1 and will stay there until the import dialogue for experienced users is restored, (or at least an ‘option for’ is put in place).

    I think if I were Adobe I would be concerned at the level of anger and concern being expressed over this. I’m sure other developers are scenting blood in the water, and more power to them if Adobe doesn’t rectify this.

  125. I can’t beleive Adobe would take features out! Seriously? Lightroom is my database for my business. Make a LR Lite if you want to make thinks easier for the newbies, but don’t remove features from a professional’s software. If you continue this, you will lose the rest of the pros who are not using Capture One.

  126. I can’t believe you would remove professional features! If you want to lose the rest of the professional field to Capture One then continue this way. Make a LR Lite if you want to court newbies or have a dumb down switch.

  127. Pieter Gellings says:

    If I read the apology correctly it’s only for:
    – releasing a buggy update
    – not communicating the import dialog change
    However it seems that you still think the import dialog change is good and in the right direction. Well let me be clear on this topic (together with many other frustrated users on many fora): taking useful options away is stealing from your customers. You promised what was getting when I bought a perpetual license to LR 6: camera updates, bug fixes and support for new cameras. Nowhere was there any warning you would take options away, only a warning I wouldn’t get functional updates like CC users. So I really feel betrayed and that’s not something you should do to a customer and in my mind requires a more clear apology than the one given (as well as a fix).

  128. I think all has been said. The import dialog never was a problem to me, though I am a mere amateur. Wasn’t expecting a new one. An improved face recognition would have helped me more… but that’s off topic.
    Maybe Adobe needs to provide optional import dialogues, like as an Lightroom “Essential” mode for beginners?
    I’ll wait a while now and see how the world looks after the storm settled. I am a Lightroom user since the pre-Adobe times, would miss it. But everything has its time.
    Henkki

  129. Tony Roberts says:

    Tom:
    I realize that expanding the user base is the only way forward for a public company with shareholders/ROI pressures. But don’t cross the line to over-simplification where, to paraphrase Thomas Mann, you become the enemy of the state. LR is a wonderful program BECAUSE it is feature rich. Among my beginner students, each finds a workflow that’s777777777777777777 (sorry, cat on keyboard) suitable to their mindflow. None of them has ever complained about the Import dialog. I suspect there’s an Elements faction holding sway at Adobe; banish them before you lose your core users.

  130. Rod Barbee says:

    The great strength of Lightroom is (was??) its flexibility. Many different workflows could be accommodated because of all the choices.
    Workflow starts with importing. Removing choices from the Import dialog hamstrings Lightroom’s greatest strength.
    Please consider giving us the choice of our own workflow, and return those features that were removed.

  131. John says:

    This reminds me of Microsoft Vista. When companies like Adobe get too big and powerful they start to “tell” us what we want, or catering to a new clientele they don’t have yet. Good old marketing. Maybe time to look at other post processing software.

  132. Ivor says:

    I am so glad I didn’t get this update. I am another person who automatically ejects card after import, I also don’t send usage data to Adobe (or any other software manufacturer.)

    Lightroom is an advanced tool and used by advanced users who have the ability to use the advanced features. Improve and sell Elements Organizer to those who don’t need or cannot use Lightroom’s advanced features, don’t take those features away from those of us who paid for them. (Here’s an idea, why not offer the full version of ACR as an option for buying Elements.) You have dumbed down Elements so much over recent years that I have stopped buying it, don’t do it to Lightroom.

    Also, dehaze update should have been included in Lightroom 6 as well as CC. I won’t rent my software license, I will only ever buy it outright. If you force those hand of those of us who don’t want to rent, then we will go elsewhere. There are other, better dehaze tools on the market as there are other, better panorama and HDR tools. Adobe’s raw converter isn’t the only one available either.

    Continue treating loyal customers with contempt then we will move onto using one of the up-and-coming rivals who respect photographers and our needs.

  133. Thomas S. England says:

    Not the first time features have been taken away. Used to be able to create a slideshow that advanced every one-tenth of a second. That’s been gone since LR4, never to be seen again. Now the fastest you can advance is once a second. Not exactly a time-lapse tool.

  134. David Martin says:

    Thanks to the Lightroom Queen, here”s how to remove the virus known as Lightroom 6.2.1:

    “Due to some stability issues with the latest Lightroom release, I’m getting lots of emails asking how to roll back to a previous version, so here’s the step-by-step:

    Uninstall Lightroom. On Windows, you can do this from the Add/Remove Programs screen. On Mac, navigate to Applications > Adobe Lightroom > Uninstall Adobe Lightroom.
    Download and install the 2015.0 / 6.0 release from https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html
    Download and install the 2015.1.1 / 6.1.1 release from: Windows / Mac

    Update 8 October – Adobe have confirmed they’ll be issuing an update to address the crashing and performance problems ASAP.”

    The last sentence obviously has little value given what we now know about the patch.

  135. Elizabeth Covington says:

    That’s a nice apology, but the proof will be in the return of functionality to those of us who have been using Lightroom for years – version 1 for me. A return of the eject-card-after-import function is important to many people. I would like to see a Preferences-centric choice to use a “classic” import function with the interface we’re accustomed to seeing or the “new and really not improved” import function just introduced. The classic form really isn’t rocket science – work from left to right and from top to bottom. Pardon me, but DUH!

    I got a heads-up about potential problems with this update, so I have not yet installed it. I shall wait until (hopefully) some form of common sense returns.

  136. George says:

    I seem to have found another “bug” and that is when I push the “F” key on my keyboard, to take everything else away besides the picture, my computer hangs. The only difference I did from my normal process routine was to use the dehaze feature in the effects panel. I am working on a Windows 10 computer. Am I the only one experiencing this problem?

  137. Brent Bergherm says:

    maybe it’s time for a “Lightroom elements” version with all the dumbed down features. I like the import box the way it was and I will not be downgrading to the newer version.
    Until this point my only lr complaint was that the catalogue can’t be on the network server. With 30 students at a time, all of which are noobies, having lr open a catalogue on the network volume would be great.

  138. imajez says:

    Adobe should make two versions.
    Literoom for the hard of thinking and Lightroom for those who can take a lens cap off without needing instructions.

  139. Please return to “old” import panel! The “new” import panel borders on being insulting to former LR users. I am sorry to see Adobe going the route that so much of our culture has taken: “design for the lowest common denominator of user and forget about the rest.” The “old” import was not complicated, but one had to use a little of one’s brain in navigating it, but I can see how “the lowest common denominator” user would have gotten befuddled.

  140. Peter says:

    I have used LR since v 4, now on 5, and used pretty much all of the features you have removed. Especially the target folder pane which I use every time I import to make sure the pictures end up where I want them. Also the 1:1 view in the import dialog is key to avoid importing all “Reject” pics. I cannot understand why you remove features that work well for so many photographers. If they are preventing new users from figuring out how to use LR then simply hide them initially and allow us that do use them to enable them in preferences or Expert mode.
    LR is to me a pro-tool, although I am an amateur enthusiast. You would never consider dumbing down PS like this, or maybe that’s a plan as well. Amateurs that will not take the time to learn such basic features such as importing should maybe stick with apps like Elements. All they need to do is watch a video on YouTube or buy a book. After all, if they cannot figure out import, how are they going to get to know all the other powerful features in LR. Don’t even mention the learning curve for PS. That also requires some studying in the beginning.
    I was days away from starting my subscription to the Photography package to get to the latest version but you gave me a really good reason to save my money and stay away. Easiest decision in a long time.
    The only thing sensible at this time is to revert back all removed features, suck it up and admit the mistake, and rethink how to move forward. And listen to your customers instead of just focusing on usability studies with new novice users and your app analytics that I always turn off.

    Lastly, keep LR a tool for advanced users, novice users and fine with elements. If you try to shoot for all types of users, you end up missing them all and a competing brand will likely take your place eventually.

  141. Boris says:

    Everything is said above.

    Hands down: What I REALLY like to hear from Adobe is an answer to ONE SIMPLE QUESTION:
    – Who are your Clients for Lightroom?

    Point! If you, ADOBE, say: “We like to build the best Photo-RAW-Tool for professionals” (professionals means “they earn money with it”) – Then you should QUICKLY change your mindset! Fix problems (speed, memory consumption), Improve Things you havn’t looked it since the very first version (Keyword-Organisation-Tool anyone? Having a definitive order of keywords in export for Stock-Agencies, etc.)
    I don’t need a toy for 80 Bucks or less – I need a helpful tool, a time-saver. I’m happy to pay 300 Bucks if the Software ROCKS!!
    Don’t make the mistake Apple made when rewriting the Desktop-Versions of iWork by reducing it to the low feature set of the iOS-Versions (just to be compatible)

    But – If ADOBE says: “We need a cool looking Photo-App ‘for everybody else’, it needs to be ‘as simple’ as an iPhone-App” – then… well… Go, move on your way making a shiny new toy BUT TELL US! Then we can start going on to some other solutions.

    for the records:
    – Eject after Import. I put in 3 to 6 SD-Cards after a shooting – HUGE Timesaver. On Workshops i get 20+ SD-Cards in 20 Minutes to import one or two images from each. HUGE HUGE Timesaver
    – showing Filename. On Workshops (on private by myself) i get the number of the filename which i need to import and i scroll down until i see that name. Doing that with Tooltip? No freakin’ way! If you don’t bring back that option, i will move to finder doing my import with Drag&Drop from there! … Until to remove Drag&Drop of course… I’m sure nearly no one in your records are using D&D – right?
    – displaying the resulting filepath. HUGE tool to avoid errors! I was showing around this feature to other companies as a great example how to visualize “what will happen” before the fact. I was checking that a lot when switching catalogues
    …i could go on and on…

  142. Peter Orr says:

    Why dumb down a complicated import process once pro users have figured out which options are important to them and base their workflow on them? Have a newby option by all means, but don’t throw out the “lesser used features” just to keep the selfie crowd happy. To remove functionality from a leading software solution is like cutting your nose to spite your face.
    Please bring back the lost features, even if we have to dig around to find them!

  143. Mark Osborne says:

    Performance is poor ever since 6 came out and despite the update the performance is still poor. whether a high end PC or Mac, turning on the GPU even though the video cards supported and with the latest driver does nothing and this need to be fixed. In fact turn it off and you gain some minimal improvement!
    As you say you knew about a bug and yet still shipped sounds too me like another Volkswagen in the making!
    Surely you must recognize that professional photographers use your product and demand advance settings not only on import but performance which is still lacking, we have businesses to run, we don’t have time for this nonsense!

  144. M C Dobbins d'Alessio says:

    You have never heard from me before but I have been a LR user since the beginning–actually before the beginning because I owned the program you bought to convert to LR so I was grandfathered into LR. I’ve never written you because LR has done everything I’ve needed. Sure, it’s taken me a few trips around the import page to make sure I got everything right but there it was, all I need to import my files, rename them, check, their names, make certain of the paths as to what drives they were going to and where the back up was going to be, what preset I might want, and then at the end, unmount my card. Wow–all in one place, follow the path around the page across the top to the right bottom–what could be more simple. It has allowed me to keep track of 3 TB of image files across several computers, multiple hard drives, and several image platforms while visiting and photographing 7 Continents. I was worth switching to paying monthly for that ability. But now–wow, it hardly works and many of the features I use in my import flow are gone. What can I say–I’m flabbergasted!. I’ve uninstalled this unmitigated disaster and reinstalled LR 6.1.1 because I’m on my way to Madagascar for a month and I hope you have this resolved and the functionality restored by the time I return otherwise you won’t ever hear from me again and it won’t be because I’m such a satisfied user–it will be because I’m no longer a user at all. Ten years down the drain–

  145. Michael M. Cohen says:

    I am still unable to use the second update this week. I can’t even get to the infamous “Import” screen. The program is now slow and very unresponsive to my commands. Twice this week I had to roll back the update to LR 6.1.1 the last stable one.

    How much beta testing was included in this update. The out lash from the user community speaks volumes. Please take it to heart.

  146. John Wilson says:

    Do the Lightroom guys ever talk to the Photoshop team? Photoshop has figured out this configurability challenge a long time ago, and with great customer acceptance. How about a “workspace” capability with pre-defined “beginner” and “advanced” profiles? Photoshop has proven that wide customization can be implemented. Isn’t it worth a look?

  147. amphotos says:

    and another for PLEASE put import back the way it was!

    also…+1000000000 for

    **NEED AUTO EJECT**

    Idiots…

  148. saveriolombardi says:

    As soon as I had upgraded my MacBookPro to El Capitan I downloaded and installed all the upgrades to the various softwares that I use. Only apps to give troubles: Lightroom and Bridge CC. Unistalled and re-installed them a few times. Ran the updates. Now Lightroom is crashing every time I Export files:-((((((((( Unistalled it and subsequently installed release 5, which is working fine as usual. But I’m f******g paying you for the CC version!!!!!!!!

  149. Mark Joseph says:

    Who is Lightroom for? Professionals and serious creatives, casual snapshooters? Both?

    I know the rhetoric is “Lightroom for everyone.” But who actually believes that’s possible? Courting radically different users means compromise, and since casual snapshooters outnumber professionals exponentially, “Lightroom for everyone” clearly means that professionals are going to draw the short straw more often than not.

    Hey, I don’t blame you, Tom. You’re looking at those 400 million happy Instagrammers out there and wondering how to slice yourself a piece of that very, very profitable pie. And’ve got a nervous eye on Apple and Google, who’ve jumped wholesale from courting professionals (Aperture + Mac, the Nik collection) to locking in the snapshooter set (iPhone-iCloud-Photos, Android+Snapseed+GooglePhotos). You’ve got to get in on that before it’s too late!

    We all know casual photographers are a fantastic market–they’re growing like tribbles (while working professionals dwindle) and they’re comparatively easy to serve. Snapshooters don’t have complicated “workflows,” legacy needs, or persnickety tastes. And it’s so much easier to lock snapshooters into an “ecosystem.” Creative pros worry about proprietary formats, extensibility, ownership, rights . . . yikes. Snapshooters just want convenience–offer a slick shot-to-share cloud archive and they’re yours for the foreseeable future.

    Anyway: thanks for the heartfelt apology, and good luck with “Lightroom for everyone.” I myself will be spending more and more time with Phase One’s Capture One, but I’ll check in now and then to see how you’re doing!

  150. C.A.M. Gerlach says:

    While I appreciate the apology, it still deploys some of the same excuses as before, is somewhat of an insult to your experienced users, and ultimately is essentially meaningless without any mention of concrete changes, much less a full rollback that it seems huge numbers of people are requesting.

    “The import experience in Lightroom is daunting. It’s a step that every customer must successfully take in order to use the product and overwhelming customers with every option in a single screen was not a tenable path forward. ”

    Overwhelming? Honestly, I’m pretty insulted. It was not too long ago, not much more than a year, that I first starting using LR5 after going the Bridge-ACR-PS CS6 workflow for several years, so I still remember what it was like to be new to the whole thing. Even then, though, I never remember having any real problem with the UI itself, much less somehow becoming “overwhelmed.” Sure, some of the more detailed options required Googling to get the most out of, but as a product aimed at advanced hobbyist and professional photographers, that’s to be expected, honestly. If the only options were easy enough that Joe Schmo off the street could figure them out, then what am I getting paid for? Plus, any experience you are referring to is only even troublesome (and even still, expected, for that matter, with most advanced products) for the first few times one uses the software.

    For anyone who’s picked up some experience using the program regularly, e.g. the vast majority of times people are using the dialog, it is a hindrance having fewer features and less easy access to them–but unlike new users, we already forked over our hard-earned cash to purchase your program, or are paying every month to not loose access to it, so it makes some level of short term economic sense. Pretending it is anything but that is fundamentally disingenuous to your experienced userbase.

    “At the same time we removed some of our very low usage features to further reduce complexity and improve quality.”

    So first you hide all your high usage features features behind multiple levels of clicking to even view their status, and then you remove the “low usage features” entirely? Please tell me, as I’ve heard this multiple times from lightroom employees, how on Earth “removing features” that were fully functional “improve quality”? How? It is utterly baffling to me.

    “In making these changes without a broader dialog I’ve failed the original core values of the product and the team.”

    Yes, you have. The most (and perhaps the only) genuine and meaningful statement in the entire “apology.” Honestly, the whole thing would have come off a lot better if you’d started rather than a long list of excuses as to why the failure occurred. You deserve some credit for this sentence, but sadly it is overshadowed by everything else that was there, and most notably what was not, namely any concrete action whatsoever.

    “The team will continue to work hard to earn your trust back in subsequent releases and I look forward to reigniting the type of dialog we started in 2006.”

    That’s all well and good, but it means *nothing* without at least *something* concrete to address your users’ #1 concern right now, which is this issue, as nowhere do you promise *anything* will be done to assuage the problems with the new UI and removed features. Given a proper “dialogue” involves listening to the other side, the fact that you clearly haven’t here in any meaningful way indicates your whole promise of “earning trust” and “dialogue” rings utterly hollow when you still refuse to listen and respond to your core userbase in their most vocal complaint propbably since that 2006 you refer to.

    Honestly, if this is how I can expect to be treated by the Lightroom team now and in the future, LR 5.7 will be the last version I buy. Unless I see concrete action on this issue, after already being burned on Creative Cloud befre, I’ll have no reason to doubt that Adobe simply doesn’t care aobut its dedicated userbase when that seemingly stands in the way of extracting money from the poor, clueless newbies who stumble across their program and think that having what was once a reliable, professional tool will somehow make them a good photographer. And if that truly must be the case, then I’ll close with this: Goodnight and good luck, Adobe. You’ll need it.

  151. Jim Goshorn says:

    Thank you for your apology because Adobe really messed up. I must say however, that statements like this from a previous post “The previous Import experience literally made people push back from their computers in frustration. Keeping the existing Import experience isn’t an option, and we needed to evolve the Import experience.” just makes me (and others I’m sure) feel that our complaints don’t mean much to Adobe and you are going to go on your merry way regardless.

    I have to say that I believe if you really took a large sampling of existing users you wouldn’t have made those changes. Eject, move and destination, for instance, are features frequently used by LR users and shouldn’t be removed or put behind a gear menu (you want to talk frustration?!). LR has been designed as a professional solution and as such, it needs to provide a complete and flexible workflow for professional users. It shouldn’t be a workflow necessitating additional steps so that it will be simple enough for novice users who wouldn’t miss those steps.

    So is Adobe planning on dumbing down Photoshop, Illustrator, InDesign, Premier Pro etc. so that they will not intimidate new users? Take a poll and I’m sure that you will find that most of your longtime users were intimidated or frustrated by Adobe’s applications but we sat our butts down and did what we had to do to learn how to use them as they were designed. You want Lightroom to be easy, then create a new app: Lightroom Elements.

    You want to earn our trust and keep us as users? Listen to our frustrations, put things back the way they were and next time, how about figuring out a way to do a poll of an accurate cross section of your users before you kneecap the app?

  152. Andre says:

    How about the fact that panorama from RAW files from Leica got broken in this new update? I spent hours with Adobe on the phone while you guys were telling me that my files were bad and it was my fault that the panoramas weren’t working only to then (both me and the woman at Adobe) try the panorama with the same files on an older version of Lightroom and voilà! It works! Do you guys plan on fixing that sometime soon?

  153. jrp says:

    Thanks for your apology, Tom, such as it was.

    It is hard to know where to start in responding to this chaotic fiasco.

    * Is it wilful publishing of “crashy” software under a subscription model that was sold to us on the basis that we would get features as and when they were ready, rather than when Marketing demanded?
    * Is it the bone-headed problem identification and half-cock solution?
    * Or is it the peek ahead to our destination, on the magical mystery tour that Adobe seems to be taking us?

    It is like watching an episode of the Apprentice. You can imagine the bright young hot shots getting their power points up and observing that billions of photos are being published / shared but the more committed / professional photography market is only small percentage of that. What they need to do is find out what it is that is preventing their products from reaching the wider market. After all, Apple (which makes money from cameras (aka phones), and selling storage), Google (which makes money from harvesting data from stored photos, and a bit from storage), et al, are doing well in that “space”, partly due to a “no brainer” workflow. Adobe is danger of being written out of the script because it offers only software, which it turns out the others can do almost as well, for the large, and growing, non-specialist audience.

    So they send out market researchers to find out what it is that is blocking Lightroom adoption. Ingesting the photos via a cluttered, poorly structured screen turn out to be a point of resistance.

    Lipstick is duly applied to the pig, in a mock-up, by the newest intern, who is too young to have heard of the Microsoft Wizard concept (which sounds even more patronising than a simplified screen, but which works very well for a multi-step process) and marketing, on seeing a demo, changes the background picture to the dialogue and presses the “ship” button, to market test reactions.

    They have a new vision. It is one of producing Lightroom Elements, over the longer term, a module at a time. It is quite clear that the (locked in) old timers are attached to their complicated and effete / elite eject buttons, they want to move files, and not import duplicates, as well as seeing where they are putting their pictures. The solution is obvious — in-App purchasing: $0.50 / month to bring up your file tree, $1 / month to be able to preview your imports. It’s a no brainer. Trebles all ‘round. Lock and load (should it not be the other way around?) baby, etc, you can imagine the contestants cry, as they high five as if they were from the ‘hood, without trust funds.

    More lipstick is applied and a few of the more egregious bugs are squashed. The market testing team goes out again and a few more people do not push back at the initial experience.

    Being aspiring Apprentices, they lack the wit and wisdom of their master, who can see several steps ahead. He can see that the “reimagined” solution of a simplified dialogue that satisfies neither those that don’t understand folder structures, nor those that do, turns out to be a blind alley.

    The master realises that the guinea pigs will soon discover that while they can now, with a following wind, get their pictures into Lightroom, and even learn to adjust them a bit, they find that they have a solid vertical wall to climb if they want to get them out.

    * Slideshows are fine, but it is never very clear which pictures are going to participate.
    * Printing pictures, the USP of Lightroom, leads to a mind-blowing dialogue (assuming that the newbie finds it, as the module names do not look like buttons) even without trying to avoid both Lightroom and the printer thing to do color management.
    * So does the newbie export the pictures or run some plug-in to get them out, risking an encounter with the file system? S/he eventually finds that s/he can also publish them, although it is never very clear which route out is best, which requires the establishment of collection (and whether that should be smart or not). They never get to Bechance because it is not clear what it does.

    So it soon dawns on our guinea pigs that sharing pictures with friends and elderly relatives requires more effort than they are prepared to put in: they are not pretending to be artists, but want to create emotional connections. Going to regex.info and downloading a plug-in that allows the households under test to post to Instagram, as the post on that website recommends, seems a bridge too far.

    Result: Adobe has a version of Lightroom that is neither fish nor fowl. It doesn’t satisfy the pros (who find ingestion slow and inflexible (leaving space for Photo Mechanic to thrive) and the newbies find that Apple or, at a pinch, Google Photos may be limited, but they do the job that the majority require, while not satisfying those with more specialised needs.

    I hope that Adobe / Tom will offer us an alternative vision of the future, but the portents are not encouraging.

  154. John says:

    An apology is good. Thank you.

    Still, by telling us that you’re sticking with the changes you made to the import function, you’re telling us we can take a hike as far as Adobe is concerned.

    Your company is now akin to a cable company: we hate you, can’t get rid of you right now, but will drop you like a brick the moment we can.

    • Lewis Frazier says:

      Amen. I used to brag about this company being “by professionals, for professionals.” Those days are over! Pathetic.

    • Art Held says:

      I agree. I was completely blind-sided when I tried to run an import. My workflow was pretty much gutted, the time to import went UP. The message from Adobe? Gee, we need to “build trust” and “communicate better”. No mention of FIXING the problem. Welcome to marketing aimed only at new sales. Right now Lightroom has no real competition. Hopefully someone will see the opportunity and give us an option.

  155. Gary Anderson says:

    Software users (which means everyone) is used to having bugs in newly released software. There are few if any major programs that don’t have a dot release to correct unforeseen conflicts that occur in an almost infinite variety of computer configurations. That’s just the way it is.
    Each time a new release comes out and it doesn’t perform in the way its advertised, users go through an analysis of their download, was it complete, did it hang up somewhere? The next step is to determine whether the equiment is functioning properly, has the equipment finally reached the point where it is no longer adequate to the task? If those searches don’t provide answers then delving into blogs and websites to see if anyone else is experiencing the same problems. Discovering that the user is not alone brings some comfort because you realize you didn’t mess up the install. Next step is to find out how to roll back to a version that actually works for you.
    How many hours? All that time delay before a professional trying to earn a living can get back to production.
    The worst part of Lightroom 6.2 release is the statement from Mr. Hogarty: “we made the incorrect decision to ship with the bug”
    That most certainly was incorrect. That blatant disregard for interests of Adobe clients is inexcusable.
    My go-to version of Light Room remains at LR 5.7, which is the last full stand alone package I purchased before subscribing to CC. It may be some time before I trust my efforts in a CC release.
    Gary Anderson

  156. Dan Holmes says:

    I have to add my voice to the hundreds of complaints about the changes to the Import Module. As a working pro, I use all the functions and they are critical to my work flow. Importing and managing is the most important function of Lightroom and by eliminating, hiding, and requiring multiple mouse clicks you have handicapped the entire process. I import thousands of photographs and have prized the ability to easily change file names, add metadata, use presets, and create new destination folders and load into dated folders.

    It is not a simple process, but is teachable. If you need a simplified “Import Light” module, please do so, but please give us the ability to continue using the advanced functions.

  157. Felipe Yang says:

    If you’re keeping count, here’s another vote for having the “eject after import” feature added back in. This greatly affects the workflow of professional photographers who import multiple cards at once.

  158. tailor says:

    Dear Adobe Team,

    thank you for the apology, but I need to agree 100% to statement of Jim Goshorn. I am a Lightroom user since the early beginning. Unfortunately since a few version I got the feeling that there is a big intension to spread LR to more and more users by making it more simple. I was fine with that because its a great tool as long as further pro features will be also added. With last update all my worries became true. The redesign of the import dialogue was never meant to have any benefit to pro users according to my understanding. (I expect, the majority of pro users are able to use old dialogue according their workflow since years, if you dont believe than you dont know your customers). The update was meant to make Lightroom more easy to get a higher market share for consumer user, (which is from business point of view fully understandable).
    BUT why did you remove features? Why do you think you know what your customers want without asking them?
    What is the future target audience for Lightroom? If you want to get higher market share, please release the from Jim suggested LR elements and keep on improving the Lightroom CC version in performance and stability.

    I am hoping that the current buggy, notatallsatisying version will be reflected deeply in your team and appropriate countermeasures will be taken that such kind of version will be never released again.( not blaming any programmer, because I expect they were not pushing to release 6.2 before solving all issues)
    If the CC will continue to be used in same understanding as “beta tester”, please inform….

    Anyway at the moment I am still convinced about the product and hoping the issues can be solved soon.
    Just my thoughts on the topic after spending several hours with crashes and rolleback.

    Regards
    S.Tailor

    p.s.
    Sorry for poor english, as i am not a native speaker

  159. Lewis Frazier says:

    Professionals use these features SEVERAL times DAILY!!!! Unbelievable that there wouldn’t even be an option to “show advanced features” so that my LR workflow can return to normal. I now have tons of extra work getting my workflow organized. If that’s what you mean by “easier,” Tom, then you got it! Please give an option to enable these features in a future update. Especially the “eject card on import” option if nothing else. I am confident you and the team will take the correct measures to repair this ungodly mess. Don’t forget who makes this program possible: PROFESSIONALS.

  160. Martin Tyler says:

    Add me to the list of unhappy customers that uses some of the removed features.

    What a waste of design and development effort the new import process was. You could have used that effort to make Lightroom better at what it already does. I am very invested in Lightroom, but it is SLOW, unbelievably SLOW. I put up with it though, because I’m not sure what else covers the same level of organisational features with processing features and I have a large catalogue already there. It is a very ‘sticky’ product, but it feels more like being held to random rather than a positive thing.

  161. Gordon Daines says:

    The new import dialog is the worst one i have ever seen. it is so confusing I couldn’t even see what my setting on saved import presets. Please give the old one back. Is there any way to get it back or do i have to revert to the older version? Very disappointed. It is not clear what most of the items in impot do. I wasted 2 hours trying to figure it out to make a preset that worked similar to one I had, I figured out the old inport dialog in 15 minutes and was happy with it.

  162. Dmitry Brodsky says:

    Thanks for including old manual focus Minolta lenses in the update. But what about just regular Minolta lenses that perfectly autofocus on Sony A mount (and FE mount with adapters)? Can you guys please include Minolta lenses profiles??? There are tons of popular lenses with good Autofocus that many A mount and FE mount owners use: Minolta 80-200/2.8, 70-210/4, 50 1.4, 100/2, 100/2.8, 200/2.8, 85/1.4G and many others. You went for old manual lenses but skipped these???? Please include profiles for those in the next firmware if possible. Thanks a lot!!!!

  163. John French says:

    My heart sank when I read about the new release. Not just for the missing features – which are used by me and everyone I know and have caused widespread dismay – but because of what I perceived as a change of direction for a wonderful pro product that we who make our living from images have come to rely on. To make vital changes based on a focus group of inexperienced amateurs had me really worried. What direction is this going in? was my thought.

    Your fulsome apology Tom is very welcome, and it cannot have been an easy thing to do, but it will only redeem you and your team in my eyes and hundreds of others if it results in you putting those missing features back. By all means hide them to keep an uncluttered interface in the way the best Apple software does. You do not specifically say you will put them back in 6.3, so a statement to that effect would be most welcome.

  164. Kim Boustanu says:

    Yes, Everything that was said in the statement before me!!!!!!!
    I just subscribed to Creative Cloud, as a matter of fact my second charge just went through today. If this is what I have to look forward to…. changes to my product that do not benefit me, what a grave mistake I have made indeed!

    I was fortunate that I saw the input on the web before I saw the downloads. I will not be updating until things are made right again. What a sad state for the wonderful software. I am counting on the features being returned!

  165. TR.Martin says:

    After reading Mr Hogarty’s apology I have to ask “Who is Lightroom’s target audience, professional photographers who are looking to streamline their workflow and reduce overhead or armature/hobbyists who are just looking for an option to manage their baby photos?” as a professional the auto-eject and move operations are huge for my workflow, especially when you consider I’m sometimes managing multiple shoots a day for different customers. It’s would be nice to get clarification from Adobe on this.

    Considering we’re at version 6 and still have no network support for the catalog, I’m thinking Adobe is targeting the hobbyist, but I’ve tilted at the that windmill for too long, so I’ll leave it be.

  166. KC says:

    Tom,
    I still cant believe YOU are dumbing down the interface from what the pros are used to and use everyday to make their living to an interface that the selfie crowd is more comfortable with, I am just shaking my head in disbelief…

    …and

    Demoing Capture One Pro

    Cheers

  167. Axel says:

    To orient the ui and features simply on the (representative?) amount of usage is a fallacy, it stops LR’s appeal as an app that keeps up with the knowledge you gain.

    If it’s just about usage, what features will be next on the kill list? I imagine about 1/4 of the sliders in the develop module, probably including the tone curve that keeps confusing new users about the difference to the basic sliders.

    Adobe, as a gesture of good faith please restore the removed features from the import dialog to an advanced (default hidden) tab in a quick 6.2.2, and *then* think again what really isn’t deemed necessary by your *existing* users.

    For me, please start with restoring “move” – the removal breaks my whole work flow (rate/tag before import & manual export/process/re-import, all on the same hd). Whoever got confused by that option? Do you insist users do it all inside LR now that you’ve got those fancy (lacking) hdr & pano options?

  168. KC says:

    PS. I am so very happy that I didn’t upgrade to 6.2.X on my primary workstation. It will remain at 6.1.X for the foreseeable future, e.g., until my CC subscription expires. Then there are other choices 🙂

  169. Tom,
    As I was rolling back from LR CC2015.2 to the previous version, I recalled when I was first working with LR and could download the beta version. That was a superb approach. I suspect it hasn’t been used lately, but also suspect if it had, the problems everyone has noted, would have been corrected.

    LR is a great product. I use it daily. It’s essential to my work.

    I support the idea of the option to select import settings for various levels of users. One size can’t fit all.

    Mark

  170. D.A.Wagner says:

    Remove eject after import not being used? Adobe needs to reconsider putting this back. What I do know is there are far fewer professionals using LR than there are amateurs. So for that, we pay the price. What was the big deal about leaving it in? Did it confuse anyone?

  171. Mlonier says:

    There was nothing broken about import that in my history of digital imaging which goes back to Triple-I in the seventies, that needed fixing. So after scanning all of this, I have a fix for the broken update– I’m not updating.

  172. It’s pretty simple. LightRoom is going after the middle 80% of the market, which is dominated by prosumers and entry level users. I don’t blame them. For every advanced user (professionals and enthusiasts who actively hone their craft) there are ten users who get confused by the idea of manual camera controls and f stops and software with multiple sliders to make the picture “brighter” or “more colorful”.

    If you’re a pro and are looking for pro software then Capture One Pro is the answer. They don’t care about the prosumer or the just-learning photographer; they make their software for pros who need functionality, power, and speed over simplicity. They focus on workflow and quality of the raw conversion in ways that Adobe does not.

  173. Tina Manley says:

    The dumbed-down Import function is a disaster! My whole cataloging system of 750,000+ photos is filed on external hard drives that remain off-line and on an on-line Drobo. I need to be able to import duplicates and that was never a problem with LR5. Please listen to your professional users and bring back the old Import function.

  174. Walter Gladwin says:

    Before the recent ‘updates’, as a user of the standalone version of LR I was on the point of moving to the CC version. Over the past few hours I’ve been researching Capture One instead, and find myself sorely tempted. One can even import one’s LR catalog! That will make the transition a lot easier.
    Actually taking out features critical to discerning users is to betray the ideals LR was founded on. Unless the trend to dumbing down is reversed, starting with the reimplementation of the original import dialog in the next update, I will be taking my dollars elsewhere.

  175. Chris Hill says:

    Not to mention that I have to agree with most comments on the horrible import dialog changes, but importing doesn’t work for me at all. I tried importing 105 raw files with the latest update today, after figuring out how to use the new import dialog I hit the import button then as usual LR presented me with the library pane and the previous import section of the catalog, but importing got stuck after 3 files. I quit LR an then I copied the files from the sd card using apples image capture, back to LRs import dialog, this time I selected the files from the hard drive folder, hit import and the same happened, import got stuck after 5 files. The I tried synchronizing the folder, wich managed to import 35 of 105 files into my catalog after 6 hours…….

    I can only say that this LR update is just a shame for Adobe, it seems their man power is getting concentrated at pushing out more and more smartphone apps, very professional indeed … thanks adobe for choosing that path, by the way why am I still paying 12€ a month????

  176. Elizabeth says:

    Thank you Tom Hogarty for acknowledging some of the issues, and even fixing some of the bugs. But I agree with the majority above, I still feel like you’ve missed the biggest concern – the missing features and the complete lack of respect shown to long time users.

    Just because someone completely new to Lightroom can’t understand every last button, slider and other settings withing 60 seconds of starting the program doesn’t mean you start removing options! It means either you’re targeting the wrong customer or you haven’t done a good job with the help/training features. Guess what people – this is a complicated program that does a lot of complicated tasks. It’s not Instagram where you slap a filter on and call it a day. If you DO want to attract new customers with a simpler version, then great, please do. Photography is a rapidly expanding hobby. But if you want a stripped down version, sell a stripped down version. And leave the advanced features alone for those that *already paid for them.* I’m paying for software than I can both edit and manage files with. The biggest thing setting Lightroom apart from other software is the file management. Take that away and why shouldn’t I go to other companies that realize why I bought their software instead of throwing me under the bus for someone too impatient to learn the tool they just bought.

  177. fabio says:

    the problem my be ar ein the gpu grphic accellerated card… i have update the last one one hour ago but the problem are the same: when i go to production when i change information in the imagine, ad change my strumets the sistem block and never, i must restart.

  178. solon malkas says:

    “At the same time we removed some of our very low usage features to further reduce complexity and improve quality…”
    You obviously refer to another program,i don`t know it sorry.
    Let me speak about LR instead.If the features “Eject Card after Import” ,”Move photos to a new location”,the Destination folder tree etc are very low usage then you should WIPE OUT the Book & Web Module,keywords,curves,the watermark dialog box and the Export dialog box .
    I`m sure that your new target group users : the Instagram Hipster DON`T ever use or understand those!
    Biggest FAIL in Lightroom`s History
    We want the Professional ‘Import’ dialog box BACK!!

  179. Tim V says:

    To say that I am angry would be putting it mildly. I was forced to update today when features were disengaged (smugmug export) by the availability of the new update. I came to my computer to discover a “welcome to the new Lightroom” screen. Without having opted for automatic updates, I was certainly perplexed, especially as I was in the middle of exporting and uploading 2,500 images from Fashion Week. Many hours later I have work going through LR 4, but in the meantime I have an editor screaming at me, designers waiting, and models breathing down my neck (and no, not in a good way.) Why, Adobe, why would you ship with known bugs and force me to upgrade?

  180. Tim V says:

    Oh, and as many others have noted before me, bring back the Import screen!!! I have two client shoots from today that I am importing, and this mess of ‘simple’ reminds me of the photo kiosks at CVS. Sure, you can get your prints done, but every professional photographer is going to run in the other direction. A friend is a Capture One Pro ambassador… time to go get a discount.

  181. Greg Utton says:

    I’ve read many of the comments and I’m in total agreement. You have broken or removed key features for professional photographers. LR is aimed at professional photographers! You and your team have shown complete incompetence and lack of respect for your customer. You and your team should be FIRED!

    My request/DEMAND is that you admit you screwed up and IMMEDIATELY roll back to the previous version that WORKED.

  182. Greg Utton says:

    Roll back to previous version.

    I’ve read many of the comments and I’m in total agreement. You have broken or removed key features for professional photographers. LR is aimed at professional photographers! You and your team have shown complete incompetence and lack of respect for your customer. You and your team should be FIRED!

    My request/DEMAND is that you admit you screwed up and IMMEDIATELY roll back to the previous version that WORKED.

  183. Eric Dreczko says:

    This is what you get when you eliminate the QA process in an effort to increase profits.
    I have to laugh at the apology… sounded good until you read Tom’s ONLY response to user’s comment to date.
    I used the auto eject option religiously so I question the data Adobe used to justify eliminating that feature.
    Whatever happened to: “If it’s not broke, don’t fix it”?

  184. Colin Oatley says:

    The more I think about this the more I think it’s time to start looking for an alternative to Adobe. If Adobe is losing interest in serious photographers, them I’m going to lose interest in Adobe. Not a threat, just a fact.

  185. Chris says:

    I really miss the auto eject feature. Means I have one more step to go before I can put the card back in the camera. I don’t remove images from the card for several days when I know they are fully backed up.

    So why put a big check mark in the middle of the import candidate? I really don’t get that.

    The import module has always had an interface somewhat inconsistent with the overall app. So be it…gotten used to that. But, I would have thought that Adobe would have attempted to make the interface more, rather than less, consistent.

  186. tj says:

    updated my lr last night, folder sync not working. pls fix. thabks

  187. An apology is good when there is a true willingness to change and improve. Past has unfortunately shown that Adobe doesn’t listen to its users.
    To give some context, I was a LR user of the first hour with versions 1 and 2 before moving to Aperture 3. With its death I returned, half heartedly, to LR.
    Now that LR is in a quasi monopolistic position it is to be expected that the breadth of different workflows to perform a similar task has become quite rich but also that even when armies of users might be following a certain workflow or using certain functions, their relative number might seem small and this the use of certain options or features “infrequent”.
    Especially when covering the needs of amateurs, enthousiastes and professionals it should be expected that options only used by professionals will become infrequently used but nonetheless important!
    Hiding being focus groups is not sufficient to justify stripping away essential features even if only for a limited number of users!
    The import tool is not critical to me, I now rely on PhotoMechanic for my imports and only later do I import in LR with metadata sitting in the sidecar file.
    But this “ImportGate” reminded me of other key features that have disappeared or never made it to the apps, despite users repeatedly asking for them. Here a few, but important to me “infrequently” used features
    – support for RAW+JPG
    – keyword search and selection through synonyms
    – image search and filtering through keyword synonyms
    – Vastly increased performance of the library tool, in particular: why does performance degrade over time when working on keywords and other metadata?
    – and so many more

    Similar to infrastructure maintenance: repairing a road or a bridge has nothing sexy, politicians tend to ignore these unless forced to: no one has ever won an election on bridge repairs. Adobe is doing the same : it us bragging about de hazing or removing tourists on images because there are sexy, but they take resources away of the mundane but so crucial work of optimization, bug finding, leaks and all these infrequently important things.
    Like many other users, I’m using LR because there is no viable alternative to my needs, yet. It is up to Adobe to show me whether I’m valued enough to satisfy my needs, though maybe infrequent.

  188. Fran DeRespinis says:

    All this is most distressing. Fortunately, one of the members in our club warned us through an email not to update and I didn’t yet. Now, I don’t know what to do. I don’t feel confident the bugs are fixed, and what Adobe seems to have done with the UI is just as distressing. I’m sticking to 6.1, with all its own issues. Maybe look elsewhere. Seems to me that Adobe’s competition just got a window of opportunity.

  189. Jim Davies says:

    Must add to thegrowing list of hugely disappointed ightroom users.
    Was the import dialogue so bad? Why can I no longer iport duplicates?! I appreciate things change and usally for the better but WHY REMOVE THINGS????
    Please bring back the old import screen and include all the features that were there.

    please……….!!!!

  190. i’m still completely dead in the water after the update. my lightroom crashes every time i load it.
    2013 macbook pro + el capitan

    i’d love to get back to my photography.. but i’m having to 1/2 ass it with bridge + photoshop.

  191. Reg says:

    I’ve purchased every standalone version of Lightroom from v1.0 to 6.1.1. I was annoyed with Adobe’s decision to not provide feature updates to the the standalone but understood their need to milk the subscription model.

    I almost decided to sign up for CC last week but luckily this update occurred. Sorry Adobe – I wont be signing up until I get the same import functionality as I have with the standalone product. If you want to dumb down the product to meet your ‘analytical results’ audience then at least give us a an advanced mode so we can use the features we’ve always used.

    …and Tom, maybe it’s time to go back to a limited public beta. Based on what I’m reading here whatever you’re doing now isn’t working too well.

  192. Tom Hayward says:

    I’d like to add another vote to restore the auto-eject feature. I used it always, and dislike the manual operations that are now required to eject a card every time. Lightroom’s attraction is the way it smoothes my workflow, and removing auto-eject is a change in the opposite direction. I thought the purpose of Adobe’s subscription fees was to pay for periodic enhancements, not removal of features I use just to accomodate new users. Please put back the auto-eject, and also the display of the exact directory that my imports will go into.

  193. Thank you for the apology. Letting us know we are heard feels good.
    While Adobe figures out how to fix everything, could we, please, please just undo the upgrade? It would be like it never happened and Adobe can try again, test it properly, collaborate and make something truly amazing without rushing for a fast fix.
    Everyone would GREATLY appreciate it. You literally have photographers loosing money over this. We can’t wait for a fix we just need our import process back!

  194. Josh says:

    It should be very clear to everyone at Adobe that these changes to the import dialogue were a bad decision. If the program is not returned to it’s previous level of functionality, I will soon be back with Capture One, for keeps. Adobe, please consider this as feedback from a longtime customer – if you alienate your loyal professional users, don’t be surprised if the rest of the userbase is close behind us as we exit. I can’t tell you how many times my clients have asked for my recommendation on the best photo program. My answer has always been Lightroom, but frankly, I don’t see that trend continuing. My advice – swallow your pride and do the right thing, quickly.

  195. John Quixley says:

    Thanks for the apology on behalf of your team. I see this as the first step towards putting things right

    I already own a copy of LR v5.7 & PhotoShop CS5. In July, rather than upgrading the software I already had, I felt that it was worth taking the CC Photography subscription. Since the v2015.2 release I have had serious doubts as to whether I made the right decision. I hate the new “Improved” Import tool but I could learn to live with it, IF the old options (No need to name them all) could still be accessed.

    It is a rare thing indeed to see features REMOVED in later releases of professsional software. Sometimes they are moved or hidden but still some way to access them for those who rely on them. I have now rolled back to LR 2015.1.1, primarily to resolve the removal of features which I used regularly. If those features are not returned to LR, staying on the subscription will not be practical for me as no sense in paying for a product I find makes more work for me. I will still use my LR5.7/CS5 but all new work will end up going through an alternative from one of your competitors
    Regards
    John Quixley

  196. John Macmillan says:

    Not happy! My workflow is severely impacted. I’ve lost a lot of time and effort due to Adobe’s incompetence on this release. It’s still not working right. I get as far as the CC Adobe ID sign in and then the drop down menu goes completely blank. I never agreed to be a Beta tester!

  197. Barry Styles says:

    Question to Adobe: Does Adobe consider Lightroom to be a professional-level application? Simple yes or no question, there’s no grey area here and further diatribe is not required, just yes or no. If the answer is no, then I’ll shut up, cancel my CC subscription, and complete my purchase of Phase One’s Capture One Pro 8 (which most assuredly IS a professional-level application) and you’ll never hear from me again. If the answer is yes, then I’ll wait to see what you do about the Import debacle, but I won’t wait long. In my book, it’s never ok to remove functionality from software after it has been implemented, especially based on some dumbass analytical process that most people, including myself, switch off. If you feel compelled to waste your developers time removing code and patching the hole it leaves, then at least create a forum for the users of the software and get input from real people.

    • David Martin says:

      Barry said it succinctly: Lightroom is a pro application or it is not. Regardless of the answer, it is clear from this botched release that the development staff for Lightroom do not even begin to meet the definition of pros. I have downloaded Capture One and began to work. If Adobe comes around to accepting the fact that their professional user base is the one that Adobe owes allegiance to and is willing to demonstrate that Adobe deserves our trust, then I will come back. But not before, and not after too much time…say a couple of workdays.
      Get off your butts Adobe, and get to work. Fix this.

    • Barry and I are of like minds. I’ve already been splitting my image processing time between Adobe and Phase One. Lightroom’s comprehensive import and file management features are what has kept Adobe in the game for me. If you’re going to dumb Lightroom down, I’m out.

  198. Jimmy says:

    There apology is nice, but what you plan to do about it is far more important.

    How about telling us what is next? Should I un-install and roll back to 6.1 or are you going to fix this properly in the next few days. 6.2.1 is worse than the first release, and did not fix anything for me.

    App crashes, Syncing bug, auto eject, dumbed down import, sluggish performance, minutes of spinning ball upon shutdown or change catalogue, Etc.

  199. luc renambot says:

    – Make a beta channel for experimental software (that’s what the cloud is good at after all, distributing software)

    – Give a few months of free subscription to make up for the disaster

  200. Marko Simic says:

    The conflict between the idea that as perpetual license user I am not entitled to dehaze and the fact that I am offered an “improved import” with the new version 6.2 is clearly showing new attitude from Adobe. I was stupid enough to believe that Adobe will not abandon long time users community which helped the company to create wonderful tool for professionals and advanced amateurs and I tied my workflow to close to Lightroom. I am forced to rethink my strategy and the first step is to stop converting nef files to dng in order to open the path to alternatives. Cloud subscribe model, dumbed Lightroom, no thank you Adobe.

  201. Michael Schilling says:

    6.2 is obviously not working the way it should. I cannot access my main menu, except on start up holding down shift and opt. Please consider a patch that enables a return to 6.1 until 6.2 is fixed. That would enable not having to uninstall 6.2 and then having to download 6.1. That solution would give you the time needed to do the much needed repair work.

  202. Kruno says:

    Anyone can remove features to make it simpler. But true elegance is making it appear simple while in fact being complex. What Adobe did is just removed things and that is not good enough. Keep it simple looking if you want to but don’t remove any features, find a way to implement them.

  203. Pieter Gellings says:

    Maybe an apology would not have been necessary if you would have followed the advice of some of your renowned beta-testers: http://forum.luminous-landscape.com/index.php?topic=104551.msg859377#msg859377
    For those who don’t want to follow the link, Jeff Schewe said: “Yes, I knew what was coming and yes the beta testers warned Adobe that the new Import dlog sucks.”

  204. John Peters says:

    I am an enthusiast photographer that bought in to the CC offering early in the life of LR5. As software users ‘we’ are too often subjected to poorly tested releases, so I could get past that aspect of this release of LR. In my years of being a user of creative software I have had my share of tools withdrawn – including by Adobe, I can understand the economics of those events. What I may not be able or willing to get past is the reduction of capability of the import functionality of LR. I undertood LR to be a tool for photographers, and one which was growing in strength. As it stands the import function is excellent AND the more I use it, the more I use its abilities. Why do this to your loyal users? To make it easier for less technical users to buy in to LR? By all means build a switch into the program – give users a choice. Issue an Elements version of LR. Add LR functions to PSE. Anything other than what you have done.

    I too have downloaded Capture One with an eye on the Adobe exit door. I also use other parts of CC so pay Adobe several hundred pounds every year. Just as there are alternatives to LR and PS, there are alternatives to Premiere. I’m giving Adobe until the end of the month, then I’ll most likely be gone too.

  205. Michael Payne says:

    Please Please Please give us back the old import. The new one is just terrible.

  206. bastian says:

    please add a native png-export-feature, i cannot understand why you are not able to implement this standard. png ist web-standard, not jpg. 80% of the photos are made for the web!!!

  207. Michael Schilling says:

    Managed to get to the menu now, but have to use force quit to get out of the program. Plus it seems to take a lot longer then before for the backupThis is a very disappointing experience and not up to the standard one usually expects from Adobe.

  208. Nick Walker says:

    Whoever designed the new Import feature should be sacked.

    If users couldn’t be bothered to learn how to use the old import feature I have to ask what on earth they were they doing using Lightroom in the first place?

    Fortunately for me I use Photo Mechanic by Camerabits as it has far superior ingest and captioning options with LIGHTNING speed previews, even from the biggest files. I hope Camerabits will never be sold to a conglomerate such as Adobe as they would screw it up.

  209. Blende Up says:

    Hi
    Coming from LR 4.4 I’ll switched to LR 6 because of the new performance optimized graphics card support.
    LR4.4 License is still existing and in use, because of 32bit support for my laptop.

    What I got is:
    – Slower Import then before
    – much more Memory consuming then before (6.2 tends to crash, because 16GB of Ram seems to be to few)
    – lagging sliders / GUI
    – slow update of Raster View (“G”)
    – the new import is…. is absolutely unusable! (put me on the list please!)
    – the face detection is a bad joke, isn’t it? Slow, memory consuming, unreliable (lost most of my work and quit it).
    – Why I can’t export catalogs to former LR versions?? How should I use my LR 4.4 on my Laptop now?
    – at every corner I’m pushed to use CC, and other cloud based services. What do you think I’ve bought LR 6 for?
    I don’t want any of this cloud stuff at all.
    – I payed 160€ to join this beta test!!!

    I’m absolute unhappy with this trend in LR.
    If you want to develop LR to some sort of Picasa competitor, you missed the point what LR is for…
    regards

  210. David Van Achter says:

    If it isn’t broken, don’t try to fix it.
    That’s a newbie mistake!!

    I’m glad I took a break from my photography when I did. Seems I missed the storm…
    Oh, apologies accepted. Hope you get your stuff together before to many people go to greener pastures.

  211. Penny Foyn says:

    Take a look at an ideal Photographers’ replacement for Lightroom and Photoshop. Written from the ground up. Release 10 coming next month. Very stable.
    Perfect Photo Suite 9, soon to be renamed ON1 Photo 10. I LOVE it.

  212. Lars Svensson says:

    Thanks for the apology.
    If you want to earn back the lost trust you can start by acknowledging the many functional issues, instead of pretending that all that happened was a buggy release.
    Also, it accomplishes very little to increase pre-release communication if all you intend to do in the future is to dumb down the product in order to lure new users to buy in on a product they will use a few times before moving on to the ‘next big thing’.
    You and your team might also want to read up on how QuarkXpress lost its entire market to Indesign. Tables are turned and you are right now on the Xpressway downhill.

  213. John French says:

    I posted 12 hours ago and came back here to see if anyone had added anything. Wow! It took me half an hour to read back to my post and then another hour to read on up until I gave up. And still the side slider was only a short way up the window. Every post was critical, I did not see one that was for the changes. I have never seen such a reaction to a software change, ever.

    So I repeat my request to Tom. Restore our faith by announcing the changes will be put back soon. I have never even considered changing to Capture One before, but many of these posts have made me take another look at it, and many of the issues I had with it before have been resolved. I have started the 30 day trial and I hope, and I really mean this, that you announce you will put back the changes to LR before my 30 days are up so I can stay with LR. Then I will know your apology was for real and not spin. As well as a pro photographer and designer I run courses for serious amateurs and other pros. In the past I have always said “get Lightroom – no contest”. Now I will be holding off on that recommendation until I see whether the developers and suits at LR can come to their senses.

    • Joseph says:

      Exactly my thoughts in terms of admittedly suggesting Lightroom to new photographers. Photoshop itself almost has a bad connotation to it, like you are “cheating” if you use it (we all know this is not truth though). But Lightroom was the GOLD standard for post processing; Simple, yet powerful and intuitive; 98% of my post processing was done in Photoshop.

      Lucky for me, I still have my hard copy of LR5 and have refused to use LR6 at all. To me, this debacle is part of a six month pattern of poor updates, lack of attention to detail and a clear communication from Adobe that they are no longer taking their products seriously.

  214. Joseph says:

    Sorry to be so crude… but this is what comes to mind from this apology: “Don’t pee on my face and tell me it’s raining”.

    He says they removed features in an attempt to make LR more user friendly, but they remove the option to eject memory cards after import. Until we get FULL honesty, there is nothing more to say

  215. Joao says:

    I had not used import since the last update, and now there’s a new import interface I do not recognize. What was so wrong with the previous (traditional) import interface that you had to mess with? I read people complaining about the auto-eject feature but actually, for me, it’s the whole redesign that messes things up. The way it was before was simple enough. Why fix what’s not broken? Bad, bad move…

  216. Alex says:

    Analytics never offer complete data. Period.

    By basing your decisions so heavily on analytics and pure metrics without any depth or vision, you are looking only at clicks and ignoring the actual people using your product. Never, ever ignore your customer, but you should never let your customer design your product for you.

    Look at what happened with Final Cut Pro – the gold standard of professional NLE software abandoned the professional and went from the industry leader to a dead-end product. Apple handed over their most vocal supporters to Adobe and Avid. I’m sure if you chat with the Premiere team they will verify the huge bump in usage.

    Migrating my 750,000+ images to Capture One would be a major pain in the ass, but it would be a better solution than being bound to a poorly designed product.

    Please fix this now.

  217. As someone who doesn’t just use LR as a big part of professional workflow but also teaches PS and LR, the last changes have been a serious issue. I have no problem with a different, easier to understand import dialogue, but why can’t there be an “expert” option, giving all options back to those who use the software daily? It goes into the same as the fact that we can’t create our own keyboard shortcuts as example, it simply doesn’t make sense.

    Making software more accessible and easier to use is fine, but it shouldn’t be hindering those who use it as part of their work. Offer both, a simplified and an expert mode, and everyone would be happy.

    Additionally, the single most asked for “feature” is speed and stability. New visuals and features such as dehaze etc are fine, but should not take away development circles from optimising what we already have and use. I personally would love to teach people how to create awesome books as example, but since the book modules was introduced, it still doesn’t allow for custom designs (just as another example).

    LR is brilliant and I enjoy using and teaching it, but I hope we see a few updates that focus on optimisation rather than any new features.

  218. Torsten Heine says:

    Put me on the list of totally p… off customers. Subscribing to the CC photographers program was a no brainer for me, but I´m scared now about what to expect in the future. Im not a pro, but the import dialog was easy enough to handle for me or anyone who can handle a dslr or any modern cameras menu system. I was happy to find the auto eject feature one day. Please don´t remove any more features and bring back the old dialog. It was a joy to work with and there are lots of easy alternatives out there.
    Get back to reason or it seems you will loose a lot of your core customers and recommenders of Lightroom in very short time.

  219. Jon glaser says:

    I want the old screen back and functions. I have been using LR since version 1 when Aperature was the other competitor. I have had issues with the import of photos, but I figure it out. It’s not that hard. Kits too late to keep it simple stupid (kiss). This is another reason to just use bridge.

  220. Alex Marino says:

    ah..yeah….removing auto eject was a dumb idea. Please put it back!

  221. DD says:

    This is enormously frustrating. I’ve never had this much trouble with a software update before. I spent most of a day trying to figure out what was wrong with my system and why it was freezing up. I finally concluded that the problem seemed to be related to LR. When I googled it, I found this page.

    I was a little encouraged when I read about the “fix”. I was immediately discouraged when I realized that my copy of LR was already at 6.2.1 and still crashing. All I know to do is to “roll back” to 6.0.

    What a waste of my time. Why couldn’t Adobe have sent out an e-mail when the problem was discovered? Why wasn’t there an immediate rollback update sent out?

    • DD says:

      Now it’s my turn to apologize. It turns out that some other software was at least partially responsible for my system’s instability. I didn’t discover this until after going back to LR 6.1 but now I am afraid to try 6.2.1 again……..

  222. Phil Wiener says:

    No worries, Tom. I love Lightroom (Adobe) a lot. You do a great job and I appreciate your open words. Keep this cool stuff coming, mate! Best, Phil

    • Axel says:

      Gotcha! It took some searching, but it seems you’re the one user that loves the new import experience and is happy with the removal of the low usage features 🙂

  223. Steven Patrick says:

    Outside of my disdain for the amateurish new import layout, the first thing I made sure to do was to disable the frightening new splash screen.

  224. Lucio Daou says:

    As David Madison and Clicio, I was a also an user of the removed options and I’m trying to find my way without them.
    The big mistake was to only see the numbers, not the actual users’ feedback. It doesn’t take rocket science to know that you don’t make a major change like this on a minor update of a established software, specially removing features.
    Take Microsoft’s example: even tough the Windows 8 and 10 have almost all settings on their new interface, the old control panel is still there.
    There’s nothing wrong in trying to improve the software, but there’s a lot of wrong in removing features. The outrage would be minimal if you just made the non-functional cosmetic change but keeping al features.
    Please, at least add the missing options to the new panel. But the perfect thing would be to allow the old import panel back.

  225. You took a great import interface and screwed it up. Now I cannot import duplicates if I want to you added more work to what was an easy work flow

    • David Martin says:

      If Myer says so, then by George, it is true. I have tons of respect for this seasoned pro, who convinced me to take the CC path. And if Myer says you screwed up a great import interface, then you idiots at Adobe can take that for gospel.

      I downloaded Capture One and it is currently working on importing my catalog of over 1M images. I’ll lose the Smart Collections, but gain a professional application in the process. To me, that’s damn well worth it.

      Adobe, you have two (2) working days to fix this screw up. Counting…

  226. KC says:

    PSS. I must congratulate you Tom. This one epic shit storm that you created, hahahahaha…

    I imported a portion of my library into Capture One Pro (Demo Version). It will do…

  227. Serge Beaudoin says:

    Tom,

    Thank you for apology. For my part, the new interface is a step in the right direction. After spending 15 minutes exploring the new interface, my workflow (destination selection, presets, renaming) has remained exactly the same. Now choosing the folder destination for the imported files is the same as any other modern software (Office, etc.). Most tools are still there. Adding the missing tools would be appreciated in a future update.

    – Duplicate photos cannot be forcibly re-imported (personally don’t care about that one)
    – Eject after Import
    – Removed Zoom from the Loupe Preview
    – Thumbnail filtering by destination is gone
    – Total file size is gone

    The loupe preview could be restored in the single image view. The single image view in import is too buggy to be useful. When all images are selected for import, unselecting an image than moving to the next shows that new image unselected too. Moving to the next image then going back to the previous image shows it now as selected for import. Needs to be fixed to be useful. Can’t rely on the check marks under the images.

    When I moved from Aperture, Lightroom reviews praised its editing tools but its interface was outdated. This new interface is a step in the right direction. Better communication and tutorials on how to use the new interface would have avoided many of the criticisms. For example, one comment below was to bring back the view where you have your source on the left, images grid for selection in the middle and tools on the right (renaming, presets, etc. ). Well, this is what I see every time I click on import now. Other comments ask Adobe to bring back features (file renaming preview as an other example) that are still there.

    As a Lightroom 6 perpetual license holder, consistency would be appreciated. Do we get the new features or we don’t? We don’t get dehaze but get the new import interface? I would like to get all the new updates, not just a few selected ones.

  228. Guy says:

    Apologies are fine but action is what’s called for. Since the apology the silence from Adobe has been deafening.
    I want to see Adobe PROMISE that ALL functionality is going to be restored and PROMISE that it will NEVER be removed on any future “upgrades”. If thy expect their customers to trust them with what, in many cases is the livelihood for many LR users, they should be absolute in their commitment to current customers rather than the populist appeal of the smart phone shooters. I’d also like to hear when they expect this problem to be fixed so I can decide if I’m going to waste more time and money with them or just move to Capture One and consider Adobe having become a company with no vision and who cannot be relied upon.

  229. Cardinal says:

    “Do not change what isn’t broken”

    more so, why not ask the public audience for approval, in the long run, whomever responded, are the ones who truly use the product.

  230. Ed says:

    the entire run of LRCC has been of the poorest quality. I’ve been surprised at how bad the product has been and only wish I kept my last version of LR. It’s enough to make a guy hit up Capture One. I’ve come to expect better quality and performance from Adobe.

  231. Fabio Frosio says:

    Is it possible to reinstall LR6.1? I am a CC subscriber.
    I installed the 6.2.1 version but it’s still not usable.
    Thanks,
    fabio

  232. Ray says:

    I am in the minority who prefer it, but definitely the settings should be available under advanced or so, and it should remember the settings.

    Regarding the performance update. Maybe I’m crazy, but previewing and zooming into my Fuji raw files (RAF) seems to be a LOT faster. 3-5x. Can’t confirm the same for the Develop Module. I’ve tested before the update (thinking I updated), saw it took 3-5 seconds (yes all LR Settings optimized for performance), then realized it wasn’t installed as I had LR open, so updated, tested again, and takes like 1 second avg. Does anyone else notice an improvement with their files (guess it’s not for Fuji). I also restarted my PC, and was still the case.

  233. Danelle J says:

    Adobe, I have turned off all feedback options form all your programs as well as from windows and every other program where I can find this option. Most of my computer literate and security savy photographer friends has done the same.

    Please do NOT assume that you know from your analytics show exactly waht your most loyal and experienced users are using. We do not want Adobe looking over our shoulders all the time.

    Please reconsider deleting functions having to do with how we import photos into LR. We all have different needs and workflow systems. The experienced users will do things differently than the casual user. Please so not “dumb-down” the program.

  234. Caroline says:

    Oh dear Adobe, what have you done? I wish I had read this before downloading. Bring back auto eject NOW please. Where has the file tree gone on the left hand side? Listen to your professional photographers please…..

  235. Graeme says:

    The only thing that crashed my Mac was exiting Lr and it still does after the update fix???

  236. Jamie says:

    An apology is always a good first step, but to be honest it really doesn’t mean much without the next step, which is asking “What can I do to make things right?”
    My issue is a simple one. My workflow depends on the ability to view file names along with the thumbnail when I select which photos I want to import into Lightroom. Hovering over each of hundreds of photos one at a time in order to find that information is not acceptable.
    I’m a CC user so I’m not aware of a way I can revert back to an older version.
    In the near term, you have forced me to redesign my workflow. In the longer term, you may have also forced me to another software solution.

  237. Han Balk says:

    Dear Mr. Hogarty,
    Your mentioned “very low usage features”. Do you mean the Eject card after import? This is a very useful feature every photographer who works with multiple cards or cameras uses. For all of us you’ve introduced a additional action and the chance to corrupt your card or to make the OS instable. Thanks a lot, not!
    I was wondering to whom your team has spoken.
    Get real and don’t mess with your professional users who embraced LR since 1.x to gain some newbies uploading their selfies.

    Regards,

    Han Balk
    Adobe Certified Expert Photoshop Lightroom

  238. larry says:

    Please bring back the old import window. I’ve been using Lightroom since version 2. One of the reasons I switched to Lightroom was the import window which featured automatic ejection of the memory card. That was a big deal back then and really helped my workflow. I’ve been taking it for granted for years now. WHY WOULD YOU REMOVE THIS SIMPLE FEATURE THAT I NEED ?!?!?!?!!??? I read today that Capture One can import Lightroom Catalogs. If Adobe continues to remove intelligent features and turn the program into some sort of touch screen toy, I will consider switching to Capture One.
    Don’t remove features pros have been using for years. Bring back the old import window this week.

  239. John French says:

    Danelle J says:
    “Adobe, I have turned off all feedback options form all your programs as well as from windows and every other program where I can find this option. Most of my computer literate and security savy photographer friends has done the same.”

    Good point, I do the same and all the professionals I know do the same, we distrust such feedback as it is often only used for marketing purposes. Possibly not in your case, maybe you genuinely collect user data and learn from it, but it has become a reflex default position to turn it off with many computer users. So I don’t think you are necessarily getting a representative section of the LR community that way. Had you done proper beta testing among professional users this whole sorry mess could have been avoided.

  240. John Blackwood says:

    I have complained along with hundreds of others about the changes to LR Import. Here is an idea that will I think work for everyone. When teaching LR new students are a bit baffled by all of the options that appear before them. Changing the interface and removing functionality to dumb down the software is not the answer..
    Here is my idea:
    1. Revert back to the previous import. Once you understand it I heard very few complaints.
    2. Develop a Wizard that walks a new user through the steps and briefly explains the options available at each step. After a user imports their photos a few times they will have the process down and can turn it off.

    Tom I hope you read down this far and seriously consider proposing options that will both please your long time paying users and make the software accessible to new users.

  241. Rob Sirota says:

    How about bring back the more technical (old) import and have a general preference to use the new or the old… The eject is 1 line of code and needs to be added back.

  242. Andrew Coleman says:

    Please, please, please listen to your users Adobe. The old import box was superb! I use all the features removed, especially the destination tree and eject after import. Removal of these features (and an obvious attempt to ‘dumb down’ Lightroom) had me off searching for alternative software (Capture One looks like it will fit the bill) – and this is from someone who teaches both Lightroom and Photoshop, so selecting a different product would have been unthinkable to me before this update!
    If you must produce a dumb version for the masses – please develop a ‘Lightroom Elements’ version like you have with Photoshop, and leave the produce we know and love alone. Please.

  243. Michael Hitzler says:

    Dear Sir / Madam,

    I am a German so please forgive me my English.
    Do you have a secret plan to oust your customers?
    I just updated my LR on my Mac and than experienced this new import routine, which is everything but an understandable useful workflow. I WANT to copy data from folder a to folder b, Punkt. Which worked fine until yesterday. No everytime i dare to click on something, it starts earching and trying to find every image somewhere on my drives . SCRAP.
    It took 12 Minutes to copy 45 24-MB-Imagefiles from a SD-Card to my NAS-drive, and than after restarting Lightroom: Adding to the catalog failed. So importing again which took me ten minutes(really) to click and WAIT through the two !! Subfolders on my NAS.
    Did you ever read the ISO 9241-11? Its seams to me: no.
    THE SD-Card-NON-Functionality has been discussed enough ; I dont understand why you have removed this function.
    And still: did you ever here something about ntworks? I want to work on my catalogue on an network drive. This is standard technology today. Punkt.

    From my side: apology rejected.

  244. John Abraham says:

    Thanks for the apology. I most miss the auto-eject card and the ability to save the destination folder as a default and in a preset (seems now I have to pick my folder every time?). Also, the ability to review photos by destination folder (i.e. date) before importing.

    I do appreciate the availability of a simplified import dialog, as long as defaults (e.g. destination folder) can be set/saved. But I don’t understand the logic of removing features that are useful to pros in an attempt to simplify for newbies. It’s a challenge in software design to simplify the interface while retaining functionality, but I think you guys are up to the task. In this particular instance, you could do something as simple as having two import dialogs, the “easy import” and the “advanced import”.

  245. Dear Mr. Hogarty,

    As a Lightroom paying customer since day one, allow me to express my disappointment with the entire V6 release cycle. Your firm, and your supporters at KelbyOne for example, made many comments about performance improvements and increased functionality in the original release. The majority of customers who use Lightroom in the course of their business will openly tell you that this was not true. The HDR and Pano functions are decent enough but will appeal to beginners and new users, not to seasoned professionals or serious amateurs.

    Then came the first update. Big storm about DeHaze. As an educator I have found that I have to spend a lot of time with my clients helping them understand what it is doing and why they are unhappy with the results. Another beginner feature more fitting for Instagram than a professional digital asset manager and editing platform.

    Then came the latest smoking hole in the ground. Shipping a product with a known bug is a difficult business decision and while you may not reply, I suspect that the release was a push from somewhere in the company to have something new to coincide with AdobeMAX. I’ve been in software a long time, and have seen this before. If it happened, I feel for you and your team, because it meant something had to give to meet the ship date, in this case it was QA. I am glad to see a fix for clients impacted in short order, but thousands of angry clients would not exist if the company had held the release until the bug was addressed. Because the primary fix arrived so quickly, it’s apparent that the engineers were very close.

    On the subject of the Import dialogue, I, like many other respondents depend on Lightroom. I do not want nor need an Import dialogue that looks like iPhoto circa 2009. I use the functions that were presented to me. I understand the need to get new users. As an Educator, I know that the standard Import screen can be confusing to new users. So offer Basic or Advanced as a choice, if you believe that the import screen is a show stopper but do not rob those who have supported the firm for years in the hope of getting new buyers. It’s a bad decision.

    Also please be aware that most pros disable the phone home junk, and even more use tools to prevent the invisible phone home events that some manufacturers build into their software. This should not be a surprise to you, so making decisions solely on in application analytics that require phone home to work is misleading to you and your teams. There are lots of good people who have posted who have an investment in Lightroom and its use. Why not ask us directly for input instead of making decisions without us?

    You have to do what you have to do, but I am stunned and saddened to listen to peers who are actively looking for alternatives and who claim to have given up, having stayed on 5.7.1 and who see no future for their needs with Lightroom.

  246. Walter Gladwin says:

    Maybe we’ve all got the wrong end of the stick. Maybe this is not the beginning of a dumbing down process, and the intention always was to put the currently missing import features back under an advanced tab, but they had to rush out an update under exceptional circumstances and didn’t have the time. In which case, a promise to have these features back, because their absence is hurting people, would go some way towards quelling unrest.

  247. Brian says:

    I appreciate the apology – but still – please commit to FIXING the import. Frankly the only thing that made sense to me when I was learning Lightroom at the beginning was the import. Now I simply don’t know what you’re doing with my files, I have to assume you’re doing about the same thing it did before, but I don’t KNOW like I used to. Also, bring back eject after import – I used it constantly and just now as I’m importing files from 3 different cameras I’m frustrated that I now have to remember to go outside of Lightroom to before swapping cards. This is ridiculously stupid. Hoping you fix it soon, or I may just downgrade and drop CC in favor of stand alone or a competing product. If this is progress I’m not interested.

  248. Brian says:

    Also – greyed out photos with check marks on them makes me believe the files have ALREADY been imported. This UI blunder is causing me to second guess everything. Please fix it already.

  249. Aaron says:

    It frustrates me to no end when software people remove features because they believe that it’s what people want. Why would they get rid of the “eject after import” which was tremendously useful?? Lightroom is for professionals; if people can’t figure out how to use it, perhaps they shouldn’t even be using a computer. This should have remained a toggle switch at the very least. The other changes are terrible too including copy only instead of move. Adobe: Please admit your mistake and restore the former import wizard. If you need to, add in a “moron” setting so that people can use the 6.2 version if they are unable to figure out the full version.

  250. Bryan Hansel says:

    I teach Lightroom and many students still use older versions of Lightroom. With the changes to import, it makes teaching significantly harder. Definitely, less motivated to offer that class in the future.

    I used the effect card after import feature all the time. Bring it back.

  251. Aaron says:

    Agree that the new UI is HORRID. Check-box on top of the photos, etc. Obviously the coders at Adobe are not photographers and have never worked an actual day using Lightroom.

  252. Dj Hogg says:

    I have tried to use lightroom, to me the interface from day one has been to hard to use. I always go back to bridge and photoshop. This is also not the first update to Lightroom that has crashed my system. I think a redo of Lightroom from top to bottom is something you should consider. It has got to be more user friendly.

  253. Mike I. says:

    It’s quite interesting (and sad)…

    The “selfie crowd” (and the reference is not meant derogatory, it’s just a specific target audience) wants basic features and ease of use. A lot of programmers can code such apps, resulting in an abundance of basic photo apps of which most are free or available for a symbolic price.

    The ‘intellectual value’ is in the knowledge of how to make advanced tools that can handle requirements requested by professionals. That’s why real photographers and prosumers don’t mind paying for their tools. They know the tools are not easy to make and expect the tools to be professional too.

    In comes Adobe with the brilliant idea of dumbing down a professional tool for the selfie crowd (who doesn’t want to pay for it) and make the professional users (who don’t want it anymore) pay for it. Brilliant, absolutely brilliant…

    Just like the marketing campaign for vacuum cleaners by Electrolux in the 60s (“Nothing sucks like an Electrolux”), I can imagine the “Adobe way” becomes a use case in business schools on how NOT to do it.

  254. Matthew O'Brien says:

    1. The import dialogue needs more not less features.
    a. Option to select raw, jpg or both.
    b. Option to import by date range.

    2. If you are really interested in your customers you would not continue to ignore the most popular feature requests on your own forums. What happened to “Let’s do it” and the promises of a “CC” model.

    3. I assume the “committee” responsible for this import decision shares the same dna as the committee responsible for the key design features of the crippled book module, locked into a Blurb model and dumbed down to a template based excuse for a book module.

    4. Adobe does not have the right to decide what I should include or exclude from my Catelog.

    5. I suspect the removal of existing features in the manner just experienced could be open to legal challenge.

    6. Fresh scars on top of older scars take an awful long time to heal. This is not the first time that ‘trust’ has been broken. The pattern reeks of both arrogance and incompetence, endemic within Adobe.

    Finally and most importantly, I am taking active steps to make myself as independent of Adobe as I can. Thanks for the push

  255. Today I got the update…. I read before that the last update was awful. First time I called the Import Dialog I was frightended – because I saw some nude pictures from my personal folder…. I don’t want to think about, how this imagine to a customer who sit beside me, after taking some pictures for application for a new job.
    I don’t know, who you are asking about the Import Dialog of Adobe Lightroom. It seems, that you don’t ask professionals. Perhaps, you got in the moment some extra money, if you make the Import Dialog more comfortable for amateurs…. But you forgot there one thing: Amateurs don’t use a software because it’s user friendly. They use a software, because professionals use it… If you go this stupid way forward to develope Lightroom in direction as a toy, you will lose the professionals and some time later also the amateurs….

  256. Jimcamel says:

    I’ve been following this all week – since the first updates were released on Monday – and I’ve installed all of them. I count myself fortunate that LR is not crashing on either my Yosemite or El Cap systems – and I have been working them and test cases all week to be sure. This probably indicates that many of these issues are the result of software conflicts that would have been revealed with more thorough beta testing…and I just don’t have those conflicts.

    Nonetheless I too am very disappointed in the removal of the old IMPORT dialog (not that it wasn’t without it’s problems) – but the new one is a User-Interface disaster. The options are hidden and have to be revealed, the checkmarks obscure the image, selecting/de-selecting is cumbersome; Auto-eject is no longer an optios. And this has been re-iterated by the hundreds of post before me so I won’t belabour it.

    Tom, your apology only retains sincerity if you followup by rolling the removed features back.

    Here’s what I would advise.
    1. Re-instate the old dialog; enable it with a PREFERENCE
    2. Implement an IMPORT WIZARD, as John Blackwood has suggested – excellent idea.
    3. Ignore the analytics – I’ve turned mine off too.

    But if you read your LR Forum – and I do each week – you will see that hardly no one there is complaining about IMPORT. What there are are countless occurrences of people losing photos by ‘de-linking’; lost folders; an inability to move photos/catalogs from one computer (like an older one being replaced) to a newer one; people with ‘corruption disasters’ and so forth; and things hidden in the user interface all over the place so you have to click-around to find things and you can never remember where they are as they are ALL NOT referenced in the dropdown menu structure. It’s so painful to read! The whole paradigm of how LR is organized and how it works is probably your biggest user issue – and you could well spend time on fixing that through education and wizards so all that confusion and pain goes away – and leave the facility that works alone.

    Finally, one specific issue about the IMPORT user-interface you could fix, that no one has mentioned deals with PRESETS. When you set one up for a new user, with options set that would work for that user, you can’t just simply use it because it embeds the destination folder – and the IMPORT then, by default, goes to an un-expected place. Setting up a working default requires clicking the IMPORT button in Library; setting all the options in IMPORT the way you want and then completing the IMPORT within Import by clicking on it’s IMPORT button….now you have set the options and they will default to that next time (so a PRESET isn’t necessary) – but this is soooooo easy to break – so it’s not reliable. That’s the sort of thing you need to address in IMPORT.

    Finally, for some time I have done imports by starting in Library, always showing my Parent folder, and clicking on the parent folder in the folder tree, doing a “Create folder inside…”, followed by selecting that (new empty folder) and doing a right-click “Import to this folder …” That still works in the new system, fortunately, and is a workaround until the loss of the display of the Destination tree is resolved.

    So, please address these issues quickly.
    I apologize if this is a duplicate – I am having difficulty posting it.

  257. Zsolt Arkossy says:

    Please give us two import panes: 1-Simplified 2-Expert
    That’s all we need.

  258. Stuart Nafey says:

    I would love to evaluate the new features installed and removed, but after updating LR CC, it is taking hours for the program to launch and get to the Import screen on my Windows 10 machine.

  259. Canyon Mike says:

    Hi Tom,
    We all appreciate the apology. What concerns us is the process by which something like this could happen. The two issues here are pretty fundamental, and really out of character for most of our experience with LR.

    First, removing features is not an upgrade. Example — eject after import. Why take that away? There are many others, but the idea is the same. Less is not more.

    Second, how could you have missed the crashes? The most popular photographers platform is Mac, which seems to be where the crashes happen. It was so common that we wonder how you could have missed it, as we would expect your testing to be much tougher than any of our normal usage.

    Please take your time here. Your product is not some game or novelty. It is a production tool many of use to earn a living. Deadlines are getting tougher. Throwing a stick in the spokes like this can lose us clients. No one needed 6.2 that bad, except maybe your management. So, take you time. Get it right. Stuff like this kills companies.

  260. Jayne Buckley Sykes says:

    Unhappy, unhappy, unhappy…

  261. Bob Hamilton says:

    I uploaded and installed Lightroom firmware 6.2.1 and now I am completely unable to import files. I can see folders already imported and worked on but cannot import new files and folders. Camera used is the Leica S type 007.
    Is there any way in which I can delete this upgrade to return to where I was?

  262. Sascha Peilicke says:

    I’ll keep this short. Please bring back the old import dialog. It was perfect as is. Is LR still meant to be a pro tool?

  263. steve barbour says:

    outrageous .

  264. Thank $deity I had a copy of LR5 on my laptop this last weekend. I was on a field trip many hours from any resemblance of usable bandwidth and went to import photos into LR CC to have the application crash, every single time. Adding photos from an existing location worked, but then the application crashed if you wanted to export them.

    The new import dialogue’s lack of a move option is an issue (I use that often) as well as ejecting on import. To make such major changes with essentially no notice is irresponsible in the least.

  265. Michele says:

    I always use the auto eject of the card. And I move photos and use the directory tree to import photos to different folders in my directory. Why would you delete these items?!

    I’m still ticked that I bought LR6 and then you stuck Dehaze on CC and won’t provide it to us 6 users in an update. It really has turned me against Adobe. Up until this spring I raved about LR to everyone. No more. Phooey. You just want your dollars apparently. And yes, I’m a big user (having taken over well over 150, 00 photos in the last four years – but my eye is out now for other editing options.
    Michele

  266. Jez says:

    Seems to me that Adobe are jealous of all the attention VW are getting so they had to do something similar…

  267. Mike I. says:

    This just in:

    Telemetry data has shown that values between 1 and 1.2 in the Exposure slider are the least used.
    These values will therefore be removed in the next update.

    (Yes, Adobe, that was sarcasm…)

  268. Will says:

    This apology is utterly meaningless. All of the explanations have been absurd. Just restore the dam import function so that it’s useable again — THEN apologize. Until then, be quiet.

  269. PLEASE GO BACK TO THE OLD IMPORTING SYSTEM!!!!!!!

    I had to completely uninstall LR CC after I updated. OMG>..what a mess. Now to import off my external hard drive the import window is EVERY SINGLE IMAGE on my hard drive and that’s thousands. Even if I click on a specific file or sub-file ALL images are in the import window. None of the files are in sync.

    It took me HOURS today to find the images I needed to send to an editor today when it should have taken me 5 minutes. I finally uninstalled CC and downloaded my stand alone version that I WONT upgrade since it’s going to do the same thing. Now, I don’t have “dehaze” and a few other features that I like.

    WHY????? WHY did you do this??

  270. Bob says:

    This recent level of communication of an apology seems similar to me as the pattern of a failure to understand the end users (purchasers) and customers of this product. Very much an arbitrary dictate as opposed to a POSITIVE level of interaction.

    Examples: THE Forced change of the SUBSCRIPTION model of Photoshop
    The issue of the ‘dehaze’ brush
    Now the ‘dumbing’ down of the import process and the elimination of user configuration.

    What next Adobe? Whatever it will be will fall into the category of being arrogant. Many great companies in the USA have failed to recognize that their OWN ARROGANCE has led to customers eventually leaving for other option. Wake up.

  271. Again, where was the preview on Adobe Labs?(where all of these criticisms would have happened a lot less vituperatively)
    I think I am only going to happy when Apple iPhone is removed as a ‘camera’ in LR- or installed as a camera in LR4D. That’s where all the newbies are coming from…
    And don’t get me wrong, I totally love Apple (crossing fingers)
    I especially love the way they update software, add and remove features based on ‘user’ input. Oh, that’s what ADOBE just did….
    Any way, note to self: We have got to find that ‘user’ and stop him.
    Al Hamilton LR3-4-5/PS6 ACE.

  272. gilbert says:

    Not ready yet, it is to late for all of us. Even with the latest patch I still have black photos import and what will be the solution now?

  273. “we removed some of our very low usage features to further reduce complexity”
    Just a heads up, your software is relied upon by professionals to do their jobs. You DO NOT remove features, or knowingly release software with bugs in in without notice or peoples work will be effected and people will not rely on your software again.

    I’m one of them, this is absolutely unacceptable behavior for a professional software provider.

  274. Tom Scott says:

    Has anyone has a problem with the lens correction panel? In the past there was a scroll down menu of lenses to select from. this seems to be gone from the latest update. After I select a lens brand, the lens correction feature keeps selecting an incorrect lens model and profile by that manufacturer.

  275. Wow!

    This “upgrade” is for sure the worst one i ewer experienced.
    The new import module is a big step in the wrong direction.
    Not being able to see exactly where my photos will be in my folder structure causes me a lot of extra work.
    The same thing goes for the lack of “move photos”.
    Something i use more than 90% of the time.
    I have used LR for 8 years now. At this moment I’m really close going elsewhere.
    In total my confidence for Adobe is absolutely rock bottom.
    To bad i can´t cancel my subscription of the full Adobe CC until July next year.

    Please give me back the old import module ASAP.
    And then do some serious work to improve performance, so that i can speed up my workflow. That´s really important to me.
    Pro sports photographer, working for a wired agency. So each second does matter to me.
    The new import truly costs me a lot of valuable time.

    I´m truly really upset at this moment.
    And it seems that I’m far from alone.

  276. Michael Nault says:

    How about you just step back to the last version before you all screwed it up? How did you ever let such crap be released?

  277. Adobe, this thread has become very long. Can you please inform us here what you have done to address the problems/issues mentioned? Have you acted on them? Thank you!

  278. David White says:

    Tom Hogarty,
    If you really want to earn back the trust of your customers can I suggest
    1. Let customers vote on what they would like in new features, and don’t let Adobe staff have a vote
    2. Maintain a public list of all bugs, allow customers to indicate the impact of each bug, and fix at least the top 95% of all outstanding bugs when shipping any Lr update.
    A lot of people are watching to see if you are serious about doing better, or if this is just a PR stunt.

    David

    • Hi David,

      1 & 2: This is what do at feedback.photoshop.com

      • Scott says:

        Jeffrey —
        Implicit in David’s list is the expectation that Adobe will act on the user-created feature requests in #1 before adding “improvements” that no one wanted. And I think you missed the crucial part of #2: “and fix at least the top 95% of all outstanding bugs when shipping any Lr update.” That is not currently happening.

      • David White says:

        Jeffrey,
        My experience of feedback.photoshop.com is much closer to a black hole – suggestions and bug reports go in, and disappear forever. As one example of many current issues I have: slide shows have been unusable for me since the initial Lr 6/CC release. I have see other people’s reports of the same issue along with more input confirming that it is a general problem. But slide shows still do not work.

        If you believe that feedback.photoshop.com is providing this function, where is all the feedback asking for useful functions to be removed from Import?

        David

  279. Danelle J says:

    I commented earlier today, but as I continue to think about this fiasco I have come to the conclusion that Adobe has no respect for the abilities and intelligence of most of your users. “Dumbing-down” your program shows that you have no respect for your loyal users.
    If you must, offer a separate “Lightroom Elements” program for beginners where you can have “guided” steps for those who choose not to learn how to use the “grown-up” program.
    But respect all of us who have spent the time and effort to learn how to effectively and efficiently use Lightroom to process our prized photos. BRING BACK OUR OPTIONS AND GIVE US BACK THE ABILITY TO MAKE DECISIONS FOR OURSELVES.
    We all can find another program to use if this continues.

  280. Zack says:

    Ahhhhhhhhhhhhhhhhh, please don’t remove features from Lightroom! I seriously love Lightroom and you’re making me want to cry. Importing is SO cryptic now. Everything was perfect before. All info laid out in front of you, nothing hidden. Don’t pander to software dummies. People shy away from Apple software and towards Adobe because Adobe creates professional software for professionals. Please don’t lose focus on pro users.

  281. clemont says:

    sorry but the complete update is a bug!
    that new import dialog is a joke! so i have to go an check out Capture One Pro…
    looks like lightroom is going straight down for regular consumer software…

    🙁

  282. Bob Lang says:

    Lightroom 6.2 for Dummies? Some people think Adobe have dumbed down the interface for file import of Lightroom 6.2 to the point that ONLY dummies can use it. But that’s not true. Dummies much prefer that little app on the phone that adds the nice photo frame, so even they don’t use Lightroom 6.2. So, Adobe, NOBODY likes 6.2. Please do more than apologise for this poorly thought out release, withdraw it and reissue a 6.3 quickly with the restored file interface. By all means add a “input for dummies” button, but honestly I don’t know anybody who would use it! Meanwhile, my advice to everyone – DON’T UPDATE TO LIGHTROOM 6.2

  283. Adam Bridge says:

    I appreciate the work the Lightroom makes in improving your product. But I think the changes made to the import process weren’t well thought out or researched. The user interface is so dark its difficult to read. The lack of ability to automatically eject the memory card is a seriously nasty decision that makes my life more difficult.

    I get the feeling you dumbed-down the interface far more than you needed to, taking away feed-back features (where, exactly, are my images going to be placed?), and taken away control I really need. This isn’t an application for an iPad or an iPhone – it’s for a full-blown computer. It needs to respect the user.

    Please revisit the Import process and give us back the features we have used. Respect your users.

    Thanks for listening.

  284. Have you ever heard the term, if it ain’t broke don’t fix it? But you all decide, hey we are going to completely redesign the import, for no apparent good reason, just to do it. Your apology is worthless because this wasn’t a oops we made a mistake. This was a conceded effort to deliver an inferior product. We are photographer’s who have paying clients who rely on options, even advanced options for our workflow to make things run smoothly. Whether you think some of the options are useful is irrelevant. You introduced the options within the import function of Lightroom and for years we have been using them, then you decide out of the wild blue we just don’t need the import function to have too many options because of a few new people who can’t seem to figure it out. Really? I mean what happened? Did you all forget you are Adobe? The king of options. That pretty much is what we love about Adobe. Is the fact that we have a slew of options to utilize if we need to. I mean why not turn Photoshop into Paint. Hell, look at Photoshop, tons and tons of features that some of us never use, but does that mean you just arbitrarily delete those because you are too lazy to update them when you put out a new release. And who says some functions even need updating. This whole thing is completely ludicrous and your half ass attempt at an apology is laughable to say the least. If you truly did care about your product you would have never released this ridiculous update. Besides the import issue itself, on a programming level it is extremely buggy and should have never been release on that alone.

  285. Josh says:

    The new import is a major disappointment.
    I feel like it has been dumbed down and feels more like iPhoto than a professional piece of image editing software. I have been using Lightroom since version 3 and never once did I have a problem with the import process, even as a beginner.
    Please, as others have suggested, create an option to switch from this basic version to a “pro version” of some sort.
    This pro version should be exactly as it was before, from the look to the process of using it. Thank you.
    Josh
    (Hopefully not a future pro1 user.

  286. Greg says:

    Incremental updates are meant to refine and improve a product, not devolve it. LR, with the “bug fix” just crashed el Capitan so badly that it corrupted my external hard drive. Before that crash, after a wedding import, the image preview generations were so slow that flagging wouldn’t display the icons. Please allow your users to revert to a stable product. I’m completely stuck and seriously looking at CaptureOne.

  287. Jonas Mouritsen says:

    I use Lightroom as a foundation in almost all the projects i do, effectively locking all my work in Adobes proprietary catalog-format. I wan’t to be ABSOLUTELY sure that the software I use professionally today, will be BETTER tomorrow. I used to think that about Lightroom, not any more.

    To me Adobe needs to restore the faith that is creating software respectful of it’s professional user base. And the more I think about it, the more I realise that that faith won’t be restored, if Adobe now adds a checkbox for Eject after import. And maybe slowly over the next half year a little bit more of the functionality that the software has lost, and say “see we really care”. I will still fear that the underlying reasoning behind designing for the lowest denominator and “removing very low usage features” will seep through when Adobe starts updating the rest of Lightroom.

    I need to see a radical decision from Adobe to show what direction they want to take Lightroom in the future, and a blog post like this does nothing. The only thing I can think of is, for now, to pull back the new “update”, restoring all the functionality that your professional users obviously depended upon. Only that will send a message that you really care about the feedback you get.
    If you don’t, we will know what future you have chosen for Lightroom…

    I agree with you that the old import process could be improved, and please keep working on a better solution it in your labs, and rerelease it when it is actually ready. But please don’t let us all beta test it while try to figure it out. Your current customers will respect you for it, and newcomers won’t know what they are missing for a few months.

    If I don’t see decisive action from Adobe, personally I will start to look for alternatives.
    A software like Capture One may not be perfect as it is, and I will probably miss some features from Lightroom, it really is a great software. But at least I have faith that they respect their users and will make the software BETTER tomorrow than it is today. And that means a lot to me.

  288. Lynda says:

    Having update, again, and believed the crashing and bugs were fixed, I’ve just attempted to upload some images from my hard drive and not only can I not upload nor find the uploads – my entire library has disappeared. THOUSANDS of images just evaporated and a deadline looming and no time for faffing around with retrieving from external hard drives.

    The previous import process was clunky, but it worked, and at least it didn’t magic my work into the ether. I’m feeling pretty ill right now. An apology isn’t enough, a working product is what is needed.

  289. Jens Arbogast says:

    I don’t see any improvements after the new update. Lightroom still keeps crashing.

  290. I am running a MacBook Air (11-inch, Mid 2011) with Lightroom 6.2.1 and it is a disaster. Lightroom goes into a mode where it uses about 90% of the CPU. As of yet I have not been able to import any files into a catalog. It takes ages to even open, if it opens at all, the new Import widget. I don’t know if any new versio of Lightroom has previously been so buggy as this version is and I am a long time Lightroom user.

  291. Dennis Zito says:

    Hi Tom,
    Thanks for the apology. Yes, the import is a mess, and you should go back to the original format. That said, my biggest hang up is the stability or lack of in LR-CC and previous releases. Since version 4, I have not been able to use my adjustment tool using my Wacom tablet. I’ve upgraded my Wacom tablet driver with no success. Other issue are quirky sliders (moving erratic). Therefore, I’ve pretty much have deep 6 LR, and now use PS-CC and ACR for my editing. ACR works just fine with my Wacom Tablet and the sliders move smoothly. Also, LR-CC is sooo Slow at start up and constantly reloading my files, wasting my time!

    Thanks,

    Dennis

  292. Ed Nazarko says:

    When I went to import files and the new interface came up, I actually gasped out loud. My first words were “OMG, Fisher Price is now doing the UI for Adobe.” (Actually said something much less repeatable than OMG…)

    And then I proceeded to fumble and stumble around trying to import my files, when I should have been tagging and editing to get them out to the customer.

    Simple and clean doesn’t mean dumbed down. My problem with Lightroom isn’t complexity of UI – it’s that the UI sometimes has a mind of its own, and the program exhibits all kinds of weird behaviors that speak to poor coding and testing. Like how images twitch on the screen when you open some editing controls on my 2 year old Macbook Pro Retina with max memory… if you can’t run fast and reliably on that, you need to go back to coding school.

    Making that many decisions about defaults is like saying, we’re going to remove all the exposure modes from your camera except P, because we know better than you how to take pictures. And, if you still want to shoot Aperture mode, you fossil, you can go into the menus and make it so that even though the command dial says P, it’ll be Aperture mode… unless we change our minds about it.

  293. Bo says:

    Really looking forward to the old import dialoge.

  294. Bob Silva says:

    Bring back the old import dialogue, I like to rename my photos on inport.

  295. Really? There is no longer the “option” to eject the card after import? Why would you remove this option? Give us the choice please. I found it convenient, and more importantly, if I got an error message when I pulled the card, I knew something may not have gone correctly on the import.

  296. Bev says:

    This new version of LR is awful. It keeps locking up on me. And I ditto the above comments about the import function being ruined. I use auto eject on my memory cards all the time. I also used the file rename function. I don’t see that anymore. I don’t get it…if people can’t figure out the import function then how do you expect them to use the develop module? It’s alot more involved. Are you gonna dumb that down too & make it useless??? Is the the beginning of the end of LR? Can I go back to an older version of LR before you screwed it up???

  297. Apologies are welcome, but this one isn’t satisfactory. Here’s why: “At the same time we removed some of our very low usage features to further reduce complexity and improve quality”. Keyword: “REMOVED”. I’m paying monthly for something I find useful, only to find one fine day that it’s not there anymore. This time it was taking control of the folder structure on import; what will go missing next? Truth is, Adobe will still consider future release as just “releases” – as opposed to “upgrades”. I don’t see myself using LR for long if they don’t change route clearly.

  298. Please bring back the previous and very useful import process as a selection. The dumbed down import process is ineffective and inefficient as compared to the current system. Please make it go away or provide a way to revert back to the old process and all its controls.

  299. Ann says:

    I haven’t run the update yet, but…completely removing eject on import because your metrics say it’s a low usage feature. What is wrong with you people? I’ve worked in the software industry long enough to know that you don’t break backwards compatibility for your customers unless there’s really no alternative.

    Your product managers are idiots if they don’t know that.

  300. lyle says:

    Sorry Tom , the product I pay to run isn’t called “meaculpa”, it’s called “Lightroom” – now FIX IT ! 😉

    No on one in their right mind p*s off their existing userbase with the type of releases which have typified the 6.x cycle thus far. Graphic card acceleration releases – fail. This new import – fail. Really bad speed… fix the previews speed issues so people don’t have to use PM… Why didn’t you just build a simplified import interface, leave the old one available and let the users select in Preferences between them ?

  301. Warren says:

    What’s with the big tick over photos on the import screen? I don’t format my card after every import and I don’t import all photos from a shoot so being able to preview the photos without a stupid big tick on them allowed me to uncheck the photos I didn’t want quite quickly. Also removing the folder tree has made importing more difficult. As a real estate photographer I can have several houses on a card from a days shooting and could easily select the appropriate house and destination folder then import 1 house shoot at a time. This new UI and those stupid bloody ticks have made my whole import process unnecessarily more time consuming and difficult.

  302. Thanks for the note Tom, much appreciated.

    The is a lot of power and functionality in Lightroom and this of course means complexity and all that entails.

    Perhaps its best if future refinement of Lightroom be presented in a way that can be tailored by the user so that they can choose to be presented with a simplified or “complexified” dialog in much the same way that current games can be played in “easy”, “normal” and “hard”?

    The underlying functionality and code would be the same for either interface (excepting that the simplified would cut some of those options off)

  303. Tim Ashman says:

    I’ve been very disappointed with Adobe moving to a Software Rental Model. I’m still on 5.7 and will be until the RAW converter fails me, then it will be time to move to a different product.
    Adobe – People want stability in the products they use. Lightroom should move slowly, cautiously and with purpose not just so everyone feels like the money they pay each month is worth something.

    tim

  304. Sandy Woods says:

    Just in case Adobe engineers are counting votes, I would be grateful if you would add back the move option on import. I use it often.

  305. Tom says:

    Apologies are fine, but no one has directly addressed customers’ concerns about the loss of functionality and the usability of the Import module. What’s Adobe’s plan moving forward regarding Lightroom? I think that’s what customers are waiting to hear.

  306. I appreciate the appology; however, I am VERY concerned about your comments on the import changes.
    Your statements imply that you still believe these changes are the right move. They are NOT. You have taken away many very imortant features. YOU may call them “rarely used” but that is not excuss to remove valuable features for those who do. People who don’t wish to use them don’t have to, but don’t take them away.

    Just let users choose an interface they prefer within Options. It’s that simple. “simple import or adv. import”.. see how easy that was?

    Adobe MUST stop making changes based on the ideas of non users. If you simply read your own comment forums you’ll see that the vast majority of people do not like or want this change.

  307. Mary says:

    You haven’t fixed all of the issues, the crop tool keeps shrinking to nothing when I try crop. And it’s slow rendering previews.

  308. Frank says:

    Your apology accounts for nothing as they are meaningless words. I believe, as do most others, that your comments about the Import program are somewhat less than the truth.. It they are not then at the very least you should open an independent poll accessible to all. You might get a shock. If you are proven right, I for one, will cancel my subscription, as I would consider that you are changing a classic into a silly consumer product.

    As I cannot afford to lose my income I have reverted for the time being and will re-asses whether I should continue with Lightroom. I as many others will be voting with my custom as well as public media – maybe somebody might explain the gravity of what you’ve done.

  309. Waldo Nell says:

    I agree with many here. I pay a subscription fee for PS and LR. I pay it because I know what I am paying for – I have subscribed once I reviewed the trial and decided the feature set is what I need. Now that I have subscribed, moved all my 200000 photos to your system, meticulously catalogued them and basically locked myself in to your products, you take away major features in an update release?

    How would you feel if you buy a shiny new Mercedes SL55 then 1 year down the line you take it in for its service, only to have it returned without the passenger seat – reason being cited is that it reduces maintenance by not having two seats. You would be furious!

  310. Keith Swalley says:

    I really do need to view and select my import destination folders. It appears that Lightroom defaults to the last parent folder used.
    Why is it even an issue not to leave the card auto eject?
    If I am using the “Add” feature, I am perfectly capable of selecting the correct folder and do not need the program to scan the whole drive.
    I cannot update until at least the first issue is restored.

  311. Ron says:

    Having worked as a software product manager for several Software firms including IBM your replies remind me of responses from my developers who felt that only they knew what was good for the end user. While some of the import functions may not be used as much or often as others they play an important role in many photographers workflows in certain situations and now when needed .. poof not there. The import move function may not get used that often as I only use the add function for my CF and SD cards but I use move quite a bit when moving photos from disparate Hard drives, CD, DVDS etc and trying to consolidate data or to cherry pick a particular photo from a device. You need to stop going down this road that you are going down to “make it simpler to use” . If you want to make a dummies version of Lightroom make it a separate Elements like product. You are alienating a huge population and you aren’t listening. Wake up.

  312. John French says:

    I am really worried. 3 or 4 days and over 400 negative comments from professionals since the apology on this blog alone, and still no word about when the import features will be put back. So many of the comments say the same thing: we paid for a product that did certain things, base our busy workflows around them, and you arbitrarily remove them!

    I am the last to want to “break someone’s bread bowl” but surely heads must roll at Adobe unless the apology becomes more than words and translates into action. I am not expecting the missing features to be put back tomorrow, I just want a categorical assurance that they will be put back, and sooner rather than later.

  313. Okay, you are sorry. So am I!!!!!! Now, I can be okay with the new layout although I do not like it and I can see where the totally new screen is easier for novice users but why make the rest of us suffer. As you gave us the ability to click the “Settings Gear” icon to see the rest, why not give us back all the prior functionality. Now, I have to eject each card manually, one at a time? Now I cannot select multiple cards? Now the prior keywords do not pop up during import mode? Are you guys really serious? Okay, add a new “Easy Import” – All of us will be okay with it as long as we do not have to use it and as long as you do not remove the powerful functionality that keeps all of us PAYING for this product.

  314. Patrick Anderson says:

    I’ve been a huge supporter of Lightroom since the first version, encouraging many photographers to see the beauty of the tool.

    However, now I am completely stunned by this “upgrade”. I hated going to the subscription model, but now when I lose functionality I’ve grown to rely on, I am really ticked off.

    I remember back when you said Lightroom was created by photographers for photographers. What happened here? Look at all these comments!

    According to CNET: “Adobe has made it clear it won’t step back from the simplified photo-import process. “Customers were universally unable to decipher the Import dialog without getting frustrated,” Sharad Mangalick, Adobe’s senior product manager for digital imaging, said in a blog post.”

    WHY dig in your heels when so many of us really treasure the product? Or what it was at least.

    If you must have a simple format, make that an option or a wizard or another basic product. Time to move past the apology and make it right for your customers.

  315. Jeff Hirsch says:

    Incredibly disappointed in the dumbing-down of the Import dialog in the latest release.

    While I understand the desire to appeal to a wider audience, please don’t punish experienced users by removing useful features in the name of “simplicity.”

    You can still keep things simple in a default view and have the more advanced options hidden behind the gear icon.

    Please bring back:
    Destination folder tree preview. (Very useful to see exactly where files will go.)
    Filename preview (Useful to see exactly how files will be named)
    Move option (useful for reorganizing an existing set of images into dated folders)
    Eject Card after import (very helpful when ingesting multiple cards)

    Stop trying to turn Lightroom into Picasa! (Scanning of all folders, for example).

    I am advising all of my students and clients to hold off on the latest update. Something I have NEVER had to do in the past.

    This is a downgrade in no uncertain terms. The new import “experience” punishes existing users in the hopes of luring in new ones. It feels more like a marketing decision than a software engineering one.

    So, pretty please, with sugar on top…give us back the basic functionality we have enjoyed for so long. You can keep your fancy new “Add Photos” dialog, just let the rest of us get back to work.

  316. Oleg says:

    Please give me advice to downgrade LR via Cloud to the old import feature. I’ve tried but I cannot work professionally without the Auto-Eject-Card feature. I have to handle up to five SD-Cards and I need to switch them fast. I have no time to eject the cards manually. But my notebook forces me to do so because I can only switch two or three times without the eject. Afterwards the notebook doesn’t accept a new SD-card and I have to restart the operating system.

    It is also very poor for my work that the 2-click-import is a 3- or 4-click-import now.

    I really need to downgrade to a stable release. Otherwise I need to look out for another solution.

  317. Dave says:

    After trying both the upgrade released on Monday and the following “upgrade” later in the week, I’ve gone back to the previous version of LR CC. Even the latest “upgrade” version crashes on what used to be straightforward operations — like opening a LR catalog from an external drive!

    The team has broken more than it fixed, or provided as enticements to upgrade. and I haven’t bothered to look at the new import feature; all the negative comments have dissuaded me. I was quite happy with the old way.

  318. Gianluca says:

    I miss the possibility to import from a source previously selected. I copy the photos from the card to the final position in the SSD and import into Lightroom from there. It’s a pain all the time to start from the root to navigate down tot he actual folder.
    Am I missing something? (I had not ime to read the +400 comments above…)
    Kind regards,

  319. Aaron says:

    The new import is garbage. I have worked with Lr since the first release in 2006. Ps since 1990. It is work to learn Lr well but if I can learn it anyone can. I am slooowww. The new system looks just like that silly useless simple interface style, like an Intuit (Quicken, Turbo Tax ets.) program. Bring the old system back as an advanced option. Just because new users have a learning curve does not mean old users should be punished by dumbing it all down. Unless new $$$ is Adobe’s only concern. They hold all the cards now since the introduction of Creative (Cash) Cloud. Check marks covering the image I need to see to add or remove is beyond clueless. Also I do not want to look at a background photo in the first import screen. I am trying to focus on my own asset images when working on an import not any other work. I could go on. Capture One may be my new .raw manager if Adobe digs in their heels. I would cut loose Ps but I am stuck with it.

  320. David Nissen says:

    1. Bring back the destination tree.
    2. Get rid of the horrid check marks.
    3. Is the “Synchronize” fixed. I had to reimport my whole image collection.
    4. In fact, let the user revert to the 6.1 import dialog.

  321. David Nissen says:

    What an opportunity for Capture One, which is a significantly better raw converter. If Adobe screws up LR as a DAM, who needs it?

  322. Ed Chatlos says:

    UPDATE 10/12/2015

    That Update you speak of coming this week better have the original Import dialog window or I for one will be cancelling my subscription plan.

    You and your TEAM (Bunch of idiots if you ask me) made a BONE Headed error thinking you could try to change the way images are imported to the LR catalog and removing some KEY features along with it.

    And who’s the person that came up with the idea to place a LARGE check mark in the center of the image?
    They should be Let Go.

    I can’t believe you had testers like Jeff Schewe that told you this new import dialog window would never fly and You & Your TEAM went ahead with it anyway.

  323. Well, I am glad I was out of town teaching a workshop last week and teaching the old lightroom ways. From what I see right now I hope my CC subscription isn’t coming to an end. I don’t want a cute user interface I want one that works and one that flows (over 180,000 photos in my main catalog).

    I will be waiting for the update that un does the update, or at least give us a prefrence setting
    ___ cute light room
    ___ Professional Lightroom

    Who know maybe we would grow to love the cute Lightroom if we could turn if off when needed.

    Thank you for listening
    Joe Cosentino

  324. Guy says:

    “Update October 12, 2015: With 432 comments and counting I just wanted to let folks know that I’m reading all of the feedback and the team will provide an update this week.”

    Personally, I hope we’re going to hear that all functions will be restored and a guarantee that they will remain part of the software. Some simpleton in marketing disregarded and disrespected the customer base as a whole and those professional photographers and their customers who rely on Lightroom in particular. Anything short of that will certainly cause me to abandon Adobe in the same way they have abandoned so many of their customers.

  325. Mark Chernis says:

    Scratching my head on this update guys… I can understand the bugs–software is complicated and bugs happen. But, I really can’t understand the thinking behind removing the features you did or bolting on an entirely different looking and feeling interface to an otherwise polished and coherent product. Is this the result of a new leader or a new team? Should I expect years of half baked interface changes and feature subtractions ahead?

    Please, accept this was a bad experiment and just put it back the way it was. Still time to make this right. Or, would you like to lose most of your installed base like MS did with Windows 8?

    Mark

  326. Dean Holland says:

    I must agree with Tom that changes were desperately needed to the import process; the dialogue was far too confusing for new users. But the designers have chosen the wrong type of simplicity – hiding the complex stuff instead of clarifying it.
    Importing and organising IS complex with a choice of file formats, locations, backup locations, when to eject and how to format etc. and no single right way to do it for everyone. The old dialogue smacked new users with having to learn half of a DAM process before they could understand what each option could possibly be FOR, let alone make good choices in the dialogue. The dialogue needs to explain and CLARIFY this unavoidable complexity, so that each user can do it they way they want. Taking away clear, easy-to-understand choices like “move” and “eject” makes it harder for experienced and new users alike, not simpler.
    Trainers have a saying that there’s a cheap simplicity on the “near” side of complexity, and a very different simplicity on the “far” side of complexity. It’s the one of the far side that we want! I’m hoping the team get the right simplicity to let everyone import how they want, and also expand the LR user base – that will benefit us all.

  327. Over the last several years, I’ve been teaching hundreds of students Lightroom through community colleges camera stores, and other venues. I have not found one student who couldn’t understand the import dialog box. In fact, many of them have used options no longer available, like the move tool to transform the mess of their file collection, into an orderly folder structure by being able to see where their files will land after import in the directory tree. But that is no more, since you removed this feature, and a few others.

    The new import dialog box looks like something designed by Fisher-Price. And what’s the story with the checkmarks on the photos? Does that mean you like that or you don’t? It’s not obvious, clearly a design flaw.

    The problem lies not with the import dialog box, which is been around for the last eight years, but in Adobe’s inability to clearly convey how to use their products. The previous import was clear: where are the images, what you want to do with them, where should it go? It couldn’t be more clear. Anybody who doesn’t understand this basic concept is not ready to import their images into Lightroom. If you want to dumb down the program, then come out with an Adobe Lightroom Elements.. You cannibalized a program that professionals depend on with the intention of taking a shortcut toward increasing your market share at the expense of those of us that have supported and promoted your program for years and years.

    I was so excited with Lightroom, that I even made my own Lightroom baseball hat. With what you’ve changed and how you’ve changed it without soliciting imput is an embarrassment and makes me ashamed to be associated with the program. As others have said, they subscribed to the creative cloud program expecting one program with certain features, only to have it mauled in a dark alley by the developers and marketing staff.

    It’s experiences like this that discourage me from recommending my students convert their files to the DNG format, and also encourages them to write changes to XMP sidecar files, so that if Adobe to kneecap us, it will be easier to migrate to another program.

    We aren’t asking for anything new: just for you to honor peoples’ request to restore what was previously in the program, and not blindside us for the sake of your profit.

    Reid J. Thaler
    http://www.lumiograph.com

  328. J. Braun says:

    Sirs:

    Please return the import process to the original form. If you wish to provide a simplified process, please allow the user to choose alternatives. Thank you.

    JB

  329. Tim smith says:

    The piling on Tom is unfortunate but incorrect electronic feedback morphing into LR changes were made
    at the expense of Adobe LR customer base. I would be very surprised if Adobe does not
    do the right thing considering what is at stake.

    As a side note and not a cheap shot but is anybody at Adobe a photographer ?

  330. Tina Manley says:

    I have got jobs pending that I cannot do without LR. If you don’t fix it by tomorrow, I will be migrating everything to another program so I can get my work done!! I can’t even get LR to open now. I’m up late working and extremely frustrated. I hope you are, too!

  331. Tim kwong says:

    Please don’t copy everything Apple does. They get by because they have hardware. You are a software company mainly for professional. You can’t sell subscriptions to consumers because they will use other free options.

    Focus on professional and build consumer software separately. Without us, you guys are nothing.

  332. Tim kwong says:

    If anyone finds the original import too difficult, they sure can’t use the rest of the program. How changing the import function alone would bring in new customers? It is a solution looking for problem. Make the program runs faster and more people will come

  333. Anna McCullough says:

    Let me add my voice to the above; I’ve been a LR user for a number of years. I use auto eject all the time, I LOVE “Move” as a feature, and I hate that “dehaze” is left out of my user experience simply because I’m not buying into the Creative Cloud kool-aid. I’ve started looking at other software (Zoner Photo Studio is looking halfway decent, as is ACDSee). I don’t mind a simpler interface as long as the fully featured one remains available, but if it doesn’t… Bye-bye LR.

  334. Brian Smith says:

    I am definitely not a fan of the new import interface. Its clunky, confusing, and lacks options. Hopefully this will be fixed.

  335. George Jolly says:

    The subscription plan says we get access to previous versions. As far as I can tell, the CC installer only offers the latest CC version and version 5. Version 5 had a different catalog format, we cannot just switch to it in the middle of working. If the installer gave us easy access to revert to any previous CC version, people could rescue their businesses by reverting to 6.1 while you work on our feedback.

  336. Nick Pudar says:

    I have been very busy lately and have been procrastinating upgrading from 6.1 to 6.2. Wow, am I fortunate not losing the Import features that I use all the time!
    I’ve been a loyal Lightroom and Photoshop user since the beginning of LR and the early days of PS, paying for upgrades, and putting up with the quality issues — but always confident that Adobe would eventually get it right. This last move has eroded a lot of brand equity.

  337. Jim says:

    This is not an update! It is a downgrade. The “new” import dialogue has me totally trying to rethink my workflow with less than optimal results. This was just the sort of thing I worried about with the move to the “CC” model. My worst fears have been realized. My trust has been violated. I the next few days/weeks i will assess my continued use of this product and consider moving to alternates…… what you have done is unacceptable! When I leave I will not be back!

  338. Sean says:

    Is this push to simplify the import interface coming from a desire to attract consumers? The previous import UI was quite simple to use even if it wasn’t exactly pretty. Over the years, since the beta, I’ve noticed fluff features enter the software such as Books, Slideshow, Maps, Web which must have eaten up quite a bit of programming resources when professionals (I’ve run 600k+ images though LR) care about speed, tools and speed. Doesn’t LR report that these fluff features go unused? I personally spend 70% in Dev and 30% in Lib and 0% anywhere else. I have a 4790k quad CPU at almost 5GHz with a 4k monitor and LR is pretty unusable in the Develop module and, no, enabling my 280X GPU makes everything *worse*. It surprises me when new features/refinements are rolled out that completely do nothing for my workflow in a pro-focused app. Time is money and I’m spending a lot of money looking at a “Loading…” sign.

  339. Smitty says:

    Yeah the new import dialog screen is atrocious. This is what happens when companies blindly follow metrics without knowing the stories behind the metrics. Also personally, I used auto-eject all the time (mac and PC) and often used move functionality, all very useful.

    Amazingly, even from an interface design perspective, the import screen is a total failure.

    Look at the interface during import, and then look at the REST of Lightroom! All the team did was disorient the users of Lightroom (new AND old) by making an interface totally foreign to the rest of the program!
    Users are presented with nice left columns of file trees in the Library module, but during import all of that disappears. Wow.

    Thankfully I’ve found the instructions to roll back to 6.1.1 Now I get to go through that joy and then reinstall all my plugins.

  340. I have been developing software for almost 35 years.
    I’ve made my mistakes. Been bashed about the head for them.
    It’s unavoidable.
    Yes, LR is complicated to use for beginners, but it’s a great tool once you understood it.
    So removing those “power functions” from LR is obviously a step in the wrong direction.
    Go back, rethink your decision. Do you real want to head into the direction of a consumer product for “point and shoot photographers”? I guess not. And I think these guys will go with easier (and cheaper) programs anyway.
    All in all: Please stick to “LR is for photographers” — keep it the power tool it can be.

  341. Dear Adobe
    Can you please concentrate on the things that don’t work properly in Lightroom rather than fixing the things that aren’t broken. Seem logical?

    PS I can send you a list if you need it.

  342. “Our customers, educators and research team have been clear on this topic: The import experience in Lightroom is daunting”.
    Only if you are a F**king idiot with no clue about computers. However is this is your target market now , heaven help us..

  343. chris ogden says:

    Since you’re reading all these Tom (thanks!), I’ll throw in my two cents in support of POWER USER FUNCTIONALITY.

    I’ve been using Macintosh since serial number 676 in 1984. And despite my Mac-bias, I bagged Aperture and I’ve been using Lightroom since the Antarctica release party in 2007. I’ve taught/trained a hundreds+ people on using LR.

    Since you deprecated the awesome feature of “local” collection select status (in favor of “making it easier” to understand the program), the slide toward “Ease of Use” (which all to often ends up being simplification and ultimately “you can’t do xyz / anymore”) is disturbing.

    As an ex-software developer/exec, I understand challenge of maintaining too many customization features over time. The seemingly easy answer is to “just make the old feature/function a preference” (that old/power users can turn on/off). But doing regression testing on n-options can snowball and make code maintenance difficult.

    And, I understand you want to continue to grow your user base, and allow new users to come up to speed quickly/easily. HOWEVER, as they learn to use the program, and become more sophisticated users, confining them (and by definition your loyal base of “power users”) to a simplistic interface/set of options is very poor.

    Similarly, “taking away” functions, especially power user functions, causes harm to your loyal users, because it interrupts and sometimes destroys established workflows, for individuals and across teams. Do no harm!

    That’s the essence of a position held by me and many of my colleagues.

    Thanks for asking/listening,
    -c

    PS. Since you’re reading these, how about another request for enhanced Metadata filters in grid view. Not giving access to key EXIF data such as Exposure Bias is very frustrating. MANY photographers exposure bracket routinely now. Having to do kludgey hacks to hide all but one of an exposure bracket series is a continual frustration, on EVERY shoot. It would be such a simple addition, and provide solid returns (and no, your metric software can’t track such a thing, because one has to go to plugins or external editors to work around it).

  344. Tom
    As a professional Lightroom trainer and author, I’d like to suggest that you reach out to those of us who work directly with those learning and using Lightroom. After 7 years of teaching LR, I can safely say taht I know what my 1000’s of students and clients want and need. Every day we trainer see (and hear) the frustrations of working “in the trenches” with real users.

    I would also suggest focusing on the new features that users have been requesting since version 1 that have still not been added, rather than taking away features that we use every day. Just because the members of your team don’t use certain feature, that does not imply we don’t.

    I would also highly recommend the accelerated development of the Lightroom Elements project so professional features can be added to the current versions while simplifying the Elements version. Everyone wins.

    Again, you have an incredible collection of professionals who would love to work with your team to provide real-world feedback, ideas and new feature requests (preferably before the code is written, rather than after.) Please take advantage of those of us who have more than just personal experience using Lightroom.

    Tom, feel free to contact me personally to further this conversation.
    David Vanderlip

    • Ian Yorke says:

      I would have expected Adobe to be in contact with someone like yourself as a matter of course.
      Fully agree with the separate Elements LR idea if that is what they are trying to turn the existing LR into, which is what it looks like.
      Ian

    • Pauline Tims says:

      I hope Adobe is reading these comments and will soon listen to us and reinstate the features we have taken the time to learn .

  345. Al says:

    The worst software update I have ever seen in 30 years.
    This 6.2.1 doesn’t fix anything, after 3 minutes of spinning ball I had to kill LR.
    I installed back 6.1.

  346. Oliver Knoll says:

    Hi there,
    Could we have the “move” import option back, please? The “Eject SD-Card” functionality was also very much appreciated.

    Thanks, Oliver
    (hobby photographer)

  347. Axel says:

    “Update October 12, 2015: With 432 comments and counting I just wanted to let folks know that I’m reading all of the feedback and the team will provide an update this week.” …

    … thanks for the update! I gather it’s understandable that just the (laudable) apology alone w/o any actual announcements how to improve the new import screen for existing/advanced users was not enough. The previous clarification that there’s no going back, period, didn’t improve things either :-p

    Sorry you had to get sh*tstorm’ed as accidents do happen. But imho it’s necessary to make Adobe recognize that relying on biased telemetry or just one profitable focus group isn’t the way to go. The whole CC suite profits from the “pro appeal”, and amateurs use it because pros do – even though there are less complicated and less expensive alternatives out there that are more adequate for sorting baby shots or auto-toning odd selfies.

    • OH and if the team is looking for a bit of LR that needs improving.; What about the Book module.. It’s truly horrible. What about drag n drop? There are a whole raft of improvements that could be made to every area of LR to make it better and easier to use.

      I’d be very happy to help

  348. Patrick says:

    I am still puzzled who on earth would think to get away with such an unmotivated and unnecessary feature removal from a pro tool with the reasoning to comfort first time users by massively dumbing down the media ingest. And, to add insult to injury, pack it up in a known buggy update which leaves the already shocked user base exposed to crashing bugs at no end. Wow, way to go Adobe… you better learn from the experience!

  349. Raymond says:

    I understand one wants to simplify certain things in order to lure new customers. That’s okay. As a professional photographer and cameraman I understand this process. However, this process crosses a line when old, trusted and faithful customers feel betrayed and misunderstood.

    Give us back our import screen. It was logical, it was thorough and it was clear after studying it for a couple of minutes. Yes it could be overwhelming, yes I understand your need to dumb down, but no…. you crossed that line. We, faithful customers, feel misunderstood and betrayed.

    If you want this software to be a professional solution, than act like it is a professional piece of software. Dumb down where dumbing down is needed, smarten up where it is needed. And ooh, don’t forget, keep your hand of those parts that where clear but maybe a bit overwhelming.

    And if you do change those bits, first test it with a Beta-version or give professionals the change to click on a advanced option that keeps all those much needed options.

    So, dear Adobe, thanks for the apology, now it’s time to get back to work and reinstate that old import screen. I don’t care about a stupid bug, these happen and the service folk at adobe helped me get back on track within ten minutes. So, really, no time lost.

    But stop wasting our time, and yours on a botched import screen that will make customers look out for other options!!!! (Hello Capture One!!!!)

  350. Steffen says:

    Dear Tom Hogarty and team,
    I’m also floored by Adobe’s arrogant attitude. I left my parents’ home some time ago and typically don’t need someone telling me what I need or not. Especially, since the only thing that REALLY NEEDS YOUR ATTENTION SHOULD BE SPEEDING UP the lame performance of Lightroom. Scrolling through the library feels like computer animation of the 1990s – even the entry level Photos app made by Apple (and I’m sure your looking down at such amateurish piece of software) is BLAZING fast by comparison. GO BACK DO YOUR HOMEWORK, STOP TREATING YOUR PAYING CUSTOMERS AS THOUGH THEY WERE KIDS WHO DON’T KNOW WHAT THEY NEED.
    Cheers!

  351. One more question:
    Is it true that copying as DNG is no longer supported?
    Why would that be? I’ve build my whole library on DNG! Did I make a mistake trusting in you to keep supporting your format?
    This means I will have to add one manual step?
    One some days I import several thousand Images in one go. Works ok in LRCC6.1 — will it keep working in 6.2?
    Getting disappointed…

    • Ed Chatlos says:

      There is no more Copy AS DNG. There is an option to Convert TO DNG. I haven’t tried it so I don’t know for sure IF it makes just DNG files or Copies the originals and then Converts those to DNG making 2 files instead of only one as it did with Copy AS DNG.

    • Axel says:

      For once 🙂 this is not a bug, but really a feature: Starting with LR6 the import as native raw renders previews much quicker, and the conversion to dng is done in the background afterwards. There might be some cases where you’d rather “copy AS dng” because it doesn’t read/write raw->dng on the same hd, but that’s probably low usage :->

      CC Adobe: Now you’ve done it, when in doubt even useful changes are suspected to be total screw-ups :-\

      • Thanks for the feedback.
        I admit to having mixed it up (but I really was afraid that even this wasn’t considered “normal” anymore…)

        • Axel says:

          I just looked again and it really seems they’ve only changed the “copy as dng” method to a “convert to dng” checkbox. But your fear might be well founded, and this feature might be next on the removal list (esp. as you can convert later on in any case)!

          To check, sit your granny in front of LR and ask her to import some shots taken from her emergency mobile phone.Is she confused even by the new 6.2 import screen? Well, there you are, it’s probably due to the superfluous “convert to dng” option 🙂

          • This reminds me a bit of the DDOS attack flickr organized by themselves when they released their “auto-uploader” (including the nonsensical auto-tagger) that uploaded ALL IMAGES from the local machine (which resulted in a break down of the flickr Server farm).
            They thought they should make it “as easy as possible” as well.
            I left flickr then and switched to smugmug (and their wonderful lightroom plugin).

            Btw.: flickr has decided to go back to having paying customers again… obviously all those mobile phone user just use up space but creat no added value. Who would have guessed 😉

  352. Frank says:

    “At the same time we removed some of our very low usage features to further reduce complexity and improve quality.”
    Why do you think the features you removed aren’t used? I used the directory-tree every day. I need to see the destination and I also need to deselect some folders before import – not dozens of single images one by one to prevent them from being imported in that session.
    Furthermore you reduced quality and improved complexity in the workflow, not vice versa.
    If your goal for the future is simplicity over professional usability (visiting new users at home instead of present users at work), please communicate that clearly. Then I wont waste any more time on Lightroom and look for alternatives. I have been a happy user since version 1.0, but the current evolution is very disappointing!

  353. Steve Goodwin says:

    Reference your update of October 12. There are an awful (operative word) lot more comments over at http://feedback.photoshop.com/photoshop_family/topics/new-update-6-2?page=1. Please roll this downgrade back asap.

    • David Martin says:

      Yes indeed. 659 comments and counting. Tom Hogarty needs to keep up with the complaints. And there are other forums, not to mention the other two (2) threads under Adobe Lightroom Journal. My count is over 2,000. And what will any marketing guy tell you? For every person who takes the time to complain, nine others do not. So Adobe has over 200,000 people who are NOT pleased.

  354. Emile says:

    Thanks for the apology, Tom.

    I won’t rehash all the arguments and I’ve made some myself in the initial post that explained why Adobe felt it had to change the import dialog, but I do hope swift action follows. Looking forward to it!

  355. Modes says:

    I’m sure this point has been made in the previous comments but just in case it hasn’t…

    When you chose to look down on Lr6 users by not giving them things like dehaze or local black/white sliders your excuse was that we bought an standalone product so we would not get new features, just bug fixes and new camera support…

    So…you won’t give Lr6 users new features but you WILL take from them existing ones?! How do you justify that double thinking?!

  356. David says:

    Hi Tom

    Thanks for the note that you and the your team will get back to us later this week. Fully agree with all the comments above how removing features from LR is the wrong way to go, how getting real world input from experienced LR users would help in the future before major changes are made, and how Adobe should review there QC process to find software bugs before releasing updates. Hope Adobe listens to the comments and suggestions on this blog, learns from this, and works with the user community to fix the things in LR that need to be fixed, since at the end of the day we all want the best for LR.

    Regards

    David

  357. David says:

    Hi Tom

    One other thing I forgot to mention was that the recent update and removal of important features suggests Adobe is going in the direction of “dumbing down” LR with the goal of making it more consumer friendly. This is a concerning direction Adobe appears to be heading with LR. If you need to make a more consumer-friendly version, please consider either keeping the advanced settings for professional users in hidden panels (but allow customization in the preferences settings) or make a LR-elements version (like what is done with Photoshop. Please don’t make LR into a simplified “tablet-like” photo-editing software, but keep it the professional photo editing software that it should be.

    Regards

    David

    • Axel says:

      *Knock on wood* … but it probably takes more than some blog replies to make Adobe re-think their strategy.

      Just the other day they commented on LR 6.2 that the new direction is targeted at “people passionate about photography and who use their cameras as a creative outlet”, i.e. are not able to deal with a complex software interface. If Adobe isn’t ready to create a LR Elements, then by default the opinion of existing customers is meaningless vs. the huge bulk of the unexplored photography amateur market.

      Will existing customers with long LR experience and catalogs really take the large hassle and jump to another software even if they’re annoyed? No. But will Adobe gain much more $$$ by selling more subscriptions, gaining the management more success bonuses? Yes. There you go.

      • John says:

        Axel,
        The statement “people passionate about photography and who use their cameras as a creative outlet” should maybe read ‘social networking children who want to push one button to be passionate and creative”.

        I’ve been in this industry going on 35 years and currently do first level product testing and support for imaging plugins. A good part of my ‘support’ is telling people how to use Lightroom at it’s most basic functionality and even then most just don’t get it or actually just don’t want to take the time to learn the basics of an imaging workflow.

        The social networking children communicate in broken sentences and become extremely confused if they see more than 1 or 2 sliders or buttons on a screen. They know little about the basics of photography and use Lightroom to ‘fix’ their lack of knowledge or to run plugins or presets that make them look like they know what they’re doing.

        That, I think, is the kicker. Adobe has realized that the social networking children are a huge market and will start catering more and more to them….just look at the so called editing apps for phones and tablets that have miniscule control and no realistic workflow that have surfaced in the last few years. The children jump all over these things because they’re simple and so Adobe decides to ‘make it simple’ on the one side and
        ‘kill a pro workflow’ on the other. Does this possibly mean that the actual real working pro is becoming a thing of the past to be replaced by children with no skills that rely simply on technology?? So maybe the children of this industry is where Adobe pulled its analytics from because as you can see from the above, it sure wasn’t us ‘old’ guys/gals.
        =John

        • Axel says:

          Actually I hope you’re correct with your analysis and Adobe will agree once they’ve dug out of their heap of biased telemetry.

          If LR for the new generation :-> isn’t compatible with an old-school LR for people who are willing to learn the app, then Adobe has no choice but to create a “LR Elements”. That means stopping dumbing down and stuffing all possible “big” features like hdr/pano/mobile/… into LR, they can concentrate to improve what LR was designed for in the first place.

          Imagine what the “core” LR would have benefited by dev time would have been focused into implementing “little” requests by the existing users…

  358. John Clark says:

    I echo the vast majority’s sentiments – reintroduce AUTO EJECT, please!

  359. Thierry says:

    I do not want to be unconstructive but frankly I am scratching my head wondering about the added value of this update if any. All and I mean all features of the former import module were useful to me. In addition getting a bit old, I am reluctant ton consider change for the sake of change. Admittedly this may be idiosyncratic 😉

  360. Ron Lawrence says:

    This is the culmination of what we, the naysayers of the subscription method, feared would happen. We stated that Adobe would no longer feel the necessity to get things right. They don’t need to! We sit here frustrated about things that we use, things that we are used to, that are now broken, or completely removed, yet….Adobe keeps drafting our credit cards, no matter how bad it gets. Where do we go for a refund until LR gets fixed?

  361. Kenyon says:

    Ejection features are the least of my worries…since I can’t even get to the import dialog to start the process. After the update to the update, LR crashes on opening. I just flew from my LA studio to Sydney bringing a great deal of work with me to finish while here. As of the update LR crashes on start-up. I have read all the workarounds which require one to access the preferences menu which, of course, you can’t do unless you can get the program to stay open a few seconds which isn’t happening at the moment. A request for help over at the Adobe forum elicited a response basically to un-install the program, un-install all of my Adobe programs and related material…reload the updated version of LR, spend the better part of the next week getting all the plugins, presets export programs etc. that I had attached to LR and my other Adobe programs working since I joined the “Creative Cloud” at the beginning and hope it then works. This is NOT a useful solution. Please devise a patch that we who are non-programmers can use to roll the program back to 6.0 or 6.1. I love Adobe and the Cloud but this is inexcusable and I am basically dead in the water until there is another update to fix the update of the update. 🙂 All kidding aside, please rectify this ASAP. Thanks 🙂

  362. Tim says:

    I can´t understand why they killed a feature (autoeject) – it doesn´t cost any money but really saves time for pro users.

    On a work day I import photos 10-20 times a day into lightroom and have to return as fast as possible to shooting. This feature is (was) excellent…

  363. Gary says:

    Where’s the apology for the patch? You’ve moved the crash to the exit instead of the launch (slow hand clap), but now the import takes the exposure slider all the way to the left, and the actual exposure loss is worse than appears as sliding exposure back does not bring the picture back. LR is dead in the water. When are you fixing the fix? I’ll go ahead and save time and ask now when you’ll fix the fix of the fix.

    • David Martin says:

      That’s correct! The so-called patch was a horrific failure. Nothing has been patched. I had to uninstall 6.2.1 and reinstall 6.1 and then patch that with the 6.1.1 patch. And everything I imported while in 6.2.1—albeit, thank the gods, not much—had to be deleted and re-imported because they were black images.
      Quite possibly the worst point upgrade in the history of upgrades.

  364. Daniel Sroka says:

    I’m a professional photographer, and been working with Lightroom since the beginning as both alpha and beta tester. While I appreciate the intention to make the import process simpler, I believe that a couple decisions has had the opposite result, making it more confusing and difficult to use.

    (1) the remove of the option to eject media after import:
    Proper practice is to safely eject any media before removing it from the card reader. When you are doing a photoshoot, you end up ejecting the card dozens of times a day. When the option existed to have LR eject the card, you could do this process quickly and safely. But now, you need to remember to switch to the Finder and manually eject the card after each import, or face the OS warning that you did not eject the card properly. I am not sure why this option was considered too complicated for new users, since it actually helps them work more safely with their media.

    (2) Dimming/obscuring thumbnails of images to be imported:
    The new design obscures the preview thumbnails of the images you have selected to import by dimming them and partially covering them with a large checkmark. First, this is contrary to the UI cues used in the Library, were a dimmed image mean is is rejected. Second, this means you have no way of visually confirming if these photos are the ones you want to import or not unless you counterintuitively unselect it for import and move your mouse away.

  365. Martin says:

    I stick to some of the other comments up there: Offer both import dialogues like “easy” and “advanced” or whatever names. Like that you really offer your professional users the quality they liked and worked with for years now!

  366. oingh ing says:

    Tom, I really hope that you are reading all this complaints. If there was anything daunting in Lr it’s the speed but not the import. I really hop that you bring back the old dialog.
    Or is this just the first step in redesigning the whole LR interface? Why should there be a develop-module necessary as there are quick adjustments? Simply kill the dev-module with all it’s daunting little sliders I don’t know how to use right…

  367. John says:

    I doubt anyone at Adobe is still reading – and this has nothing to do with the most recent releases..
    But I’m still annoyed that LR 6 forces the catalog backup to be zipped! I use a plugin called “TPG LR Backup” which is now fairly useless. The nice thing about that plugin though is that it would zip the catalog in the background, while still being able to work in LR. Now I have to wait, not able to use LR while the catalog is zipped. I have a disability in which I exit solely to backup the catalog very frequently, because I don’t want to lose any changes I’ve made. Of course I write the changes to XMP also, but it still takes a lot of time to backup the catalog – which includes things that writing out XMP doesn’t. Unfortunately the author of TPG LR Backup doesn’t seem to be updating his addon to at least allow for a uniform backup name in a specified single directory.

    Hopefully someone is still reading these and can make this change in a future release – perhaps an option of whether or not to zip the catalog is in order here.

    Many thanks if someone is still reading these.

  368. tim says:

    Please, please return to the previous import mechanism.

  369. Run Mac OS Yosemite and I have to force quite EVERY TIME I close the app, I also agree on the eject after import feature need to come back. But First fix FORCE QUITE ISSUE.

  370. Martin de la Herran says:

    This move is a big misake, really….
    Adobe, I usually love you. LR is my software of choice for my catalog of over 130K pictures, and I’ve been using you since LR2.
    Let me tell you something – there is one thing that your telemetry tool is probably very bad at: I set up MY preferred configuration, and then change it seldomly. That I do not click buttons does not mean that I do not use them…for example, I check the destination folders EVERY TIME I do an Import. I check the destination filename, and although I do not change it… I make sure that everything is all right….
    I won’t repeat again what everybody is already saying, only…

    WE ARE YOUR POWER USERS, AND YOUR MAIN RECOMMENDATORS (to our friends, family, etc…). WE HAVE NOT ASKED FOR THIS!
    Add an easy mode if you will, but don’t treat us for dummies, please.

    I hate to say, but these actions just add myself to the pool of people starting to check other software makers software….

  371. Erik says:

    I don’t know where and how to begin without being sarcastic… but are you totally oblivious to the needs of the pro users and I dare to say 99% of the amateur photographers? Do you care even a tiny bit? You should really bring back the old import dialog, because there was no problem with it. LR (or each software of this kind) is not ment for people who are not willing to spend at least 5 minutes learning how to use an import dialog and everybody with an average IQ needs less than that. It’s not that difficult and it was not that difficult. There is a saying of Einstein “Everything Should Be Made as Simple as Possible, But Not Simpler” Your change was the latter. I hope you care for your customers because the customers are the kings. They pay you, they pay adobe. You could at least implement an option for the old dialog, which 99,9999% prefer and the new one (for folks without a brain… but ey, what will they do after the import … LR is to complex for them…)

    erik

  372. Having downloaded and installed the update to fix the error that is Lightroom 6.2 I still find the import process buggy. Also commenting in the library module only works 50% of the time and the whole program is running very slow. Please up date the update and fix all these problems. Roll it back to how thing where in LR 6.1 as I’m yet to see any pluses in LR 6.2

  373. Rory says:

    Glad to hear you are reading all the comments Tom. Must be a daunting experience. I have found your/adobe response to this debacle to be most interesting.

    On the one hand there is some evidence that you are listening in the responses that you and Sharad published here and your statement that there will be another release later this week, although I am still waiting to hear you say that all the import functionality will be reinstated. Why are you being coy about this?

    On the other hand, actions speak louder than words and we have endured a number of negative actions like botched releases, removal of functionality, poor reliability, poor performance, poor design decisions, inconsistent UI elements, modest amount of enhancements and failure to address long requested shortcomings in the program.

    If you are truly going back to the drawing board I am encouraged, but it is going to take a lot of action to get me to the point where I can recommend lightroom to others. I wonder how many new lightroom customers come from the advice of existing users?

  374. While we are on the subject of slow and buggy.. How about fixing the stuff that doesn’t work before you go on to break the stuff that does..
    http://petapixel.com/2015/10/13/lightroom-import-is-600-slower-than-competition/

  375. Johan says:

    Interface design by Adobe: you get a bunch of thumbnails, but you can’t recognize the images because they are dimmed and covered by a huge checkmark. Those are the images that will be imported. You want to know what those images are? Uncheck them, so you can properly see them. But wait, doesn’t unchecking mean they will NOT be imported? Yes indeed, so after you’ve looked at the unchecked images, you have to check them again so they will be imported. That’s how we make Lightroom easier to understand for newbies…

  376. Timothy Spear says:

    Tom,

    The apology is a very good start. I have stopped learning Capture One, and renewed my CC Photography plan and will give you a few months to come through on your statements.

    In terms of the import screen, the original justification given for the rewrite was that new users could not use it. The way it was stated, very much lent itself to a consideration that you only were concerned about the selfie crowd Apple has chased with the new Photos app which even decides if you want whole or skim milk with the image (just a little bit of an exaggeration). It was this attitude more then anything else which made me cancel and start looking at Capture One.

    The original import screen was designed by a engineer; not by a UI specialist. As such, it was ripe for a significant overhaul. I commend you for trying to go in that direction; but I will say the removal of features and the way the downgrade of functionality was handled was about the worst I have ever seen from Adobe, or any software company for that matter.
    Hopefully, you guys will restore the functionality, fix the massive bugs, re-learn what beta-testing means, and learn that the phrase “lies, damn lies and statistics” applies to the metrics you have gathered. I along with many of the more sophisticated users, which seem your target market, have always disabled such data gathering programs.

    Tim

  377. Jim Elliott says:

    Thank you for the apology. Yes, it was sloppy work. Please bring back the old import module. It worked fine. The new one does not work well with any workflow.

  378. KC says:

    Lightroom’s Import is 600% Slower Than Competition

    Adobe has already apologized for fumbling its latest Lightroom update, which was riddled with bugs and missing features. Now there’s a new story that’s putting a stain on Adobe’s image: a new test has found that the latest Lightroom is about 600% slower than its competitors.

    Jim Harmer of Improve Photography writes that Lightroom now has “dramatically poorer performance” when compared to alternatives out there such as Capture One, Photo Mechanic, and Apple’s new Photos app.

    “My question is if I should be looking at alternatives to Lightroom to improve the culling process, which has progressively gotten slower with each version of Lightroom over the last 18 months,” Harmer writes.

    To test Lightroom’s performance, Harmer took 97 RAW photos shot with a Fuji X-T1 and imported the photos (on his hard drive) into each program. Here’s a chart showing how long each program took (the longer the bar, the slower the performance):

    Apple Photos was by far the fastest: the full import too just 9 seconds. Photo Mechanic wasn’t far behind, clocking in at 12 seconds. Capture One was slower, taking 27 seconds to bring in the photos and 114 seconds to build full previews. Finally, Lightroom took 190 seconds just to bring in the photos, and a whopping 685 seconds to build full previews.

    **********************

    WOW!!!

  379. Stephen says:

    Please give me back the old import dialog – I moved to Lightroom because Apple abandoned Aperture, I would rather not move again but changes like this are making me look at alternatives again.

  380. Andrej Korenc says:

    This speed issue is just … unbelievable … JUST FIX IT!

  381. bob says:

    Adobe said:
    quote To all the disappointed perpetual users, you’re getting the same level of update support in previous versions of Lightroom, which is ongoing lens and camera support. If you weren’t aware of why new features can’t be added to perpetual software, it’s because the US Government has made ‘it illegal for a vendor to add unadvertised features to software that has already been paid for through the Sarbanes-Oxley act’ as noted by Micah Burke in the Lightroom Journal comments. If you want this changed and you’re a US citizen, then start lobbying your politicians. While people will use this a vehicle to imply greed on the part of Adobe, it’s simply Adobe complying with a law they have no say over. It doesn’t apply to the subscription model because you’re renting the software. /quote

    Adobe if you want to think this ‘new’ interface is a change in a feature and not a new one, you are deluded. You called the old interface “daunting.” If the interface it not daunting, it’s new.

    Why is dehaze not a feature change in clarity?

    If that is true, then why did you give the perpetual license users the ‘new’ interface?

    • David White says:

      +1
      It is now quite clear that the SOX talk was just a way to hide Adobe marketing push to get more $ from all the beta testers – oops I mean CC customers. The change to Import proves it even more than the dehaze presets and plugin for Lr 6.

  382. dan says:

    It pleasant that you’ve already apologized but seriously whose driving the car here? Major changes (that don’t work well) and majorly change your work flow with ZERO warning? Who does that? I’m a working photographer slammed in my busiest season ever and I come to the office to quickly upload my images…and What? I don’t know how to anymore! My product is completely different and I don’t know where any of my import items are.
    Add to that, the start up process was glacial. SERIOUSLY, give someone a heads up when you’re going to redesign the workflow. By the way, I hate the new import simplification. I took the time to learn the old way and clearly you’ve dumbed it down for cell phone users. I made the mistake of thinking this was a photographer’s/artist software and not for the cute selfie taking crowd.

  383. Tobias says:

    Hey,
    just wanted to say that I noticed this blog post by accident and find it very pleasing to know that you as the developers care about us users and I am glad that I am paying money for using your top of the line product.
    That said, thinking about it, I answered several Adobe surveys all about pricing, etc. Nothing about in depth usage of particular products. Like what do the users really care about, what works well, what could be better. Maybe do surveys about Lightroom. Or have a usage reporting thingie in lightroom users can opt-in to, just like mozilla has it.
    All the best
    Tobias

  384. Tobias says:

    Oh and btw, just give us back the old import dialog. I’m using Lightroom as a professional tool, my grandma doesn’t need to be able to use it. Dumbing it down kills usablity and established workflows.

  385. Lightroom has become unusable even with this bug fix. I depend on Lightroom every day to just work. I hate having to explain to clients that I can’t meet my deadlines because the software is broken. I’ve downloaded Capture One as an alternative to complete my jobs. You’ve lost a customer if I like it after 30 days.

  386. Keith Ringers says:

    Just got back home from a vacation photo shoot. Updated Lightroom before we left. Went to import photos and #%{}}*++##! What has Adobe done? Quickly restored my Win 8 and thanked the good Lord that I had not downgraded from Lightroom 6.1.1 on my Macs. If Adobe has so misunderstood its customers, let this yet be another appeal to restore the full import functions in Lightroom. We use all of them from time to time. All this update did was to destroy our workflow. We never minded changes to software as Lon as the changes were improvements. THIS IS NOT! We turn off analytics so you should not be tracking our stuff. Take a look at Proshow, another very advanced program that found an easy wAy to include novices with the simple use of wizards. With those, everyone can create professional looking products. Adobe would do well to learn from them. And your apology seems nothing except an arrogant response. Learn here from the incredible Windows 8 fail. Lightroom 6.2 is right up there with Microsoft. We do not understand why a company that has never been afraid of complexity suddenly came down on Lightroom import. It seems inconsistent and a dismal prelude to dummying-down things to come. If this is adobe’s course, my subscription is out in a couple of months. ACDSee is quickly improving and their latest offering is starting to leave you in the dust. Other than your insincere apology, because nothing has changed, for us, Adobe is standing on the thinnest ice. Restore Import soon.

  387. Gordon Brown says:

    Bring back auto eject for flashcards.
    Bring back the regular import dialog.
    Quit trying to dumb down Lightroom.
    Listen and act on your users’ requests in a timely manner instead of offering excuses on why something cannot by done.

  388. Rob Levandowski says:

    I’m not a professional photographer. I’m a relatively new user of Lightroom. So, in theory, I’m the target demographic for the import changes.

    And I hate them.

    I’ve been an avid Mac user since 1985. Until this year, iPhoto met my digital-photography needs. Okay, when I finally got around to purchasing a DSLR, it started showing some limits, but it worked.

    Then, Apple decided that iPhoto’s interface was too complex for new users, and they brought out Photos.

    Photos eliminated many features in iPhoto, particularly those useful to experienced users. It introduced numerous bugs. It brought in a theoretically “friendly” interface that was inscrutable and difficult to use. At the same time, Apple eliminated their professional Aperture application, so that wasn’t an option. Adobe can thank Apple for directly driving me into Adobe’s $9.99/month arms.

    But if Adobe is going to go down the same path—taking a powerful app and dumbing it down to the lowest-common-grandma level—then I might as well stop paying Adobe and go back to dealing with Photos. Apple doesn’t charge me anything for Photos.

    Yes, the old import interface was a little busy. It could have benefited from an improved layout. It didn’t need to be nuked and replaced with the interface from an iPad. If you care enough about photography to pay $10/mo for a photo organization and editing tool, you probably want considerable control over your photos, and that’s what the old interface provided. It’s actually MORE confusing, because so many options are hidden and abbreviated.

    Take choosing an import location. One place where Photos failed me is storing pictures on a network storage device. Lightroom, before this version, made it pretty easy, and it was reasonably easy to verify that pictures would go to the share instead of to a local drive. With the new import dialog, I have to click on the gear, click Destination, then click “Select” to find out WHERE my “Lightroom data” destination folder is—the internal drive? The external drive? The network share? I could tell this at a glance with the old interface.

    Adobe gained customers because Apple alienated power users with Photos. For Adobe to then alienate power users by making Lightroom work more like Photos is, well, absurdly incompetent management. It plays away from the strength of your product and away from your growth opportunity.

    • Carol says:

      [“…dumbing it down to the lowest-common-grandma level—then I might as well…”]
      Hey Rob, some of us who are just as affected and perhaps just as professional as others here are actually “grandmas” and grandpas I dare say. You shouldn’t make statements like that.

  389. CalifDan says:

    Look. Adobe seems hell bent on fixing what wasn’t broken. For some reason they convinced themselves that the Import dialog as too confusing or too cumbersome or some such non sense. Now the managers are married to the idea. They don’t want to appear like they threw tons of time and money down a rat hole (after all performance review and bonus calculation time is coming up) so they will stay married to this misguided idea that the Import Dialog must be dumbed down.

    At this point I think the only hope is that if everyone who feels strongly about this keeps bombarding these Adobe feedback pathways with a simple “Put back the old Import dialog without change” message. Plain and simple. No long verbiage needed. No debates on the merits of the Eject, or any other option. just lots of people saying the same thing – :Put Back the Old Import Dialog Without Change.

  390. CalifDan says:

    PUT BACK THE OLD IMPORT DIALOG WITHOUT CHANGE

  391. What happened to “Move” on import?? 90% of all the people who come to me for training on LR have images scattered all over their PC. Now they have LR and the first thing I show them is how to import into LR and use Move to organize their existing files into a manageable hierarchy.

    So please as everyone else has said please put back the original import dialog – at the very least as an option!

  392. Tony Triolo says:

    I did not just sign up for the Creative Cloud to get Lightroom Light or Lightroom Elements. Put back the old import dialog without change or I shall be looking closely at different options.

  393. Michael Hoskins says:

    I agree with the Import issues. Adobe BAD.
    The one feature I was looking forward to updating was the “Dehaze” , but alas it is only for the CC version(ie monthly subscription) and not for the eternal (is anything eternal) license.
    Must I look at other providers?

  394. David Nissen says:

    “These changes were not communicated properly” Huh?

    Not “bad communication’. Mistake. Man up. Give us some confidence that you will fix it. I’ll bet the guys at OnOne are looking to add DAM to their, now, pretty fast, Browse module. Gleefully.

  395. Bob Graf says:

    To TH and the Lightroom Management Team: While you’re at it (fixing Lightroom), please fix the issue where Tether Capture will not work with Nikon Cameras and El Capitan. It’s very frustrating not being able to utilize this feature of Lightroom after using it for several and years and coming to rely on it.

  396. Mike says:

    I cannot figure out how to select “move” in the import dialog. Under “File Handling” I see Copy and Add, but not move. I have tried searching, but cannot seem to find it. Could you please put the move functionality in a more obvious place?

    Thanks (looks like you have a lot of suggestions, hopefully this is an easy change to make),
    Mike

  397. LR Team:
    My workflow, which includes import and naming presets using custom text and copy destination, was setup in 2006. Not having a visible destination path or file name preview seriously impacts my workflow. Please restore these features, as well as eject after import.

    You need to continue to support your professional and advanced users. They are the ones who have paid for and purchased LR over the years.

    You can maintain both a “simple” and “advanced” import GUI and expose the appropriate functions.

    Stephen

  398. Pauline Tims says:

    Adobe ,you need to reinstate the import features and anything else you have removed from Lightroom. I have been using this software since Lightroom 2.. I have updated each time, glad I never clicked the update button this time , so many pro photographers had their workflow wrecked.
    All to suit the newbies!, you need to get together with the professional photographers and people like me who subscribe to cc because they wanted the convenience of having the latest updates all the time. This is not the service I signed up for and am paying good money for. I could get a similar editing programme to the new interface for free.
    I expect to see a reinstated Lightroom 6 soon. Maybe listen to the clients who are telling you to have an elements dummies version and a professional version. Can’t be too hard surely.,???? Listen to,your valued clients for a change not he instagramme selfie brigade.!!

  399. Pauline Tims says:

    Also some comments or replies from Adobe would help . Some assurance is needed here.

  400. Jef Christian says:

    My primary complaint is speed. Even the second new release has performance problems which in the import process. I was very happy with the previous method but probably could get used to the new one except for the hit to performance. It made this software go from a must have to unworkable.

  401. Kilrah says:

    The Mac version is still highly unstable, even if it doesn’t just crash anymore like after the initial update it still kind of “locks up” in semi working state after doing a couple of operations upon launching the app. For example filtering based on flag status will work if it’s the first thing you do after launching the app, but if you browse a bit and switch between modules a couple of times selecting it will have no actual action. When it enters this state mouse operation also breaks, for example click and drag on a zoomed picture won’t work to scroll through the photo, LR will just take the click alone and toggle zoom completely ignoring the fact the mouse button is still held down to scroll. Flagging a photo shows the “flag as pick” notice, and that never disappears anymore.

    I’ve been on an important shoot these past days and these bugs (the constant crashes on the first shoot day, and the above issues on the next days after the latest update) made LR basically unusable on my on-set machine (Retina MacBook Pro with El Capitan). Fortunately I have a Windows PC at home also with the latest version but that was not afffected by the reliability issues, just the usual slow performance. When do we get a properly multithreaded app that makes decent use of current machines’ many cores without spending most of its time waiting?

  402. Kris Coppieters says:

    Put back the old Import dialog without change.

  403. Peter says:

    I can totally imagine what happened here. One of the managers went home for summer vacation. He met his whole familiy and his granny said: “Hey boy, how you’re doin’ at work?” He replied: “Hey granny. Look, I’m working with this team on a fantastic photosoftware. You just put your SD-Card in your computer and … wait … there comes up the import. You can see all your photos taken and select where to import. See…”
    “Ohhh boy, that’s to complicated for me. Look at my new iPad, that’s an easy way to look at all the photos.”
    He couldn’t sleep for two weeks. After he returned back to work, he pushed his team to get an easy import-dialog so he can satisfy his grand-ma. This had to be done fast, so he can show his new work on Thanksgiving to his beloved granny.

    Hell, man. This is a bugfix-release. I bought Lightroom 6 because I don’t want no cloud-managed software. I want to keep my workflow like it is at the time I buy the software. You take away functionality with a bugfix-release! Keep your hands away from that. You communicated in the past, you can only add new functions in the CC-Version. So, why can you take away functionality in Lightroom 6? Bring back the import-dialog to Lightroom 6, it has no Rolling Release mechanisms!

  404. Thierry says:

    The only apology worth its while is to swallow your Adobe pride and to return to the former import module.

  405. Christian VERMEULEN says:

    PUT BACK THE OLD IMPORT DIALOG WITHOUT CHANGE
    There is a French proverb which says “Des erreurs se commettent et se paient” i.e. “Errors are made, and have to be paid for”. So please, don’t make it worse by having a stonewalling attitude.

    • David Meier says:

      Agree. If LR will offer a simple import for new or unexperienced users – well, that’s a fine thing. But do not forget about all the users, who have their workflows since years.
      Just bring back the old Import-Dialog – as en ‘expert-mode’ if you wish, but bring it back.
      (In fact, Adobe should feel proud about all the complains – it just says, that LR is a good product and no one here want’s to look out for an alternative)

    • Same here! Leave it as it is!

  406. Rebekah says:

    I updated Lightroom. And now each time I open an image and click on the develop module it opens the image in a distorted view almost like a infra view. Don’t know how to fix it – never seen it like that before