Lightroom playing silly buggers?

Ed Sutton

Ed Sutton

Suspended / Banned
Messages
8,556
Name
Dave
Edit My Images
No
The first pic is a screenshot of the file in LR. I thought my camera was fecked but the image on the camera's screen was fine so I exported from LR as a jpeg which is the second pic.. It's got me scratching my head.:thinking:

2023-12-26_163644.jpg

_7822121.jpg
 
I feel like recently when viewing images in library module the image is a lower resolution / quality, but when I go into develop module it's better resolution / quality. Dunno if it's some sort of processing power saving tactic of something. Although in library waiting a few seconds of so the quality gets a little better. Or is the first image in develop module already?
 
rd6743 said:
I feel like recently when viewing images in library module the image is a lower resolution / quality, but when I go into develop module it's better resolution / quality. Dunno if it's some sort of processing power saving tactic of something. Although in library waiting a few seconds of so the quality gets a little better. Or is the first image in develop module already?
Click to expand...
Doesn't matter which module it's in the effect's the same.
 
It looks like you have got the thing that indicates blown highlights turned on, although looking at the jpeg the highlighted area doesn't look blown. If it is highlighting clipping then click the little triangle in the histogram to turn it off
 
sirch said:
It looks like you have got the thing that indicates blown highlights turned on, although looking at the jpeg the highlighted area doesn't look blown. If it is highlighting clipping then click the little triangle in the histogram to turn it off
Click to expand...
It's not that. :(
 
Is it just this photo or others that it happens on?
 
rd6743 said:
Is it just this photo or others that it happens on?
Click to expand...
A few others. Although it's happened before. That time I made it go away using some slider or other then forgot about it. It's something to do with the reds/pinks/skin-tones.
 
Though I don't use LR currently, could it be in the sphere of soft proofing / rendering intent / gamut warning?
 
You can reset it to defaults I see some stuff about doing it on google.
Re-install would be another option but would be nicer to get to the bottom of it and turn it off.
 
Last edited:
4wd said:
You can reset it to defaults I see some stuff about doing it on google.
Re-install would be another option but would be nicer to get to the bottom of it and turn it off.
Click to expand...
I've thought of restoring to defaults. That will be my last resort!
 
  • Like
Reactions: 4wd
I've just opened up LR6, which I haven't used for ages, which never exhibited this strangeness. It does now. :ROFLMAO:

I give up!
 
Not the same but perhaps related ... for me the image in the navigator window (top left) was showing all of the changes I had applied but the main image window wasn't. This was also the case for exported files i.e. no changes applied. The answer was to turn off graphics acceleration in the settings and then both windows looked the same (i.e. showing the changes applied)
 
ecoleman said:
Are you assigning some sort of color profile on import?

What is the color profile of the image. Ie Adobe Color, Adobe Landscape etc.
Click to expand...
Camera flat is my standard import profile, but changing it makes no difference.

paulmck said:
Not the same but perhaps related ... for me the image in the navigator window (top left) was showing all of the changes I had applied but the main image window wasn't. This was also the case for exported files i.e. no changes applied. The answer was to turn off graphics acceleration in the settings and then both windows looked the same (i.e. showing the changes applied)
Click to expand...

It is off.

As it's not affecting exported files I'll live with it for now.

Thanks for all suggestions, though.
 
Ed Sutton said:
Camera flat is my standard import profile, but changing it makes no difference.



It is off.

As it's not affecting exported files I'll live with it for now.

Thanks for all suggestions, though.
Click to expand...
Why don't you share a RAW file and see if other people et the same result as you.
 
From the information provided basically this looks like "a computer chewed my image", and essentially that's that.

Perhaps share your settings and calibration recipe if you actually want to get down to this?

It looks like you are either "fecking" with the reds, applying some strange camera calibration or proofing for some off matt paper, or your screen calibration is way way out. And what are your export settings. Somehow I fear this will be combination of everything I mentioned.

The two images have different colours throughout. Not just the red areas.

P.S. It looks horrendously soft.

sirch said:
It looks like you have got the thing that indicates blown highlights turned on
Click to expand...
that's the first obvious thought but then it would be a solid red 255,0,0 or nothing at all and yes it doesn't look that blown out.

ecoleman said:
What is the color profile of the image. Ie Adobe Color, Adobe Landscape etc.
Click to expand...
errr that is NOT a colour profile.

4wd said:
You can reset it to defaults I see some stuff about doing it on google.
Re-install would be another option but would be nicer to get to the bottom of it and turn it off.
Click to expand...
format C:\ as administrator :LOL: {please don't}
 
This could be a mask overlay if you manage to somehow perpetually remain stuck in a masking mode and apply same silly mask as preset on import. It is unlikely, but frankly everything is now likely here :LOL:

maybe format c: is not such a bad idea after all.
 
Last edited:
Could be a bad monitor profile. The Adobe products are fully color managed which includes converting the image's color space into the monitor's color space, and a bad monitor profile can cause issues like this.

This is part of why a lot of programs are not fully color managed and simply assume/assign sRGB to everything... full color management only works well when everything is done right; otherwise, it can actually be worse.
 
sk66 said:
Could be a bad monitor profile. The Adobe products are fully color managed which includes converting the image's color space into the monitor's color space, and a bad monitor profile can cause issues like this.

This is part of why a lot of programs are not fully color managed and simply assume/assign sRGB to everything... full color management only works well when everything is done right; otherwise, it can actually be worse.
Click to expand...
I don't think that would explain why it started happening out of the blue.
 
Is this happening on both LRCC and LR6 on the same PC?
Could there have been a windows or gfx driver update that has caused this?
If you can identify when it started happening, you could roll back any updates since that point and re-apply one at a time.
(I'm assuming Windows, but the same applies to fruit based OS' or teh lunix).
 
Last edited:
LC2 said:
Is this happening on both LRCC and LR6 on the same PC?
Could there have been a windows or gfx driver update that has caused this?
If you can identify when it started happening, you could roll back any updates since that point and re-apply one at a time.
(I'm assuming Windows, but the same applies to fruit based OS' or teh lunix).
Click to expand...

Same in LR6 and LRC

Harlequin565 said:
It's a wierd one for sure. I'm no expert, but a quick Google suggested the OS level colour management setting (more info) which Tim has alluded to. It links to a LR Queen article about corrupt monitor profiles (which Steven alluded to) and how to check it: https://www.lightroomqueen.com/how-do-i-change-my-monitor-profile-to-check-whether-its-corrupted/

is it just reds affected or other colours too?
Click to expand...
I'll check that out. Thanks. Yes, just reds.
 
Ed Sutton said:
I don't think that would explain why it started happening out of the blue.
Click to expand...
I've seen it happen before... but IDKW a monitor profile might go bad (other than drift). You can try viewing the original file with another program that isn't fully color managed... was the original a raw file?
 
sk66 said:
I've seen it happen before... but IDKW a monitor profile might go bad (other than drift). You can try viewing the original file with another program that isn't fully color managed... was the original a raw file?
Click to expand...
Raw file. All good now the profile's been reset to defaults. No idea how it went off piste.
 
Ed Sutton said:
Raw file. All good now the profile's been reset to defaults. No idea how it went off piste.
Click to expand...
:woot::woot::woot: Got there in the end. Great teamwork! My Google search was inspired by @sk66 and @LC2 so we got there together!
 
ecoleman said:
If you're an argumentative pedantic T&^t then sure it's not, but as Adobe call it a profile I'm 100% certain that most people probably understood exactly what I meant.
Click to expand...
perhaps you would care to enlighten us all why would a well-tested Develop module profile affect colours in such a way? Hint: they don't.

I'm rather disgusted with your language to be absolutely honest, not that I expected any better :exit:
 
I had similar happen editing an image in lightroom classic so i tried lightroom and all was ok.
 
sirch said:
@ecoleman and @LongLensPhotography

Knock it off

The issue is resolved and apart from you two it has been a constructive and helpful thread
Click to expand...

My first post was just as helpful and constructive as any other. Maybe not the cause of the problem but certainly something that could have caused the problem.

LongLensPhotography said:
perhaps you would care to enlighten us all why would a well-tested Develop module profile affect colours in such a way? Hint: they don't.
Click to expand...

Because anybody can make one of those profiles. I bought some for my Canon R5. I have made some of my own. They are files that can become corrupt just like any other file. Therefore HINT. They can and do cause problems sometimes.

Every post I see of yours you are belittling somebody of picking holes in something they have said so as for the language. Grow up.
 
Last edited:
ecoleman said:
My first post was just as helpful and constructive as any other. Maybe not the cause of the problem but certainly something that could have caused the problem.



Because anybody can make one of those profiles. I bought some for my Canon R5. I have made some of my own. They are files that can become corrupt just like any other file. Therefore HINT. They can and do cause problems sometimes.

Every post I see of yours you are belittling somebody of picking holes in something they have said so as for the language. Grow up.
Click to expand...
When I said knock it off, I meant it ...

I'll help you out with a thread ban
 
You must log in or register to reply here.
Back
Top