[voip-ninja]

XBMC's limited range setting 16-235 can ONLY work if graphics is set to full range (and AVR passes the signal through)

@lmyllari is correct, the setting does not make much sense with VAApi rendering because we can't influence YUV-RGB conversion done inside VAAPI.

Some AVRs convert full range to limited and you can do anything about it. In this case leave gfx to default which is limited and set TV to limited as well.

So I've been doing some testing, and what I'm seeing is this;

I'm using Greyscale-Steps.mp4 to test this, just to see if BTB and WTW is visible;

With SW decode, RGB set to "full" and 16-235 set in XBMC I see BTB and WTW in the test pattern, the image looks as close as I've seen to the PS4... but I do have some video overscan issues going on.

With HW decode I am having a hard time getting it to look the same;

With RGB set to "full" and 16-235 turned on, I get black crush. No BTB and no WTW in test pattern.

With RGB set to "full" and 16-235 turned OFF, I get even worse black crush. No BTB and no WTW in test pattern.

With RGB set to default and 16-235 turned off, I get the closest picture to the SW decode (at least I think). No BTB and no WTW in test pattern.

With RGB set to default and 16-235 turned ON, the XBMC menus look noticeably washed out... video though is pretty close to RGB = limited and 16-235 set to off... which I guess is the default... weird.

So, at the end of the day it looks like possibly best PQ is with software decode which is kind of a bummer. Will have to tinker some more.

Also, I had never checked the color/etc video settings on the PS4. I just did, and color as well as YcBR, etc, are all set to "automatic". I haven't found a way to mount my USB stick on the PS4 so I was not able to run the same test pattern on it to check BTB and WTW.