How to get Full Range RGB from Intel HD Graphics?

[KLill2]

Has anyone found the trick to get Intel HD Graphics 3000 (on a SandyBridge 2500K) to output full range RGB to a full range capable digital television?

With my TV, it is impossible to get the iGPU to output Full range RGB. Both "Full" and "Limited" settings look the same, flat washed out. I tried connecting both directly to the TV and via the my Onkyo TX-SR605.

Then I went back to my ATI card, changed it from Full to Limited RGB, and the colors there now looked just as flat and washed out as the iGPU always outputs. My TV is a Samsung DLP 50A650.

I have also tried the various tricks found in http://www.avsforum.com/avs-vb/showthread.php?t=1351837 this thread on avsforum, incl. downgrading to driver version 2509, but nothing works.

It is strange Intel can't fix such a serious quality problem, which ATI, NVIDIA, Sonyhttp://rover.ebay.com/rover/1/711-53200-19255-0/1?toolid=10029&campid=CAMPAIGNID&customid=CUSTOMID&catId=293&type=2&ext=190673184840&item=190673184840 (PS3) and Microsofthttp://rover.ebay.com/rover/1/711-53200-19255-0/1?toolid=10029&campid=CAMPAIGNID&customid=CUSTOMID&catId=293&type=2&ext=170825419607&item=170825419607 (Xbox360) all nailed down years ago (by providing a working Full range option). I have had to use a discrete ATI card to get decent colors, while the otherwise high quality Intel GPU should be perfectly capable of providing this.

Win7 x64, latest Intel HD Graphics Driver 2696.

[JFry1]

Actually when using the madLevelsTweaker (which sets the registry change I mentioned), it does seem to work on the celeron NUC.

I think it was just needing a reboot...

madLevelsTweaker come from here: http://forum.doom9.org/showthread.php?t=146228 http://forum.doom9.org/showthread.php?t=146228

hope this helps

[dxin]

I think you missed the "CVT-RB" timing, which is specified by the "-r" parameter in the "cvt" command.

By forcing a "CVT-RB" timing, I manage to force the GPU to recognize my display as a computer monitor, instead of a flat panel TV.

But I think your <<span style="font-family: intel-neo-sans-1, intel-neo-sans-2, tahoma, helvetica, sans-serif; background-color: # ffffff;">--set "Broadcast RGB" "Full"> is a better way to go.

For more info on setting timing mode on Windows: http://www.intel.com/support/graphics/sb/cs-029478.htm Graphics — Custom Resolutions & Modes

[ARama10]

Is this issue been fixed? I am using a nuc with 3rd gen intel processor, win 8.1 connected to a jvc projector through a yamaha receiver. I need to send YCbCr signal to the projector in order to get the calibration done for best video quality.

Need to do the calibration as mentioned here

http://www.missingremote.com/guide/display-calibration-part-i Display Calibration - Part I | Missing Remote

[dxin]

I think I found a solution.

I tried this method to force HDMI to CVT-RB, and then the black level become normal, magically.

http://william.shallum.net/random-notes/linux-force-1920x1080-cvt-rb-timings-for-lg-m227-tv-monitor Linux force 1920x1080 CVT-RB timings (for LG M227 TV Monitor) - William Shallum

My environment:

Intel XEON 1245V3 with P4600 graphics.

Acer GR235H display, connected to computer via HDMI cable and HDMI to DisplayPort converter.

Ubuntu 12.10 LTS

[Allan_J_Intel1]

Thanks for joining the community and sharing the post.

Allan.

[dxin]

I want to share some of my new discoveries. Video output level is actually another issue.

1. When I set my video mode to "Limited" in the driver settings, the (16-235) in video window is the same as (0-255) on the desktop. However, neither of those levels are displayed correctly. Video is converted to (0-255), combined with the desktop, then converted back to (16-235). The blacks looks the same but equally gray.

2. Set video mode to "Full", the black in (16-235) video window is kept as (16-235), combined with the desktop, then converted to (16-235). Finally, the video is displayed as (30-219) and desktop as (16-235). The blacks looks both gray but the video's black grayer.

3.The pitfall is that, output level settings are applied just before the final stage: transmit to display device via HDMI port. Even though you might be able to resolve the low (0-15) and high(236-255) levels, they might still not be correctly displayed, because they are converted to (16-28) and (219-235) and you are always able to resolve (16-28) and (219-235).

4. Setting HDMI mode to YCbCr works, because YCbCr is always limited range, hence the display device and video processor agree easily and avoid all the trouble.

Conclusion:

In order for a video to be correctly displayed, you need: 1) set video mode in driver settings to limited so that (16-235) in the video data can be displayed the same as (0-255) on the desktop, and 2) make sure they are displayed correctly on your display device.

Using a resolution other than 1080p standard might works, such as customize resolutions, or, as I stated in the previous post, a CVT-RB advanced timing. I did not find a way to change timing options with the Intel drivers for Windows, so I'm not able to test it on Windows.

My environment:

Xeon E3-1245V3 with P4600 graphics

Windows 7 SP1

Driver 9.18.10.3165

[JTerr5]

The problem is 100% Intel's software. As the original post stated, Nvidia and AMD control panels let you do this instantly - there are no limits to the custom resolutions and refresh rates you can set. If you blow your monitor up, then that's on you. The fact that Intel limits this and seems to think that 60hz is perfectly fine, it's completely wrong. I get headaches and migraines from 60hz. I need minimum 100hz. I know for a fact that your standard laptop screen can run 120hz easily. I've tested it MANY times on non-optimus laptops.

So Intel is simply just screwing it's customers over. Stop buying Intel products and stop supporting this terrible company that hates their customers.