dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-83226-502-PS28TEQi2a@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-83226-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2218 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=83226

--- Comment #14 from Andy Furniss <adf.lists@gmail.com> ---
(In reply to Peter Frühberger 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_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 - was
really testing something else) and now AMD are scaling I can't think why, given
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 fully
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 it'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 setup
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:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3361 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-02-24 12:23 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29  7:27 [Bug 83226] New: Allow use of ColorRange and ColorSpace in xorg.conf.d files bugzilla-daemon
2015-02-21 22:54 ` [Bug 83226] " bugzilla-daemon
2015-02-22  7:10 ` bugzilla-daemon
2015-02-23 16:17 ` bugzilla-daemon
2015-02-23 16:17 ` bugzilla-daemon
2015-02-23 20:53 ` bugzilla-daemon
2015-02-23 20:56 ` bugzilla-daemon
2015-02-23 21:45 ` bugzilla-daemon
2015-02-23 22:19 ` bugzilla-daemon
2015-02-24  0:12 ` bugzilla-daemon
2015-02-24  2:32 ` bugzilla-daemon
2015-02-24  7:26 ` bugzilla-daemon
2015-02-24 10:15 ` bugzilla-daemon
2015-02-24 11:40 ` bugzilla-daemon
2015-02-24 12:23 ` bugzilla-daemon [this message]
2015-02-24 14:36 ` bugzilla-daemon
2015-02-24 22:38 ` bugzilla-daemon
2015-02-25 10:00 ` bugzilla-daemon
2015-02-25 15:04 ` bugzilla-daemon
2015-02-26 15:03 ` bugzilla-daemon
2015-02-26 15:25 ` bugzilla-daemon
2015-02-26 15:31 ` bugzilla-daemon
2015-03-27 13:08 ` bugzilla-daemon
2015-03-27 13:29 ` bugzilla-daemon
2015-05-02  3:04 ` bugzilla-daemon
2015-08-19  7:07 ` bugzilla-daemon
2015-08-19 13:32 ` bugzilla-daemon
2015-08-19 13:41 ` bugzilla-daemon
2015-08-19 15:56 ` bugzilla-daemon
2015-08-19 15:56 ` bugzilla-daemon
2015-08-19 15:56 ` bugzilla-daemon
2015-08-19 20:43 ` bugzilla-daemon
2015-08-27 11:22 ` bugzilla-daemon
2015-08-27 13:55 ` bugzilla-daemon
2015-09-03 13:32 ` bugzilla-daemon
2016-06-05 14:04 ` bugzilla-daemon
2019-09-25 17:51 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-83226-502-PS28TEQi2a@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).