Image not displaying properly in CS5

<p>I have a folder of raw files that I edited in CS5 and saved as jpg's. That went well. I imported them into LR3 and made a collection. That went well. I deleted the collection in LR3. This is when I noticed a problem. After deleting the collection, I opened one of the jpg's in CS5 (LR3 deletes the collection but leaves the jpg's on the hard drive). It was a mess. I opened the same file in Windows Image Viewer and it was fine. I uploaded the image to my web site and opened it using Safari. It was fine. But it continues to look bad in LR3, CS5 and Abobe Raw. <br>

This is the actual .jpg. It is LARGE ~5 MB.<br>

<a href="http://www.patrickdillonphotography.com/gallery/1517.jpg">http://www.patrickdillonphotography.com/gallery/1517.jpg</a></p>

<p>The screen capture of the same file in CS5 is 245 KB.<br>

<a href="http://www.patrickdillonphotography.com/gallery/screencapture1517.jpg">http://www.patrickdillonphotography.com/gallery/screencapture1517.jpg</a><br>

The blacks are blocked. The contrast is screwy. The exposure is wrong. etc., etc.<br>

What is going on here? <br>

I would like this image and all the others to revert to their original state that I see when I display the image in any program but the Adobe programs. Is this a thumbnail vs actual image issue? <br>

The underlying question "What did I do in LR3 that caused this" will probably never be answered.<br>

Any help would be appreciated.<br>

thanks,<br>

pat</p>

<p> </p>

<p>Windows Image Viewer isn’t color managed, LR and Photoshop are, so if LR and Photoshop match, that’s the correct rendering of these images. Check that the JPEGs have an embedded profile in Photoshop (Assign Profile, sRGB). Look different? </p>

One thing about LR3, PS CS5, and Camera Raw is that they use color management when displaying photos. Whether Safari does is unknown, and it probably can't even do it theoretically unless (1) the JPEG had an embedded profile, or (2) it's sRGB so Safari's guess will be correct.

 

If my hypothesis is right, what you are seeing in LR3, etc., is correct, and what Safari is showing is wrong.

 

To test the hypothesis, export from LR3 and make sure sRGB is set for the exported color space. Then view in Safari again. You should see the so-called "bad" JPEG that you see in LR3.

 

Then, fix the image in LR3, export it with an sRGB color space, and you should be OK.

<p>Andrew. Yes. Image viewer, IE, etc are not managed and the three Abode products are. My understanding is that Photo Mechanic, like Adobe, is also color managed. And when viewed in Photo Mechanic the images look normal. If that is correct, I have two color managed programs on the same computer giving very different results.<br>

I posted the whole jpg so others could look at the image in their copies of CS5 or LR3. Or they might look at info inside the jpg. I thought it was going to be a "side car" file issue. But jpg's don't have any associated files (my raw files can have a xmp file associated with them).<br>

Marc. When I get back I will try your suggestion. But it implies that I made corrections in LR3 and as far as I know I did not. The only thing I did was delete the collection. If I did make changes in LR3, I have no idea how to undo the effects in LR3. It took me almost 8 hours in CS5 to edit the raw files. I only imported them in to LR3 so that I could make a gallery for my web site. Which I did and the gallery looks fine. If I cannot find out what is going on, I will have no choice but to delete the jpgs and start over again.</p>

 

<p>Check that there are embedded profiles in the questionable images. Then check your Photoshop color settings. Untagged documents are assumed to be in the color space you select for your RGB working space. <br>

LR assumes untagged documents are in sRGB. <br>

Safari is color managed but when viewing untagged documents, assumes the display profile. </p>

<p>image look good in Lr3 and CS5.. something wrong in your color preference or something... image i download was in adobe rgb.</p>

<p>dont redo everything, it look good here.. make some test print to comfirm.. im sure it is just a monitor problem somewhere.. all should be fine when print by you / your client</p>

<p>It is not color profile problem.<br>

When I open your jpeg-file in CS3, it opens it straight at the Camera Raw. Seems that your JPEG-file has embedded XMP-information at the EXIF-fields, including all color and brightness corrections. Photoshop is using these values for some reason also for the JPEG. Seems that "Blacks" has value +18, and it blocks all the dark areas. If you check JPEG-file for example with exiftool, it shows all this data.<br>

Had to admit, I have no idea, how to reverse this. When I zeroed all the corrections in Camera Raw, it looked quite same as when showed in ordinary image viewer.</p>

 

<p>I'm with Olli. Those two images are so far off it couldn't possible be a simple color management problem. It looks like the contrast and blacks have been cranked and then run through a poor noise removal filter.</p>

<p>Patrick, Thank you for looking. I want to send these jpgs to Millerslab for printing. I need to know if they will print correctly. I will call them and ask them to advise. Your thoughts?</p>

<p>Olli, Garrison. Thank you for confiming what I thought might be the problem. I didn't know what the EXIF info is or how it was stored. But you confirmed I was on the right track. Here is the oddest thing. I didn't make any changes in LR, EVER other that the BW conversion en masse. All of my editing was done is CS5 (I don't know how to use LR for those edits such as Liquify). The CS5 were saved as jpgs, Imported into LR and everything was fine. My web gallery was produced without any problem.</p>

<p>This is the sequence of events. The LR image on the screen looked fine. I deleted the BW conversion collection and the next image I browsed to after the delete had this problem. All the images had this problem. It makes me nervous that I do not understand the cause.</p>

<p>If I find a way to undo the EXIF I will post it back here.</p>

<p>thanks everyone.</p>

<p>The image has been edited in ACR or LR, it has a black, Exposure, Vibrance and Saturation adjustment described in the metadata as Olli points out and sees in ACR. If you do an <em>Open</em>, select <em>Camera Raw</em> for the type, you can force the image to open in ACR instead of Photoshop proper and see the differences here. Just use the menu option in ACR to “<em>Use Camera Raw Defaults</em>” everything zero’s out and it matches the JPEG when opened in Photoshop. <br>

This is one of the problems using metadata edits in ACR or LR on rendered images like this JPEG. You have defined an edit, but you didn’t click “Open” which would have applied that edit and rendered a new document (A JPEG if you save it as such). Or in LR, exported (or used “<em>Open in Photoshop</em>”) which would render the image <strong>with</strong> the metadata edits. When you open the original JPEG <strong>in</strong> ACR (or if you viewed it in LR), you would have seen this metadata edit. But when you simply open the file AS a JPEG in Photoshop, Photoshop doesn’t “see” the edits, it sees the original JPEG.</p>

 

<p>You can fix this by deleting the XMP-crs information from the image. This can be done with exiftool and the following command:<br>

exiftool -xmp-crs:all= 1517.jpg<br>

- Phil</p>