Lightroom Color Space Problem.

Hello,
I am processing my photos in Lightrrom. The histogram in Lightroom looks ok without any clipping, but when i export them to AdobeRGB or sRGB (for web) the photos have clipped shadows or highlights or both. I belive that the problem is that the histogram in lightroom reflect the data of the photo in ProPhoto RGB, and when you export to a narrow color space the clipping happens.
Is there any way to fix this? I will always have clipping if i export to AdobeRGB or sRGB? What do you do to not have this problem?
Beside of the clipping problem. The diferece between the histogram in the develop module in Lightroom and the histogram of the exported photo in AdobeRGB or sRGB makes that you don't know what the exported photo will look like, is like working blind. I don't know about you guys, but for me the is a big problem. Well, maybe if you work all in ProPhoto RGB this is a little issue.
I would appreciate a lot any help or comment that you could give me.
Thanks, :)
Marcelo.

Another thing I sometimes do is to save the development settings (save metadata in metadata menu) to file in LR, and then open the RAW in Camera RAW. In camera RAW the histogram reflects the color space you set, so you can optimize the development settings there. Then I close Camera Raw, which updates the xmp file (or the stuff written into the dng) and in LR do read metadata from file, which will apply the changed settings. This does the trick typically.

Similar Messages

Color space problem/confusion

I posted the following message to another thread, but at the recommendation of a member I am starting a new thread here. For a couple of answers see the thread below.
http://forums.adobe.com/message/3298911#3298911
I will provide much more information hoping an Adobe support person will chime in. This is extremely odd.
System: HP, AMD, Windows 7 64-Bit, Nvidia 9100, all updates to Windows, latest Nvidia 9100 driver
Display: Samsung 226CW, Windows settings 32-bit color, correct resolution,
Calibration: Done with ColorMunki, D65 target, done after monitor has been on for more than 30 minutes
Personal: (I am adding this information with some hesitation, please excuse it if it sounds like I'm bragging; I am not). I have multiple posts on my blog, have made many presentations on color managed workflow and am very comfortable with the settings in Photoshop and Lightroom. Please take this only as a baseline information, I am not bragging. In fact, I am begging for information!
Problem:
Any, I mean ANY, original JPEG image in sRGB space coming out of the camera with no adjustments, any PSD file in sRGB space, any TIFF file in sRGB space look significantly paler in Lightroom and in Photoshop CS5 than they look in other Windows based image viewers like FastStone or XnView. This should not need these applications to be color space aware, but the situation is the same with or without their color managment turned on or off. I have done the following:
1. Totally uninstalled Lightroom 3 and reinstalled it
2. Recreated a brand new Lightroom catalog/library and reimported all the images, converting all the RAW files to DNG (just in case!)
3. Recalibrated the display
When I view a file, any file and I will use for the sake of simplicity a JPEG file in sRGB color space, in Lightroom it looks pale. Since the file is in sRGB color space, I have verified this, the rendering in Lightroom should be the same as rendering in anything else. But it is not. I took my monitor and connected it to this system with the same odd behavior of rendering in Lightroom being much paler than outside. It appears as if I am viewing an image in Adobe RGB in a windows viewer that is not color managed.
I further tried the following:
1. I copied various versions of one file, all in sRGB color space. One PSD and two JPEG files from the folders of the above system and copied them to my system, Intel, Windows 7 64-bit, display calibrated and profiled with ColorMunki to the same standards as the problem system above.
2. Imported them to Lightroom on my system
3. The rendering in Lightroom is identical to rendering outside Lightroom for all the files and all are same as the rendering in FastStone on the problem system. Outside rendering was done using FastStone as on the problem system.
My deduction is that something on the problem system outlined in the opening of the message is interfering with the Adobe rendering engine and I have no idea what it could be. I WILL GREATLY APPRECIATE if an Adobe engineer could chime in and steer me in the right direction. I am willing to try other things but I have run out of ideas despite the fact that I have reduced much of the problem to the lowest common denominator of sRGB and JPEG against a PSD in sRGB.
Waiting anxiously of your help.
Cemal

Also, I know enough to calibrate a monitor when it is connected to a new computer. That said, even without calibration the behavior should have changed to display all the images in question the same but perhaps with somewhat off colors. Am I right? I am not arguing the point, I am rhetorically raising the question. If the 226CW is wide gamut and 244T is not, when I connect 244T on the same computer the wide gamut issue should be eliminated, should it not? I am not talking at this point about the "correct" color, but the same color in or out of Lightroom.
Unfortunately when you connect another monitor to a computer and don't calibrate or manually change it, Windows will not change the monitor profile. Macs will autodetect and change the profile but this innovation has not reached windows yet. The behavior you observe is caused by managed apps using the monitor profile and unmanaged apps not. If the monitor profile is not changed, the behavior doesn't change.
BTW, for a "cheap" software to be color space aware it does not need a quantum leap in technology I believe. It simply needs to know how to read the ICC profile and the LUT, is that correct?
It's extremely simple to program color management into apps. Standard API libraries have been available in Windows for over a decade. The reason why this hasn't happened is related to the fact that Microsoft hasn't made IE color managed and the software makers do not want to confuse folks when images look different in their program vs IE. Considering that this still is the biggest issue people wrongly complain about in every color managed application (just check Photoshop fora) that is maybe not that strange.

Color Space Problem

Ok so I'm having a huge problem with when I go from lightroom to photoshop to edit it is changing the color space on my photos and is causing me a lot of headache and my photos to look muddy and the colors to be off. I know this because the photos I started editing in lightroom and switched over say that they were for some reason save in Pro photo RbG and then the photos I pulled up directly from camera raw to photoshop save in srbg. I would love to know what setting in lightroom I need to change to make this not happen anymore! Thank you!

Also, I know enough to calibrate a monitor when it is connected to a new computer. That said, even without calibration the behavior should have changed to display all the images in question the same but perhaps with somewhat off colors. Am I right? I am not arguing the point, I am rhetorically raising the question. If the 226CW is wide gamut and 244T is not, when I connect 244T on the same computer the wide gamut issue should be eliminated, should it not? I am not talking at this point about the "correct" color, but the same color in or out of Lightroom.
Unfortunately when you connect another monitor to a computer and don't calibrate or manually change it, Windows will not change the monitor profile. Macs will autodetect and change the profile but this innovation has not reached windows yet. The behavior you observe is caused by managed apps using the monitor profile and unmanaged apps not. If the monitor profile is not changed, the behavior doesn't change.
BTW, for a "cheap" software to be color space aware it does not need a quantum leap in technology I believe. It simply needs to know how to read the ICC profile and the LUT, is that correct?
It's extremely simple to program color management into apps. Standard API libraries have been available in Windows for over a decade. The reason why this hasn't happened is related to the fact that Microsoft hasn't made IE color managed and the software makers do not want to confuse folks when images look different in their program vs IE. Considering that this still is the biggest issue people wrongly complain about in every color managed application (just check Photoshop fora) that is maybe not that strange.

Camera Raw vs Lightroom Color Spaces

I photographed RAW image of a Gregtag color target with my Nikon D300 and opened it in camera raw in the ProPhoto Color space and adjusted the develop sliders so that the tone squares on the bottom row matched the ProPhoto values, (e.g approx 238,189,144,103,66,37) and ran the Robert Fors calibration script.
So far so good. I have read that all one needs to do is use the same settings in Lightroom. But when I opened the exact same RAW file in Lightroom and use the exact same develop and calibration settings that I used in ACR, it gives different values for the tone squares. And in fact the values are almost exactly the values for Adobe RGB (e.g. approx 242,200,159,121,84,53). And when I open that file in Photoshop from Lightroom using the ProPhoto color space option the value stay at the same Adobe RGB levels within the ProPhoto color space.
What am I missing/doing wrong?

the values in lightroom are not based on prophotoRGB, but on a prophotoRGB-derived space with the same primaries but with a sRGB tone curve. Since adobeRGB has almost the same tonecurve as sRGB, your values came out close. Bottomline is that the values do not correspond to the ppRGB values in ACR.

Color Space Problems w/ Files?

I use Lightroom 2.5 to manage my photos. There are several things I don't understand regarding embedded color spaces in files.
When I export a file from LR to Photoshop CS4 as a TIF in the Adobe RGB color space the file shows as "Uncalibrated" in the EXIF & XMP metadata.
Using PS CS4, if I save a JPG file from the above Adobe RGB TIF file, and then use the edit -> convert to profile function, with Destination Space -> Adobe RGB selected, toggling the preview check box shows a color shift in the image. If I convert an image to the same color space why is there a color shift?
Is the color profile stored in the EXIF or XMP metadata?
Jack

I can provide some general information on the topic, though I do not use Lightroom so thers may jump in.
Information about color space is contained within the tiff file proper. That is, in a tag (the T in TIFF) and if I am correct it is tag 262 (PhotometricInterpretation). I do not know if LR also puts this info into the metadata.
When you convert a file to jpg you invoke the YCbCr color space and convert your source data into it. That is, the "compression" process also involves a color space change if you did not start out with YCbCr. This could account for the color shift you are seeing.
Paulo

DeviceN color space problem

I'm trying to create a DeviceN color space, all is fine but when I set the PDEContent to the page I get segfault
can someone try to help me ?
        CosDoc cosDoc= PDDocGetCosDoc( pdDoc );
        CosObj clrspc = CosNewArray(cosDoc,true,4);
        CosArrayPut(clrspc,0,CosNewNameFromString(cosDoc,false,"DeviceN"));
        CosObj names=CosNewArray(cosDoc,false,6);
//adding colors name
        CosArrayPut(names,0,CosNewNameFromString(cosDoc,false,"Cyan"));
        CosArrayPut(names,1,CosNewNameFromString(cosDoc,false,"Magenta"));
        CosArrayPut(names,2,CosNewNameFromString(cosDoc,false,"Yellow"));
        CosArrayPut(names,3,CosNewNameFromString(cosDoc,false,"Black"));
        CosArrayPut(names,4,CosNewNameFromString(cosDoc,false,"Spot1"));
        CosArrayPut(names,5,CosNewNameFromString(cosDoc,false,"Spot2"));
        CosArrayPut(clrspc,1,names);
        CosArrayPut(clrspc,2,CosNewNameFromString(cosDoc,false,"DeviceCMYK"));
        CosObj domain=CosNewArray(cosDoc,false,12);
        CosArrayPut(domain,0,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,1,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,2,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,3,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,4,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,5,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,6,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,7,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,8,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,9,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,10,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,11,CosNewFloat(cosDoc,false,1.0));
        CosObj range=CosNewArray(cosDoc,false,8);
        CosArrayPut(range,0,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,1,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,2,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,3,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,4,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,5,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,6,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,7,CosNewFloat(cosDoc,false,1.0));
        CosObj cosFuncDict = CosNewDict(cosDoc,false,4);
        CosDictPut(cosFuncDict,ASAtomFromString("FunctionType"), CosNewInteger(cosDoc, false, 4));
        CosDictPut( cosFuncDict, ASAtomFromString("Domain"),domain );
        CosDictPut( cosFuncDict, ASAtomFromString("Range"), range );
        char* psFunc="{0.3 0.4 0.5 0.1}";
        ASInt32 iSize = strlen(psFunc);
        CosDictPut( cosFuncDict, ASAtomFromString("Length"),CosNewInteger(cosDoc, true, iSize ) );
        ASStm objNewStream = ASMemStmRdOpen( psFunc, iSize);
        CosObj psFuncStreamObj = CosNewStream( cosDoc, true, objNewStream, 0, false, cosFuncDict, CosNewNull(), -1 );
        ASStmClose(objNewStream);
        CosArrayPut( clrspc, 3, psFuncStreamObj );
        PDEColorSpace pdeColorSpace = PDEColorSpaceCreateFromCosObj( &clrspc );
        ASFixed notused = fixedZero;
        ASFixed basex = FloatToASFixed(0);
        ASFixed basey = FloatToASFixed(0);
        ASFixed maxx = FloatToASFixed(200);
        ASFixed maxy = FloatToASFixed(200);
        PDEPath pdePath = PDEPathCreate();
        PDEPathAddSegment(pdePath, kPDEMoveTo, basex, basey, notused, notused, notused, notused);
        PDEPathAddSegment(pdePath, kPDELineTo, basex, maxy, notused, notused, notused, notused);
        PDEPathAddSegment(pdePath, kPDELineTo, maxx, maxy, notused, notused, notused, notused);
        PDEPathAddSegment(pdePath, kPDELineTo, maxx, basey, notused, notused, notused, notused);
        PDEPathAddSegment(pdePath, kPDEClosePath, notused, notused, notused, notused, notused, notused);
        PDEPathSetPaintOp(pdePath, kPDEFill|kPDEStroke);
        PDEGraphicState gState;
        memset(&gState, 0, sizeof(PDEGraphicState));
        /* graphic state initialization */
        gState.strokeColorSpec.space = pdeColorSpace;
        gState.fillColorSpec.space = pdeColorSpace;
        gState.miterLimit = fixedTen;
        gState.flatness = fixedOne;
        gState.lineWidth = fixedZero;
        /* setting colors */
        gState.strokeColorSpec.value.color[0] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[1] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[2] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[3] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[4] = FloatToASFixed(1);
        gState.strokeColorSpec.value.color[5] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[0] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[1] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[2] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[3] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[4] = FloatToASFixed(1);
        gState.fillColorSpec.value.color[5] = FloatToASFixed(1);
        /* add color to swatch */
        PDEElementSetGState ((PDEElement)pdePath, &gState, sizeof(gState));
        /* adding swatch to main container */
        PDEContentAddElem(pdeContent, kPDEAfterLast, (PDEElement) pdePath);
        PDPageSetPDEContent(pdPage, NULL);

Now I tried to do that differently (always without success) with PDE Layer,
I create my function as usual
CosObj domain=CosNewArray(cosDoc,false,12);
        CosArrayPut(domain,0,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,1,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,2,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,3,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,4,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,5,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,6,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,7,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,8,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,9,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(domain,10,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(domain,11,CosNewFloat(cosDoc,false,1.0));
        CosObj range=CosNewArray(cosDoc,false,8);
        CosArrayPut(range,0,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,1,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,2,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,3,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,4,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,5,CosNewFloat(cosDoc,false,1.0));
        CosArrayPut(range,6,CosNewFloat(cosDoc,false,0.0));
        CosArrayPut(range,7,CosNewFloat(cosDoc,false,1.0));
        CosObj cosFuncDict = CosNewDict(cosDoc,false,4);
        CosDictPut(cosFuncDict,ASAtomFromString("FunctionType"), CosNewInteger(cosDoc, false, 4));
        CosDictPut( cosFuncDict, ASAtomFromString("Domain"),domain );
        CosDictPut( cosFuncDict, ASAtomFromString("Range"), range );
        char* psFunc="{0.1 0.1 0.9 0.1}";
        ASInt32 iSize = strlen(psFunc);
        CosDictPut( cosFuncDict, ASAtomFromString("Length"),CosNewInteger(cosDoc, true, iSize ) );
        ASStm objNewStream = ASMemStmRdOpen( psFunc, iSize);
        CosObj psFuncStreamObj = CosNewStream( cosDoc, true, objNewStream, 0, false, cosFuncDict, CosNewNull(), -1 );
        ASStmClose(objNewStream);
then I create my colorspace
        PDEDeviceNColorData data;
        data.size = sizeof(data);
        data.names=calloc(1,sizeof(ASAtom));
        //~ data.names[0]=ASAtomFromString("Cyan");
        //~ data.names[1]=ASAtomFromString("Magenta");
        //~ data.names[2]=ASAtomFromString("Yellow");
        //~ data.names[3]=ASAtomFromString("Black");
        //~ data.names[4]=ASAtomFromString("Orange");
        //~ data.names[5]=ASAtomFromString("Green");
        data.nNames=0;
        data.alt=PDEColorSpaceCreateFromName(ASAtomFromString("DeviceCMYK"));
        data.tintTransform=psFuncStreamObj;
        PDEColorSpaceStruct spcstruct;
        spcstruct.devn=&data;
        PDEColorSpace pdeColorSpace=PDEColorSpaceCreate(ASAtomFromString("DeviceN"),&spcstruct);
If I create a pdf document like this all work fine and my DeviceN colorspace is well defined:
     11 0 obj
      [/DeviceN[]/DeviceCMYK 12 0 R]
      endobj
      12 0 obj
      <</Domain[0.0 1.0 0.0 1.0 0.0 1.0 0.0 1.0 0.0 1.0 0.0 1.0]/FunctionType 4/Length 17/Range[0.0 1.0 0.0 1.0 0.0 1.0 0.0 1.0]>>stream
      {0.1 0.1 0.9 0.1}
      endstream
     endobj
Now when I try to add one colorant (Orange or Cyan for example), my application crash, and I don't know why either ...
Can somebody say me what I miss ?
Regards,
William

Color space problems

Somewhere the colors seem to get messed up. Viewing in LR and Photoshop the skin tones look pink but when viewing in windows photo gallery on computer or typepad site the skin tones are grey. I have LR and Photoshop set to ProPhoto rgb 16 bit resolution 240, monitor calibrated with spyder 3 and exporting file setting is procolor rgb. Does anyone know what's wrong? Where are my settings getting messed up. It really is messing with my editing b/c I keep trying to put more pink in b/c I know it'll print and web view more grey than I see it in LR/cs3. Very frustrating. At this point I'm afraid to edit any photos b/c nothing is what it seems.
thx for any advice.

>and exporting file setting is procolor rgb. Does anyone know what's wrong?
Yes. You're using prophotoRGB. The other apps you mention are not color managed and thus do not understand the prophotoRGB profile. You need to use the sRGB color space and even then will you see small differences if your screen is correctly calibrated and profiled. Non-managed apps (internet explorer and such) always lie to you color wise, even if you calibrate your screen. Read this excellent (but long) article on this: http://regex.info/blog/photo-tech/color-spaces-page1 If your images are meant for web viewing, ALWAYS use sRGB.
Also consider using a managed browser. Safari is one and Firefox (
using the secret setting) is another. Flash galleries will not be color managed even in those programs however.

Color spaces problem

Hi guys, i try to make a program that would let me choose a color, then modify some images i need using the color i choose. so i have an image, 12x12 pixels, casted to a BufferedImage. I loop through each pixel (counters x and y), executing:
mybufferedimage.setRGB(x,y,mycolor.getRGB());
sadly, the image i gat is not at all a square of my specified color, instead it is some other color (i noticed a similarity between my color's brightness and the colour that got on the image, but i'm not sure it has any relevance). I'm thinking this may be due to differences in Color Spaces (hence the title of this topic) but i am not sure.
so my question is this:
I have myColor and myBufferedImage. How do i set some (any) pixel(s) in myBufferedImage to be of the same color as myColor? And please explain (if you can) why my variant doesn't work.
thanks.

Teodor.Sandu wrote:
Hi guys, i try to make a program that would let me choose a color, then modify some images i need using the color i choose. so i have an image, 12x12 pixels, casted to a BufferedImage. Where does this image come from? What does calling getType() on the BufferedImage return?
I loop through each pixel (counters x and y), executing:
mybufferedimage.setRGB(x,y,mycolor.getRGB());How is 'myColor' created?
Post an SSCCE:
http://www.physci.org/codes/sscce.html
Jim S.

Photoshop Edits Import into Lightroom, Color/Noise Problems

Hello! When I edit photos in Photoshop (CS5), it looks completely different when I save it/re-import it into Lightroom. The color is usually way off, and there tends to be a significant amount of noise in the imported version. Tiffs v. Jpegs makes no difference. I read in another forum that someone else said he only has this problem with his Canon 7D files. My files are all Canon 7D. Would that be a Canon problem to solve, or Adobe? I'm attaching a screenshot of an image I had just saved in Photoshop, and then how it appears when it automatically re-imported back to Lightroom. Thank you for any help you can provide. It's killing me to work so hard on my images, just to have them look completely different afterwards.
Thanks, Heather

Looks like you are applying a preset, have set camera defaults, or have enabled auto-tone. In Develop, all sliders should be at zero for tif files. You probably have a large amount of shadow fill dialed in. Go into your preferences and make sure to uncheck "apply auto tone adjustments" Also reset all default camera adjustments in the same dialog. Then hit reset on the file in develop.

Lightroom color export problem

Hello there. When I export a photo in lightroom it does not export the photo with the same colors as in lightroom. It loses some of the warmth, and that not very helpful. The problem might very well be in lightroom, because when I convert to black and white the picture still has a slight yellow-ish color to it, but when exported it becomes regular black and white. I've tried all the export color settings and that doesn't help. I have also checked if there is a filter that applies when importing, but there don't seem to be. What do you guys think?
I've just exported and open the photo on the left.

You see that the histogram also has a slightly yellow tint? That's because you have a corrupted monitor profile. You can confirm it using these instructions: http://members.lightroomqueen.com/Knowledgebase/Article/View/1137/188/how-do-i-change-my-m onitor-profile-to-check-whether-its-corrupted

Logic of Lightroom Color Management

There are, I know, endless posts about Lightroom color management issues. This question, I hope, will be somewhat different, as I don't have a specific problem, yet, but am trying to understand the logic of the software in the hope of avoiding problems down the road (as when I add file types, e.g.) I am also reading a book on color management, but it is on general theory with specific references to Photoshop CS3 (or 2), not to Lightroom. So here are my two questions and I'm hoping that the answers, should I be fortunate enough to receive any, will help not only me but other neophytes.
First, the Adobe online manual says this: "For rendered files such as TIFF, JPEG, and PSD files, Lightroom uses the images embedded color profile to display the image, histogram, and color values. If the image doesnt have a profile, Lightroom assumes the sRGB profile, and the image may not look as expected on your monitor." Clear enough, but what does CS3 do when it is launched from Lightroom to do pixel editing on an image primarily managed in Lightroom? That is, if CS3 is used essentially as a Lightroom plugin does CS3 adopt the Lightroom color management or does CS3 independently have to be set appropriately for the image to appear the same in CS3?
Second, the online manual says this: "Raw photo files generally dont have embedded color profiles. For raw files, the Develop module assumes a wide color space based on the color values of the ProPhoto RGB color space. ProPhoto RGB encompasses most colors that cameras can record." This is confusing, at least to me. Consider the paragraph above in this post, where the manual explains (or at least intimates) that if you create a file with values of a broad gamut such as Adobe RGB but don't embed that profile Lightroom will think it has a narrower gamut, sRGB file and the display will be off (unsaturated and washed out, I presume). That makes perfect sense. But why, then, does Lightroom assume for RAW files the wide Prophoto RGB color space when a camera might not record across this gamut? Wouldn't a camera that records in a narrower gamut cause the same problems for the display as does an Adobe RGB file read as if it were an sRGB file?
Thanks in advance.

>For rendered files such as TIFF, JPEG, and PSD files, Lightroom uses the images embedded color profile to display the image, histogram, and color values. If the image doesnt have a profile, Lightroom assumes the sRGB profile, and the image may not look as expected on your monitor.
Funny but if this came from the manual it is actually incorrect. For tiff, jpeg and psd files, the image is rendered into the linear lightroom color space using the embedded profile or assuming sRGB if there is no color tag on the image. The histogram Lightroom shows is always based on the Lightroom color space with a gamma 2.2 toning curve applied no matter what the source of the file. To answer your question, if you do an "edit in CS3" from Lightroom a copy of the file is rendered in the color space that you requested in the dialog and CS3 uses that space if your Photoshop is correctly set up to respect embedded profiles.
>Raw photo files generally dont have embedded color profiles. For raw files, the Develop module assumes a wide color space based on the color values of the ProPhoto RGB color space. ProPhoto RGB encompasses most colors that cameras can record.
The manual is again not correct here! Embarrassing. I have never seen a RAW file with an embedded profile so generally is incorrect. Also, for RAW files, the module DOES NOT assume prophotoRGB color space. The actual primaries are actually stored in a internal database that is based on calibrations that Thomas Knoll and other ACR engineers did of the specific type of camera. They ARE not the prophotoRGB primaries. The RAW files are rendered into MelissaRGB using those primaries. MelissaRGB has ppRGB primaries but a linear gamma instead of 1.8.
>hat makes perfect sense. But why, then, does Lightroom assume for RAW files the wide Prophoto RGB color space when a camera might not record across this gamut? Wouldn't a camera that records in a narrower gamut cause the same problems for the display as does an Adobe RGB file read as if it were an sRGB file?
See above, the manual is wrong. Lightroom knows the actual gamut of your camera and uses that, not prophoto.

Problem of color spaces when i switch between photoshop cc 2014 and lightroom 5.7. where to ask

hallo,
where can we ask questions on photoshop cc 2014 tools ?
i have a prophoto nef in lightroom which is retouched.
i edit in photoshop cc to make a selection and come back to lightroom with a huge psd.
it says color space of photoshop is not correct and advises prophoto. i say yes.
first one day i lost the pen tool mask when i wanted to re-edit from lightroom. fortunately the version of psd on hard disk was ok. never understood what happened
second is i want to open a jpg background on my hard disk, perhaps srgb, in photoshop and add the selection.
how to manage color spaces because my colors of the selection or the background become ugly
not sure i still need to use lightroom for this step. bridge or photoshop itselfs can open files,...
best regards
marc

That's great, but what exactly did it - matrix (gamma) profiles instead of LUT? It would be good to know for future reference.
I have seen small problems with LUT profiles in Firefox, like black clipping up to value 6 or 7, but Lightroom seems to behave well with LUT profiles here. The problem with LUT profiles is that they are "heavier" and more complex, because they contain complete tables for all possible transformations - whereas matrix profiles do it by much simpler mathematical formulae. LUT is more accurate, but matrix simpler and more reliable.
Not that I think accuracy is a problem with Eizo CGs. Which is why it's a bit puzzling that ColorNavigator has LUT as default. I use mostly matrix targets these days, my feeling is that the simpler the profile, the better.

Color problem with ProPhoto RGB color space

Hi, everyone,
I have wery special problem I think. I use MacBook pro 15" with retina display, adobe Photoshop CC and when I export RAW (from Nikon D7000) from Lightroom 5 to Photoshop with settings: 16 bit TIF, color space: ProPhoto RGB I have a problem with displaying the correct colors. As you can see in this picture:
My problem are some "green" artefacts in absolutely black and white picture. I tried myself to solve this problem and found the following facts: when I convert picture into Adobe RGB or sRGB color space is everything OK - without green artefacts.
But here is one important fact: I have calibrated monitor by datacolor spyder4elite and problem with ProPhoto RGB incorrect color displaying is only when the color calibration configuration is loaded. When I change my display calibration to standard apple color LCD profile than is everything OK.
But using uncalibrated monitor and also Adobe RGB color space are no right solutions for me.
My question is why I have problem with displaying ProPhoto RGB color space in photoshop under calibrated monitor profile and can anybody help me please?
Thanks for answers.

That's a classic example of the basic problem with 16 bit color. There is no solution that I know of.

Lightroom,Nik plugins and color spaces

I'm having an issue and not sure who is holding the smoking gun. I have the Nik ultimate collection installed which covers Lightroom and Photoshop CS5 extended. I work primarily in Lightroom and apply most corrections globally but occasionally i need to do localized adjustments so the photo gets shipped off to Photoshop. Here's a typical scenario:
1) From Lightroom edit in Dfine 2.0 for noise - as copy with Lightroom adjustments which gets copied as a tiff.
2) From Lightroom edit in Viveza 2 - as original since we're now working with a tiff and I don't want a copy for every single thing I'm doing.
3) Edit in Photoshop
Now there's two issues at this point:
1) The edits do not show up in the Lightroom history - it's like nothing happened.
2) Photoshop will complain that the assigned profile is sRGB. Really?
#1 is a PITA because if I want to rewind I have to start all over since there's no history - what exactly is responbsible to set an edit as history? Lightroom or the plugin?
#2 is by far the most serious as it degrades the work in a seriously bad manner. I mean, WTH - I'm moving along in ProPhoto Ferrarri space and all of a sudden - *boom* - I'm running in sRGB moped mode.
I looked at edit->Preferences->External Editing -> Additional External Editor and indeed when I select the Nik plugins from the combo box preferences the default for the plugins is sRGB. I can change to ProPhoto and quit. I repeated this for each plugin assuming that somewhere the setting was remembered. Nope LR acts dumb as a rock and shows sRGB as the defaults for all except the currently selected plugin.
So my questions are:
- who's gonna own up to the problem - LR or Nik?
- how can I work around it?
- how can I make LR remember the settings? Not a registry key nor INI file in sight to set them - so where/how are the plugins tracked?
Thanks for any help!
Jon

Jon,
The User Interface for changing how external editors are invoked is about as smart as your average chunk of granite.
After you change the Color Space to the one you want, you have to click on the Preset box and choose "Save current settings as new preset...". Not exactly intuitive, but there you are.
Hal

Photoshop not seeing export color space setting in Lightroom 4

MY LR or PS programs are not acting as expected.
When my Lightroom 4 is set to export to Photoshop in either the sRGB color space or the AdobeRGB color space, and Photoshop is set for the sRGB space, Photoshop gives a color mismatch error in both cases, saying the image is an AdobeRGB embedded image. However, if the color space in PS is set for AdobeRGB, even if the export setting in Lightroom is sRGB, there is no mismatch error.
Apparently, PS sees every image as embedded with AdobeRGB.
I have a Sony NEX6 camera. I have taken pictures in the camera sRGB color space and the AdobeRGB space, which I used for this test. Since I shoot in RAW, this should not matter, so I don’t think it is the issue, and, in fact, I get the same result no matter which color space the camera is in.
If LR export and PS color space are the same, why should there be a mismatch, and why is PS not seeing the sRGB space? Might there be a setting in Lightroom or Photoshop that I am missing?

howdego wrote:
I am, however, trying to decide on the right color space to use, which is how I noticed this problem. I rarely make prints of my photos. I make bluray movies using Proshow Producer. I recently got a new monitor and Samsung LED HDTV, and found that my photo videos did not display right and I am trying to find out why. I found the normal viewing settings of the TV have too much color and sharpness, so I established another group of settings for photos, which helped. However, I am still not satisfied.
These are two separate but related issues.
1) It's almost impossible to get accurate Color and Luminance level rendering inside LR if you don't use a hardware monitor calibrator to adjust your computer monitor.
2) LCD TV's use settings to "enhance" color, brightness, and contrast that is usually very, very inacuuarte. But this is what most non-photography people seem to like so TV manufacturers crank up the "default settings." I also have an older 52" Samsung TV (LN-T5265F) that I've manually adjusted for more accurate color. Try using the 'Movie' mode, which is the most accurate mode and turn the Backlight setting down. Here are the settings I use with my Samsung TV. I assume your Samsung TV's controls are similar:
Setup Screens
HDMI 1 (Cable Box) & Coax (Cable)
HDMI 2 (Panasonic Blu-Ray Player)
PICTURE - 1
Movie
Standard
Dynamic
Movie
Standard
Dynamic
Contrast
82
82
82
82
82
82
Brightness
43
45
45
43
45
45
Sharpness
25
25
35
15
15
25
Color
42
45
45
44
45
45
Tint
77 R
77 R
84 R
77 R
77 R
84 R
Backlight
5
6
7
5
5
6
PICTURE - 2
Color Tone
Normal
Normal
Normal
Normal
Normal
Normal
Detailed Settings
Black Adjust
Off
NA
NA
Off
NA
NA
Dynamic Contrast
Low
NA
NA
Low
NA
NA
Gamma
-1
NA
NA
-1
NA
NA
Color Space
Auto
NA
NA
Auto
NA
NA
White Balance
R-Offset
13
NA
NA
13
NA
NA
G-Offset
15
NA
NA
15
NA
NA
B-Offset
17
NA
NA
17
NA
NA
R-Gain
15
NA
NA
15
NA
NA
G-Gain
12
NA
NA
12
NA
NA
B-Gain
17
NA
NA
17
NA
NA
My Color Control
Pink
15
NA
NA
15
NA
NA
Green
15
NA
NA
15
NA
NA
Blue
15
NA
NA
15
NA
NA
White
15
NA
NA
15
NA
NA
Edge Ehnacement
On
NA
NA
On
NA
NA
xvYCC
Off
NA
NA
Off
NA
NA
Digital NR
Low
Low
Low
Low
Low
Low
Active Color
Off(NA)
Off(NA)
Off
Off(NA)
Off(NA)
Off
Dnie
Off(NA)
Off
Off
Off(NA)
Off
Off
SETUP - Screen 2
Energy Saving
Off
Off
Off
Off
Off
Off
SETUP - Screen 3
HDMI Black Level
Low
Low
Low
Low
Low
Low
Film Mode
Off(NA)
Off(NA)
Off(NA)
Off(NA)
Off(NA)
Off(NA)
howdego wrote:
So it occurred to me that some colors might be wrong, or too saturated, because I am not seeing them on my monitor as they will appear on the HDTV. I am thinking that since sRGB is my final color space, I would try to do everything in the sRGB space, including setting my monitor to sRGB (I have a Dell 2413 which supports adobeRGB too). I was inn the process of trying this when I found the issue at hand. Might you have any thoughts about this color space choice
If you have a wide-gamut monitor you are better off using it in Adobe RGB mode with a monitor calibrator. But then the monitor will not look correct in non-color managed applications:
http://www.gballard.net/photoshop/srgb_wide_gamut.html
You can circumvent this issue by using your monitor in sRGB mode, but I'd still suggest you use a hardware monitor calibrator. Either way it is imortatnt that you have a proper monitor profile assigned in Windows or OS X Color Management. The monitor manufacturer provides these, but they don't always work well with LR for numerous reasons.
To insure the best image quality you should do all of your editing in PS using 16 bit TIFF with ProPhoto RGB profile format until you are ready to Export. For use with ProShow you can use TIFFs or JPEGs, but use sRGB color profile to avoid any color management issue. JPEGs are fine and a LR Quality higher than 80 (10 in PS) is a waste of disk space for slideshow images.
In short you've got a lot of "variables" between the uncalibrated monitor and out-of-the-box non-adjusted TV. The former requires a good hardware calibrator aad the latter a good "eye" to adjust it.

Lightroom Color Space Problem.

Similar Messages

Maybe you are looking for