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.

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.

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.

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 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

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.

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.

I have a problem with color prints from photoshop elements 12. The pictures are too light and with strange colors. I have a Canon pixma mg615I0 printer and use mac os X yosemite. The pictures are taken with a coanon eos 550d in the color space sRGB. I hav

Hi
I have a problem with color prints from photoshop elements 12. The pictures are too light and with strange colors. I have a Canon pixma mg615I0 printer and use mac os X yosemite. The pictures are taken with a coanon eos 550d in the color space sRGB. I have followed adobes recommendations and have tried both letting the printer respektive photoshop manage the colors. But nothing works. I see that there are different opinions about which is best to do so I tried both. I have the latest printer driver installed. Can anyone help me with this?

Do the following:
Print a test page from the printer. Perhaps the print head needs cleaning via its maintenance facility.
Let the printer manage colors, not PSE
Calibrate the monitor

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 space-creating a book in My publisher-.when I look at the share book pre print the colors are all dulled out. I work in pro photo rgb in LR and PS -.My Pub is sRGB-.where is the problem?

Color space…creating a book in My publisher….when I look at the share book pre print the colors are all dulled out. I work in pro photo rgb in LR and PS ….My Pub is sRGB….where is the problem?

I finally got to my references. This had to do with "soft proofing" on screen in Photoshop.
So this may not help you at all. Re: Strange sRGB soft-proofing behavior So go ahead and leave that setting at Basic.
However there is a Color Management forum that you also go to and see if anyone has answers for your particular problem.
Here is the link: Color management
I hope they can help you out.
Gene

Watermark, color space, and transparency problem

I'm having a problem with inserting a watermark image into my pdfs.
I created the watermark image in Photoshop. It is 8-bit gray with a transparent background. I saved it as a pdf (pdf 1.4 to allow transparency).
The main pdfs (to be watermarked) are created through a seperate process (they are scans of old book pages). The pdfs are produced from 8-bit gray tiff images, but I cannot determine what color space the these pdfs are.
To the problem: in Acrobat 9, when I insert the watermark above, all of the blacks on the page shift to grey, as if the opacity was shifted lower. The opacity is set to 100%, so this should not be a problem! The watermark does have a transparent background, though.
Since this seems to be a color space conflict, if I save the watermark PDF in CYMK or RGB, it does not cause the tonal shift (blacks remain true), but the watermark now has an opaque background. I need it to be transparent, as the background of the files to be watermarked are not tonally consistent (old discolored paper).
I guess these are my questions:
(1) Is there any way to determine the color space of a PDF? File->Properties does not list color space.
(2) Why does the watermark PDF, saved in CYMK or RGB, not allow a transparent background? Is this an Acrobat issue or color space?
(3) Does anyone have an idea on how to solve this? :)
Thanks a bunch.

First, I have 2 questions: 1) How do the color and watermark background look when you have Advanced > Print Production > Output Preview open? 2) What version of Acrobat are you working in?
The most common reason that people see an almost "washed out" appearance (or looking as though additional opacity is applied) is due to a bug in Acrobat 8. This was fixed in the 8.1 dot release. One way to determine if this is what you are running into is to view the file with the Output Preview dialog open. If it views correctly then, make sure you have the update installed.
I don't work with watermarks, but understanding the general concept of watermarks it seems like a reasonable guess that they would use overprinting. I'm wonder if this is what is affecting the display of them (non-transparent background) since Acrobat needs Overprint Preview ON to accurately display objects with overprint flags . As with above, turning on Output Preview will help you deduce if that's what is happening since Output Preview automatically enables Overprint Preview (which is off by default).
BTW, Preflight will let you know what color spaces are in PDF file. Run any Profile. In the results panel, drop down the "Overview" section. There you will find a color spaces section listing the color spaces of the document.

Color space conversion problem when importing JPEG's

Hi,
I'm currently playing with the trial version of LR. While importing JPEG's with different color spaces (sRGB and Adobe RGB) to LR I've noticed a strange effect: There is a small but noticable difference in color, depending if the JPEG was previously saved in AdobeRGB, or sRGB. All the images I've tested so far should not contain critical colors that exceed normal sRGB. When opened in CS2 both versions of a JPEG, AdobeRGB and sRGB, typically look perceptually identical, no matter if I leave the sRGB image to sRGB, or convert it to the working space (AdobeRGB). Also my color-managed image viewer behaves as it should. So I don't think it's a matter of the different color spaces.
Looking at the imported images in LR I would say that the AdobeRGB image is correctly converted while the sRGB image suffers from a slight reddish cast, most noticable in skin tones. The effect is not as strong as if I would load the sRGB image into CS2 and skip color conversion to my working space (AdobeRGB).
The sRGB versions of the JPEG's were obtained from the AdobeRGB JPEG's using CS2 for conversion.
Anyone else here experienced a similar problem? Is this a bug in the xRGB-to-ProPhotoRGB conversion of LR, or a feature?
/Steffen

Hi Uli,
thanks for pointing me to your thread. I followed the discussion with great interest. Actually, I think the effect I am describing here is of different nature and a LOT stronger, at least for the type of images I've tested.
I did some more experiments yesterday with interesting results:
1) When I export a processed RAW from LR to JPEG or PSD, no matter what Color Space (I tested AdobeRGB, sRGB and ProphotoRGB), and re-import those JPEG/PSD's to LR, they look absolutely identical to the RAW I started with. Also, at first glance, they look similar when opened in CS2, but only because I tested with color images. I can indeed see small differences when testing with B/W, as you described in your "Color management bug" thread.
2) When I change the color space of an PSD or JPEG inside CS2 (I used the default setting 'relative colorimetric') and save it to JPEG and then import this JPEG to LR, colors are far off. The strength of this mostly reddish color cast depends on the color space of the imported JPEG, strongest for Prophoto, less strong for Adobe and sRGB. Interestingly, when I convert the color space inside CS2 and save the result to PSD, it will display correctly when imported in LR. Another interesting side effect: the thumbnails of LR-exported JPEG's in the "Open" dialogs of CS2 and LR (I guess those are not color-managed) show the typical color-flatness for the Adobe and even more the ProPhoto version. For the CS2-converted JPEG's, all thumbnails look just a colorful as the thumbnail of the sRGB version.
3) Such an image which doesn't display correctly in LR will keep its color cast when exported again to a JPEG (not sure about PSD). So something goes wrong with the color conversion during the import of such CS2-converted images.
My explanation so far is that CS2 uses a slightly different way of coding the colorspace information in the metadata of JPEG's which somehow prevents LR to recognise the color space correctly.
Can you confirm this behaviour?
Steffen

Photoshop 7.0 - Problem Retaining Original Color Space After Export

I just registered for this forum & would appreciate your input.
I convert Canon RAW files to jpgs & always embed the sRGB color profile & color space in the converted files.. Once I open & edit one of these files in Photoshop 7.0 & save it, the color space is changed to Abobe RGB. I have tried many changes via Edit > Color Settings, but still the same results. I thought that the settings preset "Web Graphics sRGB Color Space" would do the trick - but it doesn't.
If I go to Image > Mode > Convert to Profile & select sRGB for both source space and destination space for an opened jpg file, the sRGB color space is embedded in the saved file - even after reopening in PS, editing, and re-saving. Must I do this for each jpg I edit?
Please educate me how to set PS so all exported files either retain the sRGB color space or have PS embed the sRGB color space upon export.
Thank you.

This is of course, an issue of permissions so there may be no solution.
Absolutely not. Don't jump to false premature conclusions. As Noel said, it solely depends on detecting a previous install/ verifying the install media. Since the latter is out of the question, the first would be way to go, the point being that it merely looks for the respective registry keys in HKEY_Local_Machine\Software\Adobe. Lucky for you, back then nobody cared to encrypt such stuff so it could be hacked in manually. Off hand I'm just not aware of the specific structure for the keys, though, but a little digging might turn up that info. In fact it would be almost identical to the ones for PS 7, which might already linger there just lacking the proper vlaues...
Mylenium

Asking the Bridge Team: Bridge "working color space" setting when one does not have the Suite?

Common sense tells me there is really no such thing as a
"working color space" in Bridge, because
Bridge is not an image editor, just a browser
Therefore, this may turn out to be a purely academic question; but that doesn't keep my curiosity from forcing me to ask it anyway. ;)
Is there a way to set the Bridge
"color settings" when one does not have the suite?
The only Adobe program I keep up to date is Photoshop, so I've never had the suite. My version of Photoshop is 11 (CS4) and I run updated
(not upgraded) versions of Adobe Acrobat 7.x, Illustrator 10.x and InDesign 2.x. Consequently, the Synchronize color settings command is not available to me.
It seems to me that Bridge is behaving like a proper color-managed browser (e.g. Firefox with color management enabled), in that it displays tagged image files correctly and assumes sRGB for untagged image files. This normally works fine.
But what if I wanted Bridge to assume my
Photoshop color working space for untagged images
so that it behaves the same as Photoshop? I'm just curious, as I deal with a minuscule, practically negligible amount of untagged files.
My reason for bringing it up now is that I don't recall this being explicitly mentioned in forum replies when users inquire about color settings in Bridge. A recent post regarding Version Cue in the Photoshop Macintosh forum got me thinking about this. Just wanting to make sure that I'm right in my assumption that
there is really no such thing as a
"working color space" in Bridge, because Bridge is not an image editor, just a browser.
Thanks in advance.

Hi Ramón,
Thanks for sharing the outcome of your tests. However, I may have found a bug/exception to Bridge's colour management policy!
It appears that CMYK EPS photoshop files are not colour managed in Adobe Bridge, even if they contain an embedded ICC profile.
I've tried every combination in the EPS 'Save As' dialogue box, so it doesn't seem to be an issue with file encoding. Also, Bridge doesn't rely on the low-res preview that is held within the EPS itself.
My guess is that Bridge is previewing the CMYK EPS with a Bridge-generated RGB image, but it's being displayed as monitor RGB (assigned) rather than colour managed (converted to monitor RGB). For most users the difference will be barely perceptible, but the problem became very noticeable when using Bridge to preview Newsprint CMYK images on a wide-gamut monitor (images that should have appeared muted really leapt off the screen!).
How do I report this to the Colour Police at Adobe?!?

Color space problems

Similar Messages

Maybe you are looking for