2016-11-05, 18:05
(2016-11-04, 05:46)Matt Devo Wrote: can you provide more detail about what input signal the KS8000 is getting such that it determines it to be a "PC" input vs another type? If it's an issue with the color space, that should be able to be resolved by changing the driver mode via an xrandr command in an autostart.sh script. If you can, fire up an ssh session to your Chromebox, and run 'xrandr --props' and see what the Broadcast RGB setting is. The default is automatic; you can try setting it via ssh to Limited 16:235 via 'xrandr --output HDMI1 --set "Broadcast RGB" "Limited 16:235"' (alternately, try the "Video 16:235 pass-through" option)
I dont know why or how the KS8000 determines the input to be "PC", its like its too damn smart for its own good. This is the 1st time I ever splurged for a high end model TV & this issue is honestly the biggest pain in the butt since I have to spend 5 mins every time I want to watch TV to get it showing properly (the wife hates it). The whole issue with it being labeled as "PC" is you are limited to 2 picture modes & cannot use "Movie" which is what you want for color accuracy. I have the JU71000 2015 Samsung model & never had an issue once with it relabeling inputs on me. Im guessing its related to the KS8000 firmware & Chromebox. I just removed the AV receiver from the chain & went straight from Chromebox to KS8000, issue still persist. Tested powering on the TV 1st, Chromebox 2nd, vice versa, makes no difference. When both the TV & Chromebox are off & then powered on, the TV relabels the input as "PC" every time. Ive scoured through the all the TV menus for any setting that could be related, nothing I can find.
I ran the commands & it was set to "Automatic". I was able to change the Broadcast RGB modes as u suggested, but they don't stick on reboot. So I am unable to confirm if forcing them prevents the TV from re-detecting the input as "PC" When I reboot, it returns to automatic. Im willing to do anymore testing on the issue you may have, thanks for spending time on looking for a fix!
xrandr --props output
