d_hob's profile

12 Messages

 • 

160 Points

Fri, Feb 5, 2021 5:32 PM

Inconsistent color display on external monitors, Photoshop v 22.1.1 and Bridge v 11.0.1, Mac

I'm having serious color management issues in Photoshop v 22.1.1 on a MacBook Pro, and this started sometime within the last month (maybe a bug was introduced in the latest version of Photoshop?). Specifically, when working on a color image on an external monitor, the colors of the image will suddenly and unexpectedly shift. Also, colors will be inconsistent within the app. For example, the image I'm working on will appear one way, yet in a sub-window – like the Navigator – the color will appear differently. By far and away the easiest way to replicate the problem is to simply open a color image on an external monitor and then just resize Photoshop's window within the screen. Suddenly the colors will jump. Adobe Bridge 11.0.1 also exhibits inconsistent color handling, showing one set of colors in thumbnails and another in the Preview pane.

 

I have tested this problem and replicated it on two laptops - both older 15" MacBook Pros (one Retina 2012, one Retina 2013) with Nvidia GPUs, both with 16GB RAM. I have replicated the problem on both Mojave and Catalina. I have replicated the problem across two different high end color critical external monitors, one an NEC PA272W, the other a brand new Dell UP3017 (both connected via miniDP). I have replicated the problem both with and without color management (it occurs even after doing a factory reset on the monitors and deleting all monitor icc files). I replicated the problem using an external SSD that I loaded a fresh install of Catalina on and on which I only otherwise installed the latest versions of Photoshop and Bridge (I booted off this external SSD via Thunderbolt 1).

 

Any help would be *massively* appreciated. I'm basically stopped cold in my work because of this.

Responses

125 Messages

 • 

2K Points

7 m ago

Not entirely sure what triggers it, but every once in a while, PS has issues when re-drawing the screen. For instance when I move an image, it 'flickers' between correct and incorrect (desaturated) appearance.
If I then hit CmdR twice (rulers) I get stuck with the incorrect view.


Gone after I restart PS.

(I think I occasionally saw this in a previous version of CC, but not entirely sure.)

Screencast of the issue (PS CC2019 for reference, which displays the image correctly here) 

https://www.dropbox.com/s/maw0ojnjrli61zv/PS%20CC%20Display%20profile%20issue.mp4?dl=0


Working on a 2010 MacPro with an Eizo CG223W (wide gamut), calibrated using Eizo Color Navigator.

Note: This comment was created from a merged conversation originally titled PS CC 2021 display profile issue

125 Messages

 • 

2K Points

Update: I can confirm PS CC 2019 occasionally buggers up as well: happened just now when I arranged windows '2-up vertical'.

But happens way less often, and unlike 2021, it does switch back to the correct view.

Haven't been able to consistently reproduce, but in 2021 it happens a lot on my system.

tomekbu

81 Messages

 • 

560 Points

6 m ago

This is a critical issue for me, which makes the outcome product from PS just unpredictable, in terms of colors and/or brightness of the final images. I have run through lots of similar cases reported in the internet, in discussion groups, etc., with some workarounds proposals, but no stable not ultimate solution so far, so I am just desperate. I am preparing images in PS and I just can’t be sure what quality images will be saved/printed/published/delivered.

The issue regards working with two monitors – one in laptop, the other external, an Eizo one, and it regards apparently hardware monitor profiles, which are being used by Photoshop incorrectly.

I am using Photoshop on Eizo monitor only, so expecting Eizo profile to be used by Photoshop.

I am always using the latest version of PS by now (22.1.0), also always hoping, that Adobe would fix the problem with next version.

I am running MacBook Pro with Catalina 10.15.7, but the issue was present also in previous versions (I have checked 21.2.4 – also errors).

The simple example of this, while working with an image is that: I am having a couple of some simple adjustments layers in the Layer Panel. Now I click on the last layer (the bottom one), and then make a second click on an empty area below this layer – these are just clicks which should change nothing. Instead, each click changes the brightness of the image with each single click. Just a magic.

Another case – I am opening a JPG image and this is being displayed by PS desaturated (just from the very start). I just maximize the PS app window (click on the green circle button in the left right corner – as usual to OSX) and the image gets saturated properly.

Another case – I go to full screen view in PS (F button) and the image gets oversaturated.

Another case – PS displays image properly, I switch to Chrome browser (on the same Eizo monitor) and go back to PS – the image gets oversaturated.

Another case - It is also enough to switch from PS to Chrome on the same monitor, and after that image in PS is desaturated. The for example, clicking F (for full view) restores colors, next F oversaturates, next desaturates again. And so on. Really crazy and whats more, I am never sure which state is correct, so in these terms PS is unreliable. I am not facing any kind of such problems with Lightroom, which I am using also strongly intense.

Generally, some actions destroy displayed color/brightness, some other actions restore from incorrectly displayed

Anyway, PS behaviour is just the behaviour is random. I can never be sure if an image is being displayed properly or not, so I am not sure if my processing is in proper direction (if i.e. PS desaturates, I am going to more saturate, which in turn can make the final image oversaturated). I perform lots of processing also as a service to others, so this is just disaster when I can’t be sure if what I see in PS is correct or wrong.

I tried some other workaround like setting on my laptop the profile od Eizo monitor (even if getting wrong colors on laptop screen) – to deprive PS of a chance of using incorrect profile, but PS is unpredictable, sometimes working correctly, sometimes not. So generally a failure.

You can see an example PS behaviour on sample video screenshot attached to this post.

This problem occurs in many different ways, the video shows one of them.

I have found over internet, that there are lots of cases people are struggling with, the OS (Mac or Windows), the type of external Monitor does not seam to be important.

I have performed many tests - i.e. reset all my PS preferences, made different configurations of Eizo monitor (using LUTs, not using LUTs, etc) - all with the same result.

I have tested the situation with all the same hardware (laptop, Eizo) but I have run PS CS6 (yes - very old version) with OS High Sierra - no problem at all, I have done lots of tests with only positive effects. This would indicate, the problem came with newer versions of PS or OS, however considering the behaviour of PS I have just described, I doubt OS to be the reason.

********************************************************************************

In this place I will keep up to date the summary what we know at this moment:

1. There is no fix and no workaround, that might be considered as working; the failure appears mostly randomly - after performing some operations in the apps, but some cases are repetitive and quite easy to recreate. The workarounds have different impact on the failure – at the beginning seam to work, but after some time the defect appears again.

It seams that Photoshop CS6 was not affected by the failure, but since Photoshop v 21.2.4 up to current version the problem exists. It appears also in Lightroom.

2. Doing the following:

a) setting the external monitor as primary

+

b) launching the app there

+

c) not dragging the app to another screen

+

d) setting destination external monitor profile before launching the app

+

e) not changing the external profile while working with app

+

f) not switching to other apps/monitors while working with the app

+

g) set on laptop the same hardware profile as on external monitor - to have the same profiles for both screens

seams to have the best effect, however cumbersome and not confirmed yet, that the failure doesn’t appear, so needs still attention

3. Switching the GPU off – does not help and introduces another problems

- the app behavior is not smooth, it works very laggy

- there are some artifacts appearing on the screen like solid gray boxes – different sizes, places, appearing and disappearing while working with the app

the paths being created with the Pen Tool change color from blue to black, making paths just invisible on dark areas/images – making the tool unusable or requiring some dedicated workarounds (like inverting the image to make it light)

4. Avoiding using certain features of the app may help – i.e. not switching the app to full view (F key) – most of wrong Photoshop behavior was triggered by this. In Lightroom – hiding left panel was triggering the failure.

5. Changing the hardware connection with external monitor seams to have no positive effect (no influence).

6. The app window size has some influence – the app resized to a smaller than full screen size seamed to have less cases of failure, than the app window set to full size.

Sometimes, with image being displayed with false colors on full size app window, shrinking the app window was making the failure disappear.

7. There were cases where launching Photoshop on external monitor (while external was Secondary and with its destination profile) – the image in Photoshop was desaturated just from the very beginning – after loading the image file. Restarting Photoshop and loading image again – the same false colors effect.

8. Changing parameters of Eizo monitor (like making version 2 and matrix-based profiles, not version 4 and table-based LUT – in Color Navigator) seams to have no positive effect.

9. Setting the same hardware profile for both screens - so setting up on laptop the profile from Eizo, just trying to leave Photoshop with no chance to mismatch profiles from different screens. This is still not fixing the problem, however it is showing up differently. 
Also, the downside of this workaround is having wrong colors on MacBook, but if it would have helped, it would be of course much better than having not reliable colors in Photoshop.

Other threads regarding the type of failure:

Files too saturated when initially opened, but corrected when dragged to second display and back

https://community.adobe.com/t5/photoshop/files-too-saturated-when-initially-opened-but-corrected-when-dragged-to-second-display-and-back/m-p/11876634#M518550

PS CC 2021 display profile issue

https://feedback.photoshop.com/conversations/photoshop/ps-cc-2021-display-profile-issue/5fb404ba07651a5ca42cc717

Colors won't display properly since update

https://community.adobe.com/t5/photoshop/colors-won-t-display-properly-since-update/m-p/11770484?page=1#M506097

PS CC 2021 display profile issue

https://community.adobe.com/t5/photoshop/colors-between-camera-raw-and-photoshop-are-not-consistent/m-p/11761815?page=1

Photoshop: Colour shifts when switching to fullscreen mode (CS5, Mac 10.7)

https://feedback.photoshop.com/conversations/photoshop/photoshop-colour-shifts-when-switching-to-fullscreen-mode-cs5-mac-107/5f5f45094b561a3d4230993c?page=1

Inconsistent color display on external monitors, Photoshop v 22.1.1 and Bridge v 11.0.1, Mac

https://community.adobe.com/t5/photoshop/inconsistent-color-display-on-external-monitors-photoshop-v-22-1-1-and-bridge-v-11-0-1-mac/td-p/11808668

https://feedback.photoshop.com/conversations/photoshop/inconsistent-color-display-on-external-monitors-photoshop-v-2211-and-bridge-v-1101-mac/601d811de3ae5d2eb279162b

images color changing on external monitor and MBP

https://community.adobe.com/t5/photoshop/images-color-changing-on-external-monitor-and-mbp/td-p/11799004

PHOTOSHOP CC 2015 - color management problems with dual monitor setup on a Macbook

https://feedback.photoshop.com/conversations/photoshop/photoshop-cc-2015-color-management-problems-with-dual-monitor-setup-on-a-macbook/5f5f459a4b561a3d4255d4f8

Photoshop CS5: Color shift in external monitor when switching to full screen view.

https://feedback.photoshop.com/conversations/default_topic/photoshop-cs5-color-shift-in-external-monitor-when-switching-to-full-screen-view/5f5f451d4b561a3d4234cba4

Viewing Photos in Full Screen Mode Photoshop CC on External Monitor Causing Colour Shift

https://feedback.photoshop.com/conversations/photoshop/viewing-photos-in-full-screen-mode-photoshop-cc-on-external-monitor-causing-colour-shift/5f5f45a74b561a3d425853b8

Note: This comment was created from a merged conversation originally titled UNRESOLVED Photoshop 22.1.0: Critical problem with colours / hw profiles on two monitors

(edited)

33 Messages

 • 

452 Points

A couple with similar issues on the U2U forum. I'm trying to direct them here.

tomekbu

81 Messages

 • 

560 Points

Another example:

Photoshop CC 22.1 - colour changes after resizing PS app window
A simple JPG image - opened in PS while PS app window is maximized - you get a desaturated image. After resizing the window the proper saturation comes back.

tomekbu

81 Messages

 • 

560 Points

Another example: compared to Lightroom

Photoshop CC 22.1 – colour problem compared to Lightroom
1. The both applications PS and LR opened in the same time, with the same picture. Clicking on PS changes colour/brightness each time – desaturates the image, clicking on LR has no negative effect.

2. After maximizing the PS app window image gets desaturated. Proper saturation is restored after shrinking PS app window, then situation is the same as in point 1.

3. After entering and leaving the Full Screen mode in PS (key F), the situation reverses – with each click in PS the image gets oversaturated.

26 Messages

 • 

240 Points

As I said elsewhere, I'm experiencing the exact same thing with an IMac (Mojave updated) and a brand new Cintiq 22.

I would like to ad something. In my case the problem occured when I started to use the Cintiq 22 using the HDMI cable through a HDMI>USBc adaptator.

My previous tablet was a Cintiq 21ux connected with VGA>USB-c and I never encountered this issue.

My photoshop, Imac and tablet profiles/settings are the same than before. Except for the fact that now I re-calibrated the Wacom but still had the bug.

Here's a video of my version of the bug :
At least, once the "window catching" is done, the colour get correct BUT if I go back on my main screen with my mouse, the colours change again so if I forget to click again on the PS frame, I work with the wrong colours.

tomekbu

81 Messages

 • 

560 Points

In my case, I have Eizo monitor connected directly to Mac using Thunderbolt.

26 Messages

 • 

240 Points

Weird thing for me, downgrading to PS 21.2.4 fixed the issue.

tomekbu

81 Messages

 • 

560 Points

I've already tested with PS 21.2.4 - no difference in my case, the error is also there.

For sure PS CS6 doesn't show these errors.

tomekbu

81 Messages

 • 

560 Points

What is the way to get Adobe involved in this problem?

2 Messages

 • 

60 Points

@Exoskeleton1994 I have kind of the same issue with my Eizo screen attached via HDMI + USB-C dongle.

tomekbu

81 Messages

 • 

560 Points

Next examples..

Today I have been working with my packshot pictures - take a look and guess which one is correct - Left or Right version? I do not know myself until.. I check the Photoshop output with another software. That is my workflow now.

Is everyone of you sure What You See Is What You Get in PS? I am definitely NOT.

Adobe Administrator

 • 

15.9K Messages

 • 

296.4K Points

It would be good to know if the GPU is involved or not. If you disable "Use Graphics Processor" and restart Photoshop, do you have the same issue?

https://helpx.adobe.com/photoshop/kb/troubleshoot-gpu-graphics-card.html#DisableGraphicsProcessor

26 Messages

 • 

240 Points

@JeffreyTranberry 

Hello and thank you. For now (and for me), it seems to fix the issue.

How do you explain this considering both my OS Mojave and PS are updated ?

Adobe Administrator

 • 

15.9K Messages

 • 

296.4K Points

Not sure. But knowing if you disable GPU gives me something to go on and ask the correct engineers. Did this start with the 22.1 update?

tomekbu

81 Messages

 • 

560 Points

@JeffreyTranberry 

This is on of the oldest test (with GPU) suggested and considered already a couple of years ago. I have already tested and for me it does not resolve the problem - and with each single change like this, PS is acting a little different, but the problem is still there.

Besides, disabling GPU would be still a workaround I do not like to use, since I just want to use the benefits of GPU and have the full potential of PS.

According to my tests, the problem started before 22.1, a coupe of days before I have installed the 21.2.4 (last available at CC), and the problem was the same.

Today, I have tested GPU off once again, here are the results:

1. Loading image to PS:

2. Enter Full Screen view (F button) and back to normal view in PS:

3. Switching to other apps (Finder, Chrome, etc) or sometimes when I maximize PS app window and shrink back (I do not work with PS app maximized all the time, due to other error of PS):

The third image is definiteley oversaturted, but with this PS I am just loosing control which is proper and must check in other apps the PS outcome. So the main problem is, that PS is switching display modes while working with it - it's unstable. 

I will perform some more test with GPU off to catch more cases, but I do really need to switch it back on.

tomekbu

81 Messages

 • 

560 Points

@JeffreyTranberry 

Now got another example with GPU off - see attached video screenshot.

Opening an image is oversaturated in PS just from the very beginning – the state is stable, no activity in PS changes this, even entering and leaving Full Screen view (F button) does not change oversaturation.

Now switching to other app like Chrome and back to PS – restores colours, now in PS colour seem to be OK. But once entered Full Screen View the colour gets oversaturated again and the game restarts from scratch.

26 Messages

 • 

240 Points

@JeffreyTranberry

No for me, it started as soon as I plugged a Cintiq device through HDMI/USB-c adaptor. The issue didn't popped up with my previous Cintiq and the VGA/USB-c adaptor.

tomekbu

81 Messages

 • 

560 Points

@Exoskeleton1994 

Does your problem regard only PS? It sounds very strange, that PS is sensitive to the hardware method of connection to the monitor.

tomekbu

81 Messages

 • 

560 Points

Another example with GPU off – an image opened in PS oversaturated from the very start. Switching to Finder restores colours. Full Screen View oversaturates, then switching to Finder restores colours.

Generally – a document opened in PS is either oversaturated or normal (but there are other cases when is desaturated).

Adobe Administrator

 • 

15.9K Messages

 • 

296.4K Points

Ok. Thanks. Will need help from our color management QE after they return from the holiday.

26 Messages

 • 

240 Points

I have to admit that I'm really confused because I also noticed the issue with Krita a few days ago and now everything seems to be ok. That doesn't make any sense to me, but as you saw on my video, the issue was real and has been happening all the time for several weeks.
This is not the first time I feel a vain joy so...  wait and see.
I'm enduring another major bug with my pens that nobody know how to fix, I will create a new thread about it.

tomekbu

81 Messages

 • 

560 Points

Thank you, please place the link to your new thread as it may be something common. I am facing several other issues with PS like not saving files (Program Error) or destroying PSD files on storage media. There are already threads regarding the first one, but at this point the most important for me is to have an object to save - at the moment PS is unable to display colours properly, so what's the point to save it.

tomekbu

81 Messages

 • 

560 Points

Sounds good.

PS is unpredictable and its behaviour is different each time, with regard to this issue. Every time however, I am able to find new cases of this problem.

26 Messages

 • 

240 Points

I had to re-enable "Use Graphics Processor" to use some functions as "rotate" and made another screen calibration. The issue popped up again.
So I'm back working with the previous version of PS ...

26 Messages

 • 

240 Points

And the previous version of PS also shows the issue now for me too... I'm litterally losing my mind on it, this doesn't make any sense.
I think there's a bug with the external display support of the PS window.

I also noticed that the PS scrolling menus let a "dark shadow" on the screen, which go away as soon as I catch and move the corner of the PS window.
This is visible on any screenshot I made.


EDIT : Krita seems to work fine.

tomekbu

81 Messages

 • 

560 Points

Yes, PS behaviour has no sense, it's just absurd.

According to my tests, the error arrived after CS6 version (I haven't found any issues there) and before 21.2.4 (which is already infected).


Next test I have done: I have measured the RGB values of colours of the same image in two cases displayed by PS. I have measured in two squares (average blurred) of two screenshots put in one image. So the example differences of colours PS displays are:

R: 39 vs 30

G: 49 vs 45

B: 60 vs 57

The difference can be of course seen even with a naked eye. It's just insane:

tomekbu

81 Messages

 • 

560 Points

Another example of the error - this time the difference in behavior between PS and Krita on the same screen.

PS: clicking in several areas of PS working window changes colors/brightness of displayed image. Even scrolling the image up or down show the errors in displaying – flickering all the time. Simple clicks on the Background layer and an empty area below – the same effect.
No chance to work with PS with these kind of errors, just insane.

Krita: the image is stable, displayed properly all the time.

26 Messages

 • 

240 Points

@tomekbu Ok so it confirms that PS is clearly in the guilt team
When the issue first started for me, I thought that the PS window (Cintiq) kind of trespassed on the main screen (Imac) which caused the behaviour. That's why I detached PS from the frame of the Cintiq which fixed the problem for a while but the rest proved that it has nothing to do with it.

14 Messages

 • 

120 Points

I have the same identical issue with macbook pro 16"  with

AMD Radeon Pro 5300M, I have the last OS Big Sur 11.1 and Photoshop 22.1.0, second Monitor EIZO CG2420, and colors in photoshop go randomly correct and desaturated just clicking somewhere or clicking F for switch screen view  option etc...

I have checked that if I switch off the graphic card in the PS preferences the issue is fixed, the same go right if I duplicate the display of the mac on the EIZO.

All other test, change calibration, profiles, uninstall EIZO Color Navigator 7 nothing fix the problem.
I hope the read (and have) a solution soon from Adobe

14 Messages

 • 

120 Points

PS: the issue happen only in Photoshop (I have not tried other adobe software on the eizo yet) but on Capture One for instance there are not problems

tomekbu

81 Messages

 • 

560 Points

@Nicola di Corrado Thank you Nicola for your note - the more examples we describe the more chance Adobe will start to treat this problem seriously.

I have also tested the "graphic card off" and fore some time it seamed to work ok, but after more tests the issue appeared again.

@JeffreyTranberry  I really hope to have got engaged "color management QE after they return from the holiday." as 2 weeks have passed with almost no attention from Adobe and the problem is really serious and urgent.

I am definitely against disabling the GPU as:

- we are paying the full license to have the full functionality of PS; I just reject any option to switch off one functionality to get the other working - it's just ridiculous; comparing Adobe PS to a car - would it be OK for i.e. BMW to say to a customer: please switch off the lights, then the breaks will work correctly? Would anybody buy it?

- the problem appeared long time ago (I have found posts on different internet groups), and it seams Adobe did nothing about this issue, so any workaround seams to be just another dead end

- switching GPU off reveals other problems/errors with PS and makes PS to work in a nasty way

6 Messages

 • 

80 Points

I have the same problem with mi iMac or Macbook Pro on a Eizo CG248-4K , after much frustration and a long support chat with Adobe, which said they would get back to me 6 weeks ago,I found that it is the arrangement setting for your displays that creates the problem.

The home monitor responds correctly, it is always the designated second monitor

that has the problem. Maybe someone more computer savvy has a solution !

tomekbu

81 Messages

 • 

560 Points

@tomvack Can you please describe something more about what you have found? Is there a specific "arrangement setting" creating the problem?

14 Messages

 • 

120 Points

I agree with you, we use Photoshop to edit colours (and other stuff) but without controls on colours we are blind -.- , one of the main functions of this software is compromised...

6 Messages

 • 

80 Points

I do not have the problem on my mac when changing screen modes but on my second monitor.

If I change in arrangement of displays and move the white menu bar over to the second monitor then the Eizo does not  have this effect but the iMac does.
It is inconvenient and seems a bug in the Mac OS X  monitor settings but as I said I am not a computer savvy type.
hope that helps,
tom
tomekbu

81 Messages

 • 

560 Points

OK, now I understand - you are changing which monitor is Primary/Secondary (at System Preferences > Displays > Arrangement). As PS is probably wrongly assigning profiles (in this issue - looking like PS is trying to use the profile of the Primary monitor) if so, setting external monitor as Primary and running PS there, leaves to PS no chance for misusing profiles. That's why it may work and it is not OS X fault. I must check this, however this would be still a workaround and additionally complicating situation while using an odd monitor arrangement - setting external monitor as Primary.
Thanks Tom.

14 Messages

 • 

120 Points

Personally I have the same issue on the eizo if it is primary or not

26 Messages

 • 

240 Points

What do you guys use as connecting device and/or adapter ?

As I said before, I never encountered this issue with my old cintiq plugged via VGA/USB-c (and the same version of PS and samed OS) only using the HDMI/USB-c wiring.

I'm kind of disapointed by what you said, because I wanted to buy and use an external screen as a secondary one and use PS on the Imac waiting for a fix...

tomekbu

81 Messages

 • 

560 Points

I am using just a simple Thunderbolt cable, provided by Eizo - would say a native connection for Apples. However I am still not so believing, that PS work depends on the connection type and PS is the only app facing this problem.

6 Messages

 • 

80 Points

I tried upgrading both cables with no change.

14 Messages

 • 

120 Points

Me too I use display port - usb-c cable and also a hdmi with usb-c adapter and I have the same problem 

14 Messages

 • 

120 Points

Today update, this morning I tried to switch EIZO as primary monitor, and issue is fixed for now

26 Messages

 • 

240 Points

@Niki_di_Corrado
Good to know. I've sent my cintiq back for other reason so I can't test the dual screen config anymore, but I'm planning to purchase an Eizo as well.
So it will be great if you guys could let us know if the update really fixed it. Thx
 

14 Messages

 • 

120 Points

I'm working also today with this configuration and it's all ok, Eizo as Primary monitor work great. If there are new issues I will update 

tomekbu

81 Messages

 • 

560 Points

I have also been testing Eizo as primary today and was almost unable to recreate cases of Photoshop failure. There was only once however, when entering full screen (F button) left the image in PS oversaturated. Switching to Chrome and back restored the colors and I was not able to recreate this case since then, so a bit affraid.

I will be monitoring next days and let you know how it works, also please everyone to keep informing as well.

It would be definitely a huge step for a work around one of the most heaviest Photoshop failure. This is thanks to you guys, Adobe can learn from this and it is such a shame they decided to stay dead silent, without even a single word.

In my opinion it is still necessary to push Adobe to fix their bug, as:

- the workaround may stop working due to any condition, that may happen (i.e. in next versions Apple may change the way Primary/Secondary setup works)

- it limits using Photoshop to one external screen (Primary) - so practically, with this bug, no chance to use PS built in functionality for multiple screens

- setting external monitor as Primary is a bit cumbersome as many OSX functionalities run on Primary screen only - this requires the external monitor to be switched on most all of the time (otherwise physically disconnected)

- and an obvious one one - we are paying Adobe for failure free products, so also for bug fixing

tomekbu

81 Messages

 • 

560 Points

As I have mentioned in the last post, I have experienced colour problems present even in that configuration, when the external monitor is set to Primary. This happened again many times, but I was unable to recreate the problem so far, which was driving me just crazy.

Recently however I have found an example which is stable and the error appears each single time. I think, this might be an excellent case to Adobe for further research of the wrong Photoshop behaviour – this is a ready to explore use case – just recreate and trace the error in the code.

These test were performed after the latest Photoshop update to version 22.1.1

Now, I have noticed, that the error appears when changing external monitor profile - while Photoshop is launched. Generally I am using two Eizo profiles (regularly calibrated):

CAL2” – used with all image processing software like Adobe’s Photoshop and Lightroom, when performing professional processing

Custom” – used for any other works on Macbook, like reading/preparing documents, internet, mails, OS operations, etc. which enables me to adjust monitor’s brightness to whatever suits to me while working with different external (ambient) lights

So, after starting Photoshop the colours are always ok. But when changing the monitor’s profile: Custom>CAL2 or CAL2>Custom and switching then the view mode to Full (F key) the image gets either oversaturated or desaturated. These wrong colours are stable and do not depend on any further action in Photoshop. They are restored to proper colours only after switching from Photoshop to an other application (like Chrome) and back.

I hope this helps. I wonder if you face the same.

2 Messages

 • 

62 Points

I'm having the same issue with my second monitor - go from chrome, back to photoshop and my image is oversaturated. Press 'f' and it goes back to normal. Its super frustrating and I feel like I can't trust what I'm looking at.

tomekbu

81 Messages

 • 

560 Points

@heather lin Exactly wysiNwyg (what you see is NOT what you get).

Cannot trust this tool.

tomekbu

81 Messages

 • 

560 Points

Now things are getting even worse. I know this place is dedicated to Photoshop, but I have found in Lightroom similar problems with colours, which is now terrifying me totally.

After I have discovered the influence of changing monitor profile on to Photoshop failing to correctly display image colours, I have performed similar tests with Lightroom – and yes, the problem is also present in Lightroom.

Simple test:

1. Start Lightroom with monitor profile set to “Custom”

2. Change the monitor profile to “CAL2” while Lightroom is on

3. Hide left panel in Lightroom – this gives the image oversaturated

What is interesting:

a) the image in small inspect view is displayed with correct colours

b) the image displayed in Fill View mode (F key) is displayed with correct colours

c) all other cases – the image is oversaturated; now hiding or showing up the left panel has no impact, switching to an other app like Chrome has also no influence – the colorus are wrong

Now it is a total disaster – I can never relay on colours displayed neither in Photoshop nor in Lightroom.

The current workarounds, that I think are minimizing (NOT preventing) the risk of wrong PS/LR behaviour as follows:

1. Set the external monitor to Primary

2. Set the destination monitor profile before you launch Photoshop and Lightroom

3. Do all your best to launch and run Photoshop and Lightroom on that external monitor (Photoshop may have issues with that depending on many circumstances)

4. Check results of your work frequently and confirm the final output in a third party software.

This sounds terrifying but I have found no other workarounds.

Maybe you will discover something more/better.

Maybe some day Adobe will get interested.

33 Messages

 • 

452 Points

@tomekbu

This one is easy: you have to relaunch the application when changing monitor profile in the OS. The profile is loaded at application startup, and will be used for the remainder of that session - until relaunch.

tomekbu

81 Messages

 • 

560 Points

That is not so easy, unfortunately. What you say is a kind of workaround, which I have already pointed above (point 2), and this only minimizes the risk of wrong PS/LR behaviour.

Once PS/LR is launched, changing monitor profile has positive effect and the colours are right. But after some time of working or some specific operations, the PS/LR failure appears - some cases are random, some are recurrent (easy to repeat). 

If you have watched my example videos, there is also one, when all is OK until you just scroll an enlarged image - once you are scrolling (up/down or left-right) using side scroll bars - the image is just flickering as if the profiles were switching forth and back very quickly. Once you stop the scrolling the colours get correct. Or other simple examples - switching to full screen and back destroys colours, or hiding left side panel in Lightroom - the same. So generally - until some actions, everything in PS/LR seams OK.

So the error is still there in the code and shows up in many different cases.

Relaunching the application helps, but only until the next appearance of the errors.

For me, setting the destination profile before starting PS/LR, and setting external monitor as Primary, to force both PS and LR start on that screen, is not much problem - actually I am now using this all the time (and just recommended to others). The problem is, that this does not prevent the colour errors, so I cannot trust what Photoshop and Lightroom are displaying. This is so frustrating.

tomekbu

81 Messages

 • 

560 Points

@renedamkot Is there any way to merge your thread to this one? It would be worth having all in a single place, with as many cases as possible.

tomekbu

81 Messages

 • 

560 Points

Hi @JeffreyTranberry  , is color management QE returned from the holiday? Would you please report to all of us - what is the progress and what has been done so far? It is almost 1 month as we are awaiting.

6 Messages

 • 

130 Points

I am also experiencing this issue. I made a thread about it here.

I am using the same equipment that I have for months and now suddenly there's an issue.

I've learned that dragging Photoshop to a different monitor and then back to my calibrated monitor temporarily fixes it, but this is just ridiculous.

tomekbu

81 Messages

 • 

560 Points

Yes, it seams there are lots of people suffering this failure with threads in many other places. Thank you @benjamin_disinger for the link and info.

There is no fix and no workaround at this moment, that would guarantee working Adobe software correctly. And yes - this is ridiculous, that while doing my work, I've got to strongly pay my attention and all the time be checking, whether Adobe displays colors correctly. Doing various efforts like restarting apps, dragging from one monitor to another and back, switching to other apps, avoiding some app functionality, switching off some features, trial and error methods.. all as part of the processing workflow - is it still for professionals? Should't reproducing right colours be a fundamental feature of software processing graphics?

tomekbu

81 Messages

 • 

560 Points

Just to summarize what we know at this moment:

-------------------------------------------------

I have moved this content to the very first post in this thread, just to make it easier accessible.

tomekbu

81 Messages

 • 

560 Points

Another example of the bug, this time also in Lightroom - just while using the brush tool – every single move of the tool while painting causes the image flickering, as if two different profiles where used and Lightroom instantly switch between them.

tomekbu

81 Messages

 • 

560 Points

Just found another thread regarding the same issue, from Feb 20, 2012:

Photoshop: Colour shifts when switching to fullscreen mode (CS5, Mac 10.7)

https://feedback.photoshop.com/conversations/photoshop/photoshop-colour-shifts-when-switching-to-fullscreen-mode-cs5-mac-107/5f5f45094b561a3d4230993c?page=1

The case is documented very well, there are proposals of some workarounds - and apparently the failure was present in CS5/CS6. A lot people struggling with the failure have posted there, but still without any attention from Adobe.  One of them:

Go to the color profile both of monitors and set the same color-profile and you'll get the happyness.

It seamed to work there for some cases, however this was also one of my first tests I have performed - I have set the MacBook profile to be the same as my CAL2 on external Eizo, but it did not help (however the Photoshop failure was showing up differently). The downside of this workaround was also having wrong colors on MacBook, but if it would have helped, it would be of course much better than having not reliable colors in Photoshop.

33 Messages

 • 

452 Points

New cases keep popping up in the U2U forums. It would be really nice to have something to tell them, so I hope Jeffrey can come back with some news from color management QE soon.

As observed, the issue itself is really old, dating back to at least CS5, but the frequency seems to have picked up lately.

In all my years of responding to color management questions from users, this is the only issue where I'm genuinely stumped. I have no idea what's going on here, aside from the basic fact that the wrong monitor profile is used.

tomekbu

81 Messages

 • 

560 Points

Yes, indeed, still hoping Adobe will pick up the issue.

12 Messages

 • 

160 Points

I have found a solution to my original issue by rolling back Photoshop. My original post is here:

Inconsistent color display on external monitors, Photoshop v 22.1.1 and Bridge v 11.0.1, Mac

https://community.adobe.com/t5/photoshop/inconsistent-color-display-on-external-monitors-photoshop-v-22-1-1-and-bridge-v-11-0-1-mac/td-p/11808668

and copied here:

https://feedback.photoshop.com/conversations/photoshop/inconsistent-color-display-on-external-monitors-photoshop-v-2211-and-bridge-v-1101-mac/601d811de3ae5d2eb279162b 

I discovered that if I rolled back two versions to Photoshop 22.0.1 then my problems with Photoshop disappeared, so it seems that the 22.1 version introduced a bug that caused the problems I was seeing.

That said, the problems do not disappear in Bridge by rolling back to previous versions. That's odd, since I know those previous versions worked at some point. In Bridge, thumbnails display colors incorrectly, but any image in the Preview pane does display the correct colors. In Bridge, the thumbnails will appear to start with the proper colors but then lose them after about one second. It's as if Bridge loads the proper color profile but then ... well, who knows what.

tomekbu

81 Messages

 • 

560 Points

Thanks @dirk_hobman . Unfortunately according to my tests, the problem exists also in Photoshop v. 21.2.4 .

At this point I have no idea what was the first version of Photoshop affected, as there are posts reporting this issue in CS5/CS6 (links in my first post of this thread) - so the problem seams to be really old.

12 Messages

 • 

160 Points

According to Adobe tech support, the problem is with my GPU. I thought my system met the minimum requirements for Photoshop 22.0 and onwards (indeed it works fine with 22.0.1, just not beyond that), as it has 2GB of GPU memory split between the Nvidia graphics card and an integrated Intel card, but it sounds like it needs to be a 2GB minimum on just one card. Minimum requirements are posted here:

https://helpx.adobe.com/in/photoshop/system-requirements.html

So I'm stuck with version 22.0.1 and earlier until I can get a hardware upgrade.

12 Messages

 • 

160 Points

4 m ago

Update:

Forcing the external monitor profile to that of the MacBook Pro screen profile seems to eliminate the problem. That's not a workable solution, but the reverse could be for now – force the MacBook Pro screen to use the profile of the external monitor. (Seeing the results sure does make you appreciate proper color management.)

tomekbu

81 Messages

 • 

560 Points

@d_hob In my case this didn't help - it seamed to be ok at the beginning, but after some more testing, the failure has come back. 

12 Messages

 • 

160 Points

4 m ago

Update 2:

I discovered that if I rolled back two versions to Photoshop 22.0.1 then my problems with Photoshop disappear, so it seems that the 22.1 version introduced a bug that caused the problems I was seeing.

That said, the problems do not disappear in Bridge by rolling back to previous versions. That's odd, since I know those previous versions worked at some point. In Bridge, thumbnails display colors incorrectly, but any image in the Preview pane does display the correct colors. In Bridge, the thumbnails will appear to start with the proper colors but then lose them after about one second. It's as if Bridge loads the proper color profile but then ... well, who knows what.

tomekbu

81 Messages

 • 

560 Points

I have tested 21.2.4 and have found the failure to be present there. There are lots of other examples (links to the threads I have placed in my posts), where people were/are facing these problems even in CS5 and CS6.

12 Messages

 • 

160 Points

4 m ago

According to Adobe tech support, the problem is with my GPU. I thought my system met the minimum requirements for Photoshop 22.0 and onwards (indeed it works fine with 22.0.1, just not beyond that), as it has 2GB of GPU memory split between the Nvidia graphics card and an integrated Intel card, but it sounds like it needs to be a 2GB minimum on just one card. Minimum requirements are posted here:

https://helpx.adobe.com/in/photoshop/system-requirements.html

tomekbu

81 Messages

 • 

560 Points

Well, the minimum requirements are definitely important for any software to run properly. However it really doesn't sound convincing, that not meeting these would make Photoshop to use wrong hardware profiles for reproducing colors in some cases. Besides, it is just another guess and it would really be helpful to finally hear a couple words just directly from Adobe. Still hoping their experts will get involved, otherwise it's just a tilting at windmills.

12 Messages

 • 

160 Points

You're completely right. It's not a graphics card / hardware issue. I rolled everything back to Photoshop 2020 and Bridge 2020, both of which always worked fine in the past, and they're both still broken with regards to color management. Bridge 2020 shows the proper colors in the Preview pane but not in the thumbnails. Photoshop 2020 shows the proper colors with the image being worked on, but much to my horror I just discovered that it's totally broken when printing. When designating the specific output profile to use, it just completely ignores what I enter and prints in what looks like the sRGB space. I hadn't realized that the printing was broken as well. This is beyond messed up.

 

I created a new account on my MacBook Pro and loaded Bridge 2020 and Photoshop 2020 on there, so as to avoid any issues of corrupt preference files, and they're both broken there as well, though oddly in a different way. In that new user account, Bridge 2020 now shows colors properly in the thumbnails but wildly off in the Preview pane (where the colors are hyper-saturated), and Photoshop 2020 is back to switching between different color profiles at random. 

 

What started all this is a bit of a mystery, though it seemed to break when I updated Photoshop 2021 beyond 22.0.1 something like a month ago. Before that I never had any of these problems. Also, it's definitely an Adobe problem, as the latest Affinity Photo 1.9.0 works perfectly.

 

I think it's legitimate for Adobe to dismiss my problems for the 2021 versions of Photoshop and Bridge based on my hardware limitations (since who knows what might be happening there), but not for the 2020 versions, as those have always worked until now. I'll be back on with their tech support in the next day or two and will report back. I feel like if I'm going to suffer through this, they should too so that it can be logged as a legitimate problem. 

tomekbu

81 Messages

 • 

560 Points

Yes, this regards Photoshop and Bridge, but also Camera Raw and Lightroom. I was focused on Photoshop and Lightroom as these two I have been using in my usual workflow. I have posted plenty of examples, described and catched as video screenshots, with the purpose of recreating problems easily.

I am happy you are determined strongly, as lots of people, as I observed, just gave it up. The worse is, that many people may be just unconsciously facing these problems, correcting image parameters in wrong directions and sending their faulty outputs further on, as perfect products.

tomekbu

81 Messages

 • 

560 Points

4 m ago

It seams, that latest 22.2.0 version of Photoshop is not addressing the problem.

4 Messages

 • 

92 Points

4 m ago

I wonder if this is predominantly an issue on M1 chip macs and dual displays?

It seems that Apple have 'changed' the display sensing/ display description on those Macs to show displays as "unknown", internally rather than by name.  

I was speaking to the developer of basICColor display 6 software about this today and he came across the issue, for which he has had to develop a workaround. Of course it's been reported to Apple but as their "issue with LUT type ICC profiles" has been around since OSX 10.12 and much reported, maybe a fix will not happen anytime soon.  

If anyone would like to test display 6 on their mac which is showing this issue it would be great to have feedback: https://www.colourmanagement.net/products/basiccolor/basiccolor-display-software/

I hope this helps
neil barstow, colourmanagement net :: adobe forum volunteer
google me "neil barstow colourmanagement" for lots of free articles on colour management

(edited)

tomekbu

81 Messages

 • 

560 Points

@neilB The issue regards dual displays, but definitely not only M1 - the problem has been reported even with CS5/CS6, so is really old. There are lots of people struggling with this and on many variations of Mac hardware.

Many tests have shown, that the problem is related to Adobe software rather than Apple's.

There is still a rumor about this, people presented some attempts of workarounds, however all is only still a guess, as no Adobe's comment on this topic so far.

4 Messages

 • 

92 Points

Hi

I think different dual display issues may be getting conflated here. 
For ages Photoshop has been less than reliable in using dual displays because the profiles for each were not used reliably. 
the solution (pretty reliable) was to set the important display as primary in system preferences  and be sure that photoshop opened on that display - i.e. where it would be used. 

Latterly, though, there have been reports of changes in appearance whilst the app is open, even without shifting windows to the other screen. Dragging, resizing windows could produce changes in appearance which may be due to the other displays profile being picked up. 
This seems right because my suggestion of setting the less important screen to use the same icc profile as the important one fixes the issue fairly reliably. 

AFAIK this is new. 

all this appears to be connected with which display profile is used on multiple displays but the symptoms this year seem quite a lot worse. And the workaround less acceptable. 

if switching display profiles in Eizo’s colornavigator SW (or,for normal screens, in the system preferences**) then current versions of Photoshop often need to be restarted to reliably pick up the new display profile.

[**but don’t do that with an Eizo Coloredge as the hardware LUT is not loaded by OSX]

I presume you have to done a photoshop bug report?

Be nice to see this fixed properly. 

I hope this helps

neil barstow, colourmanagement net :: adobe forum volunteer

google me “neil barstow colourmanagement” for lots of free articles on colour management. 

(edited)

tomekbu

81 Messages

 • 

560 Points

Yes, there are lots of potential workarounds - each have some influence, but none resolves the issue - I have placed all found so far at the beginning of my post. There are also the links to other threads I have found - but if you are familiar of another threads - please include links here and I will place these at the beginning.
I have done all I was able to, but still more and more frustrated due to no reactions. Seams to be a dead end.

4 Messages

 • 

92 Points

Hi, yeah I saw that but I could not tell which workaround you were liking best when you wrote

" seams to have the best effect, however cumbersome and not confirmed yet, that the failure doesn’t appear, so needs still attention

all the options above were marked with +, I didn’t see one with an "=" symbol

"Seams to be a dead end"

let's hope not it making Adobe apps virtually unusable for some users. 

hope this helps
neil barstow, colourmanagement net :: adobe forum volunteer

(edited)

tomekbu

81 Messages

 • 

560 Points

Well, "the best effect.." = a+b+c+d+e+f+g
I mean using all workarounds a..g in my opinion may give best results, but is not fixing for sure. All are based on my own tests, so I did not include links, however some of them I found confirmed by other users.
Thanks @neilB 

33 Messages

 • 

452 Points

3 m ago

tomekbu

81 Messages

 • 

560 Points

@dag_fosse Well, according to my tests it does no fix, but occasionally may seam as if. Anyway, getting rid of GPU is definitely not a good solution for working with Photoshop, as it greatly influences the functionality and comfort.

33 Messages

 • 

452 Points

3 m ago

Agreed, it's obviously not a "fix" as such. Poor choice of words on my part. But it may be a useful pointer to where the underlying problem is.

Given that the actual conversion into the monitor profile happens in the GPU, and display assignment is handled by the GPU/operating system - then a pattern may seem to emerge.

It is still a very conspicuous fact that this only happens in systems with an integrated display + external display. To this day, I have never seen it reported from desktop systems with multiple displays.

tomekbu

81 Messages

 • 

560 Points

I think, that this is a very good point (not reported from desktop systems with multiple displays) and may help narrowing the area of searching for the source of the problem.

It is interesting however what about iMacs, which do have integrated monitors.

33 Messages

 • 

452 Points

There have been several cases with iMacs on the U2U forums.

2 Messages

 • 

70 Points

Hi people, I have the same problem with a Mac Pro Catalina 10.15.7. 2 with 2 x 27inch displays. Primary Monitor is LG, secondary Monitor is an Eizo.

(edited)

2 Messages

 • 

70 Points

In addition, I've just switched the Eizo Monitor to be the primary monitor and that has fixed the problem. I didn't want to stuff around with GPU or Open GL settings as I've read also in other forums. While this does not fix the issue as I'd prefer to have the LG as my primary, I can work with this and am no longer getting the colour fluctuations. 

Also, please note before I had this Eizo 27inch monitor, I had an Eizo 24inch monitor and the same problem was occuring. So whether it's an Eizo or Adobe problem to fix is questionable. The problem is not happening on my secondary monitor, the LG 27inch.

Good luck to the rest of you. Hope you find solutions.

tomekbu

81 Messages

 • 

560 Points

Thanks @dario arnone , so still no news and still more and more people facing the failure. Playing around with GPU may be just a kind of additional test, but definitely not a good idea to work having it switched off.
I also definitely would prefer to have my setup with Mac monitor set as primary, otherwise it so much influences the way of using other software, which is cumbersome and not ergonomic. Then, it doesn't sound good to be forced to rearrange hardware setup, soft configs, workflows and processes - all just to make a room for Photoshop to behave as less faulty.
There were lots of tests performed and reported, but it hasn't been confirmed officially which software is responsible fot this problem - interesting however, that there is no single sound from this direction.

It is really sad, there are so many new features being invented, IA based solutions, 4K, sync cloud presets, performance boosts, etc. whatever you can imagine, while the simple matter of consistent colours cannot be offered.

Good luck.

4 Messages

 • 

102 Points

3 m ago

I am experiencing this issue as well. Working in a previous version of Photoshop (CC2020) it seems to be solved. Once it also appeared in that version, but after a restart it is working stable again.

Current setup / apps:

Photoshop v22.3 (CC2021)
Eizo CS2420
OSX 10.15.7 (Catalina) 

In all other Adobe apps, including Adobe image RAW, the colors are represented accurately without flickering.

4 Messages

 • 

102 Points

The Eizo is my secondary monitor connected to a Macbook Pro.

tomekbu

81 Messages

 • 

560 Points

@paul_brouns I am running exactly the same setup as yours, but unfortunately I've got to set my Eizo as primary, since I was facing the problem too often.

I have confirmed (as well as others) that the problem exists also in other Photoshop versions and also in Lightroom - all depends on specific functions being used. So still forced to pay strong attention and double check, if displayed colours are ok or distorted.

1 Message

 • 

60 Points

23 d ago

Same issue here. ACR / and PS both seem largely effected for me. It's a huge issue and effectively renders my colour management useless. Is there anyone from Adobe actively working on a fix?

My original thread was posted here.
https://community.adobe.com/t5/photoshop/photoshop-screen-colour-calibration-glitch/td-p/11980952

Cheers,
Gavan.

tomekbu

81 Messages

 • 

560 Points

It doesn't seem anyone is working on a fix. There is even no single comment from Adobe side through all this issue, so it seems to be important only for us - end users.

2 Messages

 • 

70 Points

22 d ago

Is there already a solution from Adobe or other parties ?  I have noticed the same problem since yesterday after buying my CS2420 EIZO screen some weeks ago.  I used my wacom and started from RAW photo's via 'raw converter'.  Going to test without them , also one time starting from jpeg file and also test with the Eizo as primary screen.  Look forward to hear a solution :-)

tomekbu

81 Messages

 • 

560 Points

I also look forward for a solution from Adobe, since so much time already.

4 Messages

 • 

92 Points

22 d ago

I've not seen a report here from anyone trying my suggestion of using basICColor display profiling software to see if that helps. I've not had any failures of this nature from clients using it. 

The only (apparently reliable) workaround that fixes Macs showing the issue is to set the MacBook or iMac to the same display profile as the external monitor.

- i.e. to have the same display profiles for both screens.

That way the C.M. can't get mixed up between display profiles. 

Of course doing that spoils the accuracy of the iMac or Macbook screen but when doing important work, its worth knowing the MAIN screen is reliably correct 

If anyone would like to test basICColor display 6 on their mac which is showing this issue it would be great to have feedback: https://www.colourmanagement.net/products/basiccolor/basiccolor-display-software/

I hope this helps
neil barstow, colourmanagement net :: adobe forum volunteer
google me "neil barstow colourmanagement" for lots of free articles on colour management

2 Messages

 • 

70 Points

@neilB tx

it's indeed a solution adapting the display profile.  it's a work around but helps for now

I also did some tests and what als helps is to put the monitor as primary screen.  In that case you don't have to switch from one to another.  If so, also adapt display profile

Hopefully technically PS or other will come with  a update and solutions 

1 Message

 • 

60 Points

15 d ago

I too am hoping with every update that a fix arrives but I'm disappointed every time! I just upgraded my Mac to Big Sur whilst crossing my fingers in the hope that somehow the problem would rectify itself but alas, the behaviour is still there. All my other programs handle the colour management of an external monitor without issue, but for some reason Adobe Photoshop was broken after the release of version 22 and it appears that Adobe is not interested in fixing it. I can't understand why! I have been using Photoshop for decades and never before have I been this frustrated with the loss of productivity I experience now every time I use it! I thought I could live with the workaround of changing the primary monitor arrangement to my external monitor but it just creates another problem. Sure, the colours are correct when the image opens, but I now have to "wake" Photoshop up before I can do anything to the image. Previously I could open an image from Bridge, and then do a select all and copy straight away to it and off I go. Now, Photoshop just sits there dumb until I click somewhere on the Photoshop UI to make it respond to my commands. Does anyone know how I can execute shortcuts to an image without constantly adding another action to the workflow for every image I open? It's driving me crazy...

In the good ol days my laptop monitor was the primary screen, and I would have Bridge open on it whilst working in Photoshop on my calibrated wide gamut monitor. No colour issues, no productivity loss. When working on hundreds of images per week this current situation is a definite downer.