White Balance: Library versus Develop modules

I don't understand why the WB controls in the Library versus Develop modules differ as to choices. Sometimes I work with JPEGs rather than RAW and then in Libray I can chooose shade etc, but not in the Develop module.
Is there a theoretical reason for this or a design hiccup?

There probably shouldn't be specific choices in QD for JPEGs either. This is because JPEGs don't have an absolute WB reference like RAWs do. If you shoot in daylight and select daylight WB, you'll get an entirely different WB than if you shoot in tungsten and select daylight WB.
In other words, LR has no way to know the starting point on a JPEG since it isn't encoded in the file.

Similar Messages

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

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

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.

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.

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

White balance selections, Quick Develop and Develop...let's talk

One thing that isn't well-known is that the adjustments in Quick Develop and the adjustments in Develop are *fundamentally different* from each other.
Develop is basically designed to provide *absolute* adjustments to RAW images. It can be used for JPEGs too, but in that case, the white balance setting is not absolute as it's already been corrected in-camera. So the WB settings are meaningless since you don't know where to begin and the temperatures are removed for the same reason. You just start where you are and get warmer or cooler.
Quick Develop is designed to provide *relative* adjustments to all images. What this means is, if you have many images selected and hit the right exposure arrow ">" you'll increase the effective exposure of all of those images from wherever they are now to that plus 1/3 stop. If you hit the ">>" you'll get 1 stop increments.
Since QD is always making *relative* adjustments, it may be reasonable to assume that you have a known, corrected starting point from which to make relative adjustments. That may be why the daylight and other options are available in QD. I personally think this is a bad assumption as you don't know what corrections have been applied in-camera. Thus, I think those options shouldn't appear in QD just like they don't in Develop.
Comments?

The relative vs. absolute of the QD vs. Dev modules is something I'm not familiar with LR enough to dispute. However isn't the point of LR's non-destructive nature, that all actions on an image are relative to the initial baseline, whether it is a RAW or JPG (or Other).
Granted applying a preset WB set of values against a JPG does not make a lot of sense in the development of a repeatable workflow, but if a set of WB values improves a JPG image, who cares. Its all non-destructive and I can reset at any time.
I tend to not like operating in applications that are too stringent in keeping me walled into the "right" way of doing things. Particularly based on the super intelligent decision of the software developer because they know how it is supposed to work. (I have license to berate this group because it is my vocation) Changing the user interface from one module to another (if they both do the same thing) or from one file type to another is not a good thing. Consistency is paramount to user freindliness. If indeed the QD and the Dev modules work differently then it is expected that the controls be labeled differently to express this difference. If a selection is detrimental to the image or will cause application issues it is better to leave the selection visible (for consistency) and disable it (gray out) to keep it from being selected.
The abreviation of White Balance: to WB: in the application is also bad form. It is jargony and does not assist new users to understanding. Screen real estate is scarce and I understand the inclination to do this, but there is a cost.
- Morey

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.

Allow drag to panels from single view library or develop module

In 1.1 it appears that you can only do it from grid view.
Running Vista Ultimate.
Thanks.

Try it from the filmstrip in Loupe or Develop.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.10 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

Photos in Library module and after export look different than in Development module

Hello,
I experience a problem.
After I update photos in the Development module, the updates seem not to be shown in the Library module. And when I subsequently export to Flickr, Flickr is also showing the original photo, not the adapted one.
I noticed this the first time after making Blacks a bit deeper, causing a sunflower to become a deeper yellow. I thought that my adaptations were not applied in the Library module. After I checked with cranking down the Saturation all the way back (to almost black-and-white), that adaptation WAS applied in the Library view. So it had to be something else, causing the same color difference between the Library and Development modules.
When I switch from the Library module to the Development module, I see a slight delay in applying my changes, but they are applied. Before they are applied, I can see that the original photo is shown and that looks the same as in the Library module and on Flickr.
The photostrip on the bottom of the Lightroom screen also shows the original photos only, unless I go to the development module and select a photo (adaptations are applied in the photostrip after I select the photo, not before).
After I played a bit more in the Development module, I found something strange in the Camera Calibration menu of the Development module. The Adobe Profile (my default) caused an obvious color difference between the Library (less saturated) and the Development (more saturated) modules. The Camera Standard profile also showed a (very) slight difference, but I was unable to notice the differences using the other profiles.
So I was thinking (but it's only a guess), that the profiles are not applied in the Library view and on export, but they are in the Development module?
I use Lightroom 5.6, Camera RAW 8.6.
Please help me, as this is very annoying. I currently cannot export my photos to Flickr or anywhere else, unless I overcompensate before exporting. And I really don't want to do that. My Lightroom photo is my perfect photo, and I want to keep it that way...
Many thanks in advance for any help,
Peter

Hi ssprengel,
Thanks for your reply. Let me react to each possibility you mention and provide some extra information.
- "Check your Export / File Settings / Image Format and make sure they are set to JPG not Original". Done that, it's not on Original, but on jpg. This would not explain why I see the difference in the Library and Development modules, by the way. But better to know for sure.
- "...the most likely thing that is wrong is your color-management on your computer is not working properly". It is a PC with Windows 7. I have been using Lightroom for maybe 6 years and I never had this problem before. The last time I changed my setup is more than a year ago and this problem only started to happen a short while ago (after the update to Lightroom 5.6? I'm not sure, but that's the only thing that has changed lately). I use a Spider to create a custom profile that is correct for my setup and do a regular update on the profile.
- "what brand and model of monitor do you have?" I have an EIZO FlexScan S2411W and use that for a long time as well. I chose this brand of monitors for its good color reproduction and I have been happy with it for years now.
What I am not getting is why would all this show a difference between the Library and Development module? The only difference is the Lightroom software that is switching from one module to another, and that should deliver the same photo. I'm also stating in my first post that the differences are very noticeable using the Adobe Standard Camera Profile in the Development module. I have a feeling that the profile is part of the problem.

Lightroom 2.x - Remapping Library / Develop module keyboard shortcuts (Windows)

SOLUTION: LR2 Library/Develop Keyboard Shortcuts
Prepared by: Gordon McKinney
http://www.night-ray.com
For windows users - this is the latest update to my keyboard shortcuts for Library and Develop module. It has improved performance through caching.
Quick access to Develop and Library module adjustments via your keyboard number pad. You'll need
www.AutoHotKey.com to use this script.
; Gordon's Lightroom 2.0 Shortcuts Aug-22 2008
; www.night-ray.com
; Use numpad to perform certain develop and library functions.
; This effectively disables the number pad for digit entry
; (except 5 and 0) please use the main keyboard instead.
; Left/Right - Prev or Next photo
; Up/Down - Exposure
; Minus/Plus - Fill Light
; Page Up/Dn - Contrast
; Home/End - Color Temperature
; Div/Mult - Color Tint
; Enter - Paste Previous
; Dot (Delete) - AutoTone
; F9 Library Module
; F10 Develop Module
; F11 Slideshow Module
; F12 Web Module
SetTitleMatchMode,2
#IfWinActive, Lightroom
F9::Send ^!1
F10::Send ^!2
F11::Send ^!3
F12::Send ^!4
#IfWinActive
; *** DEVELOP SHORTCUTS ***
#IfWinActive, Lightroom - Develop
numpad4:: Send ^{Left}
numpad6:: Send ^{Right}
numpad8:: lrdAdd(09)
numpad2:: lrdSub(09)
NumpadAdd:: lrdAdd(11)
NumpadSub:: lrdSub(11)
numpad9:: lrdAdd(14)
numpad3:: lrdSub(14)
numpad7:: lrdAdd(04)
numpad1:: lrdSub(04)
NumPadMult:: lrdAdd(05)
NumPadDiv:: lrdSub(05)
NumPadDot:: Send ^u
NumPadEnter:: Send ^!v
lrdAdd(delta) {
instance := lrGetControl( Static, 6, "Treatment :", delta )
ControlClick, Static%instance%
Send {=}
lrdSub(delta) {
instance := lrGetControl( Static, 6, "Treatment :", delta )
ControlClick, Static%instance%
Send {-}
#IfWinActive
; *** LIBRARY SHORTCUTS ***
#IfWinActive, Lightroom - Library
numpad4:: Send ^{Left}
numpad6:: Send ^{Right}
numpad8:: lrlClick(03)
numpad2:: lrlClick(02)
NumpadAdd:: lrlClick(11)
NumpadSub:: lrlClick(10)
numpad9:: lrlClick(23)
numpad3:: lrlClick(22)
numpad7:: lrlClick(-6)
numpad1:: lrlClick(-7)
NumPadMult:: lrlClick(-2)
NumPadDiv:: lrlClick(-3)
NumPadDot:: Send ^u
NumPadEnter::Send ^!v
lrlClick(delta) {
instance := lrGetControl( Button, 6, "Auto Tone", delta )
ControlSend, Button%instance%, {SPACE}, ahk_class AgWinMainFrame
#IfWinActive
; Fetch the Control Instance using Type, Title, and Instance Delta
lrGetControl( type, typeLen, title, delta ) {
global lrLastTitle, lrLastCBase, lrLastCache
if (lrLastTitle = title and lrLastCache > A_TickCount )
; Cached! Saves time.
return lrLastCBase + delta
else
WinGet, ActiveControlList, ControlList, ahk_class AgWinMainFrame
Loop, Parse, ActiveControlList, `n
IfInString, A_LoopField, %type%
ControlGetText, text, %A_LoopField%
IfInString, text, %title%
StringMid, controlbase, A_LoopField, typeLen+1
lrLastTitle := title
lrLastCBase := controlbase
lrLastCache := A_TickCount + (120*1000)
return controlbase + delta
return 999999
; End

latest update... I will work on making the script 'adapt' the LR's changing control IDs. However develop seems reliable. Until then - use this version
>; --------------------------------------------------
; Gordon's Lightroom 2.0 Shortcuts
; www.night-ray.com
SetTitleMatchMode,2
#IfWinActive, Lightroom
; Remap F keys for module change
F9::Send ^!1 ; F9 Library Module
F10::Send ^!2 ; F10 Develop Module
F11::Send ^!3 ; F11 Slideshow Module
F12::Send ^!4 ; F12 Web Module
#IfWinActive
; *** DEVELOP SHORTCUTS ***
#IfWinActive, Lightroom - Develop
; Use numpad to perform certain quick develop functions
; This effectively disables the number pad for digit entry
; please use the main keyboard instead.
; Left/Right - Prev or Next photo
; Up/Down - Exposure
; Minus/Plus - Fill Light
; Page Up/Dn - Contrast
; Home/End - Color Temperature
; Div/Mult - Color Tint
; Enter - Paste Previous
numpad4:: Send ^{Left}
numpad6:: Send ^{Right}
numpad8:: lrAdd( "Static144" )
numpad2:: lrSub( "Static144" )
NumpadAdd:: lrAdd( "Static146" )
NumpadSub:: lrSub( "Static146" )
numpad9:: lrAdd( "Static149" )
numpad3:: lrSub( "Static149" )
numpad7:: lrAdd( "Static139" )
numpad1:: lrSub( "Static139" )
NumPadMult::lrAdd( "Static140" )
NumPadDiv:: lrSub( "Static140" )
NumPadEnter::Send ^!v
lrAdd(class) {
ControlClick, %class%
Send {=}
lrSub(class) {
ControlClick, %class%
Send {-}
#IfWinActive
; *** DEVELOP SHORTCUTS ***
#IfWinActive, Lightroom - Library
numpad4:: Send ^{Left}
numpad6:: Send ^{Right}
NumPadEnter::Send ^!v
#IfWinActive
; End

Image contains camera White Balance setting; LR 5.5 only shows "As Shot", "Auto", and "Custom"

I have a new, Panasonic DMC-GX7. I shot a bunch of photos as JPGs. When viewing their Exif data using Exiftool, I can clearly see the camera's White Balance setting, as well as the Color Temp Kelvin, WB Red Level, WB Green Level, and WB Blue Level. However, Lightroom 5.5 only shows "As Shot", "Auto", and "Custom" when I click White Balance under Quick Develop on the Library tab or WB under Basic on the Develop tab. Exiftool shows the Exif Version as 0230 and the Panasonic Exif Version as 0405. Is LR looking for the white balance information in some other field? Do I need to configure it somehow for my camera? I am new to LR (but not to image processing), so could use some help figuring this out.

The whole question is not so simple as converting to DNG. Yes DNG is openly documented, yes the file can be read, but that does not mean it can be correctly interpreted by other software in the future and the best you can then do is starting the PP of your images from scratch. Imagine a DNG with LR adjustments that in some years you open the file in another software, possibly non-Adobe. Even if the file can be read it will not look the same, as the Adobe specific developing instructions could not be strictly followed. Even if all software manufactures agreed on a common set of adjustments, let's say everybody had a Highlights slider and a Clarity slider and so on, which is unlikely, the results would still be different as the underlying algorithms would be different.
Disclaimer: I only shoot raw and firmly believe it is the best option, but one must be conscious it has some shortcomings related to the future of our images.

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.

White Balance: Library versus Develop modules

Similar Messages

Maybe you are looking for