Linux ChromeBox Kodi E-Z Setup Script (LibreELEC/Linux+Kodi) [2017/02/21]
i'd been following the haswell nuc thread for a while before finding out 2955u in the chromebox was a haswell chip and getting that instead. lmyllari did a lot of testing and bug squashing and i believe the same information should apply. that being:
(2013-12-05, 02:17)lmyllari Wrote: The banding comes from expanding luma from 16-235 to 0-255. This is done for typical PC monitors, which expect a full range signal. New Intel linux drivers by default give TVs a limited range signal, taking the expanded 0-255 and scaling it to 16-235. This does not eliminate the banding that was created by the original expansion, and original information below 16 and above 235 was already lost in that same step. (Why do they do it? It's the right thing according to the standards, and some TVs don't like full range -> crushed blacks.)

If the player software (xbmc in this case) decodes to 16-235 (meaning "don't change luminance, keep black at 16 and white at 235"), the video card outputs full range 0-255 (meaning "don't scale the levels, just output what you're given"), and display is set to limited range input (meaning "16 is black, 235 white"), we eliminate the banding in greyscale ramp (because the range is not scaled at any point) and keep blacker-than-black (luma values under 16) and white-than-white (luma values above 235).

If your plasma defaults to limited range RGB (and doesn't listen to the infoframes in the HDMI stream) or you can set limited range manually, you don't need anything special. Just set your player software to 16-235 (which you can now do with Gotham and software decoding) and make sure the video card doesn't change the signal (the xrandr broadcast range "Full" setting mentioned a lot in this thread). In my case, the monitor obeys the infoframes (and there are other devices connected to the same input preventing a manual setting), so I need a patch to switch it to limited range without altering the video signal.

so for my vt50 setting the range to full with the autostart script and then using the 16-235 setting within xbmc gives proper black and colors.

avsforum has a good set of calibration media you can use within xbmc here:
http://www.avsforum.com/forum/139-displa...ation.html
Reply


Messages In This Thread
RE: Asus ChromeBox EZ Setup (OpenELEC or Ubuntu+XMBC) [v2.13 - 2014/07/09] - by furii - 2014-07-10, 00:31
Chromebox and Qwerty Air Mouse - by rahjer - 2014-08-13, 04:51
Wake from suspend K400 - by dontknowhow - 2014-08-20, 16:05
DisplayPort - by Charles R - 2014-08-29, 21:33
HP Chromebox 4Gb - by P3ws - 2014-09-20, 08:51
BIOS update fails - by gkingsmill - 2014-10-17, 12:05
Great Expierience - by pmpartners - 2014-12-06, 16:00
3D support (auto swtich) - by zaldwaik - 2014-12-23, 07:27
High Idle CPU - by ToBeFrank - 2015-02-28, 03:29
HELP!!! - by code_19 - 2015-03-22, 04:49
R3.15 - 2015/03/19] - by nickr - 2015-03-25, 20:55
Skipping Frames - by busta.rhymes - 2015-07-29, 15:40
External disks not sleeping... - by sixburgh - 2015-10-14, 22:02
ChromeBOX2 success in dualboot - by fishypops - 2015-11-08, 19:05
Confirm Bricked Chromebox - by Bogustime - 2016-03-20, 19:24
(LibreELEC Bluetooth not working - by jerndl - 2017-01-06, 18:20
New Audio Problem - by Pajoe - 2019-01-19, 01:20
RE: New Audio Problem - by Matt Devo - 2019-01-19, 11:13
Powering on with TV turned off - by robca - 2021-07-18, 21:20
RE: Powering on with TV turned off - by robca - 2021-07-21, 19:10
Logout Mark Read Team Forum Stats Members Help
ChromeBox Kodi E-Z Setup Script (LibreELEC/Linux+Kodi) [2017/02/21]37