[Openicc] Minimal X Color Management
Kai-Uwe Behrmann
ku.b at gmx.de
Fri Feb 17 10:36:07 PST 2012
Am 17.02.12, 09:52 -0700 schrieb Chris Murphy:
> It sure would be nice to sit down with a wayland/xorg developer and see if they really understand the color problem at all. In my experience, most people, including developers, simply are not aware of such differences. When explained, they're relatively unsurprised by the effect of different materials and gamuts, but when they see a web browser that contains products for sale on two different displays, then they really start to understand that this is not just a problem for "color critical" people.
The conversation was serious and the scheme shows real interesst.
Here are some more sentences:
http://www.oyranos.org/2012/02/x-color-management-0-4-draft1/
> I might be wrong, but I seriously think that the problem is simply not well understood or experienced. If it were, I'd like to believe this would be better prioritized. I also don't think the industry as a whole understands how display technologies are diverging from sRGB, after a decade of converging (or attempting to converge) on it.
The perception that we colour people are a vocal but minor group is pretty
common. Many people forget about, that colour matter to almost all people
even the disabled for better accessibility. So, we can put our voice for
them, which makes sense to me. Colour management is a concept with its set
of tools for many different groups.
> It may also be that I don't understand something about how much can even be done about this problem, because of unreliable EDID information. The vast majority of the market is not going to measure their displays. And the display manufacturers appear to regularly insert theoretical aimpoint primaries into EDID, rather than actual primary xy values based on some pre-manufacturing sampling...
>
> And of course the primaries can change, in some cases not insubstantially, between batches (batches 1-10 might be reasonably consistent, but then suddenly there's a supply side change and batches 11-13 are quite different), yet EDID primary information is not updated to account for this. There's just not really an incentive for manufacturers to do this.
We speculate the EDID alone provides in most cases a advantage over the
sRGB assumtion. The last percents have to be found otherwise. Taxi
ICC DB can certainly improve over EDID.
> Since the display's color behavior isn't really well known, it can't really be well compensated for. So it's an interesting dilemma. With mobile, there are in some ways fewer excuses since an arbitrary 3rd party isn't the supplier of the display. But the time frame to production and production itself is much shorter so that can cause more problems and difficulties with keeping EDID up to date.
It would be cool so see colorimeter costs as low as the cheaper
colour targets.
> Chris
kind regards
Kai-Uwe
> On Feb 17, 2012, at 5:09 AM, Kai-Uwe Behrmann wrote:
>> We had recently a long discussion on the wayland IRC channel about colour management inside wayland. The standard answere is not different to that from Xorg. Colour management will not be part of the core protocol.
More information about the openicc
mailing list