From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 83226] Allow use of ColorRange and ColorSpace in xorg.conf.d
files
Date: Tue, 24 Feb 2015 12:23:45 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0126674250=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 1B1E66E429
for ; Tue, 24 Feb 2015 04:23:45 -0800 (PST)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0126674250==
Content-Type: multipart/alternative; boundary="1424780625.DD14222.29861"; charset="UTF-8"
--1424780625.DD14222.29861
Date: Tue, 24 Feb 2015 12:23:45 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
https://bugs.freedesktop.org/show_bug.cgi?id=3D83226
--- Comment #14 from Andy Furniss ---
(In reply to Peter Fr=C3=BChberger from comment #11)
> @AndyFurniss: Use some test patterns, like:
> https://dl.dropboxusercontent.com/u/55728161/fullrgb-video.mp4 or
> https://dl.dropboxusercontent.com/u/55728161/graustufen-rgb-0-bis-10_1724=
35.
> png or https://dl.dropboxusercontent.com/u/55728161/fullrgb_test.jpg
Thanks, it's always nice to have more tests - I was already using ones I got
via you(r forum) + the original W6RZ with player set to not stretch.
I have wondered in the past why anyone needs limited range from an HTPC POV=
. I
am sure there must be a reason, but as it seems that intel (from memory - w=
as
really testing something else) and now AMD are scaling I can't think why, g=
iven
the specs don't really seem to require a scale.
It seems with a 2010 Panasonic plasma I am not going to be able to test ful=
ly
as it looks like it doesn't advertise the right things (If the function
actually got called I would have forced it to see). I guess the tv thinks i=
t's
getting limited anyway (but still displays 0-255). Added complication being=
it
has many modes and lots of settings within each, so maybe in eg. game it
expects different from others.
I usually run it in thx and it looks good for real vid, but not so good for=
a
ramp - game is better for a ramp - I can tell that tvrgb scales using that.
>>From previous testing I know that it subsamples every mode to 422 yuv.
I wonder if TVs that do accept the full/limited info frame tweak their faux
EOTF gamma curves or something.
Whatever, for me it seems using passthrough will be best - if I use limited=
I
would have to stretch the vid to 0-255 then it would get scaled back and I
would have to set TV by eye - I guess I could avoid yuv - rgb stretch and s=
etup
round that but it still gets scaled.
Using passthrough I can stretch/not stretch as I wish and with the latter I
don't get any scale - I can set black level in TV so 16 is "right" and get =
to
see highlights in the vid rather than have them clipped/scaled.
--=20
You are receiving this mail because:
You are the assignee for the bug.
--1424780625.DD14222.29861
Date: Tue, 24 Feb 2015 12:23:45 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Commen=
t # 14
on bug 83226<=
/a>
from Andy Furniss
(In reply to Peter Fr=C3=BChberger from comment #11)
> @AndyFurniss: Use some test patterns, like:
> https://dl.dropboxusercontent.com/u/55728161/fullrgb-video.mp4 or
> https://dl.dropboxusercontent.com/u/55728161/graustufen-r=
gb-0-bis-10_172435.
> png or https://dl.dropboxusercontent.com/u/55728161/fullrgb_test.jpg
Thanks, it's always nice to have more tests - I was already using ones I got
via you(r forum) + the original W6RZ with player set to not stretch.
I have wondered in the past why anyone needs limited range from an HTPC POV=
. I
am sure there must be a reason, but as it seems that intel (from memory - w=
as
really testing something else) and now AMD are scaling I can't think why, g=
iven
the specs don't really seem to require a scale.
It seems with a 2010 Panasonic plasma I am not going to be able to test ful=
ly
as it looks like it doesn't advertise the right things (If the function
actually got called I would have forced it to see). I guess the tv thinks i=
t's
getting limited anyway (but still displays 0-255). Added complication being=
it
has many modes and lots of settings within each, so maybe in eg. game it
expects different from others.
I usually run it in thx and it looks good for real vid, but not so good for=
a
ramp - game is better for a ramp - I can tell that tvrgb scales using that.
>>From previous testing I know that it subsamples every mode to 422 yuv.
I wonder if TVs that do accept the full/limited info frame tweak their faux
EOTF gamma curves or something.
Whatever, for me it seems using passthrough will be best - if I use limited=
I
would have to stretch the vid to 0-255 then it would get scaled back and I
would have to set TV by eye - I guess I could avoid yuv - rgb stretch and s=
etup
round that but it still gets scaled.
Using passthrough I can stretch/not stretch as I wish and with the latter I
don't get any scale - I can set black level in TV so 16 is "right"=
; and get to
see highlights in the vid rather than have them clipped/scaled.
You are receiving this mail because:
=20=20=20=20=20=20
- You are the assignee for the bug.
--1424780625.DD14222.29861--
--===============0126674250==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0
cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK
--===============0126674250==--