Color Shift with ProPhot RGB in CS4

When I had CS3 I would be able to open a RAW image in Photoshop with the ProPhoto RGB color space. I would then change the color space as needed.
In CS4, I am using the 64-bit version, and there is a color shift when I open a RAW image in Photoshop with ProPhoto color space. The color is desaturated.
There is no color sift when I open the same image using Adobe RGB.
Why is this happening?
Lynnea

There is a color shift when the Photoshop color space is set as ProPhoto (Edit>Color Settings) and the RAW color space to open in Photoshop is set as ProPhoto.
There is no color shift if RAW color space is Adobe RGB and the Photoshop is set with ProPhoto (Edit>Color Settings).
But, when I save the image, the color space in file information as seen in Bridge is Adobe RGB.
Could this be connected to GPU and "Move Color Matching to the GPU?"
I have seen comments concerning GPU and color sifts, but I don't really understand them.
It is frustrating since I do calibrate my monitor and have seen some of the images in both CS3 and now CS4 and thus can see the difference.
LYnnea

Similar Messages

IBooks author color shift with "Save for web devices..."

Hi! I'm a web developer and I'm learning to use iBooks. It's a really easy tool, but there is a problem with color management wich is driving me crazy. This happen when I export images from "Save for web devices..." from Photoshop, then drag it to iBooks author.
As I do for web development, I do this:
1) Configure photoshop Color Settings to work with "Color Monitor"
2) Remove any color management from my document
3) Proof Setup > Monitor RGB
4) Disable Proof Colors
5) Use "Save for web devices..." with ICC profile and sRGB unchecked
The exported JPG looks fine everywhere... Photoshop, Preview, Safari, Chrome, FF... but looks washed out when I drag it to iBooks Author. Why?
I solved this issue converting to sRGBIEC61966-2.1 profile and checking ICC profile when "Save for web devices...", but I'm not confortable with this workaround because I'm not sure about what I'm doing exactly, and I am not sure if this images are gonna look good on any device (I only own an iPad 3).
Somebody know a best method to deal with this?
Thanks!

Hi KT. Thanks for your response. I'm already using this formats. Anyway, the problem occurs within iBooks Author interface. I mean: I can see the color shift (or washed out...) at iBooks Author at my computer screen. Of course, when I test it on iPad it also looks bad.
It's incredibly strange because the JPGs I'm using looks fine everywhere else except iBooks Author.

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.

Color shifting with intensity

We have written a CVI routine which converts the bayer color pattern encoded image from a camera to color. It works fairly well; after we do a white balance the RED, BLUE and GREEN LEDs on our instrument cluster we are testing look fine and consistant.
However, there are some LEDs which are yellow-orange. On the screen they look more greenish-yellow. This would not be so much of a problem, however the color seems to shift with intensity and/or time. As we monitor the LEDs for a while they start to shift from greenish-yellow to yellow. As a result, the matching of color test does not work very well as the values change with time. I'm assuming that the LED light output shifts as it heats up.
We also noticed that the brightest spots on
the green leds look yellow. My guess is that the algorithum does not handle intensity differences well and shifts the color.
Any ideas? Anyone else have this problem?

Hello Cabbage,
I'm not 100% certain what's happening here, but I'll make a few guesses for what it's worth. The color shifting over time is probably real. LEDs will change color if the temperature changes. Diode lasers will sometimes have a spec on the datasheet that gives this shift in nm/degC or %/degC. I'm not sure if this is true for LEDs too.
The problem with yellow-orange LEDs looking greenish may be due to the color gains being off. Your Red, Green, and Blue LEDs and the phosphors on monitor are basically monochromatic. The color filter components on the CCD are to a lesser degree. It seems that there might be little coupling beteen the colors when looking at R, G, B LEDs. Even if the color gains are off, red will still look red, green look green,
and blue look blue, however LEDs with a component in multiple bands might not look right.
Most color CCD cameras will provide spectral respose curves in the manual for each color filter and LEDs datasheets should give similar info on their output. It may be helpful to compare the spectra of the LEDs you're measuring with the response of your CCD to see where they fall.
Regards,
Brent R.
Applications Engineer
National Instruments

Save to Web Color Shift with sRGB Working Space

I'm having a problem a lot of other people have, which is the color shift when saving to web or viewing my work in a web browser.
The solutions I've found in the past have been to simply make sure my working color space in Photoshop is sRGB and that my files are being built with that profile as well. I'm under the impression that sRGB is essentially the same color space as is used in a web browser, and therefore my work should look identical in both Photoshop and a web browser.
So why am I still getting a color shift? Everything in a browser appears darker and with more contrast, as though the colors have been pumped up a bit.
My monitor color has been calibrated with a Spyder 3 Pro and I'm using the profile it created for me as my OS X color profile. Thinking the shift may be related to my monitor profile, I tried switching to other profiles, but I still get a color shift in every single one.
Any ideas? Thanks!

sRGB based on capabilities and trends of development (circa late 1990s) for commodities CRT computers displays. sRGB per se has nothing to do with web browsers. The reason it has become associated with the web is the assumption that most web users are looking at content using a commodities CRT monitor using Microsoft Windows.
It should be obvious that the use of a standard of some kind for display is better than none if there is to be any trend towards predictability of image display. Today, in commodities computing, that standard is sRGB: neutral color where R=B=G, and a gray ramp and primaries typical of the electron gun and phosphors used in CRT displays perfected for use in color television. It just so happens that this coding is rather will suited to get good value out of a minimum numbers of bits for color representation (e.g, 8 bits per channel 24 bit color)
Web browsers in and of themselves don't have a color space. A few, such as Mac Safari, use the ICC color management capabilities of the system, and these display compensated color just like Photoshop does: if the image is tagged with an ICC profile, compensation will be applied in the browser window. But for the vast majority of computers and users, browser color is monitor color, and it's easier and most reliable for designers to just assume sRGB because it's the space that's the best approximation of the internet at large.
You work usually will not look identical in Photoshop and a web browser (assuming that the browser does not or cannot do color management) because Photoshop is always soft proofing the working space onto the display. It is this quality that leads you to see parity between photoshop and the web browser when you choose you monitor profile as the working space: the soft proof produces no compensation.
But while this fixes up your local experience it is -not- the solution because this projects your monitor characteristics into the image when you share it. For example, if your monitor has a lumpy non-linear tonal response and you correct image shadows or saturation for a certain look the image data will code your monitor response as well as your intentions for the image appearance. Others will see the combination of your correction for your monitor response mapped over their monitor response, in fact they will see an inversion of your monitor's response coded in the image, and to whatever extent your monitor deviates from the norm is the extent which at the very least others displays of the images you correct will deviate from your intentioned look.
The answer to your problem--and this may surprise you--is to tolerate and appreciate the difference in display between photoshop's rendition of color and your browsers. Photoshop is showing your image more truly--within certain significant local limits--in terms of your working space than your web browser. By choosing an appropriate working space, and for the web it should be sRGB, and by profiling your monitor as you have, you are ensuring your images are normalized to current standards for web presentation. Others may still see crap, but it's most likely their problem and if they don't want to do anything about it that's their problem, not yours.
There are a wide variety of reasons why a properly calibrated monitor will not match a working space which the soft proof cannot overcome. A monitor gamut larger than sRGB is not one of them. Photoshop will properly display sRGB data if the display profile properly characterizes the larger gamut display. This leads to questions about the effects of monitor quality on workflow. Maybe the most important of these is "How do I know my Spyder has properly calibrated my display!!!" But this is a topic for a whole 'nother thread.
Where I run into trouble is when trying to make visual color comparisons during web design between my photoshop website mockup and a published site. I get confused and try to make color picker style matches by eye rather than by the numbers because I forget my web browser is not color managed. Sometimes I forget how all the parts play together and get confused and disoriented, then I make compounding mistakes. Then I start blaming my tools. Pity me.

MacBook Pro, dual Monitor color shift with Photoshop CS4, OS 10.5.5

I'm observing a strange behavior: With PS CS3 i could just drag an image from
the laptop monitor to the external Eizo and the color would adjust instantly, with
consistent color (All monitors calibrated, no settings have changed). The same applies to Lightroom
2.0 too. Now when i do the same move with the same image opened in PS CS4 the color does not
adjust to match but stays the same and the result is a oversaturated image on the external monitor.
Any thoughts? Thanks, Mark

It should adjust to the display the same as CS3.
Have you tried turning off OpenGL image display?
(it could be a bug, or a driver issue)

Gamma shift with LStar-RGB profile

Hi everybody
I have a problem with gamma shift when I import a picture which has the LStar-RGB profile embedded. Anybody else with this problem? Any solutions?
If I open the same image in Preview or Safari everything is fine.
Thank you
Marc

Hi Marc,
I have had a similar problem using the eciRGBv2 profile which I believe is the same as LStar-RGB. In my case when I exported images to an external editor they would open up dark in the editor. After work on the images they would return to Aperture and open up too light. I have also noticed that existing images that use this profile display too light in Aperture; the preview is fine but when the image finishes loading it is light. I thought this was some exposure issue as there seemed no effect on colour (although all of my images are black and white conversions) but gamma shift would sound right.
I noticed this problem after simultaneously upgrading to Mac OS 10.6.7 and Aperture 3.1.2 so I am not sure which is the source of the problem. Apple engineers are currently working on the matter but I wonder myself whether this is an ICC version 4 profile problem. All the images I have had problems with use the version 4 profile. I have tried using the ICC version 2 profile and this works okay. You will know (or can look up in ColorSync Utility) if LStar-RGB is a version 2 or version 4 profile, and depending on the answer to that you could try to use the eciRGBv2 profile in its ICC version 2 guise.
I hope you find an answer soon as I realise how frustrating this is.
Phil

Aperture Colour/ Color Shift with Lion

Hi I have just added Lion to my least important computer and in Aperture when I double click on a thumb and it goes into full photo mode it is fine for a millisecond and then you can see the Colours shift to a dull flat image as you can see from images. Not a massive shift but a shift nonetheless.
If you just view them with "Quick Preview" On they are fine but when the image is rendered the colours shift.
Anyone else got this or is it just me again and if so any solution?

Well,
same old story...with every OS upgrade a new or revised RawCameraBundle file is provided and this, at least in my system, is causing the colour shift.
I had this problem since the very first serious Aperture 3 ugrades, my Canon 30D images were horribly magenta-shifted, no way to change them back properly...well, maybe with an insane amount of extra work.
So I keep the "good" RawCameraBundle file in a folder (it's version 3.0.1) and at every OS upgrade I delete the new RawCameraBundle file, put back the new one, restart and everything's fine again.
The last upgrade for me was OS 10.6.8, it installed the RawCameraBundle 3.7.1 (RawCameraBundle file is located in Library/CoreServices folder)...I decided anyway to open Aperture...I displayed an image from Canon 30D....for a while it was good then suddenly (when reprocess starts with the new engine) skin tones were shifted to magenta...ok then, deleted RawCameraBundle, put back the old one, restart, launch Aperture 3, the image was good.
Honestly I don't know how far I can go with this, I mean I don't know if Lion will allow that or if the RawCameraBundle file has been changed again.
Maybe you could check the Lion version of the RawCameraBundle file, I bet that is not 3.7.1 anymore.
Maybe is this causing your colour shift problem within Aperture 3, maybe not...You can try...if you have the old RawCameraBundle file; I think you may retrieve it easily from a Time Machine backup.
Bye!
Alberto

Color shift with second monitor using develop module

LR 4.1 RC2, OSX 10.6.8 - when I'm trying to use the develop module with my second monitor, the image initially looks accurate. After a second or two and before any edits have been applied, the images desaturate and look very flat. Images viewed with the second monitor in Library module look great. I can't figure out what is happening and am wondering if any others are experiencing this. Thanks.

Will be fixed in 4.1 final.
Sent from phone.

Third party profiles results in color shifts

Using LR on a calibrated iMac and printing to an Epson Pro 3800, I'm now getting easily noticeable color ***** in the printed output, when using 3rd party paper profiles (e.g. Hahnemuhle Fine Art Pearl or Pixel Genius Epson Exhibition Fiber profile), but if I specify an Epson profile, the output is a perfect screen match!? I specified the Epson Glossy Photo profile in LR and printed on their new Exhibition Fiber paper, and the print was perfect. Of interest here, is that print Preview showed the color shift with the other profiles and printed the same, which suggests Print Preview is an accurate rendition of the final output to paper (and yes ... no color control was specified in the driver).
This was not the case prior to the last LR update, as the 3rd party profiles the job accurately!?

"Also, I've emailed the correct people at Epson regarding the issue with the info sheet inside the paper. From what I know and the discussions I've had with the product manager for the 3800 and the EFP, the info sheet is WRONG. But, due to the holidays, I don't expect a response till mid-week next week. "
I'd be curious to hear back what the response is. I hate ambiguities. There is one other thing that is bothering me about your theory, and that is I just came back from mounting an exhibit of my photos, printed using LR specifying the HFA3800FineArePearlPK.icc profile printing to their Fine Art Pearl paper. The results on paper matches the current LR screen images. This I did I think prior to applying 1.3.1 (a few weeks past). Those images in LR look the same to me, yet the profiles are now visibly altering the tonality. I will re-calibrate, but my confidence level is in the sewer.
btw I'd love to see what PS does with the profile, but I can't install CS3 trial. It says CS3 is already installed, but it isn't.
"System check: Adobe Photoshop CS3 cannot be installed because it conflicts with:
Adobe Photoshop CS3"
I had installed it a while back, but it got uninstalled along the way. Any tips around this. My gut feeling is CS3 won't have any problems with the profiles.

Color shift from Photoshop to InDesign?

I'm using Adobe's Creative Cloud family of apps, which have been color synchronized with Adobe Bridge using the North American General Purpose 2 color setting. All of the files I'm working with are set to CMYK. My Photoshop files are set to 8 bits/channel.
I just placed several .psd files in an InDesign document and there is a rather large color shift, with the placed image in InDesign being much darker than the Photoshop image. In addition, and even with InDesign's Display Performance set to "High Quality Display", the placed image is not as crisp as the Photoshop image.
So, my questions are:
Why is there a large color shift between both apps?
Why is the placed image not as clean as the Photoshop image?
What can I do to fix both issues?
Thanks in advance for your help.

First and foremost, do you have a high-quality monitor, and is it properly calibrated and profiled (using an instrument)? Without that, judging color on-screen is like picking the best picture at the TV dealer.
When you place an image in ID you are looking at a screen preview, not the pixels you see in Photoshop. View > Display Quality > High Quality Display will get you the best quality preview, but it's still just a preview. Turning on Overprint Preview will give you the most accurate color rendition for CMYK.

Consistent RGB Color Values with Photoshop CS4: An Impossibility??

What I want is very simple: I want the Photoshop files I am working on and the rendered PNGs in my browser to have the same color values. I don't care if my web images look the same color on other screens or anything like that. All I want is for the screenshots of PNGs my web browser to match the color values I have used in Photoshop. I've had it up to here with color shiftsthis did not used to be an issue in CS3.
Moreover, if I save a file on my Mac, and a color value is, say, #cf4640, I want someone who opens the file on a Windows box to get the same color value for that pixel. Ditto for the images I have saved for the webI want the RGB values to be consistent. This does not seem like too much to ask, does it?
Right now, I have turned all color management policies set to Off, working spaces are all set to Generics, and documents are set to "Don't Color Manage"my Windows colleagues also have these same settings. This used to work as expected in CS3we all got the same color values on the same files, and colors didn't shift when viewed in a browser.
Once again, I don't care if the colors *look* the same from platform to platform or screen to screen. I just want consistent RGB values.
Color management has never caused me anything but headachesleave my colors alone, Photoshop! I really really wish there was a "Work Like Photoshop 4" setting for color management.
Does anyone have any ideas how I might solve my problems?
Thanks very much.
Oh, and, incidentally, I was originally thinking of calling Adobe about this; how foolish of me. I looked into it, and can I just say how fantastic it is that you have to pay extra money for actual first-party tech support on a $700 piece of software?

The sounds/language analogy isn't really relevant to this problem, because it suggests transforming between two entirely different media. One medium: the medium of sound information, to another entirely different medium: the medium of thoughts and meanings. That's something that simply can't be done without an intermediate translation. That's not the case with color transforms in the RGB space, where it's just a matter of taking RGB values and pushing them through a matrix to produce other RGB values. That's the process that messes everyone up and creates all the confusing color output, and frankly it's an unnecessary process. Your assertion that the values in a source image have no meaning without an associated profile isn't entirely true. What if those source values were simply pushed directly though to the display? After all, a display simply renders 8 bits of R, 8 bits of G, and 8 bits of B for each pixel.
I think the original poster has some very valid concerns. Sometimes we just want to set some color values, and know that everybody's display, on every platform, will render those color values the same way. As he said, they may not look identical to the eye, but the values going through that DVI cable will be setting that pixel to the same 24-bit value no matter what. That's how things would be if there were no such thing as color management. That's how things used to be long ago, and in many ways the world of color was far more predictable and less confusing back then.
Here's my vision for a perfect world: color management doesn't exist in the RGB space. None. No such thing. Source RGB values in images get pushed right through to the display. The onus is on the display manufacturers to produce hardware that renders those values as consistently as possible. In the world of print, sure- color management is incredibly useful. But if only we could go back in time and keep color profiles out of our RGB, I believe we'd be much better off today.

Illustrator CS4 hex color shifts again

In cs4 Illustrator on mac
Color settings:North Amer/Internet
Document Color Mode: RGB
Proof Setup: Monitor RGB
Proof Colors: Checked
When I make a web safe colour in my color picker (example #0088CE) the number is fine when measured with the Digital Color meter. But once it is placed in the swatches pallette or on an object on the desktop the color shifts and consequently passed onto "save to web". Photoshop CS4 seems to be fine still though... What's up???

Our small group just figured this out. Maybe because of the upgrade things get reset, I don't know for sure... but under EDIT>Assign Profile... my setting was for "Don't color manage tihs doc...". I didn't know this was here before and I dont understand why it wouldn't automatically change when choosing my "Color Settings" to 2.1 (or Internet/Web N. Amer). Soooooo, when you change it to 2.1 HERE TOO the proof colors check/uncheck works resulting the hex on screen to match the save for web output. Anyone in Adobe have a suggestion or instruction where this can all be changed in one place so it stays this way for us web peeps on all our documents? Sick of checking these settings yo.

Converting RGB to CMYK - Huge color shift. Any tips on getting some decent color back?

I just downloaded a St. Patricks day background from iStockPhoto. Nice vibrant green. We all know when converting to CMYK from RGB, there is a color shift but this is pretty dang dramatic. Any basic tips on getting some of that vibrant color back after converting?

You can boost greens by printing another pass of yellow with the same halftoning on top of your cyan areas. Black and yellow naturalyl also can give the appearance of certain dark green colors, but this may only work on vbery fine rasters. Printing an extra color is always an option, but also keep in mind that a lot depends on what paper is used and how it interacts with the inks. Also many magazines use gloss coating on their front page, which hugely influences perception of "depth" in the colors. And don't forget all the perceptional tricks - such mags often use colored pages because the green looks more saturated when surrounded by a dark red, brown or ocre...
Mylenium

Color "shifted" in CS4 RAW files

Hello everyone.
Ill try to explain my problem. Until last year I used ACR (combined with Bridge CS3) to color manage my images. Then I would convert them to DNG using the Adobe DNG Converter, and bring them into iMatch (www.photools.com), which is the program I use to manage my image database. I would work with a calibrated monitor, and a sRGB color profile.
The DNG images would look the same in Bridge and iMatch, and if I extracted the JPG preview from any DNG image it would also look the same.
This year I bought a new laptop and a CS4 license (previously I was doing the CS3 work using a license from the place I work at). Ive calibrated my laptop screen with a Pantone Huey Pro screen calibrator.
When I open my images in CS4 the color in all of them looks "shifted", as if the white balance was off. They look consistently greenish and somewhat washed out. This happens in Bridge, ACR and Photoshop.
However, if I open any of the JPG images (the ones that I created extracting the preview from the DNG files) they look the way they should. So from this I can infer that it can't be a screen calibration problem (otherwise both the JPG and its DNG counterpart would look wrong, instead of just the DNG).
So it seems like CS4 is rendering the DNG images differently than it should. But I havent been able to find out how to correct the problem.
Some other info: In the ACR flyout menu I have Image Settings selected, and under the Camera Calibration I have Embedded selected. Ive already tried (at the suggestion of Adobe support) to reset the Bridge preferences by holding CTRL+Shift when Bridge loads, but this hasnt corrected the problem.
Also, here are my system specs,:
- Precision M6400: Intel Core 2 Duo P8600(2.4GHz,1066MHz,3MB)
- Display : 17in Widescreen WUXGA (1920X1200)
- Memory : 4096MB (2x2048) 1067MHz DDR3 Dual Channel
- Graphics card: 1GB NVIDIA Quadro FX3700M (with 1GB dedicated memory)
- Hard Drive : 200GB Serial ATA (7200RPM)
- Operating System : WXP Pro SP3
I have already contacted Adobe support about this a few days ago, but so far no luck. So I thought Id try the forums as well and see if anyone here has any theories as to what the problem could be. Im stuck until Im able to solve this, so any help would be appreciated.
Thanks.

Hello,
I'm still having trouble with this same issue, wondering if anyone has further thoughts.
I've read some of the similar threads, like: http://forums.adobe.com/message/1203718 and http://forums.adobe.com/message/1203965
But I'm still confused.
I hadn't noticed the color shifts in Bridge being so pronounced until recently. So maybe something got inadvertently reset?
It would be a bad idea to change my computer's color profile to generic sRGB (as someone suggested), since I have a good calibrated color profile via the Gretag MacBeth (yeah, it's older) EyeOne Display. I've used that calibration device for years, updating every 6-12 months. Never been a problem.
It doesn't make any sense to me that Bridge should alter the colors of thumbnails/previews for RAW images (from the very good looking camera setting) before I even open Camera Raw to work on the RAW images. I don't work on every single RAW image, and doubt anyone does. But if I have 50 landscape shots, and the mere act of looking at their previews in Bridge turns all their skies unnaturally purple (which is currently happening), I lose any visual record of what the skies really looked like -- or at least a much closer approximation.
My Canon 40D's jpg previews for RAW images are quite good when they initially show up in Bridge. I'd really like to keep them until I work in Camera Raw, to give me a good visual memory starting point until I can get to work in ACR. Sometimes I don't start serious work on an image for many months after shooting.
Someone please correct me if I'm wrong, but it also doesn't make sense to me that a solution is to make a new Camera Raw default based on a photo I've worked on in ACR, because the color settings always depend on the lighting situation a photo was taken in, don't they? How could a daylight photo's settings be right for an indoor or sunset shot with totally different lighting and color temps?
Bottom line question: Is there any way to prevent Bridge from altering the color in thumbnails/previews of RAW images before you've worked on the images in Camera Raw? (Even if you click on a thumbnail to see the preview in Bridge, I mean.)
Thank you very much!!!
~Glenn
Message was edited by: glennooo - for clarity and to fix a link

Color Shift with ProPhot RGB in CS4

Similar Messages

Maybe you are looking for