dan_siney

<p>Thanks again Tim.</p>

<p>The dialogue box is as you describe it should be when I opened a file in CS2. I do all my scans with no adjustment either during the scan or afterwards and I have never had a problem with color shifts when opening a new Nikon file into CS2. Also as I mentioned the difference between the Nikon space and ARGB 1998 is only a very slight shift in hue. </p>

<p>Since making the changes to color settings there is a new dialogue box concerning color profiles. The new one says "The document XXX does not have an embedded RGB profile" -- as opposed to the one I'm used to getting, which says, "The document has an embedded profile that doesn't match your RGB Working Space... Embedded: "Nikon Apple RGB...") I am getting one or the other depending on the file; but for what reason I don't understand. I have tried opening various files and it appears to be totally random as to whether it recognizes the Nikon color space.</p>

<p>I also tried opening a few versions of an image (saved as tiff's, jpg's, worked on and not) that have been acting erratic. I discovered that if I choose to "assign profile: Nikon RGB..." or "discard the embeded profile (don't color manage)" (depending on the dialogue box) they come out looking the way they should. This seems inconsistent also.</p>

<p>Thoughts?</p>

<p>Hi Tim, thanks very much for your response. I've never submitted to one of these things before and I'm sort of astounded somemone wrote back. Your advice seems to have done the trick for the most part - so I am much obliged -- but I don't quite understand how: </p>

<p>- I'm shooting 35mm negative film and scanning. The color profile the Nikon software applies is "Nikon Apple RGB 4.0.0.3000" If I convert or use the embedded profile the result is very similar.</p>

<p>- When I open one of my first SFW attempts now I'm prompted to color manage. "Leave as is" (this is the default option) and "Assign working RGB" both give me over-saturated images. If I choose "Assign profile" and select SRGB (since that's what I saved it in) it looks fine.<br>

>><strong>Why was I not being asked to color manage before, since the SFW file should be out of sync with the working space? And Why do I now have to assign the file a color profile if I converted and saved it as SRGB?</strong></p>

<p>- I made a new SFW file, ticking the ICC box (what is this?) and viewing in the optimized window. The image still looks desaturated in the window, but when reopened selecting "Use embedded..." looks fine. (Very slightly but perceptibly off; cooler and maybe more saturated. Color sampling confirms this.) I uploaded this image to the web and the web image is almost exactly the same again. Only very slightly different. So for the most part, problem solved!<br>

>><strong>Why, since my first SFW files and my new ones are ostensibly the same when opened in SRGB, do they look different from each other when uploaded to the web? And why when opened do they prompt two completely different color management windows if they're both SRGB? Is this the doing of the ICC box?</strong></p>

<p>I have been having similar troubles over the last year. I will reopen an old file I had spent a long time color correcting in the working space - and which I would have saved and reopened several times in the process - and suddenly it will be over saturated. Only choosing "Discard embedded..." changes that, but I can't be sure if what I'm looking at then is the same as how I originally saved it. How am I supposed to know what my images look like if they are constantly changing on me like this? I get paranoid that I'm loosing hours of work and that the files I send away to people/magazines are mutating into whatever they want.</p>

<p>I noticed in the color settings window there is an icon in the top left of a fractured color wheel/target and a warning that says "Unsynchronized. Your Creative Suite applications are not synchronized for consistent color." Could this be the culprit? I do bring images in from Bridge. Could there also be complications when using iPhoto? I use that application quite a bit for squencing and often drag a file into PS directly from there.</p>

<p>I realize this is a lot of information but I thought I'd throw it out there. I think this has solved my immediate problems, so thanks again for your help. If you do have any further wisdom to share it would be much appreciated.</p>

<p>Seeing as this post is half a decade old and I'm suddenly struck with the same dilemma I thought I'd sign up and see if anyone is still out there. I've picked through about half the posts and they've been educational, but I'm still stuck. My own situation is similar, except for a few bizarre complications. I'm hoping I'm just not savvy enough to be picking up on some simple problems concerning color spaces and management. Here's what I'm doing:<br>

- When my image is resized and sharpened I "convert to profile" from argb to srgb. The image looks good after the conversion.<br>

- I save for web.<br>

- I upload the image to my website and it looks desaturated.<br>

To further complicate things, when I reopen the SFW version of my image to PS it does not ask me how I want to color manage, and the image is suddenly OVER saturated. When I reopen the pre-SFW argb version it looks correct. I tried saving and reopening an srgb (not SFW) version. If I choose to "use the embeded profile" or "convert... to working space" they look the same, but if I "discard embeded/... don't color manage" it has the same kind of over saturation I'm getting when reopening my SFW versions. <br>

This is especially confusing because it means I don't know what my SFW versions even look like, since they close automatically when saved. Of note however, in the SFW window: 2up: both images look desaturated.<br>

I am using a mac and running CS2. If anyone has any updates or suggestions I would be very grateful, as I am utterly lost. Thank you, and thanks to all the previous contributors too...</p>