Color shift between Library and Develop module

Hi,
I recently noticed a color shift between in the image when going from the library to the develop module. Yes, I know this is mentioned in the FAQ, but I did not find the solutions given there to be satisfactory.
Let me explain what happens: I have taken Photos with my Canon EOS 300D, in Jpeg mode with Color Space in the Camera set to AdobeRGB. The photos I am talking about were taken with Tungsten light with auto white balance and have a distinct orange color cast. I use Windows XP and view my Photos on a LCD Display calibrated with the Pantone Huey system. The Lightroom Library Module and Photoshop CS2 both display the original image almost identically (there are no changes applied inside Lightroom or Photoshop, I view the original image in both applications). Photoshop is set to use the Adobe RGB Color space as its working Color space, Softproofing is switched off. However, when I switch to the Develop Module, the colors (especially the orange hues) shift very noticably toward pink. I can only assume that the Colorspace conversion or maybe some implicit soft proof used differs between the modules. So, to restate the problem: If I switch back and forth between Library and Develop, without changing anything and in 1:1 view to avoid errors introduced by different zooming methods, the colors shift quite drastically back and forth.
I have to say that this is really quite annoying. The whole point for me to use the develop module is to use it to make adjustments to the colors, and for this to work properly I have to see the same colors in both modules and in Photoshop. There is no point in correcting a pink color cast away in Develop that is not even there in either the library module or Photoshop (and that would then have a stronger orange tint because I tried to counter the pink tint in develop).
So this leads me to the final question: Is it possible to tell Develop to use the exact same color settings as the Library Module? Or is there another way to compensate for the color shift?
I hope I was clear in what happens and what I tried to do. If it helps I can gladly provide a sample photograph that clearly illustrates the point.
Thank you in advance for your help,
Daniel

Thanks for your comments, Don and Fred. I hope that this issue will be worked on soon.
Fred, I have set the Preview Quality to High, but it doesn't seem to make any differences concerning the color shift. I have investigated this matter further by now and made the following observations:
*The color shift is a lot less noticable on my laptop (the laptop screen is also color profiled). On my laptop the change is more of a subtle shift in contrast than in color. This might be caused by the smaller color gammut of my laptop display though.
*I have uploaded a testimage so that others can check if this shift occurs at their workstations too - after all, it might be a misconfiguration of my color management software, though I doubt that (because Adobe already states that library and develop render different previews). I would be interested if the color shift I describe is noticable at other workstations too. The link to the testimage: http://www.danyx.com/colorshift.jpg (permission to use the image to test the color reproduction is of course granted hereby).
Thanks for your help, I hope Adobe will listen soon,
Daniel

Similar Messages

Sharpness between library and development module

for some reason, after working on photo and putting it back into library if i open the very same shot in development all the other new work will be present but the shot will look less sharp. if i flick back to library it sharpens up again. The same happens a little differently in CS6. Here, if i zoom just a litle the shot sharpens to what it should be but if come back out it softens a bit.
Bit weird really
Can anyone help ? I'd like them all to look exactly as they are shoudl obviously...
Cheers,
S

Thanks for that Bob,
the really confusing thing is that the magnification appear to be identical between the library and development module while the development module is still softer....
Date: Sat, 12 Jan 2013 11:01:33 -0700
From: [email protected]
To: [email protected]
Subject: sharpness between library and development module
    Re: sharpness between library and development module
    created by bob frost in Photoshop Lightroom - View the full discussion
The general rule is that sharpening will only appear correctly at 1:1 in Lightroom, or at 100% in Photoshop. Any other magnifications are just a simulation of what the pixels would look like if you could see them all, i.e. not accurate. Bob Frost
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4988844#4988844
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4988844#4988844
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4988844#4988844. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Photoshop Lightroom by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

LR 5 slow in Library and Development module

Hi,
Used LR 5's trial version for a month and then bought full version last week. Withing 2-3 days of useage, started experiencing time lag to import, view, edit and export images. Even a simple exposure correction takes couple of seconds lag !!
Any solution to this issue?

Thanks for that Bob,
the really confusing thing is that the magnification appear to be identical between the library and development module while the development module is still softer....
Date: Sat, 12 Jan 2013 11:01:33 -0700
From: [email protected]
To: [email protected]
Subject: sharpness between library and development module
    Re: sharpness between library and development module
    created by bob frost in Photoshop Lightroom - View the full discussion
The general rule is that sharpening will only appear correctly at 1:1 in Lightroom, or at 100% in Photoshop. Any other magnifications are just a simulation of what the pixels would look like if you could see them all, i.e. not accurate. Bob Frost
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/4988844#4988844
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4988844#4988844
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4988844#4988844. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Photoshop Lightroom by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Library and Develop Module Photos Appear Different

I am using Lightroom 4.4 Dell Ultrasharp monitor is calibrated. I own and have been referring to Scott Kelby's Lightroom4 book for digital photographers. I recently took some photos of my daughters prom. She had on a beautiful reddish orange dress. I notice that the dress appears very red in the develop module, however, appears a bit more orange in the library module. The change is very noticeable between the modules. The dress also appears similar to the library module view (a bit more orange) when viewed on the web via Flickr utilizing Chrome, Firefox, or IPad. It also appears the same when exported to a JPEG file.
I have done some experimenting and have determined that this color change effect appears to be very noticeable utilizing the Adobe Standard Camera Calibration Profile. It does not happen (at least to a noticeable extent) with the others such as Camera Standard where the dress appears a bit more orange in both the library and develop module. I do, however, like the appearance of the Adobe Standard profile better and this happens to be the default profile as well.
I have also noticed that the dress looks more orange when Soft Proofing is enabled. The change happens immediately when the check box is enabled. Checking the box makes the photo appear similar to the Library module view. Enabling Soft Proofing does make noticeable that there is Destination Gamut Warning which mainly involves the dress which is the point of interest, however, there is no warning with the Monitor Gamut Warning. I am intending to place the photos on the web at this time via Flickr. I will be printing several later so will be worrying about the printer gamut at that time. But for now, I would like to get the photos on the web looking as intended.
Having the photos look so different in the Library and Develop Modules is very frustrating. I am hoping that there is a simple setting or fix for this problem that I am experiencing. Your assistance will be greatly appreciated. Thank you.
-Mark

Hi Victoria. Thanks for your reply. Re the saturation of the yellows, an example of a photo which shows the behaviour is that of a sunflower shot in direct sunlight. So a typical bright yellow. The raw files are from a D7000, so I have several "camera" profiles to choose from in LR4, in addition to the default Adobe Standard. None of the camera profiles show a difference between Library & Develop. Also, the Adobe Standard profile only shows the described behaviour when yellows are present. I can find plenty of examples where the photos are identical between the two modules when there are no yellows in the shot. I doubt this is a monitor profiling problem, given that it affects just the Adobe Standard profile, however I will try re-profiling. My U2412M display is not wide gamut. I posted here because the issue I am seeing sounds very similar to the original poster's. We're both using Dell Ultrasharp displays, although that could be a coincidence. I'll see if I can get some screen grabs from my Mac and upload here later today. I'm on my Windows 7 laptop at the moment.
R
Update:
I have a pair of screen grab JPEGs from the Mac which I'm happy to share, however the upload here in the forum is limited in size. Any suggestions how I can best share the full size JPEGs?
Re-profiling hasn't changed anything. I'm pretty sure my profile is good. Ambient natural lighting, monitor warmed up, etc. Native white point used as always. The difference between profiled and unprofiled is very subtle. The U2412M appears to be pretty accurate at factory settings.
If I turn soft proofing on in Develop I see the less saturated image which matches Library. Turning it off again and the differences return.
LR4 on my Windows 7 laptop doesn't have the same problem. The screen on that is calibrated with the same Spyder3, however the laptop's screen is of a mediocre quality compared to the U2412M.
Found another thread where the poster is having the same problems with yellows, this time in LR5.
http://forums.adobe.com/thread/1265004

Do we need a Library and Develop Module?

Do we really need a Library and Develop module? There's lots of dissatisfaction with Lightroom speed and one of the problem areas is when switching from Library, when in standard preview or 1:1, to Develop and the 'loading' message appears or as on my mac the dreaded spinning beach ball goes crazy. Even with all the previews created it's still slow.
So, if we have a standard preview or 1:1 loaded why can't we automatically be ready to apply any adjustments and save an extra step to another module? The quick develop in the library seems unnecessary and I've never used it. That leaves the metadata and keywording panels requiring a new location, but again these are not something I need to refer to on a regular basis.
Anyone else any similar thoughts?

> ...but I'm pretty darn sure there won't be any back-stepping to REMOVE or substantially alter LR's basic premise...pretty sure Develop will always be about dealing with a single image adjustment (and applying that adjustment to other images if you wish).
And I'm okay with this premise, but it needs additional functionality, such as the ability to apply relative adjustments. It already has this via the keyboard shortcuts while hovering. It just needs a UI adjustment (I once did a mockup of this, and I think it works) and the ability for autosync to recognize them as relative adjustments to the other images.
It also needs additional views. Grid, survey and compare would be nice, but you're only adjusting a single image's RAW data rendering at a time - the others are shown as previews and adjustments to them are rendered that way (like Library does).
The issue is, many people like me end up switching modules far too often. I generally go back and forth between Library and Develop hundreds of times per day. That's way too many times to be suffering the module-switching penalty. I'd prefer to select the images I'm working on in Library, and never see that module again until I'm done working on them. For now, grid and survey are too often needed, and so are relative adjustments.
Develop already has most of the needed functionality. Relative adjustments are already available to one image, a grid is available but only at 1 row (film strip supplied by Library) and a quick-render (the image in the upper left) is available as well. This just needs to be expanded and adjusted so that going back and forth to Library isn't as necessary as it is now. Ideally, you'd import in Library, to your metadata stuff there or in other related modules, choose the image group you want to work on using filters/folders/collections/find, then go to Develop and work on them until you are done.

Color shift between play and pause

Hello,
On CC 7.0 and 7.1, I noticed there is an important color shift between pausing and playing my timeline when using "CineForm Visually Perfect" encoded source material.
This is especially noticeable on reds.
Using other codecs, there is no such shift.
My video card is a Geforce 650M. At first, I thaught it might be related to the video overlay settings of the card, but there are no such settings in the control panel.
Besides, using Quicktime to play the source produces no shift as well.
As I am often doing color correction using Premiere, and as I have dropped Avid exactly because I always had this same problem (when using a profiled calibrated screen), I would like to know precisely what is going on. As I'm regularly producing shows for broadcast, it is a real problem not to be sure whether what you see matches the final exported output in all circumstances.
NB : For the need of searching the cause of this problem I disabled any custom profiling of my screen.
Thanks ! for any answers.
Fred

Sure and thanks. But nevertheless, if you color correct using a calibrated screen, and produce for the web ; or if you do a first pass of color correction before the ultimate pass happens with a "properly calibrated TV", wouldn't you like that your paused frame would look like your playing frame ?

Color shift between viewer and browser after pro kit update

hi there,
i thought i be one of the lucky guys since updating and running 3.0.1 was easy on my system. but after yesterdays pro kit update i experience a weird color shift between the look of pictures in the browser and viewer.
there is a strong colorshift in orange parts of sundown pictures. they turn magenta in the viewer but stay orange in the browser. the difference can easily be seen in the split screen. even weirder if i export a picture from the vier/split screen the exported files show the magenta tint. if i export them from the browser, they have the "right" orange tint.
this happens with raw-files from both d200 and d70. also exportet the raw and processed it with ps cs3 and everything was ok. anyone got a clue?
thanx in advance

just found the explanation. after my prokit update, all raw-files needed to be reprocessed and then i needed to select the standard apple camera module for the d200. that was quite tricky and i don't understand why something like this happens. why do all files need to be reprocessed and than afterwards you would have to manually select the apple standard converter and why did the viewer look different than the browser and why is there no warning module that tell you all files will have to be reprocessed?

Why is the image on my screen changing when I switch between the library and develop modules?

I've noticed in the past couple of days that I will be refining an image in the develop module, feel I've gotten it the way I want it to look, and then switch back to the library module to export. When I do so, I notice the colors are quite different than they were just a second ago in the develop module. When I switch back to the develop module, it goes back to the way it looked in the develop module. How might I fix this?

Is what you see in Library the original, camera-embedded preview or is it just a messed up version of the LR-rendering? You can test this by making a significant change to an image with the problem (Exposure -4 or Saturation +100) and see if the Library Preview also darkens (or the colors saturate) significantly or not. You might also try explicitly telling LR to recompute the Standard then the 1:1 preview to see if either of those show up in Library.
If the Library view never shows any LR adjustments and is always the camera-embedded JPG preview or a LR-preview from some days ago that never changes no matter what you do in Develop, now, then your Previews cache is likely corrupted and the entire should probably be deleted so LR can rebuild them. The previews folder is called catalogname Previews.lrdata and is a subfolder of where your catalog file (.lrcat) is stored. You can location your catalog by going to the General tab in the Catalog Preferences and clicking the Locate button. You should exit LR before trying to delete the Previews subfolder and make sure you’re not deleting the catalog or backups folder, just the folder with Previews.lrdata in the name.
If the Library view just shows a different-looking version of the LR adjustments then perhaps something is wrong with the display-driver or the monitor’s color profile.

In Lightroom CC images look different in Library and Develop modules. After output, images do not appear as they do in Develop.

As above.

Mac OS X 10.9.5 has a color management bug that can lead to colors appearing different in Develop and Library: Jao's photo blog: Serious color management bug in Mac OS 10.9 "Mavericks" . See also: Jao's photo blog: Further quantification of the Mavericks color management problem and Jao's photo blog: Color management in Safari is broken in Mavericks too. Sorry for all the links to my blog, but this bug really annoys me and it bugs me that it hasn't been fixed all these months that Mavericks has been out. This can lead to color shifts especially in the deep tones. You can sometimes work around it by turning on soft proofing and proofing to adobeRGB or sRGB. Adobe could fix this but they haven't so far. Apple could fix it too, but they haven't until now. They fixed some code that lead to Aperture working correctly but Lightroom still has the problem.

Significant color shift between FCP and COLOR?

Hi there,
I get a significant color shift when sending footage - either adjusted or unadjusted/unmodified - from FCP to COLOR.
Before anyone asks, the color shift is visible both internally or on an external broadcast preview monitor.
From within COLOR, I 'send' back to FCP this sequence - which is still without any form of adjustment (apart from being sent to COLOR), the apparent color shift is now visible/added to the imported sequence (from Color).
I've tried this on three separate Macs:
1. The Mac above (6.0.6). (Leopard)
2. A Mac with the same version of FCP as above. (Snow Leopard)
3. FCP and on a third Mac with an earlier version of FCP. (Leopard)
Does everyone have the same problem?
If not, does anyone have a solution?
Cheers,
Dan
PS: I've tried:
FCP > Color ProRes contrast shift
http://discussions.apple.com/thread.jspa?threadID=2150962&tstart=75

I had the same problem except that I am using version 1 of color and Final Cut Pro 6. I isolated just the video and double checked that I had no filters or if I did I turned them off. I had a smooth cam filter on one shot, but that didn't effect it. I was then able to send it to color without issue, once I had no sound or filters or transitions messing up the pass between final cut and color. Try doing the same, just duplicate or copy your timeline to a new timeline. I would have rendered your footage out to ProRes however as using the DVC Pro codec is probably not ideal. Color also only works with actual full raster files, not so good going from HDV or DVC Pro as they have an anamorphic frame size. This may be causing issues also.

Color shift between Ai and the web ... again

Hi there,
Classic problem again ... color never seems to let me rest in peace
Well, I copied colors hex numbers from this palette
http://www.colourlovers.com/palette/2077685/Stargazer
When I fill 5 squares in Illustrator, each one with the palette's colors, the 2nd (#592997) and the 3rd (#7208FE) are showing completely different in Illy (more magenta) than in Chrome (more blue).
I need help here since :
- my screen is calibrated (5 days ago with Spyder3)
- the color profile in Ai is set to sRGB
- the document color mode is set to RGB
- as far as I know, Chrome supports color management & the palette comes from a site about color which I suppose does things right
Is it the same for any of you if you try out ?
Any idea about what's going on ?
Thanks.
(Sorry, it's being late, maybe I'm just tired & dizzy and just cannot see the evidence anymore )

Oh good god !
Did not know that !
I am so used to work with my mac on Safari and here I am on a PC using Chrome & Firefox which were both completely off after checking.
Apparently it is off by default in Firefox too.
I had to go to G. Ballard's website to see that I needed to set the following parameters as such :
gfx.color_management.enablev4 = true
gfx.color_management.mode = 1
And I also found that you can force Chrome to display according to the monitor's profile by using this trick
http://www.binaryturf.com/enable-color-management-google-chrome/
Well, now everything seems ok.
Thanks. I think I need to go to bed now

Lightroom 6 difference in color in Library vs Develop module

Hello,
i have recently installed LR6 and converted existing LR5 catalog. I have an issue that in Library module, all pictures looks yellow (like wrong color balance) and in Develop module they look correct. When i export a picture into JPG file it also looks correct. But the color difference between Library and Develop modules is huge with Library shifted into yellow tones.
Does anybody know what to do?
Best regards,
Pavel

Hello,
i have recently installed LR6 and converted existing LR5 catalog. I have an issue that in Library module, all pictures looks yellow (like wrong color balance) and in Develop module they look correct. When i export a picture into JPG file it also looks correct. But the color difference between Library and Develop modules is huge with Library shifted into yellow tones.
Does anybody know what to do?
Best regards,
Pavel

Image appears different in Library and Develop modes?

I have an image that appears different depending on whether it is in the Library Module or the Develop Module. Only this one image does this. The develop module version is the one I want to work on in Photoshop. However, when I click on "Edit in Adobe Photoshop CS3" the resulting tiff that opens in PS has an appearance that matches that of the Library module version of the image. It makes no difference whether I click on "Edit in PS CS3" from the Library or Develop module, the tiff always matches the Library Module version of the raw file.
Any ideas what might be causing this?
Thanks.
J.

How are you calibrating your monitor? The only real difference between the Library and develop module is that the Library module shows a preview that is generally stored in the adobeRGB color space. The Develop module uses a color space based on prophotoRGB primaries and can encompass any color your camera can capture. It is possible that your green falls outside of adobeRGB and gets clipped in the library preview, while in the develop module it shows them. This is only possible to see if you have a wide gamut monitor, or when your calibration software generates a perceptual rendering intent. If you export and you do not use the prophotoRGB color space, you will loose these colors.

Color problems between Lr5 and other software

I can not see where to make adjustments to get the same tones between Lr and my other software: Photoshop, Irfanview, Windows Viewer ...
My test conditions:
My monitor is calibrated
... - Export Lr Jpeg quality 85% and also tests 16bit TIFF (sRGB, Adobe rgb and prophoto)
... - When exporting, I checked the "add to catalog" to view the same image in Lr.
Conclusion: Other software gives almost the same tones (some small differences due to the chosen color space) and Lr gives a much warmer picture (Raw or treated Jgeg reimported in the catalog). Will it have a preference of Lr to settle?
Note: the direct opening of RAW file in Photoshop with Camera Raw (same engine as Lr) without special settings, also gives a duller color different image, that directly Lr.
What is the solution?

In general, any difference between Lightroom and other color managed software is indicative of a corrupt monitor profile. No idea about Irfanview, but Lightroom, Photoshop and Windows Photo Viewer should all display identically.
What they all do is convert from the source/document color space to the target color space, which for display is your monitor profile. The result should be identical - that is in fact the whole point of color management. But since the source space may be different the actual conversion itself may also be different. So one conversion may go bad but not others.
A difference between Library and Develop will have the same explanation (different source spaces; Library is Adobe RGB while Develop is linear ProPhoto).
It also happens that different applications react differently to a bad monitor profile. It may work in one application and fail in others.
Any software that is not color managed will simply display in the native monitor color space, which can be anything under the sun, so you can just ignore and disregard that. It won't be accurate anyway.
So the solution is to have a valid and healthy monitor profile. Then everything color managed will display identically (save for gamut differences, but in practice that only applies if you have a wide gamut monitor. With a standard monitor any source space will have equal or larger gamut than the monitor).
Some calibration software has been known to not follow specifications strictly at all times, so check for updated software. Or the profile can simply have become corrupt. It happens. A way to test this is to set sRGB as default monitor profile in the OS - or Adobe RGB if you have a wide gamut monitor - and see if the problem clears.

Color shift between Develop Module and other modules in Lr 5.7.1

Hello,
I'm getting a color shift between the devolop module and any other module in Lr.
It's a recent problem that I've been experiencing since the last update.
I'm using Lr as part of the Adobe Photographers Bundle in a Windows 8.1 pro.
Below I have an example for the kind of color shift i'm seeing. The image on the left is from the Devolop Mobule and the one on the right is form the Library Module.
Is this happening to any one else? Does any one know why?
I would appreciate any help.

Gautam is correct in that the preview mechanism isn't the same in Develop and the other modules and, you must view the color in Develop at 1:1 to see an accurate preview. The color space is different that's probably why you see this difference in reds (especially if you use a wide gamut display).
IF you build your own ICC profiles for your display, be sure the software is not building a V4 (version 4) profile, stick with V2.
As for exporting and comparing, be sure the secondary application is color managed! Otherwise it's expected that there is a visual disconnect between LR and that app.

Color shift between Library and Develop module

Similar Messages

Maybe you are looking for