[argyllcms] Re: Compatibility with i1 (Eye One) Display Pro 3 retail and OEM?
- From: Ridouan Agarad <ridouan@xxxxxxxxx>
- To: "argyllcms@xxxxxxxxxxxxx" <argyllcms@xxxxxxxxxxxxx>
- Date: Wed, 15 Feb 2012 22:38:35 +0100
Ah, thanks for the clarification! I rather thought maybe you were
referring to slide projectors :)
BTW, do you think the CMS mangling also holds true if the input is
already in Ycc, or is this particular to RGB input only (e.g. a bluray
player or pc output preconverted to Ycc)? Insofar the HDTV doesn't do
a Ycc->RGB->Ycc conversion, but I honestly wouldn't see why that would
make sense to do on the TV's part...
Op 15 feb. 2012 om 22:23 heeft János, Tóth F. <janos666@xxxxxxxxxx>
het volgende geschreven:
> HDTVs convert the RGB input to YCC for internal processing and do a
> lot of messy stuff inside.
>
> It is usual for HDTVs to output a different intensity of the Red
> subpixels with R=255 B=0 G=0 than R=255 G=100 B=100 and then G=200 is
> another story, even if you keep the average picture level constant
> (it's not the blacklit dimming on LCD or the ABL on the plasma, it's
> the CMS which can't mix the colors properly).
>
> 2012/2/15 ridouan <ridouan@xxxxxxxxx>:
>> On 15-02-2012 17:00, János, Tóth F. wrote:
>>>
>>> Can the current version of ccmxmake create ccmx files from 3 patches
>>> only (R, G, B at 255)?
>>> May be this would not be a bad idea when the display is not additive
>>> (like HDTV sets).
>>>
>> Excuse me for barging in (and maybe this is something that is covered by
>> some basics), but when you say non-additive display, what do you mean/what's
>> the context, given the fact that all displays are using an additive color
>> system by definition? Thanks!
>>
>> Kind regards,
>> Ridouan.
>>
>
Other related posts:
