Lightroom 4 Known Issues

Overall, the response to Lightroom 4 has been great, but big changes are never without a few big glitches.

Tom Hogarty’s just posted about the major bugs they’re tracking with LR4 right now:

His main ones are:

  • Point Tone Curve Migration
    • The upgrade loses some custom point curves – they’re working on a fix, and also a way of fixing already upgraded catalogs, so don’t panic. Yes I know it’s a pain.
  • “Edit in” Workflow for External Editors/Plug-ins
    • NIK plug-ins (and some other 3rd party editors) are not working when using Edit In. They’re working on a fix.
  • Edit in Photoshop Workflow
    • ACR 6.7 is available as an RC – once you’ve installed it, it’ll still say you need ACR 7.0 (which will be the officially compatible version) but pressing Open Anyway will work correctly.
  • Reverse Geocoding Delays
    • It wasn’t working a few days ago. They’re monitoring with Google but it seems to be ok now.

I’ll add a few more I’m aware of:

  • Some people are seeing performance issues, but not everyone, which makes it hard to track down.  If you’re seeing performance issues, they’d like some clues on where to start looking, specifically…
    • Where does it feel slow?
    • Is it interactive speed in Develop?
    • Walking through images in Develop? Or in Library?
    • Does it slow down over time (hinting at poor memory usage)?
    • Does turning off the second window help?
    • Does turning off noise reduction or lens corrections help?
    • Do you see the same with a clean catalog (i.e. is it catalog-specific or an upgrade problem?)
    • Post your answers on the Bug Report forum where they can be tracked by the engineers
  • Some can’t see the contents of large folders after converting their catalog. The engineers are investigating.
  • Some are seeing an AgExportRendition error when trying to email photos. It appears to be related to a built-in preset which is only added when you press Restore Export Presets (so don’t do that if you’re not having trouble!). If you’re seeing it, please post it on the Bug Report forum and we’ll test the solution.

One final thing – some people are pressing Update All when asked about updating to PV2012.  Lightroom does try to translate the settings, but the rendering is so different that you may end up needing to make further manual adjustments.  Unless you want to practice your processing skills on your whole back catalog, don’t press Update All – only update the ones you intend to reprocess.


  1. I have an issue when exporting. The list of folders I’ve previous exported to appear in the dropdown list but are all greyed out and can’t be selected. Rather frustrating and adds time to my workflow. Any fixes?

  2. I use Nik plug-ins all the time and have no issues at least Silver Effects Pro 2, Color Efex Pro 4, Define 2 and Sharpener Lightroom Plug-Ins are all working for me fine. But I do get that Photoshop workflow warning (Nice to know that it is still working.)


  3. No performance issues here (on a catalog of 67K+ images), but I definitely have the problem of not being able to see large folders. In my case, I can see the sub-folders, but the parent appears empty if there are a lot of images. Not sure of the boundary that trips it though.

  4. Also, in tethered capture, the image does not auto-advance to the latest capture. That is, I in the Library expanded (single image) view doing studio tethered capture with a Canon 5D MK II. I shoot 5 images and LR4 sits on the first image until I go to the keyboard and right-arrow to advance to the later ones.

    Under LR3, the most recent arrived image was always shown, so I could just glance at the monitor from across the room and verify framing, etc.

  5. Karayuschij says:

    Other (to verify on other machines/configurations) – I am on Mac with 10.7.3
    • LR4 don’t import files if the name is written with cyrillic characters
    • If I export a photo in Photoshop, and then if I save this photo in jpeg format it will not be automatically imported in the LR library (with the previous versions of LR it was).

  6. lightroom 4 is veeeery slow when installed with lr3. is anyone else having the same problem?

    • There are quite a lot of reports. We’re trying to track down the cause as it’s not affecting everyone. Do you see the same problem in a clean catalog? Just as a test, I’m not suggesting you start using a clean catalog.

      There are a couple of tricks that seem to be helping – trashing the previews file, and exporting the whole catalog to a new catalog. The one warning with the export as catalog is it loses any Publish Services, although there are workarounds for that.

      • Yes, same problem with a brand new catalog, previews trashed and all, dunno what the problem might be. Also i tryed installing lr4 in a virtual machine and it works like a charm.

  7. Jmckinnon says:

    When sending images over to PS cs5 from LR 4 my edits seem faded or lacking contrast….don’t look the same as they did in LR

    However LR3 is working fine????

  8. Jmckinnon says:

    It Worked!

    Thanks so very much.

    • Excellent!

      • Demetrius says:

        What solved the Jmckinnon’s issue? I am having a very similar situation with catalogues I upgrade from LR3. 1 catalogue in particular, when I updated (has 145 raw files), the grid view is fine, but loupe view is fine, but NO thumbnails will show. This makes it difficult to go directly to the Develop window and being editing because the only image available is the single loupe view image I activated while in the Library.

        • 2 possibilities Demetrius. If you’re on 4.0, rather than 4.1, then there’s a bug with big folders not displaying properly. In that case, try the 4.1RC which is linked in various replies here (or the next blog post). The other possibility is a corrupted preview cache. The way to fix that is to close LR, find the catalog on the hard drive, rename the Previews.lrdata file next to it, and reopen LR. If that solves it, you can delete the renamed Previews.lrdata file.

          • Demetrius says:

            Victoria, THANKS! It appears to have been a corrupted Previews.lrdata file. The weird thing is that I attempted that a couple of times prior with different results.

            Either way, thanks!

          • Excellent! It does happen now and again, particularly around major upgrades, so I’m glad that’s working now.

  9. Just decided after looking here and several other sites – I’ll wait to upgrade. They are all self-selecting samples, but it really sounds like LR4 is not ready for prime time.

    • I don’t blame you Gary. Lots of people are having no trouble at all, so you could try the trial version and see if you’re affected by the performance issues, or just wait for the .1 release when hopefully all of this mischief will have been squashed.

    • You can wait if you think it’s better, but for what it’s worth the people who use LR4 with no problems probably don’t tell you about it.

      Well, I am one. Using LR4 on my Win7 64bit laptop with i7 820qm processor and 4GB RAM. LR4 is running like a dream so far…

  10. Harvey_sapir says:

    Hi all,
    I am experiencing following issue with print presets in LR4:
    – when changing print presets in the Print module, it works fine for 2 -3 presets.
    – then the last used preset becomes “stuck” and can’t be changed without booting LR4 again
    I have seen similar issues on various forums, but still can’t see anywhere a formal response from Adobe.
    Is this a local issue I’m having that can be self-corrected?

  11. Importing from other hard drives keeps crashing, contents contain multiple file types and video files (MP4), the import preview doesn’t show any thumbnails or are blurry. When importing, it crashes.

  12. nicola zingarelli says:

    Hi Victoria, I have just installed LR4 in my PC and the clone toos is darn too slow, even slower than the .3 version. I have windows 7 6GB RAM and two hard disk: Lightroom is on C and the catalogue and the cache is on D, could this be the issue? Thanks a lot for your kind feeback



    • Having the same type of problem.When using clone tool and the other mask tools.I get a delay each time I click.I have win 7 with 12 gig ram,1 gig ati hd video card,etc.I have been using Lightroom since it first came out.I do not have these problems with Photoshop CS5.

      • CS5’s a different kettle of fish Mark. When Photoshop clones, it’s applying adjustments directly to rendered data. When Lightroom clones, it runs a long set of text instructions and that takes a lot of processing power. That said, if it’s new to LR4, there’s a good chance they can improve it yet.

  13. Hi Victoria
    I’ve found a problem in the Print module, where the image layout in the main window will not update if a different print template is chosen from the template list. The program is also very s…l…o…w compared to LR3.
    Has anyone else found this problem, is Adobe aware of it and is there a fix in the offing?On the upside, the new process is very good and deals with colour and detail much better. However, the print problem is so fundamental that I am disappointed that LR4 was released with such an obvious flaw.
    Not good, Adobe!

    I’m running an iMac with Snow Leopard, 10.6.8.

    • Some people are seeing performance problems, and Adobe are working on a fix for that. The weird thing is it’s not affecting everyone. I’m hoping it won’t be too long, but I don’t have a day on that yet.

      I can’t reproduce a problem with selecting print templates though, so it would be worth reporting that at

    • I’m having the same problem on a Windows 7 64bit PC and Lightroom 4. I’m stuck on a contact sheet and can’t use any other template. Help please!!!

      • Hi Lynne, does it unstick if you restart LR? I’m hopeful that it’ll be fixed in the final LR4.1 release.

      • I’ve also come across this problem and for me the solution was to delete all of my user templates. All the bundled templates worked fine until I selected one of my own and if I selected an image that I’d last printed with one of my templates the whole thing ground to a halt. I intend to rollback to LS3, export all my templates, delete them then upgrade my catalog again and import them to see if that works.

  14. Harvey_sapir says:

    I also have the issue with the print presets.
    it has been reported in a number of forums, but doesn’t seem to be a universal problem, haven’t seen any formal feedback from Adobe.
    the only “solution” that worked for me was to delete all my user presets.
    Then the LR presets work fine, also new user presets that I define.

  15. I have reported the print problem on
    but no acknowledgement yet.
    I cannot quote an error message because none shows up. It just seems that print templates from LR3 are not being recognised, though they appear in the templates list.

    • Was this your report?
      I couldn’t find another one, but I may have missed it. If that is yours, it would be worth posting back to say it still happens in the release version.

      • No that was someone else’s post. Mine is posted under ‘Seahawk’ – at least someone else has the same problem though. My post did refer to the release version.
        I have to say that given the number of problems that are being reported with LR4 this seems a pretty abysmal performance by Adobe and it probably shouldn’t have been released; here in the UK I doubt this version could be deemed to be ‘of saleable quality’, don’t you agree Victoria?

        • Post the link here then Seahawk, and other people can vote on it. The more people with the problem, the higher the priority of the fix.

          Undoubtedly there are some big bugs that slipped through the net this time. They fixed more than 800 reported bugs between the beta and the 4.0 release, but SO many things that changed this time round, that there was a lot more potential for bugs not being picked up.

          Personally, I’d have liked to have seen a release with less features and more polish, but that’s got to be a tough call to make in a publicly trading company. They had deadlines and targets to meet, and the Lightroom team worked incredibly hard to make it the best they possibly could. It’s been a rough ride all round.

          Tom posted on the bug report forum today, to say that a new release should be available this week, which fixes the biggest bugs, particularly the tone curve and performance issues. I hope that will settle the major issues, and I’m pleased that they’ve managed to do it so quickly. There will still be bugs leftover, as those big issues have been the main focus so far, but unlike Photoshop, the bug fixes carry on throughout the cycle, so there’s still hope for them.

  16. Realspear says:

    I’d been noticing how slow web gallery output is so I ran a test. All tests used the same parameters – Lightroom html gallery, same 24 images, 800px at quality 80, simple text watermark. Only one version of LR running at a time, web browser and email also running but not actively used. Here are the results for exporting the gallery to my desktop:

    LR 3: 1:16
    LR 4, 2010 process: 3:52
    LR 4, 2012 process: 5:27

    This performance is insanely bad, especially because I frequently export galleries with 100 – 200 photos. When I do those in LR 4, I have time to cook dinner. I suspect most of this time is in export, and may try testing that later, but it really doesn’t matter what is causing it, this is awful performance.

    (iMac 2010, 3.2 Ghz Core I3, 8GB, images on FW 800 connected 7200 drive with big cache)

  17. there is also a known issue with having upgraded catalogs or having installed over the beta causing massive slowness. I reinstalled and started a new catalog and saw a massive speed increase.

  18. When sending an image from LR4 with edits to PS CS5, it changes in PS… it’s washed out and doesn’t look the same. This doesn’t happen if there are no LR4 edits. What’s wrong?

  19. LR 4.0 crashes when playblack is selected for a Canon 1d Mark iv 1080 30p video. When LR is restarted all option bars for develop and library are reset to factory defaults.

  20. Installed LR 4.1 RC version and it seems to have resolved the print module problem. Still feel it’s slow in the develop module though.

  21. Mafeuer says:

    LR4 Freezes when I try to import photos.

  22. Hi, I recently upgraded to LR4. I have an iMac, 2.8 GHZ, i7, 16 GB. When I started using LR 4, I had 8 GB and I found as I worked on my photos, I would almost run out of memory. I usually have LR, Mail and Chrome open, when I work. I might open a photo in PS, but then I will close it. Now, I thought that maybe upgrading my memory it would be faster, but I upgraded to 16GB and it’s doing the same thing! How is it possible for my memory to go so slow with 16 GB? I really think there must be a problem with LR4. I will browse the forum to see, if there are possible solutions. Thank you! Gloria

    • Hi Gloria, if you open Activity Monitor, can you see what’s using all the RAM? And are you using 4.0 or the 4.1RC?

      • Hi, Victoria, LR has improved, after increasing the cache and rendering Previews. Right now it’s first on the list with 2.3 GB. I have it admit, it’s working better. I don’t know, if 2.3 GB is normal. I’m using 4.0 as I read some people weren’t too happy with it and I don’t want to risk it. Thank you very much!!

  23. Hello, I’m hoping someone can help… (Adobe Support haven’t been useful yet!) I’ve got a Toshiba, 4Gb RAM Win7 laptop running LR4.1RC and LR crashes *every* time I try to open a video in the loupe view. I can play all the videos (from various cameras in various formats) in Quicktime without a problem and LR can display/edit settings in the grid view but trying to use the loupe view causes the program to crash without any error message. All drivers are up-to-date as far as I can tell… Is my video card (Intel HD) incompatible or is something else going on? Otherwise, I’m liking the upgrade! Suggestions please… Thanks, Adam

  24. Dyroff, Sean says:

    I can’t see the contents of small folders after converting my catalog. I have some folders that are large, but I tried to look at 4 images in a folder after converting to LR4 and it still won’t load the images. I’ve gone back to LR3 because this is unusable.

    • You can’t see the contents of the LARGE folders Sean, or the small ones? Have you tried 4.1RC? Related bugs were fixed. If it’s small ones, tell me more about what you can see.

  25. Teus Renes says:

    Definately poor memory usage over time, once I open lightroom I can export a file. But once its been open for a few hours I simply cannot. (I know I have a really poor system)

  26. Jmckinnon says:

    having trouble with LR4 import window. After opening images into the import window(from card reader) my images show up in the grid view as expected, but when I click on the loupe view I only get a thumbnail image and not the full size. Also my vertical images need to be rotated as I don’t remember having to do that in LR3?
    Any help?
    Running Lion 10.7.3 on an imac

  27. Alec Beattie says:

    Lightroom will not find my Canon 5D I have to use Lightroom 3 to download photo’s is there a cure ?

  28. Musiccat4 says:

    I am running Lightroom3, and Lightroom4 on my Mac because Lightroom4 will not allow me to use my NIK software. When will this problem be resolved?

  29. Musiccat4 says:

    You are truly the “Queen of Lightroom”, I followed your instructions, and now everything is moving along smoothly.

    Thank you

  30. David Eichler says:

    Actually, editing in PS and rendering with PS will not work crrectly if you have applied a significant amount of clarity in LR4. The rendered image appears significantly lighter, and perhaps lower on contrast, when this is done. It is apparently a known bug. The recomended workaround is supposed to be to have Lightroom render, which doesn’t help if you want to open several images together as layers in PS or if you can’t et the warning dialogue that allows you to have LR render, and are unable to reset the warning dialogue box.

  31. Hi Victoria, every time I export picture, after editing of course.. it’s exported with not all the editing preferences that I edited. Almost nothing. What should I do?

  32. I using LR 4 and CS5 on a Mac running Lion. Sometimes when I apply a few tweak in LR; such as highlights or shadows and I go to Edit In the LR changes do not carry over to PS. Is this a known issue?

  33. Nsphotodesigner says:

    I just upgrade to lightroom 4. I have a 2011 i-7 Quad Core iMac 27 with maxed out 16GB RAM. The lightroom 4 is very sticky, slow and the thumbnails jump around = when I click one, another photo opens up in main window not the one I clicked. Very disappointing.

  34. Hi Victoria
    Found another printing problem; using Soft Proof, anything green (eg leaves, grass) shows up as ‘out of gamut’ for destination, if you follow me. I use Canon Pro 9000 and iMac running OS Mountain Lion. Have re-calibrated monitor, using correct profile for paper, etc. but problem remains. Prints are awful. The only work-around seems to be to set colour to be managed by printer.
    Never had this problem with LR3.
    Anyone else experiencing this?
    Could the print profiles be incompatible with LR4.1?

    • That does sound like a problem with the printer profile. Can you print using that profile in LR3, or were you using Managed by Printer there too? Mountain Lion could be a factor too. The print path may have changed.

      • Sorry Vic, I’m an idiot. I should have said using Snow Leopard, not ML.
        Yes, I could print using the profile using LR3 without problem. My guess is that it is incompatible with LR4.
        Also, the other print problem has re-appeared ie. print templates not updating on the fly. At first LR4.1 seemed to have cured it but it’s back. Must be a bug.
        This is very frustrating, very disappointed with Adobe and I still think this version of LR was not fit for purpose when released.

        • I know it’s frustrating. They added SO many new features to this release, the bugs are certainly a lot bigger too. Send me the printer profile and I’ll try it here too. They’re looking into the print templates issue.

  35. I seem to be having some difficulties in lightroom 4. Virtual copies not being able to export to desktop.
    If you know if this problem or perhaps have a solution please let me know.

    • I haven’t heard other reports of that Brando. Tell me more – is it only a problem for virtual copies or all files? Will they export to another location? What file format are you selecting? And is there an error message, or what happens?

  36. twiggs says:

    hello!! well, i’m dealing with a whole different issue and i have no idea how to change this. i’m working with RAW images and after editing them and exporting them both in high-resolution and 72 dpi 800px with watermark, i notice that this last one is actually sharper. how does this happen and what to do? i’m so frustrated right now… editing a photo session and there is now way i can deliver these to the client. can you help me? thank you!

    • First thing to check would be the Sharpening settings in the Detail panel in Develop, to check that they’re set to the same value. Also check Clarity.

      • twiggs says:

        oh whow you were fast! well, but if i’m working on an image and then go from Develop to Library, and export it twice in different resolutions, Detail and Clarity shouldn’t change right?

        • You caught me catching up with the days emails!

          I see, I thought you meant that 2 different photos were ending up with different sharpening. What are you viewing the exported photos in? Most likely scenario is that the resampling on the high res is making it look softer. You could also try applying output sharpening, which is adjusted automatically depending on the resolution.

          • Yes, they do look softer and I might don’t even notice on other photos, but on portraiture, I want to see sharp faces and smiles… And I’ve tried that now sharpening for screen and matte paper and nothing changed. It keeps almost blurry. Any more solution? Or at least some other place I could look into to find some answers? Thank you so much for your help!

          • You haven’t told me what you’re viewing them in?

          • what do you mean? LR version? 4. and Windows 7.

          • The photos after you’ve exported them – are you importing them back into LR and viewing them there? Or Windows Picture Viewer? Or which program are they looking soft in?

          • Yes, Windows Picture Viewer. But I do notice that they soften from Develop to Library, though i’m aware that this doesn’t mean that they’ll end up blurred in the end. But I’ve tried to export them again twice, each with a different resolution and it keeps happening.

          • It will do – that’s primarily because Windows Picture Viewer is having to resize the image. If you zoom into 100%, you’ll get a more accurate view, but obviously that means you can’t see the whole picture! If you’d like to email me the full res and low res photos though, I’ll be pleased to take a look.

  37. Mars Fotographi says:

    Okay I’ve been using LR3 for year and updgraded to LR4 when it came out and I’ve no issues with either of programs that many are experiencing online and other places.
    Here is one big question that seems to make LR4 run slow only under one scenario.
    I normally import all my images from card into LR4 and after import is completed I go and select all files and then go into Library -> Preview > Render 1:1 preview, it does whatever processing it needs to do and after that is comes back.
    After this moving from one file to next within Library module works just fine without any issues.

    Now I doubleclick on single file from Library and open it under Develop module
    – it seems like it waits for 5-10 seconds trying to generate historgram (applying whatever settings it needs to apply).
    This happens only first time I open image in Develop module. And this happens for each and every image.
    Is there a way to overcome this situation or you’ve to sit thru each image and let it do this process for 5-10 seconds ?
    And yes this happens both LR3 and LR4, I only shoot in raw so file size are 18-21MB on Canon 5Dmk2.
    My machine config has 8GB RAM + 256GB SSD + Core2Duo 2.4GHz processor.


  38. I’ve heard a similar report, but I haven’t seen a published fix for it. The best I can suggest is reporting it over at the Official Feature Request/Bug Report Forum where the engineering team will be able to see if and may be able to provide extra information – or you may be able to help them reproduce it so they can fix it.

  39. I’ve just upgraded to 4 from 2.7 and it’s really nice, I love it. ONly glitch I’ve found so far is that when I export a batch of images to a subfolder, they show up in the next folder up in the hierarchy, i.e. if I had Photos>Subphotos, and told LR to send images to Subphotos, it puts them in Photos instead. Anybody else had this happen? It’s been a few times now, kind of annoying, both before I figured it out and now, since I have to weed out those files from whatever’s in the wrong folder which is a time waster for sure.

    • That’s weird. If you’re using an Export preset, I’d try manually setting it. Other than that, I’d try trashing the preference file as that fixes the weirdest issues. If you need instructions, just tell me your OS.

  40. Bdonnelly41 says:

    I have a Mac 10.6 version. Not the 0s mountain lion. Just downloaded LR4, have all my topaz plug in keys listed, when i go to photo-edit-click on topaz fusion express 2, nothing happens. Is this a LR 4 glitch? thanks,

  41. After upgrading from 3 to 4, some editing is lost. In my case, the use of graduated filter with various effects are completely lost.

  42. I have recently upgraded to Lightroom 4 and when I connect my Canon G11 the import screen finds the camera, displays thumbnails. However, when I press the import key the software displays a message that no photos have been found.

  43. I have recently upgraded to Lightroom 4 and when I connect my Canon G11 the import screen finds the camera, displays thumbnails. However, when I press the import key the software displays a message that no photos have been found.

  44. Hi Victoria, I sure appreciate all of your comments on this blog and hopefully you can help me after an unsuccessful internet search. I have “exported a folder as a catalog” from my laptop Lightroom 4 catalog without negative files or previews and then when I select “import from catalog” on my tower, Lightroom 4.1 does not recognized any of the updated metadata changes (primarily ratings.) Both computers have the same dng images. I saw somewhere in my search that this might be a known issue already, have you heard something similar or doe you know of any potential work arounds to sync catalogs and image adjustments across computers?

    Many thanks,


  45. Kdifato says:

    I’ve been using LR since it first came out and I’m having difficulty with getting LR4 to print large file jpgs from raw files. When I use export command the largest file I can get is a 5mb photo from a 23 mb raw file. If I use Print to File it only gives me a 700kb file. I just did a wedding and have tons of shots that I have to export as jpgs and I’m not understanding what is different in this version from the past or if this is just a bug. Anyone know? This has really slowed down my workflow trying to figure this out. THanks for your help.

  46. i ahve LR4 on a creaming fast machine and it is VERY VERY SLOW. Much slower then LR3. this is a serious problem and i have seen a lot of people are having the same problem on new macs like mine

    • Yep, there are undoubtedly some performance issues going on with 4.0. 4.1RC has helped some people, but not all. I’m hopeful that the final 4.1 update due out ‘soon’ will improve things for a lot more users. The odd thing is, it seems to be affecting high end machines more than older ones.

  47. phcastagna says:

    Good evening,

    I’m a LR3 user and never had to complain.
    I just bought online,download and install successfully LR4 yesterday.

    I find, comparing to LR3 on the same computer/screen, that LR4 doesn’t react the same.
    Some delay in between an action made on a cursor and the change made on the photo (3 to 5 sec).
    For one photo it’s “ok” but to treat 100 photos it’s just not possible…

    Also, when I press F11, I got an unstable system where a “wide black bar” appear on top on all the length of the LR screen. It stop as soon I press again F11.

    I was checking for the version and an eventual update but I got a message that the server is not responding or my internet access is not working but in real it is working.

    I already contact the tech support of Adobe who answer me that they do not deal with the computer issues of the customer and that they do not support for issue with a second screen…
    Explain that everything was fine with LR3 is not the point for them…

    I’m not sure that I’m posting at the proper place on this website, and I apologize for that (and my bad English :-)), but I feel that I should get an honest and professional answer here…

    Kind regards,

    • Hi Philippe. Some of the advice I hear given out by the tech support department gets stranger!!! But yes, I’m pleased to help. Lightroom 4.1 has just been released today – when you tried to download the update earlier, it was probably while they were still getting it ready. I think that should solve the issues you’re seeing, but if it doesn’t, pleased post again and I’ll be pleased to help.

      • phcastagna says:

        Hi Victoria,

        thank you for your answer.
        Actually 4.1 fix most of my issues… Really good!

        however I have 2 questions:

        – The box for the automatic removing for the chromatic aberation disapeared from the lens preset… Do you confirm?

        – I was not able to find the new HDR treatment listed in the adds for the version 4.1

        thank you again Victoria and have anice evening

        • Excellent! The checkbox for chromatic aberration has move to a Color tab within the Lens Corrections panel, along with the new axial chromatic aberration correction controls. And the HDR 4.1 addition is the ability to import 32-bit HDR files, and extends the slider range for those HDR files automatically. You do still need other software to create the HDR files in the first place – Photoshop has a Merge to HDR command which can do it, or Photomatix is another popular option.

          • phcastagna says:

            I found the color tab :-)

            Understood for the HDR… I’m already using Photomatix pro

            Thank you Victoria and have a great day

          • phcastagna says:

            Hi Victoria,

            I notice that my former issue on 4.0 (slow reaction of the cursor in development and black band on top of Lightroom when I activate F11) which seems to be solved with 4.1 in fact still exist when I start to treat the noise.

            Are you able to replicate this issue?

            kind regards,

          • Do you have Clarity turned on too Philippe? There is a known issue on that combination, which is noted in my what’s new in 4.1 blog post.

  48. Ferreri Mike says:

    I have been a LR3 user for a while. I installed the LR4 update last night and noticed that the program as a whole runs slow…too slow to even be productive. I thought it might be the image files, but when brought into LR3 everything is as fast as ever. Just waiting for the image to show up on the screen after a zoom could take up to 30 seconds.

    Does anyone know what is wrong? As it is now, I can’t even use LR4.

    • Have you installed 4.0 or the latest 4.1 that’s only just been released Mike? 4.1 should be better.

      It may speed up automatically once it’s finished upgrading the preview cache in the background, but the easy way to force it would be to delete and rebuild the Previews.lrdata file/folder.

      Other than that, it might help to know your system specs so we can troubleshoot in more detail.

      • I have installed the latest 4.1 version. I am running it on Windows Vista (32 bit) with 3gb of RAM. I run other programs like Photoshop and Illustrator…even super memory taxing programs like AutoCAD without a problem. LR3 also runs perfect.

        I am not sure what you mean by the preview cache.

        I tried turning off all of the retouching settings one by one until I was back to my original image… still super slow. Sometimes zooming in close will result in parts, or all of the image to go black on the screen. To even adjust a single slider, I have to keep holding the cursor on it until it catches up. Sometimes I can’t even see the adjustment I made…it’s just so slow in processing these changes that it locks up.

        I have switched back to LR3 now and feel I have wasted my money on LR4 since it’s not useable.

        • Mike, that sounds like it could use more troubleshooting. You’re certainly quite close to the minimum requirements, but if LR3 runs ok, then there’s something else going on. Feel free to post on the forum (link on the menubar) and we’ll help you narrow it down.

          • After some more use, I have figured out that the detail adjustments are the culprit. As soon as I touch the noise reduction or sharpening sliders, the performance instantly slows to a snail’s pace. To add either of these adjustments, I have to grab and hold the slider button down until the computer can catch up with my actions.

            Also, exporting is extremely slow. I exported 20 images the other day (high quality jpeg), which took a little over 30 minutes. The same export in LR3 takes a fraction of that time.

            Are these issues that Adobe is aware of and will be fixing?

          • Do you have clarity turned on at the same time as the noise reduction/sharpening? If so, yes that’s a known issue noted in my 4.1 what’s new post.

            The new LR4 processing is significantly more processor intensive than previous versions, so I’m not overly surprised that it’s taking longer to export. Some exact times (i.e. the same photos exported from LR3 and LR4 to compare) and also your full system specs (i.e. which processor) would help me answer whether it’s a known issue for your export times. It would also help to know whether you see the same slowness exporting from LR4 with photos set to Process Version 2010 rather than 2012.

            They are continuing to work on performance issues, but there are a lot of variables involved so we do need more detail.

          • Mike Hailey says:

            I have had the same issue. When editing in Silver Efex Pro 2 (a plug-in), it runs even slower. It can take just as long to undo an edit as it does to edit, which is frustrating. I have the Radeon x300/x500/x1050 series graphics card; Intel Pentium D CPU 3/40GHz; 3 GB RAM; 32-bit operating system; Windows 7. Is it my hardware, or a bug in Lightroom 4?

          • Mike, I’m going to guess it’s your hardware, sorry. You’re pretty close to minimum specification, and those are the minimum to make it run, not run well. You could check Task Manager to see whether you’re running out of RAM, which seems likely if it’s having more trouble when other programs are open too, but I would start thinking about saving for a new computer. Even a really cheap modern computer will be faster than your current spec.

          • Mike Hailey says:

            Thanks for the info

  49. Ledeane says:

    My print presets show up but no longer have any effect on the selected photo in LR 4.1. I use Win 7 and have used some of these presets since LR 2, and 3. How do I restore the function of these print presets? James Crocker

    • I think I’m going to need a bit more information on that one James. 4.1 (the one just released a couple of days ago, not the RC) was supposed to have fixed that, so if you’d like to post on the forum, we’ll help you troubleshoot.

      • ledeane says:

        Thanks Victoria, you are correct! I installed the latest 4.1 and it works properly. They did in fact fix it! jc

  50. Torrihoward says:

    Since upgrading to LR4 I have been unable to click on Edit in Elements. It use to bring up Elements and open the file. Now it does nothing…I upgraded to Elements 10 and made sure that my external setting in LR shows Elements 10 but no luck.

  51. Email not working on 27″ IMAC in Lightroom 4

    I have checked and re-checked and it keeps telling me it cannot send mail and to check my configuration. I have. It is correct. Port is right. User name and password is right…but I did change it 6 months ago, and used the old setup with LR 3. ANyone with help or suggestions?

  52. Hi Victoria. I moved to LR4 a month ago, have updated to 4.1 and find LR4 to be frustratingly slow particularly in the develop module. I’m working on a 2010 Macbook Pro with the following specs …
    10.7.4 – 8GB Ram – 2.66 Ghz Intel Core i7 Processor – 64Bit and its all on a solid state hard drive. I’ve not had any problems with my computer with any of my programmes running slow until now with LR4. I am a professional photographer and process anything from 100 to 2000 pictures per job and LR4 has added hours to my editing. Is this a technical issue that Adobe will fix sometime soon or have I done something wrong in my initial setup? I cannot go back to LR3 as the files from my cameras can only be processed in LR4 …. Thankyou

    • Hi Claude. Some people are still having issues, although it’s a small percentage of the userbase now, so let’s look at a few other possibilities. Which camera are you using now? Where are the files stored (i.e. internal SSD or external drive)? And where specifically are you seeing the speed issues?

      • HI Victoria thanks for your response. I am shooting with the Canon 5DMK3 and the Fuji XPro-1. The files are on my Macbook Pro SSD when i am editing and moved to external drives once i have finished the edit. I am noticing the ‘slowness’ in the develop module of LR4. For example when i am colour correcting, or dodging & burning etc this is when i really notice how slow it is. It takes longer for the image to change or generate from a pixelated image to a clear image and for me to see what i have just done. I’m talking 4 to 10 seconds per change i make per image or batch. So basically everything i do in the develop module is slower than LR3 and i constantly have the mac spinning colour wheel. All my files are rendered at 1:1 before i begin my processing and i don’t have any other programmes running when i am using LR. I’m hoping you can help … Thankyou so very much for your time

        • The 5D Mk3 are big files for it to be dealing with, so that’s mainly down to processing power, particularly as the new LR4 sliders are more processor intensive. I’m hoping that Adobe will be able to improve it further, but that will always be a bit slower than smaller files in LR3. There are a few things you can do to help though. There’s a known issue with Clarity/Highlights/Shadows conflicting with Noise Reduction. That should be fixed in 4.2, but can slow things down a bit. Lens Corrections are very processor intensive, so leaving those turned off until the end can help. The brush tools are also very processor intensive, although I’m told that closing the Filmstrip can help with that a little, as it’s bogging down a little trying to constantly refresh the previews. Finally, don’t worry about rendering 1:1 previews unless you need them for other purposes. They’re not used in Develop, apart from briefly showing the standard-sized preview when you first switch to a photo.

          • Hi again Victoria. Thanks so much for your repsonses! It has helped just a little bit. I have turned off film strip but I guess you should know I’m working on a second monitor. I use my laptop screen to see my Grid view or thumbnails and I process my files on an Eizo monitor. I will try all your other suggestions also and see how it goes. I really appreciate your assistance, thanks again!

  53. LightRoom 4 is really slow, I just upgraded to the new 2012 retina macbook pro, still a bit slow. but I found that if I turn off the Noice reduction switch when go through imgs it would be a big more faster. but still slow, Hope that one day Adobe can use GPU for accelerate this.

  54. Every aspect of LR4.1 is slower than LR3 on my machine: import, export, thumbnail generation, basic develop tools (stamp, saturation, contrast, etc.). Some functions are conservatively 10 to 20 times slower, no exhaggeration. Things that used to happpen essentially in real time as I moved sliders, now take 15 seconds or more to show up on the screen. I can essentially forget about trying to line up the gradient filter because the response is so slow and herky-jerky. An order of magnitude slower is not an upgrade in my book, also, the near 10x increase in the size of the program makes me wonder if Adobe has been taken over by Microsoft programmers. Now I’m looking at reinstalling LR3, but am concerned that the new catalogue I had to generate to get LR4 to work (another bug?) won’t be rearward compatible. I’ve been using LR since the version 1, and this is by the far the worst version – all the others simply worked. (If LR3 were relabeled and re-issued as an upgrade to LR4, we’d be marveling at the performance increase.) Machine: Dual core 2.2 ghz; 6 gb ram; 2 gb video card; 7200 sata and esata drives.

  55. Hello!
    Firstly i must say you have a sweet website!

    I was about to go nuts because of the snailo speed of Lightroom 4… But i think, at least in my case, that i found the answer.
    Due to my work, i rarely import single image, but more likely 100 raw images and above… and each time i applied my user preset (which was applied to all images) when importing. And that means every image was assigned to this preset, and this preset includes almost every tool there is in LR4 adjustments, even if a tiny one… And that was just a killer for any good workflow later on. Every additional adjustment to images took a century to process. I’ve tried to disable lens correction,nr etc.. nothing did much.
    And then i tried to import all the images without applying preset..instead of that i applied preset to each and every image separately in develop mode, and that worked for me..All is going smoothly now and without any pauses and glitches…
    I don’t have huge processor power, it’s 2.8ghz Core2 and 8gb Ram…
    ..anyhowitzer, if my option will be helpful to anyone, you’re welcome 😀

    • That’s really good that you’ve found a solution that works for you!!! I’d love to see what was included in that preset, just in case it offers some extra clues on what’s going wrong. It might be that you’re hitting the known bug with clarity/highlights/shadows combined with noise reduction, but there might be something else we haven’t come across yet.

  56. Jim Lawrence says:

    Hi, don’t wish to add my voice to the chorus re LR 4.1, but it’s definitely got some sluggishness issues. I disabled some of the suggested other things like everything except Library and Develop, and in Develop, closing everything but Basic editing unless I need to work over a specific image.
    The sliders have been a bit sluggish for me since LR 2.7…I use a Wacom 4×6 pen tablet though, that may be why. Have latest drivers etc.
    Sliders are a bit sticky. I resorted to clicking in the values such as for highlights, exposure etc. and typing in what I wanted, was a bit quicker that way, I got pretty good at it.
    I have a fairly robust new system I built a few months ago: Intel I7 2600K (not overclocked though), 16GB DDR 3, all SATA 3 SSD drives (Samsung 830, super stable, and Corsair GT, not so stable) which are smoking. Windows opens ready to work in 30 seconds after hitting the power button; LR opens in 4 seconds the first time, 2 seconds afterword. Ditto for PS CS6). And 1GB video card. Windows 7 Pro 64 bit. Certainly fast enough I would think to make LR work, if it was indeed not an over-loaded program, which it seems to be.
    I just finished a shoot and imported 9000 images at 1:1 in LR 4.1. I did have the Import settings at Punch, wasn’t paying attention, so that may have slowed things down…still…6 hours.
    But even with all these, it’s a fabulous program. I just hope that Adobe figures out how to make the things you really need to speed things up, like sliders, which really do drag down the performance, and of course other user friendly user tweaks. I concur that LR 3 and 2.7 were faster on my system.

    • Hi Jim. Some people are undoubtedly seeing issues, and it sounds like you’re unfortunately one of them, sorry! There are a still a couple of known issues with 4.1, most notably clarity, highlights or shadows can slow things down when combined with noise reduction. The new PV2012 settings will also be slightly slower than the old PV2010 ones as they’re much more much processor intensive. When you’re importing, if you’re in more of a hurry, you could import your 9000 photos first, and then set LR rendering the previews overnight.

  57. mariana says:

    hi . i have lightroom 4.1 but i have a question… i am missing some “tools” over the camera calibration section on the develop module… the ones i am missing are some like “landscape” and some others .. it only says embbeded … what can i do?

    • Hi Mariana. That’s likely because you’re looking at a rendered file – TIFF, PSD or JPEG – rather than a raw file. The camera profiles are only for raw files.

  58. I’m having an issue which I have seen on forums but no consensus re solution , I first noticed this issue after I installed LR4.1 , but I did that very soon after 4.0 so may be unrelated to upgrade.
    In Library my images have a slight blur to them , but as soon as I click to Develop the images sharpen markedly (to what they should be) , I generally use FILL view , but sometimes 1:1 , I saw one tip to select render 1:1 previews in Library;Previews but I just tried that & it didn’t make any difference. Equpment is Nikon D800/Sony PC , W7
    any ideas please ?

    • If you zoom into 1:1 view in both modules, do they match? I think you’re probably seeing a difference in the zoom methods used between modules, and it’s just showing up more because of the large file sizes, but there could be something else going on.

      • Thanks , 1:1 in Library & Develop seem very similair , but marked
        difference in quality with Library/Develop on Fill remains. I just remembered
        that someone mentioned ISO , that was on a high (1600 I think) ISO image , I
        just tried a lower ISO image & there appears to be no difference between
        Library & Develop in 1:1 or FILL.

        So , it seems to be a high ISO related issue but how do I know what is “Too”
        high ? will there be a fix for this ? I can work around but it’s not ideal.

        Unfortunately the D800’s resolution sometimes dictates a higher ISO than
        normal to achieve neccessary shutter speed so I suspect I am far from alone.

        • It may be related to the noise reduction then. I’d love to try to replicate it here, to see if it’s a bug or a side effect. Would you be ok with sending me a sample file? You could either drop it on my server (, username webupload, password 123) or send me a dropbox link. And also knowing the settings you’re using would help.

          • ok , it’s uploading now , what settings do you need ? was not developing image just doing an initial review of what I shot when I noticed issue

          • Martin Rosindale says:

            Hi Vic
            I’m getting the same issue and I use a Nikon D90, much smaller file sizes than a D800. It seems to be spasmodic, happens with some images not others. It’s not restricted to high ISO shots either.

          • Hi
            can you confirm reciept of files please ? didn’t get a confirmation at this end…

          • Got them Donald.

            What OS are you using? And Martin, you too? I can’t reproduce it here so far. Do you see the same if you import into a clean test catalog? And what sharpening and noise reduction and clarity settings are you using?

          • Windows 7 Home premium 64 bit Intel I5 & 6GB Ram
            AFAIK Sharpening , NR & Clarity are still at factory defaults , Sharp, amount = 25 ; rad = 1.0;detail=25 ; mask = 0 Noise Reduction Luminance =0 , other two greyed out. Clarity = 0. Not sure quite what you mean by a clean test catalog ? I have had this issue on 3 successive imports from different days all going into new 2012 sub folders for each day.

          • I mean go to File menu > New Catalog and just start a temporary catalog on your desktop or somewhere, and import that photo into it. That will rule out a problem with the preview cache (and you can delete that catalog and go back to your normal catalog afterwards)

          • Ok tried that no difference I’m afraid , in Library with FILL selected image is markedly less sharp than same image in Develop. Again I can detect no difference between Library & Develop @ 1:1 , which does not make sense to me ! Unfortunately I much prefer to use FILL for my initial image sort & it worked fine on LR3 with a Nikon D700….

          • Yep, I’ve got it replicated. I’m not so sure you’re going to see that one changed though, as I think it’s a result of the difference in zoom methods, but I’ll bug it anyway. Library’s using fixed size previews that it downsizes on the fly to show you at Fill size. Develop is downsizing and then applying settings. 1:1 view will always be the most accurate, but you should find that picking of the fixed zoom ratios (1:3 is pretty close to Fill here) will be a much better match.

          • Thanks for all your help Victoria , that gives me some options for workarounds. I’m curious as to why issue is only appearing on High MP images with High Iso but not High MP images with low Iso ? Is it a gradual drop off or is there an Iso level above which I am likely to encounter problems ?
            Will it make a difference if I use Library;Previews;Render 1:1 Previews . before I start viewing ?
            I will need to pick up one of your books from Amazon UK

          • That’s a good question Donald. Fancy dropping me one of the low ISO ones too, so I can compare? Without seeing it, I’d assume it’s to do with detail and noise reduction, but I could be wrong. I tend to use Fit more often than Fill, so I haven’t particularly noticed it on my own photos.

          • Ok , now I am REALLY confused , the image that I looked at last night that did not show issue is actually the same Iso as the one I sent you ! it’s coming to you now anyway. I only got D800 a few days ago & weather has been terrible so actually not shot much at all at “normal” ISO’s , hopefully we will get some sun @ weekend & I can play around more

          • Same orientation too?

          • Good point , no it wasn’t . Right just found a shot taken moments after one I sent but vertically orientated (same Iso) , vertical shot has issue , horizontal shot does not. Do you want me to send another vertical shot of same subject I just sent you horizontal one off ? Weather looks good for thurs so I will need to go out & shoot some low Iso vertical shots at local park.

  59. 1:1 Preview rendering doesn’t seem to work. I import, say 1000 images (5DMKII, RAW), and apply a default preset on import. Convert to DNG and render previews (overnight). Come back the next day to start culling, zoomed 1:1 in Lightroom Loupe and Fit on my 2nd monitor. As I start going through the images, after 10 or 15 I’ll start seeing “Loading…”. So I stop, select the rest of the images, and render 1:1 previews, and it renders 12 to 20 images. Start culling again, and after 10-20 images, start seeing “Loading…” again. So I stop, select the rest of the images, render 1:1 previews, and LR renders 30 – 60 images. Start culling, “Loading….”, render 1:1. Repeat until finished, or crazy, whichever comes first. This is all in Library; other than initial import settings, I haven’t touched Develop at all. So no reason to re-render.

    My library and catalog are on a Drobo S, connected via eSATA, with all 7200RPM drives and about 2.5TB *free space*. Running Windows 7 64, 12GB RAM, i7 processor. ACR Cache is on a separate drive from the OS. Catalog has about 50K images in it; I optimize on a regular basis. As a programmer, I could see maybe a half-second delay accessing the previews in the database, but this completely losing the 1:1 previews is unacceptable.

    It feels like a bug, or inadequate testing, in LR 4.1.

  60. Tyler Vance says:

    Hi, working with Nik tech support on this but no help.

    Nik color effect pro 4 run VERY slowly, and uses 100 per cent CPU.

    The Nik program runs fine in Ps4, and on my laptop

    Mac Pro, 16 GB ram, intel xeon dual prosc.



  61. I’m having issues finishing up editing a recent photo session and found this forum. I’m probably missing it, but I don’t see what I should be disabling to make LR4.1 run faster for me. I’m working on a brand spaking new iMac, so I really don’t think there should be speed issues. It’s very disappointing as my husband and I are new to LR and were really hoping to speed up our processing by switching over! Right now I have 600 images imported at 1:1, and I’ve flagged and am filtering 200 of them to edit. I’m done editing the 200 and was trying to just scroll through each of them as a final look, and it is taking forever (like 30 seconds) for it to show each one. I just get “Loading”. This is horrible! What can I do to make it better? Especially since we don’t have LR3 to fall back on? Please help – it’s making me crazy! :-)

  62. Matthew Saville says:

    I just switched from a 128 GB SSD to a 256 GB SSD, (same exact brand and speeds, Crucial M4) …and I did a fresh install of Windows 7 64bit. My system is running smoother than ever, of course, however I have noticed a weird difference in my benchmark speed tests. All of a sudden my 1:1 preview render time has gone from ~2-3 seconds to 4-8 seconds. Could it be different processing applied affects the render time for 1:1’s by such a significant amount? I can get the 1:1 preview time down to 3.85 seconds if I turn off all sharpening, noise reduction, and lens corrections.

    The weird thing is that even back when I had my OS and cache on the 128 GB SSD but my LRCAT and RAW files on a secondary hybrid drive, my 1:1 render time was still never more than 3-4 seconds.

    I’ve tried fiddling with all of those page file / virtual memory settings, to try and optimize the new SSD’s performance, but I can’t seem to put a noticeable dent in the render time.

    Also, I’ve been using Paddy for Lightroom and I’d love to hear if anyone has any tips on how to get that whole system running as fast as possibe. I process 10-20,00 RAW images every week, as post-production is my full-time job.

    Another friend with a nearly identical machine renders 1:1 previews in ~2.something seconds. I have an Asus RoG laptop, i7 core witht 8 GB RAM and 1.5 GB graphics, Crucial M4 SSD (6Gbit, HDtune says 495 MB/sec average transfer speed)

    Any ideas?

    • Very odd Matt! So was the 2-3 seconds on LR3 and the 4-8 seconds on LR4, or are we talking LR4 all the way? What if you set LR4 to PV2010? The new processing, particularly at non-default settings is definitely a bit slower than LR3 because the new controls are more processor intensive, but something certainly sounds odd.

      Have you looked at Task Manager while you’re working? I’ve heard of a few people who found that it was only using a single CPU and chance an Affinity setting did the trick. It certainly sounds like a problem processing data. Also double check that your anti virus isn’t checking the files, the catalog or the previews, as that could slow it down.

  63. I am a Mac Os Lion user of Lightroom 4. I already have LR3 on the computer, hence I have an LR3.2.Icrat catalog. When I installed LR4, the process asked to upgrade current catalog which I did. Now when I open LR4, at the top of the page, it shows the new LR4 symbol but also “Lightroom3.2-2.Icrat-Adobe Photoshop Lightroom-Library”. And under “Catalog Settings” it has /Pictures/Lightroom3.2. It looks to me as if it just duplicated the previous library. Is this what’s suppose to happen? The box the software came in certainly says Lightroom 4. I am confused. When I go into Finder to LR4 there isn’t a LR4.Icrat catalog file. What will happen when I import new photos into LR4? Will it create an LR4.Icrat catalog at that point? Also, perhaps another issue. When I’ve opened LR4 and it comes up with the above mentioned library notation at the top of the page, the “Develop” module is the LR3 version. I have to go to “Settings”-Process- 2012(Current) to change the “Develop module ” to LR4. Is this right? And do I have to do it for each and every photo from the previous LR3 catalog? While I’m on the subject of LR4, how about another question or observation? When I’m just even looking at some photos and not doing any developing/changes most times when I quit the application, it tells me that it’s still writing to the .xmp file. Is this right?

    • Realspear says:

      This happened to me also and after a few months, I still haven’t found a way to convert the catalog. I’ve removed it, reinstalled it, etc etc. However, I have fixed the import so everything opens with PV2012. You just have to create a preset that specifies PV2012 and then use it as an import preset. I’d still like to find the real fix.

      • Thanks Realspear. Maybe some other users of this forum have found a solution to the catalog issue and will share it or at least say there’s no hope for it.

        • Hi Diane. This is my blog, so there’s a limited amount of interaction here, but the forum’s always a great place to find information and ask questions. Sorry it’s taken me a while to reply. I’m actually on vacation at the moment so only popping in periodically.

          Duplicating the catalog is the expected behavior – they just add a -2 to the end of the name. If you close LR, you can rename the file using Finder. Rename the Previews to match. You’ll find further instructions in my knowlegebase here:

          Have a read of this for Process Versions too: Long story short, I’d recommend leaving photos you’ve already processed set to PV2010, unless you’re planning on reprocessing them. For photos that are already in the catalog but are unprocessed, you can press the Reset button to update them to PV2012, and any new imports will come in as PV2012 too.

          And finally, the XMP warning is because you likely have ‘automatically write settings to xmp’ checked in the Catalog Settings dialog. There’s a quick intro to xmp here:

          • Realspear says:

            Victoria – I think the issue that Diane and I are both having is that *new* photos are not imported with PV2012 with the -2 catalog that Lightroom created. I guess the question is whether a second catalog is necessary in order to have photos automatically import with the PV2012. The problem I have is that I need to make sure that every new import preset specifies PV2012 whereas I think this should be automatic. Does simply renaming from 3-2 to 4 make the import change?

          • Do they import as PV2012 if *no* preset is applied? That’s the key here. If that’s not working, then we have some investigation to do.

            The defaults should automatically be set to PV2012 for new photos, but we could try resetting the defaults if that’s not working.

            It’s not catalog-specific, but if you’re applying older presets set to older process versions, that could certainly explain it. There is a solution for that too, but let’s just confirm that’s the problem first.

          • Realspear says:

            They import as PV2010 without any preset.

          • And these are definitely new photos that don’t already have xmp data? Ok, let’s try resetting the defaults. Go to Develop menu > Set Default Settings and press the Restore Adobe Defaults button. Then press Reset to double check that it sets the photo to PV2012, before importing new photos.

          • Realspear says:

            Hi Victoria – Thanks , that worked.

  64. Phil Indyblanks says:

    I’ve been having a recurring issue with LR4 when importing. I’m shooting raw+Jpeg on a Nikon d700. When I import, I deselect all, and switch to Loupe view and go through each shot and select the keepers. On almost every import thus far with LR4, the loupe view will switch to a low rez thumbnail view of that photo, and every subsequent photo on that roll. There’s no rhyme or reason as to which photo will trigger this as far as I can tell. Any thoughts on this?

  65. I’ve been reading a lot of comments on the slowness of LR4 and 4.1 so here’s my take from my experience.
    I’m updated with the latest versions, and running on:
    * a homebuilt Asus P8Z68 Deluxe/Gen3 motherboard
    * Intel i7 2600K CPU
    * Corsair liquid CPU cooler
    * 16GB DDR III memory
    * all SSD drives (4 x 256 Samsung 830s, and they are awesomely stable and very fast — I had two Corsair Force GTs RMAd out of three, BTW),
    * nVidia 1GB video card, model 7900 I think, driving two Dell 24″ monitors.
    OS: Windows 7 64 bit.

    I was using a small Intuos 4 tablet from Wacom and having sticky sliders. I suspected there was just a bit too little resolution for two big screens, so I just got the Intuos 5 medium tablet (I’d always had a medium before – for almost 20 years!) and the slider action is much smoother, no sticking anymore and I”m back to normal on that.Also, the speed issue: I import from the camera’s CF disk (Canon 50D) onto my SSD, then import to LR from there. Rendering to 1:1, a must for my work, takes right around 2 seconds per 16-18MB image. That’s plenty fast enough and conforms to the previous 2.7 version – I went from that straight to 4, then upgraded to 4.1 from there.
    I don’t have a need for some of the more computationally intense details that many have posted about, straight processing is mostly my game, but Lightroom has radically changed how I process images and it’s plenty fast for my needs — I’m a professional aviation photographer for U.S. and overseas flying magazines.

    • That’s good to hear Jim. Very interesting to hear about your Wacom experience – that makes sense. Older Wacom drivers can also be an issue, so anyone having issues could try updating those too.

  66. LR 4.1 is so slow that I quit using it altogether. I wish I could get my money back.

    • Sorry to hear that Erik. Have you tried LR4 in a clean user account to rule out corrupted files? If so, it might be a driver conflict. If you’d like a hand troubleshooting, feel free to post on the forum and we’ll narrow down everything we can.

      • It was installed in a brand new – literally 2 days old – high end PC. No driver issues or corrupt profiles. I have also tried all of the so-called fixes on the ‘Net – renamed preference files, etc…no effect.
        My biggest peeve is that Adobe seems to persist in blaming the users. “Your computer is too slow, you have corrupted something, you have a driver conflict,” etc…Come on Adobe, the product has been out for months, and its clearly still Beta software at best. And, it seems that the faster your computer (MAC or PC) the worse it seems to perform.
        Computer specs as follows:
        Lightroom version: 4.1 [829322]
        Operating system: Windows 7 Business Edition
        Version: 6.1 [7601]
        Application architecture: x64
        System architecture: x64
        Physical processor count: 12
        Processor speed: 3.2 GHz
        Built-in memory: 16333.0 MB
        Real memory available to Lightroom: 16333.0 MB
        Real memory used by Lightroom: 292.2 MB (1.7%)
        Virtual memory used by Lightroom: 295.6 MB
        Memory cache size: 195.2 MB
        System DPI setting: 96 DPI
        Desktop composition enabled: Yes
        Displays: 1) 1920×1080
        Application folder: C:Program FilesAdobeAdobe Photoshop Lightroom 4.1
        Library Path: C:UsersErikPicturesLightroomLightroom 4 Catalog.lrcat
        Settings Folder: C:UsersErikAppDataRoamingAdobeLightroom
        Adapter #1: Vendor : 10de
        Device : 1189
        Subsystem : 126519da
        Revision : a1
        Video Memory : 1994
        AudioDeviceIOBlockSize: 1024
        AudioDeviceName: Speakers (Realtek High Definition Audio)
        AudioDeviceNumberOfChannels: 2
        AudioDeviceSampleRate: 44100
        Build: Uninitialized
        Direct2DEnabled: false
        GL_ALPHA_BITS: 0
        GL_BLUE_BITS: 8
        GL_GREEN_BITS: 8
        GL_MAX_3D_TEXTURE_SIZE: 2048
        GL_MAX_TEXTURE_SIZE: 16384
        GL_MAX_VIEWPORT_DIMS: 16384,16384
        GL_RED_BITS: 8
        GL_RENDERER: GeForce GTX 670/PCIe/SSE2
        GL_SHADING_LANGUAGE_VERSION: 4.20 NVIDIA via Cg compiler
        GL_VENDOR: NVIDIA Corporation
        GL_VERSION: 4.2.0
        OGLEnabled: true
        OGLPresent: true
        GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_ES2_compatibility GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_image_load_store GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_subroutine GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_swizzle GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_texture_type_2_10_10_10_REV GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KTX_buffer_region GL_NV_alpha_test GL_NV_bindless_texture GL_NV_blend_minmax GL_NV_blend_square GL_NV_complex_primitives GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_explicit_multisample GL_NV_fbo_color_attachments GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragdepth GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_lod_clamp GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_OES_depth24 GL_OES_depth32 GL_OES_depth_texture GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object GL_OES_vertex_half_float GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

        • I completely understand your frustration Erik. The problem they’re having is they can’t reproduce most of the issues now. I agree that 4.0 had some major problems, but as of 4.1, it’s a small percentage of users that are still having issues. That means there has to be a conflict with something on your machine, otherwise it would be happening to everyone. That’s not to stay that the problem IS you or your machine – just that it’s really tough to track down when it’s only affecting some people. Which bits specifically are you finding slow? What cameras are you using? If you watch Task Manager, is it hitting all CPU’s when you move the Develop sliders? Do you see the same slowness with photos set to PV2010?

          • First of all, let me say that I love your site and I really
            appreciate all that you do for the LR community!

            Import is very slow. On my old computer, which hardware wise
            was maybe 1/4 as fast as the computer I have now and running LR 3.6, the import
            was significantly faster. My camera is a Canon 5D classic – a 7 year old camera
            now, and my catalog is very small as well, since the product is too slow to
            really use, I have not imported very much into it.

            Develop module is painfully slow. All 12 CPUs are active
            when I move a slider, but active at like 1-2%. I have 16 GB of RAM, but LR will
            only use like 4 of that at most. I just cannot accept that PV2012 is so much more
            intensive that it bogs down a computer as fast as mine – and it clearly does
            not when I see 1% CPU usage and 12 GB of RAM un-used. I honestly see no difference
            when I switch back to PV2010. I have a solid state hard drive, but it
            “feels” like LR is struggling to pull data from a floppy disk or
            something – everything just stops for 1-5 seconds until the application “catches-up.”

            Adobe honestly does not seem to want to help, as when you
            contact support, you get into an endless loop of Level 1 support people that
            just read the same 4-5 things off a script until that is exhausted, at which point,
            they tell you that you need to format your hard drive and load everything again
            or that you have a “driver conflict” or that your (brand new) computer is not
            fast enough, or some other useless advice. If you open Google and type in, “adobe
            lightroom 4.1 slow” you get 198,000 hits…so I am not sure how limited this is…

            If I was a professional photographer I would have given up
            long before now. There is no way that I could spend hours and hours just going
            through one small photo-shoot in LR.

          • I am a professional photographer and I have lost weeks of work trying to resolve this issue. I like you keep getting level 1 support from Adobe with no real solutions. My 6T Drobo has 140,000 images cataloged through Lightroom in a couple of different catalogs, all of which are behaving the same, even the small ones. To start over again with different software would be a nightmare. I’ve been using Adobe software for 25 years and wish they could be honest with me and say there is an issue but in the meantime I am trying and retrying every solution I find with no relief. This is a busy time for me and I can’t afford to loose any more time. HELP!

          • Anne, it’d be easier to talk on the forum than it is here – please start a thread and I’ll do everything I can to help.

          • Copy one of the small catalogs from your drobo to your local disk on the LR machine, i think i read that network catalogs wasent supported or was slow at least. and that i think is what messing your drobo setup.

          • I do my best Erik. I wish I had all the answers, but I’m as confused as everyone else on this one.

            The CPU low activity does sound particularly odd. I’d expect PV2010 to run at the same speed (almost) as LR3, so that’s ringing a few alarm bells. Have you seen the posts about an Affinity setting? Double checked that one?

          • I have checked that and all cores are set to run. So strange that they run at 1% while the application just drags…

          • That really is strange Erik, and would certainly explain why it’s so slow. Moving a slider (or exporting, or building previews) should hit all cores pretty seriously, so that could be a valuable clue. If you’re up for a little more troubleshooting, there was a discussion about shutting off some of the cores (I think it was ever other core) helping. If we can narrow down what’s causing the slowness, hopefully they can get a fix in there for you to utilise your lovely new hardware properly.

          • I tried experimenting with turning off some of the cores in Affinity. I first tried just half of them and then tried every other one. Subjectuvely it felt a little better with only half of the cores active and no diffeence with every other one, but I have not used a stopwatch to verify.
            If it is indeed faster with less cores than more, and as also seems to be the case, LR is incapable of using more than 4GB of RAM, this is clearly a major coding failure. This would explain why it is not faster on high-end hardware than it is on old hardware – the coding seems unable to take advantage of multiple cores (Or, say more than 4 cores) and more than 4GB of RAM – now when it is and has been for awhile now, common for even mid-range computers to come with 6 core CPUs and 8 to 12 GB of RAM.

          • It should be taking advantage of multiple cores – I regularly see mine maxing out my 8 cores, especially when running multiple exports. The RAM is a little more limited, and I agree they could make better use of it, although extra RAM usage wouldn’t generally help with slider movements, but could help with returning to recent images.

          • Thatt is just it – it uses all 12 – but at 1% or less, and works fasetr when I diasble half of them. That says “programming issue” without a doubt.

          • Just for fun I downloaded a copy of Corel’s AfterShot Pro and was AMAZED at the speed difference. Don’t take my word for it, download a 30 day trial and then import a couple hundred images – it will take maybe 5 seconds flat to generate full previews. I am not kidding…the only thing I don’t like is that it does not read DNG files.Once that feature is added, I am done with LR.
            Oh, and this product costs $59.95

  67. Hannes Löhr says:

    Hurray, yippee!
    I think i got rid of my performance problem. I deleted all of my Develop Presets and set all plugins (Zusatzmodul) inactive. Maybe that some aren’t compatible with LR4, but which?
    Now i can change the remaining standard presets without any delay as switch between my folders, which before lasts for felt eternities.
    Hannes Löhr

    • That’s great news Hannes!!! You could start adding back your presets a few at a time and see if you can narrow it down to the problem one – and if you find it, I’d love to be able to pass it back to Adobe to see if they can find and solve the problem with it.

  68. I’ve been having issues with exporting in bulk with watermarks in 4.1. It will watermark some, and then skip a bunch after that. I am getting really irritated, and I can’t productively work like this. Please help me.

  69. Phil Scottt says:

    Hi Victoria, I Have an issue with lightroom 4 where some times when I import pre-numbered images from my HD lightroom dosnt keep the numerical order of the files and usually starts 1, 10, 100,101 then at 109, 110, 11, 112 etc
    very frustrating as I want to keep them in the same order I have on HD

  70. simon young says:

    I was getting frustrated with LR4.1 speed in switching between pictures (even though they have 1:1 previews cached). It was taking around a second (I’m that impatient). I deleted all of the presets that I had made in LR3 and reset the default development settings back to Adobe (turns off lens correction and presumably sets the preview to display instantly without any additional adjustments). I can now flick between pictures with no lag. Make my selections and then adjust. I’ve yet to make any presets but I think this may be the way to go. as the revious presets were imported from LR3.


    • That’s good news Simon! There have been some reports of corrupted presets causing issues, so you may find you can gradually add back your old presets to figure out which is causing the problem.

  71. Hi I have Lightroom 4.1 installed and I’m having a problem were when I adjust my pictures in develop mode they look very sharp and clear and I’m very happy with the results but when I go back to libary mode or export them they look very very grainy and everything I have done in the develop mode has been lost I have tried changing the previews to 1.1 but still no good pls help

  72. Evrim Icoz says:

    Victoria, Evrim from DWF here. I could not find a solution to this. If I import say 10 files from a folder (WIndows 7 64b, 16GB ram SSD Drive), and if they are the only files in that folder, it is fast. But if they are part of, say a wedding of 3000 images, but I only import those 10, it is forever.

    Another friend has the same issue.

  73. Adrian Bell says:

    My lightroom 4 is stuck on “preparing to export” and I can’t quit or exit it
    I use an iMac its a 200 pic slideshow i was trying to export any ideas?

  74. VolumeSavings says:

    Has anyone experienced the loss of both CR2 and DNG files when CR2 files are imported and converted to DNG?

  75. Hi, I’ve been using LR3 and recently moved on to LR4. Although I like
    the new interface, some things that worked just fine with LR3, don’t
    always seem to work in LR4, or don’t work at all.

    For instance, when I export my quick selection to a specific folder and
    want the images to be opened in Photoshop CS6, PS starts, but
    nothing happens. The images are exported, so that part is working fine,
    but they do not open in PS. When I export them again, and
    overwrite the exported images with the new ones, it suddenly does

    Another thing that doesn’t always work is when I put my CF card in the
    reader, sometimes the import window opens up automatically (like in
    LR3), and sometimes it doesn’t… and then some previews don’t even show up in the
    import window, or it shows a message saying the a preview is not available
    for this file…

    I really feel the LR4 is slower then LR3, so that’s more like a
    downgrade, then an upgrade. Also starting up LR4 takes much more time
    then LR3.

    I’m really considering to reinstall LR3, and send LR4, if I can’t alter these mishaps. And btw: and just so you know: I just installed 4.2 on my Mac: still no good.

  76. Murdo Messer says:

    Light Room 4.1 cannot see image thumbnails on import sometimes, then hangs on import, status bar does not move. Have to close program and restart. Sometimes works. Usually does not, have to reboot computer. Also when Lightroom 4.1 is closed it still appears in the processes section of the task manager and I cannot reopen Lightroom 4.1 unless I stop the process. Not being able to import images is a pain in the ass.

  77. Martin Rosindale says:

    LR 4.2 now out and installed. Processing is as good as ever and it seems a bit faster than 4.1 but a new issue has appeared in that importing is now really s..l..o..w! It takes twice as long to import NEF files from my D90 and sometimes misses shots on the card because the file ‘could not be read’. Re-importing usually works OK. I’m not doing anything different. This is irritating rather than a serious problem but I wonder what’s going on at Adobe.
    Anyone else noticed this new issue with 4.2?

    • Using a card reader or cable Martin?

    • Realspear says:

      I have downloaded from two shoots since installing 4.2, both about 4GB, both from card readers, one from CF and one from SD. I didn’t see any change in speed or integrity. I have had the problem in the past with missing previews on download, but not with 4.2.

    • I haven’t seen this exact issue either, but have noticed that the import previews are now no longer in order. I use to see them in date taken order, but now they seem to be all over the place. are they being read async from card via a couple of threads (sorry for tech speak) and then not sorted, or has the default setting been changed?

  78. Tara Wiley says:

    when I import my photos into LR, they look fine at first and then
    suddenly get lighter and contrastier and the tone changes. Any idea why
    that would possibly happen? It did not start doing it until yesterday.

  79. I have a new build, AMD 8 core 3.6 mhz processor 32 gig ram and 3 terabyte hard drives and LR 4 keeps crashing and corrupting the catalog. I have tried reloading. Now getting the blue screen of death. not sure what is going on. No other programs are causing any issues. Ran a ram test and it came back OK

    • Windows shouldn’t let any program blue screen a computer, so that points to a hardware issue. What ram test did you use? LR finds bad RAM quicker than most other programs, so that would still be my first port of call. Memtest is my usual choice for a really thorough memory test. Other than that, try running in safe mode to exclude some possible driver conflicts.

  80. I am having difficulty installing the trial version, even though it goes through the installation process fine and is successful. If so, where is it? And how do I open it. When I try to open it, the whole installation process wants to begin again. Help.

  81. I’ve been using Lightroom for a while now. And recently updated to Lightroom 4 from Lightroom 3.

    It appears that the clarity tool when editing the picture for some reason every so often makes a lot of the picture look blackened. For example.

    I’ve never had this issue before till now. So, I don’t know what to do about it. I have no other problems otherwise. It runs decently well enough. It’s faster than Lightroom 3 anyhow.

    • Can I see your settings for that photo Friedrich? That’s certainly not an effect I’d expect to see at normal settings. The Clarity is much stronger and has a different effect in Pv2012, so you’ll need lower values.

  82. My Lightroom 3 somehow says that all 4000 images are missing with a question mark next to it and will not allow me to edit any of them anymore. I have read about many with a similar problem. Is this a bug with LR3 and would upgrading to 4 fix this or have an upgraded version with the same issue in my catalog? Thanks for any help you can provide.

  83. TCMercury says:

    I’m having real trouble even selecting images in Library. Some will highlight when I hove over them but others don’t react even when I click them. Is this just slow processing or some crazy pro feature that I don’t understand?

  84. TCMercury says:

    I’m having real trouble even selecting images in Library. Some will highlight when I hove over them but others don’t react even when I click them. Is this just slow processing or some crazy pro feature that I don’t understand?

  85. TCMercury says:

    I’m having real trouble even selecting images in Library. Some will highlight when I hove over them but others don’t react even when I click them. Is this just slow processing or some crazy pro feature that I don’t understand?

    • What computer specs and Lightroom version? Are you fully updated?

      • TCMercury says:

        I’m running Lightroom 4.4 on Mountain Lion, 2008 Macbook with 2Ghz Intel Core 2 Duo processor and upgraded 8GB RAM (1067 Mhz). It seems to be above the system requirements and once I’m actually viewing a photo it runs perfectly reasonably. It’s just rather temperamental about which photos it will let me click on and which I need to get to using arrow keys.

        • Does restarting help? I’ve seen the same thing in the past, but never managed to find reproducible steps to get it into that state. Something in the back of my mind makes me think it was related to Spaces, but don’t quite me on that!

          • TCMercury says:

            Oddly, I just tried it again now and it’s working sweet as a nut. Possibly it was just an odd issue on startup. I really haven’t used it much yet (saving it for a new camera in about a week’s time) but it’s running nice and smoothly now with no problems. I did delete a decent amount from my HDD as spring cleaning in between startups though, so it may have just been a lack of disk space making it all confused!

          • Excellent, hopefully you won’t see it again!

  86. MaryMag says:

    I am unable to print from LR4. Message is “Could not start print job.” This seems to be a message for Adobe products. Can print from LR5 beta. Have deleted the preference file, uninstalled and reinstalled LR4 to no avail. Appreciate a solution if possible. Thanks

  87. MaryMag says:

    I am unable to print from LR4. Message is “Could not start print job.” This seems to be a message for Adobe products. Can print from LR5 beta. Have deleted the preference file, uninstalled and reinstalled LR4 to no avail. Appreciate a solution if possible. Thanks

  88. Grady Richardson says:

    Running 4.4 under Window 7 sp 1 64 bit. Imports started taking forever and then just stopped working. When I click on the import button I get the spinning blue doughnut. I can’t even end the program – it grays-out but stays there. Can’t be ended with Task Manager either – the program seems to close, but it’s still listed as a process and is holding memory. I have to reboot the machine to clear it out. I tried reinstalling the program – no effect.

    Is there any procedure to fix this?

    • I am having this exact same issue. Soon as I try to click import, it tells me the program is not responding, it took me 6 hours to import 4 pictures and put them into a catalog. I would really like to see this issue fixed as I need the program for my schooling.

      • Hi Grady & LTed, what else is attached to your computers? Mobile phones have been a major suspect in import issues recently. Also are there any videos on the card? That’s come up a few times as a possibility, although without a logical reason.

    • exact same problem with similar specs did an fix come up for this

      • Did you try the suggestion to check what else is connected to the computer? Trying to read a whole large network drive, internet drive (i.e. JungleDisk) or even a phone can make it grind to a halt.

  89. Jack Farrell says:

    I am using LR4.4 . I tried to uoload several photos that I took yesterday, It appears that they came in but only a greyed out box appears indicating my 100 ish photos but no photos. Then I check further and non of my 1000’s of photos are visible, just the greyed out boxes. Please help!!!

  90. Candice says:

    I am pretty sure you have answered this before… but i could not for the life of me find it in this thread…
    Randomly it seems that when I export jpg files from LR4 it does so at very small resolutions. so that when they go to print even a 4×6 is unrecognizable. I am assuming I am somehow creating thumbnails?
    The export settings are set to 300 ppi and come from large raw images… what is happening?

  91. Victoria Rex,
    Been using Photoshop since forever. Just purchased LR4 and I have one big issue. I hate the dark panels. I went into Preferences and tried changing things to Lt Gray or White – no dice. What am I doing wrong? The black panels are a deal breaker for me. I refuse to use LR with dark panels. Another minor issue is that I work offline. When I fire up LR, it wants to connect to the Adobe/NSA Mothership. I click it off but it’s danged annoying. Hope you can help. Thanks ever so……..Leon

  92. Victoria, Thanks much for your quick reply. So I can’t change the black panels. I don’t know why anyone thought black letters on a dark gray background was a good idea. It’s okay I suppose if you’re just dabbling around but I restore 35mm slides and I need to move rapidly from one image to the next. That stupid black background really puts a damper on workflow velocity. In my opinion, this is the classic case of a company thinking they’re smarter than their customer. The Adobe/NSA crack was a comment on the symbiotic and transparent relationship between high-tech corporations and the state. Thanks again, Victoria. Kind Regards………..Leon

    • Personally I’ve learned to love the darker interface – it doesn’t distract from the image. You can change the colour of the area directly around the image itself by right-clicking though – just the panels you can’t change.

      • Thanks again, Victoria. I bought LR because I’d been watching Serge Ramelli with LR on YouTube and the man is so cool I said, I have to have this. Didn’t think about the interface problem. I use Photoshop; Illustrator; Indesign; Dreamweaver; Blender; Premiere Pro; After Effects; and Word. Plus several more obscure applications. They all have normal black-on-white panels – not black-on-gray. Okay, I’ll stop whining now. If you say it doesn’t bother you, I’ll try and make the effort. All the Best. – Leon

  93. Hi
    I’ve always used LR and recently bumped up to LR4…..I ‘ve come across a problem and can’t seem to get answers: My skin softening tool just suddenly didn’t want to work not even if I slide the slider which ever way nothing wants to happen!

    • Hi Bea, sorry for the delay replying. Check your Flow and Density sliders in the adjustment brush panel – that’s the usual suspect if a brush doesn’t seem to do anything.

  94. Dear Lightroom Queen, please help! I have an a couple of thousand offline or missing photographs. I’ve followed steps to restore to no avail. They are actually all sitting in a folder that Lightroom self titled Missing Photographs. The folder is located in the catalog, just below Previous Import. Thoughts or suggestions? I can’t access my photos.
    Thank you so much

    • Hi Carly. That’s a special kind of collection, which has grouped all of the missing files together, just so you know which ones are missing. Now you just need to go find them on the hard drive. Do you know where on the hard drive those photos are now stored? If you click on the question mark in the corner of the thumbnail, Lightroom will tell you where it was stored the last time it saw it.

  95. Hi I’m using Lightroom 4 version, how to clear the background when the photos are very dark? (night captured photos) i adjust “Exposure”but background is not much clear, is there any method that i can edit night photos to look like day time photos in Lightroom 4 .please advise me on this, i have so many photos to edit but those are not cleared as much my Company expected. i have to re-edit them. your help is greatly appreciated in this regard.

  96. My company uses thousands of photos. We’ve been importing our iPhoto
    library of pictures into Lighroom (5), organizing pictures by folder
    titles and adding keywords. We’ve gotten about 20% of the keyword work
    done. What we need to do is find a way for our employees to be able to
    web access these photos and search them based on the keywords. Any one
    out there know how to do this? Thanks.

  97. Late to the party, but I think LR 4 is suffering from a threading issue. I’m running Win7 on an i7 2700K with 16GB of 1600Mhz memory, and 2 560 GTX in SLI, so by no means should LR Run as poorly as it does, and yet It’s been practically unusable. any action takes 5-10 seconds to respond within the Develop module. That is, at least, until I disabled the Detail component. For whatever reason, LR is constantly recalculating the sharpening and noise reduction, even when I’ve made no change to the image.
    After hitting the little switch to disable Detail, LR is running at the speeds I expect.
    Note that I’m using 4.4, and with 5 out, I don’t expect Adobe to fix this issue for users of 4, which means this may well be my first and last version of Lightroom.

    • Hi Chris, yes, the Noise Reduction particularly is incredibly processor intensive when combined with PV2012. They’ve done a lot of additional tuning in LR5, so you might like to try the 5.2RC and see if you’re happier with it.

      • I am having the same issue with basically the same system as Chris in LR5 so what should I try now? I have tried everything! My custom bud computer is less than 3 weeks old and I installed LR5 and PS Elements 11 on it the day I set it up and have yet been able to have a successful editing session as I get two or three photos developed and it will freeze crashing my whole system. Sometimes it happens when I am simply thumbing through my photos. Adobe has been little help.
        I see many threads related to this very issue out on the web yet no solid solution….
        Can you help?

        • Drop me an email at and we’ll see what we can track down. Crashing your whole system sounds like a conflict with a driver or a hardware issue. There’s a big difference between it being slow, which is what most of the LR4 threads were about, as opposed to it freezing. Windows shouldn’t allow a program to take down the whole system, so I think there’s more going on there.

  98. Hi there, I have a problem exporting my book on pdf with LR4.4, All the pictures look fade on the pdf. The pictures are all RAW files. Any help?

  99. I’ve been using hdr efex pro 2 for a year with no problem on Lightroom 4. Why is it now crashing all the time when export with presets?

  100. Did the “Edit in” Workflow for External Editors/Plug-ins issue ever get resolved? I’m using Lightroom 4.4 and wanted to try NIK plug-ins, but they don’t open.

  101. Is there a bug or problem with increased noise when exporting pictures out of Lightroom 4?

  102. Occasionally, I will notice that an image doesn’t export identically to what I see in my develop module for LR4. I shoot RAW. The exported jpeg will be less sharp, have less contrast, and the color may even change slightly.

    I DO NOT resize to fit, res at 300 ppi, color space set for sRGB. I have tried messing with sharpening output (low-high), but that doesn’t make enough of a difference to make up for the lost sharpening and contrast that is happening upon export. I’ve even tried keeping the quality at 100%. My LR4 is up to date.

    • The slight colour change will be because you’re exporting to a small colour space – sRGB. As far as the sharpness/contrast goes, are you comparing against 1:1 view, or something smaller?

      Import the exported photo back into LR and compare them at 1:1 view to see what the differences actually are.

  103. Genesis Curiel says:


    I have been asking around and going around to different companies, that teach light room, and I have encountered some issues that possibly you may or may not know the answer to.

    When editing the images in the develop module and using the brush to sharpen the face or an object, then toggling over the Library to see the image the sharpening has not been kept, everything else has, the color, vignette etc.. Even when exported the images that have been sharpened did not get transfer or exported. I went to the Adobe lightroom forum and asked the same question. I was appreciative for the responses, but may assumed it was exporting, but I do not touch any of the export thing. Also, when showing the lightroom people at exporting they thought it was weird it took so long to export the images. Thats not my main concern, it’s mostly the sharpening. Again, in the Develop Module the sharpening looks great, when exporting or viewing in Library module the sharping goes away.

    Any suggestions please? should I bite the bullet and just get light room 5, I use light room 4.4.
    Thank you in advance and look forward for any words of encouragement.

    • Can you double check both Library and Develop at 1:1 view, not Fit view. That’ll be the most accurate.

      • Genesis Curiel says:

        Thank you for replying!! Yes I do the comparison at 1:1. And in the Develop module you can see the editing which I have done to the picture and when I go to the Library module, all the colors will be there except for the sharpening. I showed some people who teach workshops for light room and they were stumped. It was at 1:1 where you can see the image and more precisely their faces as I used the brush to really get a nice crisp face and then when in Library or in exported image all of the sharpening goes away.

        Any ideas?

        Again thank you for replying.

        • Screenshots wouldn’t be a bad place to start. You could certainly try the 5.3 trial – don’t upgrade your catalog just yet, but try importing that one photo with settings, and see if the same happens there.

  104. When I see my images in my catalog… and when I export them as tiff they are tack sharp. If i export a small version… like one to give away… those are all blurry and they are all jogs… but the tiff looks just like it did in develop or library… how do i fix this?

  105. I have LR4 installed on my iMac desktop but when I connect my SanDisk card reader or my Nikon D4 I am unable to view them in loop view to decide on which ones to import. Any ideas where I’m going wrong or what I’m missing.

  106. Mrinal Bhattacherjee says:

    I had LR4.2 installed on my system to edit Nikon d5100 photos. Recently, I took some snaps using a d5200. I imported those photos to my system using card reader. These files are being shown properly in ViewNX2, but when I imported these files in LR4.2, it was unable to read the files. After googling, I came to know that from LR4.3 version d5200 RAW files are supported. So, I downloaded and installed the LR4.3. During importing the files, I got the same error.

    Even after that, I upgraded my LR to 4.4, but still getting the same error. Could you please help me at the earliest? Thanks in advance.

    FYR, the error I’m getting is: While importing it says, preview unavailable for this file. If I still click on import and go to Develop window, it shows something like “files are not being recognized”.

    • Hi Mrinal, what’s the exact message you’re getting when importing? And the exact message in Develop?

      • Mrinal Bhattacherjee says:

        During import when I’m selecting the folder from where the photos will be added, it is showing “Preview unavailable for his file”.

        If I still click on import, in Library a “Import Result” dialog pops up. It shows, “Some import operations were not performed. The files are not recognized by the raw format support in Lightroom. (105).”
        Then it lists down all the file names those were not recognized. (in my case, all the files actually). After clicking OK button, it shows “No files in current import” message in Library.

        • Very odd! It’s possible that there’s a problem with the file itself in that case. Can you upload a sample file so I can test it here? Easiest way is to go to and fill in the form, using as the ‘to’ address.

          • OMG !!! So, you are saying the files are corrupt…. But the files are view-able in ViewNX2 software of Nikon.
            Anyways, I’ll upload a sample file as you have requested. Appreciate the way you have helped me so far…. Thanks :)

          • It looks that way, sorry. I’ve checked them in Lightroom 5, Photoshop CC and in Apple’s Preview app and it can’t be read in any of them. I would guess that ViewNX2 is showing you the embedded preview. That said, how did the files get uploaded onto your computer – what software? There were reports a while back of older Nikon software corrupting files when uploading, and there was a fix floating around somewhere.
            Sent from my iPad

          • I have uploaded the file in the address you mentioned. Please have a look. Thanks :)

  107. phyllis says:

    Hello. I’m attempting to install 4.4 on my old iMac and it will install but when I go to open the application, I get the message that it is not supported on this type of Mac. I have and intel 2Ghz Intel Core Duo and I’m running osx 10.6.8. From what I can tell, I should be able to support 68 Bit. I meet the minimum memory requirements. I can’t seem to figure out why it won’t work. Any suggestions?


  1. […] List of known problems. (March 12, 2012) The official Lightroom blog has posted a Lightroom Hot Issues document, including the point curve conversion bug reported by A.J. Wood. If you’re running into a problem with Lightroom 4 or just want to know what you’re in for when you upgrade, check there first. Lightroom Queen Victoria Bampton adds a few issues of her own. […]

Leave a Reply

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