[Bug 11532] New: Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Summary: Photoshop doesn't support custom monitor profiles
           Product: Wine
           Version: CVS/GIT
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdi32
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Roland Geflitter wrote on wine-users:
"I'm running a test with Wine 0.9.51 on SuSe 9.1 and Photoshop CS (1) and 
everything works perfectly (even working with big files of 1 GB and 
launching Image Ready) BUT:

How do I use a CUSTOM Monitor Profile with Photoshop and Wine ?
There seems to be no way to assign a monitor profile to the Wine system 
(as in Windows "control panel"), Photoshop just uses "sRGB ... 2.1" (a 
substitute for the missing monitor profile of the OS, Wine).

I tried to look for a trick to assign another monitor profile to 
Photoshop, but Photoshop will only take a profile of the OS.
That's a pity, because generating an accurate monitor profile under 
Linux (with an Eye-One spectrometer and Argyllcms) would be possible.

Am I wrong - is there a workaround for assigning the monitor profile to 
Photoshop?"

http://msdn2.microsoft.com/en-us/library/ms797852.aspx
describes monitor profiles, and says they're enabled by
calling a gdi32 function like SetICMMode().  Wine's 
implementation of that function is currently a no-op.

Also, it looks like Photoshop installs a control panel, Adobe Gamma.cpl,
see http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=321608
It's possible he's looking for that, and not finding it because
we don't have any sort of a GUI to locate control panel applets yet.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Jeff Zaroyko  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Jeff Zaroyko   2008-02-10 02:14:40 ---
(In reply to comment #0)
> Also, it looks like Photoshop installs a control panel, Adobe Gamma.cpl,
> see http://www.adobe.com/cfusion/knowledgebase/index.cfm?id=321608
> It's possible he's looking for that, and not finding it because
> we don't have any sort of a GUI to locate control panel applets yet.

running wine control should show the Adobe Gamma control panel app, it might
have to be in windows/system32 though.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #2 from Dan Kegel   2008-02-10 02:23:50 ---
Even if that control panel runs, I don't think Wine actually
uses the color profiles in gdi32 like it's supposed to...

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #3 from Dmitry Timoshkov   2008-02-10 07:06:49 ---
(In reply to comment #2)
> Even if that control panel runs, I don't think Wine actually
> uses the color profiles in gdi32 like it's supposed to...

I believe that Photoshop doesn't rely on GDI support for monitor profiles
but uses builtin support instead.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Hans Leidekker  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #4 from Hans Leidekker   2008-02-10 09:54:33 ---
Dmitry is right, Photoshop has its own color engine which is enabled by
default, but you can make it use Windows ICM (mscms.dll) too. Shift+Ctrl+k
brings up the the dialog and ticking 'Advanded' shows the relevant dropdown.

It shouldn't matter for this problem however, Photoshop queries the monitor
profile and uses that, irrespective of the engine in use. On windows you
can select a monitor profile if you right click on the desktop -> Properties
-> Settings tab -> Advanced -> Color Management tab and pick a profile.

Looks like Windows stores the association in this registry key:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\ICM\mntr, which we
could use to override the hardcoded sRGB profile we currently return.

This leaves the configuration issue, unless regedit counts as a UI. Ideal
would be if we could fall back to querying X for the monitor profile when
this key is missing (and rely on native tools to configure it). As a last
resort we should return sRGB since Windows uses that as default monitor
profile.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Roland  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #5 from Roland   2008-02-11 12:12:32 ---
Thank you very much for replying that soon.
I think that the approach of Hans Leidekker is very promising.

The only problem is that Photoshop is not able to pick its own monitor profile.
The color management is done in Photoshop alone, but the monitor profile is
chosen from the settings (wherever) of the OS (WINE).

I used the "AdobeGamma" Control Panel to generate a new profile. There is an
output to System32/Colors and to Wine's "system.reg" (the entry for "Monitor
Profile" channges to the new profile by Adobe Gamma). Unfortunately this entry
of Adobe Gamma has no effect on Photoshop which sticks to sRGB as monitor
profile.

The same procedure in Windows XP does change the profile in Control Panels
"desk.cpl" (and the registry..) and Photoshop takes the new profile.

Remark: Adobe Gamma is only a test, I would prefer to calibrate the monitor
with a photo spectrometer as Eye-one.

I hope there will be a way of "colaboration" of wine and Photoshop (I don't
think Adobe will change something to make it work better under Linux - but it
is the best image editor, as far as I know).

Thanks a lot for your help!

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #6 from Hans Leidekker   2008-02-11 15:06:45 ---
Hi Roland, can you please give step-by-step instructions for the test
you described that succeeds on Windows but fails on Wine?

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #7 from Roland   2008-02-12 12:57:34 ---
Hi Hans,

there is what I tested on Wine0.9.15/SUSE9.1:

Adobe Photoshop CS, installed on a naked Wine "drive_c" (no other dependancies,
no other programs installed)
(By the way, when Photoshop CS starts up, you will have to hit the ENTER key
while Photoshop says "initialising suites", because there is a hidden error
message about missing fonts - I don't care about that)

I did test two ways to assign a monitor profile to Wine:

First: I changed the line "Monitor Profile" in the system.reg replacing "Adobe
Monitor Settings.icm" to the profile I wanted Photoshop to pick (another
profile in the folder "...\system32\Color". After "wine boot" Photoshop
didn't pick the new profile.

...
[Software\Adobe\Color\Monitor\Monitor0] 1202667817
"Monitor Profile"="c:\windows\system32\Color\Adobe Monitor Settings.icm"
"Primary Monitor"=dword:00000000
...

Second: I started the Adobe Gamma Control Panel

wine control "/home/nils/.wine/drive_c/Programme/Gemeinsame
Dateien/Adobe/Calibration/Adobe Gamma.cpl"

Choose "Wizard Mode"

This control panel behaves a bit odd, but that doesn't matter. Finally a
numerical setting of the new gamma has been stored successfully in a profile
with a new "description" "Gamma Corrected" (Photoshop only displays the
description in the profile list) and a new file name ("sRGB Gamma
corrected.icm"). I tested the new profile with lcms profiler "lprof" which runs
natively linux and also with wine. The profile had been changed apparently.

(After "wine boot") I had a look in system.reg:

...
[Software\Adobe\Color\Monitor\Monitor0] 1202667817
"Monitor Profile"="c:\windows\system32\Color\sRGB Gamma corrected.icm"
"Primary Monitor"=dword:00000000
...

The new profile was there - but after starting Photoshop: NO CHANGE of the
monitor profile. Nevertheless I could see the new profile in the list for the
color workspace ("Gamma Corrected"), but that doesn't help Photoshop to pick
the monitor profile.

IN WINDOWS XP:

First way to choose monitor profile:
Just start the desk.cpl in the Control Panel Settings, or by "Right Click" o
the Desktop. There you can choose the desired monitor profile in the monitor
preferences.

Second way: 
Start Adobe-Gamma.cpl in the Control Panel Settings and do the same settings as
in Wine. There will be a new profile in the Systems...Color folder and:
Checking the desk.cpl monitor preferences shows the new monitor profile set
(and certainly the registry is changed - I didn't check that).
After a new start Photoshop will have picked the new profile as monitor
profile.

Oops that is a lot of text. I will be on a trip until Friday, so I hope I gave
you all the info needed.

Have a nice week
Roland

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Lars Tore Gustavsen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #8 from Lars Tore Gustavsen   2008-02-19 14:25:31 ---
Hello everybody

I have just tested this on one of my computers. I normally have a color managed
workflow with other tools but it was interesting to test the photoshop beast. I
also have a spectrometer and a few colorimeters so I have my own monitor
profiles. I tried the above adobe gamma route, but I also give up.

Instead the most obvious way was off course to replace the  sRGB\ Color\ Space\
Profile.icm  in ~/.wine/drive_c/windows/system32/spool/drivers/color/  with my
monitorprofile. And copy the srgb profile to a new name
cp sRGB\ Color\ Space\ Profile.icm 
/.wine/drive_c/windows/system32/spool/drivers/color/new-srgb.icc

In photoshop color settings,  can I now read in the drop down boxes for RGB
colorspace:
Monitor-RGB-mymonitor.icc
In the same dialog I set the working space to other than my monitor profile And
since the dialog display the internal name of the profile the sRGB IEC61966-2.1
name is actually picked up from the new-srgb.icc file from above copy command,
and it is safe to use as a workingspace.

My display profiles description is in this case the file original file name.
When I load an image they are nicely viewed with my monitor profile. I must as
an addition load the lut table by hand with tools like dispwin.

I would suggest for future that wine read the xicc atom like gimp and others.
Se 
http://www.burtonini.com/computing/x-icc-profiles-spec-0.2.html
The openicc mailing list is a very nice place for discussion about that kind of
questions. I would suggest that some of the wine developers join that list.

This was tested with cs2 in tryout mode on ubuntu 7.10.

Regards
Lars Tore Gustavsen

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #9 from Dan Kegel   2008-02-19 15:28:00 ---
I hadn't heard of openicc or the xicc atom.
Thanks for the excellent suggestion.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #10 from Hans Leidekker   2008-02-20 03:01:53 ---
> Instead the most obvious way was off course to replace the
> sRGB\ Color\ Space\ Profile.icm in
> ~/.wine/drive_c/windows/system32/spool/drivers/color/
> with my monitorprofile.

Yes, that's a workaround. When you change the monitor profile Photoshop
calls mscms.AssociateColorProfileWithDevice which is a stub in Wine.

I have a hunch that this function manipulates the registry key mentioned
in comment #4 but I need to verify that. When this is implemented we
can make gdi32.GetICMProfile smarter by checking this key and your
workaround should not be needed anymore.
> I would suggest for future that wine read the xicc atom like gimp
> and others.

Yes, this is what I alluded to in comment #4. We should fall back to
querying X for the monitor profile when this key is missing and rely on
native tools to configure it.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #11 from Lars Tore Gustavsen   2008-02-20 14:01:59 ---
I guess dispwin http://www.argyllcms.com/doc8/dispwin.html is the most advanced
utility to set the x11 icc atom, since it support multiple monitors. I would be
a nice challenge for wine and photoshop to handle multiple monitor profiles.

A even better solution in the long term may be to implement oyranos, since it
will give us a way to set all color management policys globally.  With the
correct pathways it should even be possible to set up the color policy's in
wine photoshop and  native programs adjust after that and vice versa. 
There where a lot of discussion about oyranos on the openicc maling list
recently. 
http://www.google.com/search?q=oyranos+site:lists.freedesktop.org/archives/o...
If we could get google interested in oyranos like in photoshop, it would be a
very good thing, else I guess it's a few years ahead.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #12 from Roland   2008-02-21 13:09:30 ---
Hello Lars,

your workaround comment #8 really seems easy and would solve my problem - only
it doesn't work on my system.

Please check if there is something I miss:

I do run Suse 9.1 and Wine 0.9.51 with Photoshop CS Trial (no problems).
Before installing Photoshop I deleted the $HOME/.wine folder - so there is no
other application installed.

Photoshop does create a ..system32/Color folder with its own icc/icm profiles.
There I replace the "sRGB Color Space Profile.icm" by a profile I created for
demonstration purposes (very low gamma 0.8, name "sRGB dark").

After restarting wine and photoshop there is NO change in the monitor profile.
It is still set on "sRGB IEC61966-2.1", but my modified "sRGB Color Space
Profile.icm" does appear in the RGB work space list as "sRGB dark".

So Photoshop recognizes the new profile but nevertheless sticks to its default
monitor profile "sRGB IEC61966-2.1".
I also made the experience that deleting all standard profiles in the
..system32/Color folder doesn't affect Photoshop. It still offers all profiles
"sRGB IEC61966-2.1" / AdobeRGB / AppleRGB / Color Match RGB in the work spaces
list !! Seems the profiles are "built in" the Photoshop program code.

Thus the monitor profile would NOT be picked in the ..system32/Color folder.

Why then does it work on your system? I also checked a tryout of Photoshop CS2
(which also runs well) and no success with the monitor profile.

Thanks for any advice!
Roland

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #13 from Lars Tore Gustavsen   2008-02-21 16:28:20 ---
Hello Roland
I am no expert at wine at all, but there are two things I will remark.

1. Your wine version is 0.9.51. The wiki http://wiki.winehq.org/AdobePhotoshop
suggest 0.9.54 and above.

2. The path to the color folder inside wine. I created a
windows/system32/spool/drivers/color/ and not a 
windows/system32/color directory, so that can be the reason. I guess Mr
Leidekker   can teach us more about color folders in windows. I wonder why the
color folder are not created by wineprefix.

I have written down my way to this in a txt note here. 
http://ltgustavsen.googlepages.com/install-pscs2-note.txt 
It nothing new there, but I like to document for myself who I did it. Remark
the use of wineprefix. I don't like to break my normal .wine tree just to test
a program in 30 days.

And here is a screenshoot with a somewhat contrasty monitor profile.
Photoshop left and cinepaint right.
http://ltgustavsen.googlepages.com/photoshop-monitor-profile.png
The images with my monitor profile are pretty close, but there are some
differences. I guess the differences are related to different color engines and
rendering intent. I tried to use the mscsm engine in photoshop, to see if I was
closer, but then photoshop crashed.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #14 from Hans Leidekker   2008-02-22 02:48:05 ---
> - The path to the color folder inside wine. I created a
>
> windows/system32/spool/drivers/color/ and not a 
> windows/system32/color directory, so that can be the reason. I guess Mr
> Leidekker can teach us more about color folders in windows.

windows/system32/color is from the Windows 9x days,
windows/system32/spool/drivers/color is where NT and Wine store
color profiles.
> I wonder why the color folder are not created by wineprefix.

Good point. Eventually Wine should create the color directory and
perhaps bundle a set of freely distributable color profiles, or make it
easy for distributors to do so.
> I tried to use the mscsm engine in photoshop, to see if I was
> closer, but then photoshop crashed.

I'm working on it.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #15 from Hans Leidekker   2008-02-22 09:23:09 ---
I have sent a couple of patches that fix the original issue reported by
Roland Geflitter.

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #16 from Roland   2008-02-22 11:42:53 ---
Thank you for your great help Lars and Hans !

now it does work, this is one more reason to stick to linux.

What I did change:

installed new release Wine 0.9.55
moved profiles in folder
$HOME/.wine/drive_c/windows/system32/spool/drivers/color/

(My Wine is set on Win2000, but Photoshop created and installed all profiles in
$HOME/.wine/drive_c/windows/system32/Color/). As the other folder didn't exist,
I was genuine enough to think everything's alright.

Adobe Gamma does not really profile the monitor but could be better than
nothing. Now also this works:

wine control "$HOME/.wine/drive_c/Programme/Gemeinsame
Dateien/Adobe/Calibration/Adobe Gamma.cpl"

Only while adjusting the Gamma value (I have to do that numerically) Adobe
Gamma changes the Gamma of the entire Desktop (this doesn't happen in Windows)!
At the end I save the new profile overwriting "sRGB Color Space Profile.icm" -
it will be used by Photoshop then.

After finishing Adobe Gamma the Desktop keeps the changed Gamma so when using
Photoshop with the new monitor profile, the Gamma would be applied twice.

Rebooting solves that, but the Monitor Gamma can also be reset by starting
"Adobe Gamma" once more and setting the old Gamma Value there. When you shut
down "Adobe Gamma" by closing the console at this stage - the old Gamma is back
(don't close the applet window itself).

The progress of wine is really impressive. I already thought about using
windows again because I want to use a real 16bit Photoshop (in PS6 and PS7
working with layers and masks is only possible with 8bit).

Cheers and thanks again
Roland

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #17 from Lars Tore Gustavsen   2008-02-22 14:43:01 ---
> > me
> > I wonder why the color folder are not created by wineprefix.
>
> Hans Leidekker  
> Good point. Eventually Wine should create the color directory and
> perhaps bundle a set of freely distributable color profiles, or make it
> easy for distributors to do so.

Just create the folder will be a big improvement. Some software expect it. I
have used Picture Window Pro with wine for years, and the only missing step
now, for out of the box functionality is the color folder.  With that in place
picture window are fully color managed.
Some profiles would of course be nice, but I don't think that so important.

And Roland, you should really consider at least a colorimeter instead of the
adobe gamma toy.
There are support for many devices this days under linux and the software
(argyllcms or lprof) are good.
http://www.argyllcms.com/doc8/instruments.html

[Bug 11532] Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #18 from Hans Leidekker   2008-02-22 16:18:01 ---
> Just create the folder will be a big improvement. Some software expect it. I
> have used Picture Window Pro with wine for years, and the only missing step
> now, for out of the box functionality is the color folder.

Sure, why not create a bug for it?

(Picture Window Pro is great, I used it when I wrote mscms because it allows
you to choose between lcms and mscms, and since I wrote mscms on top of lcms
my mistakes were immediately clear ;-)

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Photoshop doesn't support   |Adobe Photoshop doesn't
                   |custom monitor profiles     |support custom monitor
                   |                            |profiles

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #19 from Hans Leidekker   2008-02-25 08:18:30 ---
Patches are in git, please verify that this bug is fixed.

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #20 from Roland   2008-02-26 03:12:33 ---
Hi Lars and Hans,

I would like to use a Spider2 with ArgyllCMS. I also read that in the future
the Lprof GUI will also support hardware devices.
(I didn't plan to work with Adobe Gamma, Lprof has a much nicer and bigger Grey
Patch for adjusting the Monitor Gamma and also saves it to a profile).

What about using monitor profiles made in Windows XP (on a dual boot system,
same hardware but different drivers). 
I read that the embedded LUT-table (vcgt tag) of the monitor profile can be
uploaded to "X" with xcalib or argyll. The same profile would be applied to
Photoshop by replacing the "sRGB Color Space.icm" in the
../spool/drivers/color/ folder.

Should I expect a visible difference because of the other OS and video driver?
Or is using the same LUT correction the most important thing?

Thank you for any advice - anyway I'll have to test that on my own as soon
there is time for it.

Cheers
Roland

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #21 from Hans Leidekker   2008-02-26 03:49:58 ---
> I read that the embedded LUT-table (vcgt tag) of the monitor profile can be
> uploaded to "X" with xcalib or argyll. The same profile would be applied to
> Photoshop by replacing the "sRGB Color Space.icm" in the
> ../spool/drivers/color/ folder.

Replacing the sRGB profile should not be needed anymore. When Wine is able to
use the X monitor profile configured with native tools (xicc, xcalib, argyll
or some Gnome/KDE dialog) you shouldn't need to configure the monitor profile
in Photoshop anymore either.
> Should I expect a visible difference because of the other OS and video
> driver?

No, this is what color management is about of course, if you do see
differences it might be a bug and we would like to know about it. But please,
let's not turn bugzilla into a forum and keep this bug focused on the issue
of custom monitor profiles, okay?

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #22 from Lars Tore Gustavsen   2008-02-26 14:22:12 ---
(In reply to comment #21)
> Replacing the sRGB profile should not be needed anymore. When Wine is able to
> use the X monitor profile configured with native tools (xicc, xcalib, argyll
> or some Gnome/KDE dialog) you shouldn't need to configure the monitor profile
> in Photoshop anymore either.

I'm testing with a git checkout from today, and I wonder what method other than
sRGB replace method that actually works. I have tried to create a
[Software\Adobe\Color\Monitor\Monitor0] entry with path to my profile but
no go. 
The sRGB replace works still as expected.

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #23 from Hans Leidekker   2008-02-29 06:12:55 ---
It should really be fixed now. I overlooked one patch in my queue which has
been committed yesterday.

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #24 from Lars Tore Gustavsen   2008-02-29 11:42:35 ---
Created an attachment (id=11041)
 --> (http://bugs.winehq.org/attachment.cgi?id=11041)
Loading lut

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #25 from Lars Tore Gustavsen   2008-02-29 11:45:50 ---
Sorry but the attachment is above.

Thanks. I think there still is some problems. I have used a git checkout from
today.
I have added the key
[Software\Microsoft\Windows NT\CurrentVersion\ICM\mntr] 1204305088
@="c:\windows\system32\spool\drivers\color\my.icm"
to system.reg.
and placed that file in that folder.
When I do a wineboot the vcgt tag from my profile is loaded, so I guess I'm
close.
See above attached log.

But Photoshop still use the srgb profile for the color rendering, and it is
named "sRGB IEC61966-2.1.. in the RGB dropdown box.

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

--- Comment #26 from Hans Leidekker   2008-02-29 12:52:10 ---
This is the procedure I followed to verify my patches:

1. Remove all values below these keys:
[Software\Adobe\Color\Monitor\Monitor0]
[Software\Microsoft\Windows NT\CurrentVersion\ICM\mntr]

2. Start the gamma control:
$ wine control Adobe\ Gamma.cpl

3. Load your profile and save it, without changing any settings if you like.

4. Load the gamma control again and should have remembered your choice.
Or fire up Photoshop and type Shift+Ctrl+k, select 'Monitor Color' in the
setting dropdown it should show your profile.

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Hans Leidekker  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #27 from Hans Leidekker   2008-03-05 15:00:42 ---
Marking fixed.

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #28 from Alexandre Julliard   2008-03-07 11:28:40 ---
Closing bugs fixed in 0.9.57.

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|CVS/GIT                     |unspecified

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

http://bugs.winehq.org/show_bug.cgi?id=11532

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
      Fixed by SHA1|                            |d284fd972f825f704a8bed77d70
                   |                            |13e0a0e6bdcca
                 CC|                            |[e-mail]
          Component|gdi32                       |-unknown
            Version|unspecified                 |0.9.51.

[Bug 11532] Adobe Photoshop doesn't support custom monitor profiles

https://bugs.winehq.org/show_bug.cgi?id=11532

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|-unknown                    |mscms
           Hardware|Other                       |x86
                 OS|other                       |Linux