• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Camera Raw 8.7.1 color issues

Explorer ,
Dec 15, 2014 Dec 15, 2014

Copy link to clipboard

Copied

After the recent camera raw update to 8.7.1 I have noticed some pretty bad color shifts between camera raw and photoshop cs6. The colors in camera raw look very saturated and then when moving into photoshop the saturation shift is pretty dramatic. I never had these issues before the update. I have attached a screenshot illustrating the color issue. I am working on a very good monitor ( NEC PA 242W ) and it is color calibrated using NEC Spectraview calibration system. I have double checked my color setting in photoshop and camera raw to make sure I was viewing the same color space. I am just wondering if this is maybe a bug in the update and others are experiencing the same issues or if I am just missing something.

raw8.7update.JPG

I would also add that I am using the Creative Suite CS6 and not CC. If that makes a difference.

Views

18.4K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 17, 2015 Apr 17, 2015

Copy link to clipboard

Copied

Can't see anything obvious, updated drivers too

I don't think it is a change by Adobe that is planned, I think is an issue affecting a small amount of people.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 18, 2015 Apr 18, 2015

Copy link to clipboard

Copied

I am seeing the same thing.  Check out my post.

Re: Camera Raw Bug: Preview not the same after clicking OK

Will try to go back to 8.6 and see if it fixes my problem as well.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 21, 2015 Apr 21, 2015

Copy link to clipboard

Copied

The only other way is to Open as Object and tweak from there, not ideal but otherwise we could be using 8.6 while everyone is on version 20

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Sep 20, 2015 Sep 20, 2015

Copy link to clipboard

Copied

had the same problem. going back to the old ACR-Version solved it. thanks.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 29, 2016 Jan 29, 2016

Copy link to clipboard

Copied

!

Hi,

I have the same issue :

I shot with a camera set on adobe rgb 1998 ICC.

When I open my .cr2 in a soft like ACDSee, no problem, the ICC  adobe 1998 is well interprated and my display is OK.

But when I open it in camera RAW, after setting properly the camera profiles, my image is oversaturated. If I then open it in photoshop in sRGB profile, my work is dead, there is no way to convert back the colors.

The only way I found is to open your image in PS in adobe 1998 profile. Then when the conflict ICC profile popup appears, Delete the incorporate ICC profile bring me back the correct colors.

It is a pain because when I tweak my image in camera RAW, I don't see it with the good colors.

My opinion is that camera raw is not able to handle adobe RGB 1998 ICC profile. So... What the hell ?!

Does it ring a bell to somebody ? Another workaround or explanation may be ?

Cheers

Edit : I solve the problem : So I think I was right, Camera raw 7.0 did not manage Raw in adobe 1998. It is an instalation problem. I had camera raw  7.0 on my workstation, when I installed camera raw 9.3, the installation seemed to end correctly. But no, it was still camera raw 7.0 when I opened a raw in PS. So after a few research I found that I'd better install camera raw 9.1, what I did, and it worked, no more misunderstanding with my adobe 1998 ICC in Camera raw.

I hope it'll help.

Cheers

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 01, 2016 Feb 01, 2016

Copy link to clipboard

Copied

So after living with this problem for the past year I decided to upgrade to newest version of Photoshop CC and Lightroom hoping that the color problem would be fixed, and it was not. So I started digging into this again and I have found what I think the cause is. Per this other post on the forums Adobe Camera Raw uses profile of Windows "main" monitor only in dual monitor setup I also have pretty much the same duel monitor setup. After following the steps the OP outlines as a temporary fix the color shift is totally solved.

Is there a way to set Lightroom and Camera Raw to load and only use the secondary monitor ICC profile as the file it associates with the "Monitor Profile"?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 02, 2016 Feb 02, 2016

Copy link to clipboard

Copied

flyrs88 wrote:

Is there a way to set Lightroom and Camera Raw to load and only use the secondary monitor ICC profile as the file it associates with the "Monitor Profile"?

I'd look at the operating system first. Both Photoshop and ACR should use the profile assigned as default for that display, by the operating system. Main or secondary doesn't matter to PS/ACR, they should use whatever the OS tells them to, for that display.

So before assuming an ACR bug, make sure the OS is setting up the correct profile for each display. This is done through the normal OS dialogs.

kastor julien wrote:

So I think I was right, Camera raw 7.0 did not manage Raw in adobe 1998

Julien, this has nothing to do with Adobe RGB or not. This is about the monitor profile used, those are two entirely different things.

The workflow setting for Adobe RGB doesn't apply until the image is encoded into a color space and opened into Photoshop. Inside ACR, you see the image in ACR's internal working space, linear ProPhoto, which is converted into the monitor profile and sent to the display. If the monitor profile is wrong, it won't display correctly.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 02, 2016 Feb 02, 2016

Copy link to clipboard

Copied

Yeah windows is using the correct profile for each display it is just that when Photoshop is first opened it associates the "monitor profile" of whatever display is designated the "main display" in windows. And Camera Raw uses the Monitor RGB for its profile.  So since my main display is just a regular monitor that uses a generic srgb profile when I open camera raw over in my wide gamut monitor the srgb profile camera raw is using makes all the colors way over saturated.

The only way I have found to fix this is I have to go into "Display Settings" within windows or my nvidia control panel then click my wide gamut monitor and check "Make this my main display".

Then I have to open Photoshop so "Monitor RGB" reflects the ICC profile of that monitor.

Then go back into display settings and switch back the main display.

After that camera raw associates the correct profile until I close Photoshop then I have to repeat that process the next time I open Photoshop.

That's why I was just wondering if there was an easier way like to make Photoshop always use the same profile for its monitor rgb setting.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 03, 2016 Feb 03, 2016

Copy link to clipboard

Copied

Try to disable all GPU acceleration in both ACR and Photoshop, and check again.

Just to establish the basics here: Yes, Photoshop will put up the profile for the main display as "Monitor RGB" in color settings, because it has to pick one. But neither PS nor ACR are supposed to be bound by that when actually displaying a file. They should use the monitor profile for the display they happen to be on, whichever that is at any time. When you drag - image or app window - the profile should switch when you cross the mid-line and drop.

IOW - the Photoshop Monitor RGB listing isn't supposed to matter for actual display. If it does, that qualifies as a reportable bug.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 03, 2016 Feb 03, 2016

Copy link to clipboard

Copied

Ok, I disabled GPU acceleration for ACR and Photoshop but it made no difference.

Here are a couple screenshots of what I am seeing based on what monitor is set as "Main Display" in windows display settings.

And both of the screenshots I am viewing the image on my wide gamut monitor.

- Normal monitor using generic srgb profile set as main display.

1.jpg

- Wide gamut monitor using the profile generated from SpectraView software set as main display.

2.jpg

Dragging the ACR window over to the other monitor, letting go, then dragging back still showed the same thing.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 24, 2016 Jul 24, 2016

Copy link to clipboard

Copied

Hello.

I had the same problem. I'm working with two monitors, One is sRGB and the other one is wide gamut. In my old configuration, where the problem existed, I had the sRGB monitor as main, and worked with photoshop in the wide gamut monitor, appearing the same problem like you. Today, I have configurated wide gamut monitor as main, and I open Photoshop and ACR at this monitor. Just with this, the problem has been resolved.

I think that the problem is related to moving windows from one monitor to another.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Sep 29, 2016 Sep 29, 2016

Copy link to clipboard

Copied

If you're on Windows - I'm on 10 Pro - go to control panel, color management, and then click on the advanced tab. Set your "Device Profile" to the monitor you're editing on, and then set your "Viewing conditions profile" to System default (WCS profile for ICC viewing conditions).

I had the same issue and spent three days on the phone with Adobe. No one there was able to resolve the problem, so I just dug into my settings and tried everything until I solved the problem.

Good luck.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Sep 29, 2016 Sep 29, 2016

Copy link to clipboard

Copied

I'm not sure your problem is the same as the others. A general difference between ACR and Photoshop is usually caused by a defective monitor profile. The OPs problem was that ACR uses the wrong profile in a two display setup.

Normally you shouldn't touch the "advanced" tab. That just sets system defaults, but shouldn't affect the working profile. If you want to replace a bad profile, you do that in the "devices" tab.

I don't know what happens if you have a monitor profile set as WCS system default. It's supposed to be sRGB, whatever your working display profile/s is/are.  I'd change it back and do it under "devices".

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Nov 24, 2016 Nov 24, 2016

Copy link to clipboard

Copied

I have the same problem with dual monitor on Windows 10.

The solution with "Main Display" work just one time and stops working after you restart Photoshop.

This solution correct image in Photoshop, the picture remains the same in ACR.

Untitled-1.jpg

You can see that I use the last version of ACR and Photoshop is the latest v. too.

I try to make working my notebook with sRGB calibrated display and Dell monitor calibrated with i1 Display Pro to AdobeRGB.

I have no problems with color in other application like Capture NX-D, DxO Optics or Capture One. I think that Adobe need examine this issue with Microsoft or Nvidia, because it's a big problem for users like me and one very little for theirs programmers.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 25, 2016 Nov 25, 2016

Copy link to clipboard

Copied

Let's get this clear: Are you switching main and secondary display in the OS? What exactly are you doing that first clears it and then reverts?

The problem of ACR using the wrong display profile has been reported often enough (not just in this thread) to qualify as a real bug. What is not clear is which exact display configuration that triggers it. Is ACR on the main or secondary? Is Photoshop on the main or secondary?

Two minor points here: Don't use the "Nikon Adobe RGB" profile, wherever it comes from (I don't have it). Use the standard Adobe RGB (1998) profile. Camera manufacturers do the strangest things to make their images look "appealing", and I wouldn't trust this profile for a second.

Also, you don't calibrate your display "to Adobe RGB" or any other profile. You calibrate to its native response, whatever that is, with the parameters you set for white point, black point and so on. Set the monitor to Custom and go from there. The calibrator then makes a unique monitor profile that is completely divorced from any of the standard working space profiles. The monitor profile describes the actual response of the display.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 25, 2016 Nov 25, 2016

Copy link to clipboard

Copied

OK. Can you set the Dell as primary display in the OS and try again? Most likely, ACR is using the profile for the main display even when it's on the secondary.

Your second problem should be resolved by unchecking GPU from ACR preferences.

I wasn't saying the Nikon profile caused this problem. What I am saying is that it's non-standard, an unknown entity and a wild card. As document profile, you should always use the standard profiles. I really can't see the need for it.

As I said, this is a minor point - but when things aren't working as they should, the last thing you want to do is introduce unknown variables. You want a stable, predictable environment to isolate the problem.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

A post just before my reply #65 has been removed, thus rendering it more or less meaningless.

I just skimmed through this whole thread, and it's a complete mess of at least two or three unrelated problems all mixed up. This is chaos.

I suggest those here who still have unresolved problems start a new thread. Describe the issue as precisely as possible, what type of display, how many and how they are configured, how they are calibrated/profiled (if at all), and include comparative screenshots.

This kind of "I have the same problem"-branching of a thread is common and perhaps unavoidable, but it usually just confuses the real issue. Very often it's not the same problem.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

I don't understand why, but 2 problems was a problem of calibration software from Dell.

I recalibrated my monitor with standard i1Profiler program and I have no problems with colors, shadows and image with histogram bugs.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

The problem come back after restart

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

I think that three problems comes from the same one.

After deleted calibration soft and all folders with and all previous created profiles I installed new soft Dell UltraSharp Calibration Solution make spatially for my Monitor and i1Display Pro calibrator  and calibrate my display in notebook to Native (appox. to sRGB) and Dell U2413 to Native and to AdobeRGB profiles.

No change - the difference is visible, the bugs with picture and histogram persist. In older version of ACR I don't have this problem.

Impossible to work with.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

In Photoshop on display with AdobeRGB colors this is more terrible.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

Now unchecking Use Graphic Processor help me to solving this 3 problems.

Why this affects color and shadows I don't understand. This worked 3-4 moth ago.

I will to install older Nvidia driver.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

After all. Reinstalling Nvidia driver from 1 December 2015!

Recalibrate one more time my Monitor Dell with last Dell calibration software to AdobeRGB and to Native profiles.

Check UGP. Work fine with AdobeRGB profile no difference in colors, no in shadows, no bugs with picture, no bugs with histogram.

I have the same difference with colors and shadows with Native profile applying.

I don't understand why it was difficult to know for people who working with..

Uncheck GPU may be it was good suggestion, but I think you guys need to work in cooperation to preserve this things for non professional PC users

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

OK. There seems to be a problem with the profiles written by the Dell calibration software then.

Looking at your last screenshot above, it's clear that the right profile is being used (there are no general saturation shifts, as there would be with profiles for one standard and one wide gamut). The difference is that ACR shows excessive shadow clipping.

So what it looks like at the moment, is that the Dell profile is defective/corrupt in some way. I'm not familiar with the Dell software (all I know is that it's made by x-rite), but make sure the software is set up to make version 2, matrix-based profiles - not version 4 or table-based. Both those two latter policies are more prone to errors.

Although both of these end up in the same display profile, the source profiles are different (Adobe RGB vs. linear ProPhoto) - and so these are two different conversions. With a defective profile, one can work fine and the other fail.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Nov 26, 2016 Nov 26, 2016

Copy link to clipboard

Copied

Version 2 make some problems with Mozilla colors, perhaps the only browser that supports color management.

I make one with version 4 and matrix-based.

New drivers from Nvidia and new Photoshop with ACR at first don't work with old and new profiles from Dell and X-Rite.

I prefer have the latest version of ACR with Photoshop and have old driver from Nvidia, if I have no choice.

All old and new profiles from Dell and X-Rite works fine with other photographic software. Sorry to say this.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines