<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"> <html><head><meta name="qrichtext" content="1" /><style type="text/css"> p, li { white-space: pre-wrap; } </style></head><body style=" font-family:'DejaVu Sans'; font-size:12pt; font-weight:400; font-style:normal;"> On Saturday, May 14, 2011 05:48:34 PM Chris Murphy wrote: > On May 14, 2011, at 5:25 PM, Hal V. Engel wrote: > > On Saturday, May 14, 2011 03:34:07 PM Chris Murphy wrote: > > > On May 14, 2011, at 3:03 PM, Richard Hughes wrote: > > > > On 14 May 2011 16:03, Chris Murphy <lists@colorremedies.com> wrote: > > > >> Speaking of wine, is there a passthrough from colord to wine, and > > > >> wine to apps, so that Photoshop/Lightroom are able to grab and use > > > >> the currently set display profile? > > > > > > > > I'm not sure how such a thing would work, but we probably ought to be > > > > teaching wine about the current screen profile somehow. > > > > The alternative is just to get get wine to opt into the xregion > > > > composting manager correction functionality. Other ideas welcome. > > > > > > Yes it's a small problem if we really want platform parity for such > > > apps - I think it's more compelling to allow Photoshop/Lightroom to > > > use ACE for display compensation, just as they do on Mac OS and > > > Windows, and have that pass through Wine and the compositing manager. > > > > In the past (I no longer use photoshop) I would make a copy of the screen > > profile in the normal virtual WIndows profiles directory and tell > > Photoshop to use it and ACE for the screen. Worked OK and without lose > > of functionality like soft proofing. > > > > It would be better if wine was smart enough to get the correct profile > > XAtom and handle it automatically. But setting it up manually is not a > > huge burden. > > I don't understand how this works because Photoshop doesn't have a UI for > choosing the display profile. It asks ICM "what is the display profile for > this display" and ICM forwards that info to various Adobe apps. There's no > overriding this. ICM gets it from the Displays control panel, > Advanced>Color Management tab where a profile is associated for a display > and then set as the default. That default associated profile for a display > is what ICM forwards to Photoshop, Lightroom, and a number of other apps > that have no GUI for configuring the display profile. It was a long time ago that I stopped using Photoshop so my memory is a little fuzzy on exactly how I set it up but I did have this working at one point. Since that time I have reinstalled my system several times including wine so I can't check out the installation to figure out the exact details. > > I didn't think Wine was a full VM where you see control panels and such. Wine is not a VM and does not function like one. It is possible to run the windows control panel in wine (wine control.exe) and it comes with some basic control panel applets out of the box. But wine does not have the CM control panel applet as part of the base installation. But on older versions of window (XP and older) this was not included with Windows either. So installing and running the Windows XP CM control panel applet should be possible. In addition I think all the CM control panel applets does for things like display profiles is to create registry entries so even without a working CM control panel applet it should be possible to hand edit the registry to set this up. Not very user friendly and it requires an understanding of how Windows uses the registry for CM. I wasn't claiming that it was user friendly only that it was possible. Hal</body></html>