On 25.10.2011 20:57, Maarten Lankhorst wrote:
On 10/25/2011 08:00 PM, Younes Manton wrote:
On Tue, Oct 25, 2011 at 1:35 PM, Maarten Lankhorst
wrote:
Is there a reason not to use/add to the code in vl_csc.c in this case?
It supports 601 and 709, wider gamut, and and it takes procamp into
On 10/25/2011 08:00 PM, Younes Manton wrote:
> On Tue, Oct 25, 2011 at 1:35 PM, Maarten Lankhorst
> wrote:
>>
> Is there a reason not to use/add to the code in vl_csc.c in this case?
> It supports 601 and 709, wider gamut, and and it takes procamp into
> account. It calculates a 4x4 matrix, b
On Tue, Oct 25, 2011 at 1:35 PM, Maarten Lankhorst
wrote:
> Signed-off-by: Maarten Lankhorst
> ---
>
> diff --git a/src/gallium/state_trackers/vdpau/mixer.c
> b/src/gallium/state_trackers/vdpau/mixer.c
> index 8728157..83daddf 100644
> --- a/src/gallium/state_trackers/vdpau/mixer.c
> +++ b/src/g
Signed-off-by: Maarten Lankhorst struct_version > VDP_PROCAMP_VERSION)
+ return VDP_STATUS_INVALID_STRUCT_VERSION;
+
+ switch (standard) {
+ case VDP_COLOR_STANDARD_ITUR_BT_601: Kry = 0.299; Kby = .114; break;
+ case VDP_COLOR_STANDARD_ITUR_BT_709: Kry = 0.2126; Kby = .0722; break;