<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB] Full/Limited Color range not working automatically for 1000/1001 CEA modes" href="https://bugs.freedesktop.org/show_bug.cgi?id=46800#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB] Full/Limited Color range not working automatically for 1000/1001 CEA modes" href="https://bugs.freedesktop.org/show_bug.cgi?id=46800">bug 46800</a> from <a class="email" href="mailto:vuanomarco@gmail.com" title="Marco Vuano <vuanomarco@gmail.com>"> Marco Vuano</a> <pre>Using limited range always create banding on non-video material (only 220 levels are used), furthermore on televisions and monitors set to accept a full range it lowers contrast. Many televisions now have a setting to accept full range RGB values over HDMI, and it is much easier to find for non-expert than using xrandr. In fact, on Windows we have the inverse problem, that is only limited range RGB values are output when using modes related to television with Intel GPUs, and I think this is a worse problem than having full range RGB values output as default (I solved the latter problem in much less time just by setting correctly my TV monitor). You can see the discussion on these two threads: <a href="http://communities.intel.com/message/156323">http://communities.intel.com/message/156323</a> Therefore, while I think that the automatic setting makes sense, I still think that the default setting should be full range, with the option on xrandr to set limited or automatic range.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>