Lightroom: Develop module not working since upgrade to 4.2

  • 5
  • Problem
  • Updated 4 years ago
  • (Edited)
I've installed the 4.2 upgrade and now the develop module doesn't work anymore. It was working fine on 4.1, 64bit version.
I'm on Windows 7 Pro, with second generation i7 CPU, 16 gig Ram.
Photo of Normand Guerin

Normand Guerin

  • 8 Posts
  • 0 Reply Likes

Posted 6 years ago

  • 5
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14149 Posts
  • 1765 Reply Likes
What is the symptom when you say "doesn't work" - do you get an error? or click on the Develop module button and it doesn't come up? or can you get to develop module and the sliders don't work?
Photo of Normand Guerin

Normand Guerin

  • 8 Posts
  • 0 Reply Likes
Hello Jeffrey,

When clicking the Develop botton, from the Library modules, the photo disappears and is replaced by a grey screen.

I've tried selecting other photos in the bottom strip, some will show, some will not, then selecting again some that were previously showing up, didn't work anymore.

Once I manage to get one from the strip to show up,( not necessarily the one I want to work on) then the slide adjustments that I try, don't make any changes on the photo and the photo is replaced by grey screen again.

The software doesn't freeze, since I can return to Library module and scan through my catalog.....

Thanks for the prompt response, by the way,

Normand
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14149 Posts
  • 1765 Reply Likes
Hmm. I haven't heard this issue before. The one thing I might look at is whether your video card driver is up to date by going directly to the manufacturers website (nVidia or AMD) and get the latest driver.
Photo of Normand Guerin

Normand Guerin

  • 8 Posts
  • 0 Reply Likes
Jeffrey, it's not the whole display screen that goes grey, but the area covered by the photo in the middle or center. I don't know how to say it in English... When you see the photo "1:1" or "Fit", it is displayed in the middle,right? Then it's that portion that goes grey....the photo just disappears...but the rest of the software interface is still visible and functional, i.e. I can go back to "Library", then the photo comes back on.
In the event that a Photo happens to show in " Develop", any of the adjustment sliders that I try, don't make any changes on the Photo.
Also I noticed that on a couple of occasions, a " working " thing shows up for a fraction of a second before the Photo disappears.
This was not a situation that happened in the original version. It worked great... except when freezing at start-up on a few occasions, where I needed to go and Delete the content of the "Preference" file, manualy, then things would resume their normal course.
Right now, I'm thinking of un-installing this upgrade and going back to the original 4.1.
Photo of Augusta Benvenuto

Augusta Benvenuto

  • 2 Posts
  • 0 Reply Likes
I am having similar issues since upgrading a few hours ago. I get greyed out images while working and very delayed functions also. But most of all I am having the entire program shut down every few minutes now. Yikes...Adobe what have you done?
Photo of Augusta Benvenuto

Augusta Benvenuto

  • 2 Posts
  • 0 Reply Likes
Also having another new strange issue. While working on an image the image flips upside down randomly. So very frustrated. Think I will downgrade too!
Photo of Normand Guerin

Normand Guerin

  • 8 Posts
  • 0 Reply Likes
I've un-installed 4.2,.....and re-installed 4.0 from my original DVD.
I get no Photos whatsoever showing up. Imported everything as before, all thumbnails show up for import selection, then once imported all the photos "grey" squares show but not the image inside.
I then install 4.1 update, (that was running great before installing 4.2)
Everything is back to normal, it seems, but the same thing as with 4.2 is now happening in "Develop" module.
I'm frustrated........
I'v ordered the full Nik suite plug-ins before upgrading to 4.2 as I wanted to migrate my workflow to Lightroom. Now I'm Fu**ed....and the Nik suite is on its way and I can't cancel it.
Everything was fine before upgrading to 4.2. What have you done here Adobe?
Can I send the box back for refund? as my trust level in this product is now ZERO.
Photo of Normand Guerin

Normand Guerin

  • 8 Posts
  • 0 Reply Likes
Additional info to maybe help narrow down the problem...:

1- What could be in version 4.2 that stays in the system even when you un-install, that has an effect on older versions when they are re-installed...??

2- One other weird thing I noticed is that a Photo that finally shows up in "Develop" module, is "Blured", as if way out of focus, but that same Photo is cristal clear, tack sharp focused in "Library module....??

3- I "import" DNG files produced in camera....that were working just fine up to this upgrade...??

4- Forgot to mention that my video card driver is up to date as verified after suggestion from above....??

The reason for migrating my workflow is that my previous workflow cannot handle Medium Format camera profiles, as I've recently upgraded to this Format. I really need this software to be working.....or I'll need to move to Phase One or other... I can't afford the delay, and sure don't want to spend hundred of hours in Photoshop. I've already paid good money for this software and Plug-ins, and Training.......
Photo of Ron Baker

Ron Baker

  • 1 Post
  • 0 Reply Likes
I recently installed Photoshop CS6 Extended and have run into a similar problem with Lightroom 4.2. Not sure whether it is CS6 or LR 4.2 that is the source of the problem. I see nothing but grey squares in both Library and Develop in LR for any of the files that I have on my computer (Win 7 Ultimate, 64 bit, 8GB RAM, probably first generation of i7 quad-core chip, if any of this matters). However I do see the histograms in Develop and the Slideshow works. CS6 and Bridge both seem to work okay.

I have been using Ligthroom since it was first released, but mostly new to Photoshop.

Any help would be greatly appreciated, thanks
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4322 Posts
  • 1577 Reply Likes
If you can't see anything in both Library AND Develop, you may have a corrupted monitor profile. Try this: http://members.lightroomqueen.com/ind...
Photo of Normand Guerin

Normand Guerin

  • 8 Posts
  • 0 Reply Likes
Please have a look in my thread at http://forums.adobe.com/message/4765790

"....The profile is the problem...yes,.... and no....

I use X-rite Color Munki as my profiler, latest upgrade, 1.0.2.0

Using the above info, I've switched from my profile to sRGB, to manufacturer profile and others in the list...result : mine has the problem and not any of the others.

I've just spent 7 hours straight, un-installing, re-installing, LR 4.2, 4.1, Color Munki, deleting the content of the LR Preference file, re-profiling using "easy" and "advanced", trying all kinds of combinations and sequences of the above....

My findings:

1- In LR 4.1 Using my profile, and deleting the content of the " Preference" file before starting LR, everything works just fine. Then when you shut it down and re-open it, the problem is back. Using " Task manager", I force the shut down of the " Not responding" LR, go back to deleting the "preference file" content, and LR works again. This does not work with LR 4.2

2- In LR 4.1 On the last re-calibration I've done, I tried again and it did not work. Went to change profile to my default manufacturer's one and as expected LR worked....but I noticed that the calibration profile change did not affect the monitor screen, and LR 4.1 works perfectly on multiple starts and closes.

Here is the interesting part....: My Color Munki profile is still displayed on the monitor, ( I did not "Restart" or "Re-boot" ) and the selected profile is the manufacturer's in Control Panel's Color Management, and LR 4.1 works perfectly.Can it be that the profile itself, displayed on the monitor, is not really the problem?

Is it possible the "Conflict" would be in "Windows Color Management"? or LR's color management protocols?.....

I have not tried # 2 with LR 4.2 as I'm kind of chicken of going another round of hours at it.... Like the saying goes..." If it ain't brokin', don't fix it ".....

So, for now, I'll carry on with 4.1 as I can at least continue working......hopefully, using the "Sleep mode", and not "Shut down", the set-up will maybe stay "as is",
and if not, I now know how to fool it.....until somebody finds a more permanent fix.
and if not, I now know how to fool it.....
Photo of Normand Guerin

Normand Guerin

  • 8 Posts
  • 0 Reply Likes
Well,...I thought wrong, since my last post, my compromise/temporary solution didn't work at all....
I've tried all kinds of stuff found in other post and/or threads, and still no solution

I've contacted X-Rite to see if they heard of this problem....waiting for a reply...

Thanks to the posters that directed me to the " Corrupt Profile" trail, but it doesn't fix the problem....The profile doesn't work with LightRoom only...!!! Photoshop CS6, CorelDraw , Elements 9, and others work just fine....

I'm stuck...I can't work because my Color Management workflow is broken...And I don't think Color Munki is at fault since other softwares work fine with its profile, or are they?

This is extremely frustrating, since there were no problems when I installed the out of the box version 4.0 .... everything started happening when I first installed the "suggested update to 4.1" , then worst with 4.2

Right now, neither LightRoom nor Color Munki are installed on my computer, pending a solution that does not seem to be provided. If somebody at Adobe would say that they are looking to fix this, give some feedback, it would bring "Hope". But 7 days later, still no word....so the "Trust Level" is at "Zero/0" .
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14149 Posts
  • 1765 Reply Likes
Can you post the profile somewhere?
Photo of Normand Guerin

Normand Guerin

  • 8 Posts
  • 0 Reply Likes
Hello again Jeffrey,

I'm not sure how to do what you just asked,...I'll need to look into it, probably tomorrow...
Would it be easier to attach it to an e-mail, maybe?
...Or I'd be willing to ship my box of Color Munki Display so the testing could be done in a more controlled manner, with the actual tool in hand...??
I'd be willing to give my e-mail for more direct interventions....if you don't already have access to it.

In the meantime, here's other info that could be of use...:

Video Card Vendor: ATI Technologies Inc.
Renderer: AMD Radeon HD 6600 Series
OpenGL Version: 4.1.10750 Compatibility Profile Context
GLU Version: 1.2.2.0 Microsoft Corporation

and the driver is up to date after verifying as per your previous suggestion....
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14149 Posts
  • 1765 Reply Likes
Sure. I can send you an email to get the profile.
Photo of Murl McRae

Murl McRae

  • 2 Posts
  • 0 Reply Likes
I have exactly the same problem as Normand. I am using a trial copy of 4.2 so I have not paid for the program yet. Rather than trying to chase down this problem I will probably buy Corel Aftershot instead. It seems to work fine.
Photo of Murl McRae

Murl McRae

  • 2 Posts
  • 0 Reply Likes
Ok. I got my trial copy of 4.2 working by changing my monitor profile to sRGB. Now I can continue my evaluation.
Photo of Colin Barnett

Colin Barnett

  • 5 Posts
  • 2 Reply Likes
I found this thread when searching for the problem that Norman had. I have the same problem. I upgraded to LR4.3 about a week ago. I have used it extensively since then in both Library and Develop modules. Today, for the first time, in Develop module the picture turned grey, as did the Navigator view. Library views work fine. I tried the adjacent picture in the filmstrip and it was also grey. Then I clicked on the first picture in the filmstrip and it was fine. I clicked through each of my pictures and each one displayed, including the two at the end that were originally grey. I have no idea why this happened. I hope it becomes a known bug for Adobe.
Photo of AlphaValues

AlphaValues

  • 6 Posts
  • 1 Reply Like
This exact problem started for me today with LR4.4, which had been working fine for months. The problem persisted when I installed LR5 CC, too. System is Win7 Pro 64, 4xcore i7, 32MB RAM, single SATA3/7.2k RPM drive.

After much unistalling, reinstalling, deleting preferences, etc I finally found this thread. I disabled the Colormunki profile (made with Xrite v1.0.2), set the display to sRGB and I was able to get images to draw in the Develop module for both versions of LR.
Photo of Todd Seroka

Todd Seroka

  • 3 Posts
  • 0 Reply Likes
I also had the same problem with LR 4.4. Tried to uninstall/re-install, catalog optimize, create new catalog and re-import etc. all to no avail. The discussion regarding the X-Rite Color Munki got me thinking that I had a X-Rite message reminding me to re-calibrate my monitor which I had been ignoring until I fixed the LR issue. So after reading this thread I decided to re-calibrate my monitor and it solved the problem.

The problem I was having was perplexing. I could see the images in the Library Module no problem but whenever I went into the Develop module it was just a blank screen. If I went into an image I had previously processed in LR I saw the adjustments in the sliders but no picture. I tried exporting the RAW image into a JPEG from the development module and it exported the image. It was strange that once I was in the Develop module the first image was always blank, but if I selected another image from the filmstrip it would display (or I thought it would display). When I tried to adjust the image in the Develop module the adjustment would not show in the main image area but I noticed the filmstrip image would change based on the adjustment (e.g., slide the exposure all the way the main image would not change but the filmstrip image would get blown out), Some very strange behavior to try to diagnose.

I really don't know why updated my color profile fixed the problem but it worked.

Hope this helps someone else in the future.