Skip to main content
Inspiring
September 17, 2017
Answered

Camera Raw colours different to Photoshop

  • September 17, 2017
  • 3 replies
  • 5526 views

Hi there, hope someone has an answer as this is driving me crazy.

When images are opened via Filter > Camera Raw Filter, images look over saturated and have a magenta colour shift.

Same happens when Raw (.CR2) files are opened via Adobe Bridge.

Using ACR 9.12.1 and Photoshop CC 2017.

Colour preferences are synced.

Using latest Graphics Driver.

Switching off Graphics Processor makes no difference.

Downgrading to ACR 9.1.1 solves the issue but that's not an option as that version can't read my raw files.

Adobe support has admitted there's a known issue with image saturation within Camera Raw 9.12.1 and apart from downgrading to 9.1.1 they haven't been able to provide a solution.

HELP!!!

This topic has been closed for replies.
Correct answer D Fosse

The monitor in question comes factory calibrated with AdobeRGB and sRGB profiles, which are user selectable. After initially running a calibration the difference between 'calibrated' result and factory calibrated profile was minimal, hence why I stuck with the factory one. I never had any issues till now. It doesn't matter whether the monitor is calibrated or not if ACR can't read the custom created calibrated profile.


I still don't buy this "known issue with saturation". These support people usually just read from scripts, but mainly I don't buy it because it doesn't make any sense.

This is apparently a wide gamut monitor. You need to get a calibrator. This is essential with wide gamut monitors, and they simply shouldn't be sold without one. Wide gamut changes the rules completely.

There is no such thing as a "factory calibrated" monitor. This is just marketing nonsense along with all the rest. The profile is generic, but more importantly - the instant you change any settings in the monitor, the profile is invalidated and you need to make a new one. The profile needs to describe the unit's actual, current response, not some "ideal" response. This is important!

Whenever you change profile to one that describes a different monitor response - those two go hand in hand - you also need to relaunch ACR/Photoshop/Lightroom. They load the profile at startup and continue to use that profile until relaunch.

In addition, manufacturer profiles are very often not correctly written to icc spec - in other words they are defective. So the description is incorrect, and the apps display incorrectly. This happens so often one wonders why they even bother. A defective profile frequently affects applications in different ways. Dell is notorious for this, but BenQ, Samsung, LG, Acer and Asus aren't far behind.

In short - when you buy a wide gamut monitor, a calibrator is part of the package. Without one, you'll keep getting into trouble.

3 replies

Inspiring
September 18, 2017

It seems that monitor profile was the culprit after all. I performed a hardware calibration today and saved it at the system level and it all works fine now. Thank you all for your help

D Fosse
Community Expert
Community Expert
September 17, 2017

Post a side-by-side screenshot.

There's no "known issue" with saturation as far as I know - but there is an intermittent and unpredictable bug that causes ACR to use the wrong display profile in a dual display setup. A workaround is to switch main/secondary display assignment in the OS.

Other than that, the prime suspect if you have a difference between ACR and Photoshop, is a defective or corrupt display profile. This will often affect applications differently. So making a new profile with your calibrator - if you have one - is always the first troubleshooting step.

If you don't have one, replace the current profile with a known good one like sRGB IEC61966-2.1. Defective manufacturer profiles are distributed through Windows Update all the time. It's a common problem.

Inspiring
September 17, 2017

I have the chat transcript with Adobe Support stating that there is a "known issue with saturation in ACR 9.12.1" which is why they got me to revert to 9.1.1 in the first place

Here are side by side images: Photoshop left, ACR on the right

Main/secondary assignment of monitors changed nothing.

There seems to be an issue with ACR reading AdobeRGB monitor profile.

1. Using a generic sRGB profile for the monitor -> Colours are same

2. Using a generic AdobeRGB profile -> Colours are different

The problem is when I use the sRGB profile, images saved for web look nothing like the images on the monitor, even with colour profile embedded and image converted to sRGB.

Note: monitor profile has never been updated/changed, this is definitely something to do with ACR having issues reading the profile correctly. I have the chat transcript with Adobe Support stating that there is a "known issue with saturation in ACR 9.12.1" which is why they got me to revert to 9.1.1 in the first place.

davescm
Community Expert
Community Expert
September 17, 2017

Eddie

Neither Adobe RGB or sRGB are monitor profiles. Whilst you can substitute sRGB (or ARGB for a wide gamut monitor) for a broken monitor profile as a troubleshooting step, the real answer is to use a good monitor profile matched to your monitor.

Dave

angie_taylor
Legend
September 17, 2017

I would think that if Adobe can't offer another solution its unlikely that anyone here could do any better, however I may be wrong. As a workaround could you use Lightroom? Do you have access to Lightroom?

Also, I know it's not exactly a Solution but could you take a screenshot of the image in Photoshop as a reference image. Have the reference image in the background, visible, when you open your image in CR. Then, in Camera Raw, adjust the saturation settings to visually adjust the image till it matches?

Inspiring
September 17, 2017

Thanks for your reply. Unfortunately, Lightroom isn't an option as need my custom ACR Presets