develop settings suddenly changing

[benjamingordon]

hi.

ive noticed lightroom behaving strangely recently.

when im going through photos that ive edited and i switch into the develop tab the settings suddenly change.

i could be looking at a preview of an image which is fine and then suddenly the exposure or whites or shadows will jump up and ill have to try and remember how to get the photo back to my original edit.

its incredibly frustrating.

can anyone please help?

[Akash Sharma]

Hi Benjamingordon,

Sorry that Lightroom is changing image adjustments when you switch to Develop module.

I assume that you are referring to the actual render of the image which does changes the exposure and other adjustments. I'd recommend that you take a look at this discussion Lightroom changes exposure of pictures when they are clicked and let us know if that helps.

Thanks,

Akash

[benjamingordon]

I am yes.

Please see the attached video.

What is the solution?

[Akash Sharma]

Could you please share the video URL? Your reply had no attachments.

Thanks,

Akash

[benjamingordon]

here you go

https://www.dropbox.com/s/kme5w19qpou0o5r/lightroom%20exposure%20issue.mov?dl=0 <https://www.dropbox.com/s/kme5w19qpou0o5r/lightroom%20exposure%20issue.mov?dl=0>

[benjamingordon]

Any update on this please?

[Just Shoot Me]

There isn't any update because what you are seeing originally is the Embedded JPG that is included in all RAW files. What you are seeing in the Develop module is the actual RAW file and or a Preview of the actual RAW file data.

[benjamingordon]

if was seeing the embedded jpg wouldn’t it show me a colour version of the file?

also why does it only do this with certain files?

also why has it only recently started happening?

[Just Shoot Me]

Is your camera set to capture in B&W. The camera settings are used to create the embedded JPG. If the camera is set to record in B&W then the Embedded JPG will be B&W but the RAW sensor data will be in color. That is unless you have a B&W only digital camera. There are some, not many. Leica M (whatever) is one.

[benjamingordon]

it is a colour sensor camera.

im sorry im not satisfied with your answer.

[Rob_Cullen]

When the Grid (or Loupe) view of a photo changes in appearance when you take it to the Develop module- A common cause is the Monitor Profile has changed (sometimes because of an OS update).

So the suggestion is to re-calibrate your monitor (if you have a hardware profiling device), or set the monitor profile to sRGB as a test.

https://www.lightroomqueen.com/how-do-i-change-my-monitor-profile-to-check-whether-its-corrupted/

And update the Graphics card device drivers from the OEM.

[benjamingordon]

Again I am unhappy with this answer.

I haven’t updated anything except lightroom recently.

I don’t know why you can’t see this is a lightroom issue.

Please allow me to speak with a supervisor because I’m getting lots of suggestions which are not helping me.

If you actually watched the video or read my original message you could see that the photo is not changing in colour and again to repeat what I’ve said so many times it only happens with certain photos, not all of them.

Please, please forward this to someone higher up the team as I’m getting no where.

The adobe support has let me down so many times now.

I feel like I’m paying for the software but not the support.

[Rob_Cullen]

To "speak  with a supervisor" you will have to contact Adobe Customer Support. Contact Customer Care

This "Community" forum is primarily other LR users.

I DID watch your video and I do see the monochrome image giving the problem. (I edited my post from "color" to "Appearance")

Did you read the 'LightroomQueen' link and try the advice to test your monitor profile?

I do not have forum privileges to "Forward" your post, you may get more informed answers at- Lightroom Classic CC | Photoshop Family Customer Community  or wait for Akash to add to this thread.

Did you notice that post#16 in the link from Post#1 above by Akash  mentions monitor calibration.

[Akash Sharma]

HI benjamingordon,

Sorry about the delay in my response. I see that you have a custom preset applied in the quick develop menu in the Library module. Have you tried changing it to defaults settings? Also, the shift in the image you see is because images in library module are not the actual preview of them. Only when the image is rendered in the Develop module and in the 1:1 preview you can compare the image with the original rendered image in other apps. It all depends on your monitor profile as WobertC has rightly mentioned. Please calibrate your monitor profile as mentioned in this article https://www.lightroomqueen.com/how-do-i-change-my-monitor-profile-to-check-whether-its-corrupted/

Work with couple of monitor profiles including the default profile and calibrated profile and let us know the outcome. We're looking forward to your response and would love to help you resolve the problem.

Thanks,

Akash

[benjamingordon]

i have done this and it doesn't change anything. the issue still persists.

what do you suggest?

[Jao vdL]

Make sure you reset all default develop settings in Lightroom preferences.

As noted above Lightroom 7.5 has a bug where it forgets dng files have embedded profiles but it only forgets right after the profile has been changed. If it never was changed, it will not do that. If the default setting contains a profile change, it will therefore lose the profile. You can reset it by reading "metadata from file"

[Per Berntsen · Accepted solution]

Your problem looks a bit like the one in this thread: RAW flat profiled photos turn oversaturated and overcontrasted after loading!

So what setting have you chosen Under File handling > Previews in the Import dialog?  Choosing  Embedded & Sidecar could cause the the image to change the way you describe. Embedded & Sidecar will use the embedded jpg preview – Standard will create a new preview from the raw file, which will be identical to the Develop preview.

https://forums.adobe.com/people/Akash%20Sharma wrote

Also, the shift in the image you see is because images in library module are not the actual preview of them. Only when the image is rendered in the Develop module and in the 1:1 preview you can compare the image with the original rendered image in other apps. It all depends on your monitor profile as WobertC has rightly mentioned.

The preview in the Library module is an actual preview, unless the embedded jpg is used as a preview. (Embedded & Sidecar is chosen under File handling > Previews in the Import dialog) So previews in Library and Develop should be identical, even at magnifications other than 1:1. The exceptions are sharpening, noise, chromatic aberrations and moiré, which must be viewed at 1:1. But image brightness and contrast should not change.

And the need to view at 1:1 has nothing to do with the monitor profile. (although there is a possibility that the monitor profile could be the culprit)

[benjamingordon]

its always been on minimal.

could this be the issue somehow?

perhaps its a bug in the new lightroom?

[Just Shoot Me]

So you are using a Leica camera and it looks like that image is from 2014. I have noticed some very strange behavior with some of my Leica M8 images when Viewed (opened) in the develop module with the newer versions of LR that I don't see when viewing them in LR 5.

Some kind of change in the Default profile setting being applied. The only option I found that works to get them back to "Normal" (whatever that really is) is to use the Reset button then changed the camera profile to something that works for me. Then Updating the Default settings to apply that same camera profile to all images from the 3 serial numbers for the Leica M's I've used over the years.

EDIT:

That images is not from 2014. I was looking at the Time Stamp not the Date captured. In any event same applies as posted above.

[johnrellis]

LR 7.5 has problems with the profiles embedded in Leica DNGs: Lightroom/Camera Raw: Leica M 262 DNG Embedded Camera Profile Issue | Photoshop Family Customer Comm... . Perhaps the symptoms you're observing are related. Best to start a bug report in the official Adobe feedback forum, I think (or add to the existing one, if it looks like symptoms of the same problem).