Setting the display calibration ramps using weston

[Richard Hughes]

On 2 April 2013 12:10, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> Am 02.04.2013 11:24, schrieb Richard Hughes:
>
>> On 2 April 2013 06:45, Graeme Gill <graeme2 at argyllcms.com> wrote:
>>>
>>> The display's ICC profile will also be stored in the _ICC_PROFILE atom,
>>> to make it available to the display client, so that color can be adjusted
>>> appropriately for that display. Using XRandR it will/should
>>> also be set in an output property.
>>
>>
>> There's not going to be _ICC_PROFILE atoms in weston, nor XRandR
>> output properties,
>
>
> Yes, But that was likely meant "as in analogy to X11".
>
>
>> so clients will need to query the CMM directly
>
>
> Querying a CMM for a monitor profile is top down. Most people understand a
> CMM (Colour Matching Modul) to do context preparation [1] and colour
> conversions. The needed profiles come from custom code or a CMS (Colour
> Management System). A CMS connects to the environment by configuring ICC
> profiles for devices.
>
>
>> The grand idea is to use a sub-surface
>> with a tagged color profile, which means applications don't have to
>> care about CM unless they want to opt out a region and handle
>> everything themselves.
>
>
> agreed, it is a good thing IMO.
>
> kind regards
> Kai-Uwe
>
> [1] ICC colour transforms are most often prepared from a pair of ICC
> profiles. One exception is proofing, where a third profile is involved.