or Connect
AVS › AVS Forum › Video Components › Home Theater Computers › Theory About Intel's HDMI Quantization Range Setting (Full 0-255)
New Posts  All Forums:Forum Nav:

Theory About Intel's HDMI Quantization Range Setting (Full 0-255) - Page 6

post #151 of 186

Confirmed adding the DWORD 'EnableRGBFullRange' == "1" enabled full 0-255 RGB output over HDMI on my Intel HD 4000 using latest drivers! (had to force 0-255 input on my plasma).

Yay!

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{48E96537-42C5-4ED6-8F7A-6532C553AA26}\0000

 

(found exact location by just running the madNvLevelsTweaker).

post #152 of 186
Quote:
Originally Posted by SweetLow View Post

>Intel always outputs 16-235 over HDMI. Period. Stop. Settings matter not, Intel chooses to follow strictly the HDMI whitepaper specs for HDMI (16-235).


 
Anyone, who want FullRange RGB HDMI output on Intel Graphic may try this:
1. Find your current Intel Graphic Adapter software registry instance under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\xxxx
(0000 on my PC).
2.Create DWORD value:

EnableRGBFullRange
and set it to 1
3. Reboot.
4. Enjoy.

I can't thank you enough for this, it solved all sorts of problems on my htpc.

I built PC with i3-3225 (HD4000) on Gigabyte mobo with two HDMI outputs, I have two TV's connected over HDMI, Intel drivers decided that will output full RGB to one and limited RGB to second, which would be fine if picture is good on both, but on TV with full RGB there was strange horizontal noise in picture on certain shades of colors and red flashing on some grey shades. And this simple registry edit not only enabled full RGB on both TV's but all noise and flashing is gone. Hooray. smile.gif
post #153 of 186
Quote:
Originally Posted by madwolfa View Post
 

Confirmed adding the DWORD 'EnableRGBFullRange' == "1" enabled full 0-255 RGB output over HDMI on my Intel HD 4000 using latest drivers! (had to force 0-255 input on my plasma).

Yay!

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{48E96537-42C5-4ED6-8F7A-6532C553AA26}\0000

 

(found exact location by just running the madNvLevelsTweaker).

Hello,

 

How can you test that you are really in full RGB over HDMI ? I'm using HD5000 and I'd like to be sure that it's really enable. 

Thanks !

post #154 of 186
Quote:
Originally Posted by SweetLow View Post

>Intel always outputs 16-235 over HDMI. Period. Stop. Settings matter not, Intel chooses to follow strictly the HDMI whitepaper specs for HDMI (16-235).


>You can use DVI or Displayport output to get full range , or you can add a GPU card. Otherwise just go with 16-235 and set up everything accordingly.



 
No, it's not the true. Intel remove this functionality from UI, but it still possible.
 



Anyone, who want FullRange RGB HDMI output on Intel Graphic may try this:
1. Find your current Intel Graphic Adapter software registry instance under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E968-E325-11CE-BFC1-08002BE10318}\xxxx
(0000 on my PC).
2.Create DWORD value:

EnableRGBFullRange
and set it to 1
3. Reboot.
4. Enjoy.

I personally (discover and) test it on HD4000 mobile version with drivers from May 2013 on Windows 7 x64 + HDMI1/DVI input with "PC mode" on Samsung LE40B530 TV as HDMI Sink.

Another thing which I test - Intel drivers (current) don't accept standard MS EDID override feature, but allow the same functionality with ReadEDIDFromRegistry and FakeEDID_%d_%d_%x_%x registry keys pair.
I personally use this to switch HDMI device to DVI mode (Full RGB Range by default) by disabling CEA extension in EDID to verify equality of levels of DVI and HDMI+EnableRGBFullRange.

Can anybody test and verify my "research"? smile.gif

Awesome! You just did Intel a great favor.
post #155 of 186

 

Quote:
Originally Posted by petoulachi View Post
 

Hello,

 

How can you test that you are really in full RGB over HDMI ? I'm using HD5000 and I'd like to be sure that it's really enable. 

Thanks !

 

>SweetLow

>I personally use this to switch HDMI device to DVI mode (Full RGB Range by default) by disabling CEA extension in EDID to verify equality of levels of DVI and HDMI+EnableRGBFullRange.

;)

post #156 of 186

Unfortunatelly I can't do this, as I have a Panasonic Plasma TV with only HDMI.

 

By the way, I have noticed that if I set the registry with EnableRGBFullRange key, the Quantization is not accessible on the drivers UI. If I remove the key, then I can set up Quantization on the drivers. I've check my TV EDID, and the information about Full RGB support is there ; so the Quantization parameter works and stick after reboot or resolution change. I guess it's the best way to set up 0-255 on my case.

 

This is using haswell processor with HD5000 and the latest drivers with modern UI.

post #157 of 186
Quote:
Originally Posted by petoulachi View Post
 

Unfortunatelly I can't do this, as I have a Panasonic Plasma TV with only HDMI.

 

Every (right) HDMI device in the world CAN work in DVI mode, even "Panasonic Plasma TV".

P.S. Мy Samsung LE40B530 TV is pure HDMI device ;)

 

>Quantization parameter works and stick after reboot or resolution change

What is the version of drivers? Can you post your EDID data?  I try to make this work (as minimum try to see this control) on HD4000 by EDID overriding, but without any success.

 

post #158 of 186
Quote:
Originally Posted by SweetLow View Post
 

Every (right) HDMI device in the world CAN work in DVI mode, even "Panasonic Plasma TV".

P.S. Мy Samsung LE40B530 TV is pure HDMI device ;)

Maybe I do not understand what you say with "DVI Mode" ? I though you were talking about using a DVI cable to connect to the monitor ? Also, as I have a NUC, I only have HDMI or display port.

 

Quote:

Originally Posted by SweetLow View Post

 

>Quantization parameter works and stick after reboot or resolution change

What is the version of drivers? Can you post your EDID data?  I try to make this work (as minimum try to see this control) on HD4000 by EDID overriding, but without any success.

 

I can't do that right now, I'm not home. will do asap, but the drivers are the latest available.

post #159 of 186
Quote:
Originally Posted by petoulachi View Post
I have noticed that if I set the registry with EnableRGBFullRange key, the Quantization is not accessible on the drivers UI.

Thanks, it is a valuable notice! May be i do not disable this registry key, when i try to view Quantization control on newest drivers!? But "Quantization is not accessible" mean "not visible" or "visible, but disabled"?

post #160 of 186
Quote:
Originally Posted by SweetLow View Post
 

Thanks, it is a valuable notice! May be i do not disable this registry key, when i try to view Quantization control on newest drivers!? But "Quantization is not accessible" mean "not visible" or "visible, but disabled"?

Not visible at all ;)

post #161 of 186
Quote:
Originally Posted by petoulachi View Post
 

 

Maybe I do not understand what you say with "DVI Mode" ?

Yes. "DVI mode" is mode of function of HDMI Sink, when it is attached to pure DVI Source or pure DVI Sink attached to any Source. When HDMI Sink attached to HDMI Source - by default we will get "HDMI mode". BUT, we can lie to HDMI Source in our case (pc with intel graphics), and it will be assume that it connected to DVI Sink - without any hardware (cables, boxes), only by EDID overriding.

 

Quote:

Originally Posted by petoulachi View Post
 

 

I can't do that right now, I'm not home. will do asap, but the drivers are the latest available.

 

as you can, it is my curiosity ;)

post #162 of 186
Quote:
Originally Posted by petoulachi View Post
 

Not visible at all ;)


Very good!

post #163 of 186
Quote:
Originally Posted by Wizziwig View Post

If your display has the RGB quantization range listed as "Selectable (via AVI YQ)", please try to toggle the Intel control panel quantization range setting and see if it has any effect. Also close the control panel and check if the setting "sticks" or reverts back to "limited" when you reopen it.

 

Now, on new drivers (i test version 3345) all is working as required by HDMI specs. EnableRGBFullRange now is not need, but if your TV don't support "Selectable (via AVI YQ)" by default - ReadEDIDFromRegistry and FakeEDID is your way :)

 

Quote:
Originally Posted by petoulachi View Post

 

I have noticed that if I set the registry with EnableRGBFullRange key, the Quantization is not accessible on the drivers UI.

 

Yes, it's true, now i can confirm this ;)

post #164 of 186

Here is my TV EDID :

Monitor
  Model name............... Panasonic-TV
  Windows description...... Generic PnP Monitor Panasonic-TV
  Manufacturer............. Panasonic
  Plug and Play ID......... MEIA296
  Serial number............ n/a
  Manufacture date......... 2013, ISO week 0
  Filter driver............ None
  -------------------------
  EDID revision............ 1.3
  Input signal type........ Digital
  Color bit depth.......... Undefined
  Display type............. RGB color
  Screen size.............. 1280 x 720 mm (57,8 in)
  Power management......... Not supported
  Extension blocs.......... 1 (Unknown - 0x00)
  -------------------------
  DDC/CI................... n/a

Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2,20
  Red chromaticity......... Rx 0,640 - Ry 0,345
  Green chromaticity....... Gx 0,291 - Gy 0,635
  Blue chromaticity........ Bx 0,163 - By 0,093
  White point (default).... Wx 0,288 - Wy 0,296
  Additional descriptors... None

Timing characteristics
  Horizontal scan range.... 15-68kHz
  Vertical scan range...... 23-61Hz
  Video bandwidth.......... 150MHz
  CVT standard............. Not supported
  GTF standard............. Not supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 1920x1080p at 50Hz (16:9)
    Modeline............... "1920x1080" 148,500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
  Detailed timing #1....... 1920x1080p at 60Hz (16:9)
    Modeline............... "1920x1080" 148,500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync

Standard timings supported
     640 x  480p at  60Hz - IBM VGA
     800 x  600p at  60Hz - VESA
    1024 x  768p at  60Hz - VESA
     640 x  480p at  60Hz - VESA STD
     800 x  600p at  60Hz - VESA STD
    1024 x  768p at  60Hz - VESA STD
    1280 x 1024p at  60Hz - VESA STD

Report information
  Date generated........... 13/01/2014
  Software revision........ 2.70.0.989
  Data source.............. Registry-Active - NB: improperly installed
  Operating system......... 6.2.9200.2

Raw data
  00,FF,FF,FF,FF,FF,FF,00,34,A9,96,A2,01,01,01,01,00,17,01,03,80,80,48,78,0A,DA,FF,A3,58,4A,A2,29,
  17,49,4B,21,08,00,31,40,45,40,61,40,81,80,01,01,01,01,01,01,01,01,02,3A,80,D0,72,38,2D,40,10,2C,
  45,80,BA,88,21,00,00,1E,02,3A,80,18,71,38,2D,40,58,2C,45,00,BA,88,21,00,00,1E,00,00,00,FC,00,50,
  61,6E,61,73,6F,6E,69,63,2D,54,56,0A,00,00,00,FD,00,17,3D,0F,44,0F,00,0A,20,20,20,20,20,20,01,5B

 

 

 

So as you can see it's ok for full range RGB, so I have access to quantization settings, using drivers 10.18.10.3379

post #165 of 186
Quote:

  Data source.............. Registry-Active - NB: improperly installed

 

So as you can see it's ok for full range RGB, so I have access to quantization settings, using drivers 10.18.10.3379

 

 

It is not full EDID ;)

But if you will get full - you shall view like this:

...

CE video capability data
  CE scan behavior......... Supports overscan and underscan
  IT scan behavior......... Supports overscan and underscan
  PT scan behavior......... Not supported
  RGB quantization range... Selectable (via AVI YQ)
  YCC quantization range... Not supported

...

post #166 of 186
Quote:
Originally Posted by SweetLow View Post
 

 

 

It is not full EDID ;)

But if you will get full - you shall view like this:

...

CE video capability data
  CE scan behavior......... Supports overscan and underscan
  IT scan behavior......... Supports overscan and underscan
  PT scan behavior......... Not supported
  RGB quantization range... Selectable (via AVI YQ)
  YCC quantization range... Not supported

...

oops you're right I have copy/paste a little too fast, but normally I have the RGB Quantization range set to "Selectable (via AVI YQ)" !

post #167 of 186
Hi, I am confused about the last few posts to this thread. Are you saying now with Intel Video Drivers 10.18.10.3345 (and up) that I can now remove the "EnableFullRangeRGB" entry from my registry because there is a new Quantization option in the drivers GUI (which had been hidden because of our EnableFullRangeRGB entry)? And this quantization option gives us now full color range to our HDMI displays? What quantization option are we supposed to select to get the full range? Any light on this subject matter would be greatly appreciated :-) As of now I still have the EnableFullRangeRGB set to 1 in my registry.

Note: I have HD4000, not HD5000. And am running latest Intel drivers 15.33.8.64.3345 for Win7 64-bit as of 21 Jan 2014.

Cheers
Edited by andyxoxo - 1/20/14 at 6:46pm
post #168 of 186
Can you hack the registry to output 16-235 over DVI?

How to get EDID readings for my setup?

Im trying to my HTPC to output YCbCr 4:4:4 to match the other devices connected to my reciever.
post #169 of 186

Quote:

Originally Posted by andyxoxo View Post

Hi, I am confused about the last few posts to this thread. Are you saying now with Intel Video Drivers 10.18.10.3345 (and up) that I can now remove the "EnableFullRangeRGB" entry from my registry because there is a new Quantization option in the drivers GUI (which had been hidden because of our EnableFullRangeRGB entry)? And this quantization option gives us now full color range to our HDMI displays? What quantization option are we supposed to select to get the full range? Any light on this subject matter would be greatly appreciated :-) As of now I still have the EnableFullRangeRGB set to 1 in my registry.

Note: I have HD4000, not HD5000. And am running latest Intel drivers 15.33.8.64.3345 for Win7 64-bit as of 21 Jan 2014.

Cheers

>there is a new Quantization option in the drivers GUI (which had been hidden because of our EnableFullRangeRGB entry)?

Yes, but not at all HDMI devices. Only if device report of support of this feature (RGB quantization range... Selectable (via AVI YQ)). Intel have full and strict support of HDMI specs now (in this area, with latest drivers).

 

>And this quantization option gives us now full color range to our HDMI displays?

Yes.

 

>What quantization option are we supposed to select to get the full range?

I can't tell exact names - my system is not English locale. But this control locate at second "display" property page (! not at second "color" property page).

 

>I have HD4000, not HD5000. And am running latest Intel drivers 15.33.8.64.3345 for Win7 64-bit

It is exactly my config ;)

 

Quote:
Originally Posted by slosvt View Post

Can you hack the registry to output 16-235 over DVI?

How to get EDID readings for my setup?

Im trying to my HTPC to output YCbCr 4:4:4 to match the other devices connected to my reciever.

If you have DVI source (you HTPC is only DVI capable) - no.


Edited by SweetLow - 1/22/14 at 12:49am
post #170 of 186
Quote:
Originally Posted by SweetLow View Post

Quote:
>there is a new Quantization option in the drivers GUI (which had been hidden because of our EnableFullRangeRGB entry)?
Yes, but not at all HDMI devices. Only if device report of support of this feature (RGB quantization range... Selectable (via AVI YQ)). Intel have full and strictly support of HDMI specs now (in this area, with latest drivers).

Hi SweetLow, thanks for your clear response. One final question if I may: I went ahead and installed Monitor Asset Manager and under real-time display ID's it does list my Dell S2440L HDMI external monitor. But nowhere in the big window does it say anything about (RGB quantization range... Selectable (via AVI YQ). It doesn't say anything about any RGB quantization range under the big window for my HDMI plugged in Benq W1070 projector either. Before I go screwing around with the registry again I was just curious to your thoughts on why there is no entry for RGB quantization range on either of my 1-year old HDMI devices. Cheers
post #171 of 186
Quote:
Originally Posted by andyxoxo View Post


Hi SweetLow, thanks for your clear response. One final question if I may: I went ahead and installed Monitor Asset Manager and under real-time display ID's it does list my Dell S2440L HDMI external monitor. But nowhere in the big window does it say anything about (RGB quantization range... Selectable (via AVI YQ). It doesn't say anything about any RGB quantization range under the big window for my HDMI plugged in Benq W1070 projector either. Before I go screwing around with the registry again I was just curious to your thoughts on why there is no entry for RGB quantization range on either of my 1-year old HDMI devices. Cheers

You can test easily how it will behave. Remove the registry key and reboot, you should have Quantization options. Now Select "Full" instead of "limited", and reboot. See if it's still selected on Full".

But I guess the easiest way is simply to work with registry key !

post #172 of 186
Quote:
Originally Posted by andyxoxo View Post


Before I go screwing around with the registry again I was just curious to your thoughts on why there is no entry for RGB quantization range on either of my 1-year old HDMI devices.

It's obvious - "CE video capability data" block (which contain "RGB quantization range" field) is optional (as many other HDMI description blocks) ;)

 

>on either of my 1-year old HDMI devices

It's strange, but you can post your edid data's here (only raw 256 bytes at the end of dump) -  i can view and tell more.


Edited by SweetLow - 1/22/14 at 1:10am
post #173 of 186
Quote:
Originally Posted by petoulachi View Post
 

you should have Quantization options

 

No. Read above - "Only if device report of support of this feature" ;)

post #174 of 186
Quote:
Originally Posted by SweetLow View Post
 

 

No. Read above - "Only if device report of support of this feature" ;)

My bad, as my TV had this feature I was guessing that the Quantization option is visible but does not work (select full, close the driver window and open it, it is on "limited" again).

post #175 of 186
Quote:
Originally Posted by SweetLow View Post

It's strange, but you can post your edid data's here (only raw 256 bytes at the end of dump) -  i can view and tell more.

Thanks for helping me out with this, SweetLow.

For my Dell 24" monitor:

Raw data
00,FF,FF,FF,FF,FF,FF,00,10,AC,8B,A0,51,48,43,30,33,16,01,03,80,35,1E,78,EA,2F,15,A5,55,55,9F,28,
0D,50,54,A5,4B,00,71,4F,81,80,D1,C0,01,01,01,01,01,01,01,01,01,01,02,3A,80,18,71,38,2D,40,58,2C,
45,00,13,2B,21,00,00,1E,00,00,00,FF,00,30,4A,56,44,52,32,43,49,30,43,48,51,0A,00,00,00,FC,00,44,
45,4C,4C,20,53,32,34,34,30,4C,0A,20,00,00,00,FD,00,38,4C,1E,53,11,00,0A,20,20,20,20,20,20,01,33,
02,03,1C,71,49,90,05,04,03,02,14,1F,12,13,23,09,07,07,83,01,00,00,65,03,0C,00,10,00,02,3A,80,18,
71,38,2D,40,58,2C,45,00,10,09,00,00,00,1E,01,1D,80,18,71,1C,16,20,58,2C,25,00,10,09,00,00,00,9E,
01,1D,00,72,51,D0,1E,20,6E,28,55,00,10,09,00,00,00,1E,8C,0A,D0,8A,20,E0,2D,10,10,3E,96,00,10,09,
00,00,00,18,8C,0A,D0,8A,20,E0,2D,10,10,3E,96,00,04,03,00,00,00,18,00,00,00,00,00,00,00,00,00,A7

For my Benq projector:

Raw data
00,FF,FF,FF,FF,FF,FF,00,09,D1,02,41,E9,05,00,00,1E,17,01,03,80,00,00,78,0A,EE,03,A4,57,4D,9A,25,
0E,4B,62,BD,EF,80,61,C0,81,C0,81,00,81,80,95,00,A9,40,61,7C,81,3C,02,3A,80,18,71,38,2D,40,58,2C,
45,00,00,00,00,00,00,1E,00,00,00,FD,00,17,78,0F,66,11,00,0A,20,20,20,20,20,20,00,00,00,FE,00,42,
45,4E,51,0A,20,20,20,20,20,20,20,20,00,00,00,FC,00,42,65,6E,51,20,50,4A,0A,20,20,20,20,20,01,43
post #176 of 186

>Dell 24" monitor:

As I tell above - "CE video capability data" block simply not present.

 

>Benq projector

This is not full HDMI EDID - high 128 bytes is absent.

post #177 of 186
Quote:
Originally Posted by SweetLow View Post

>Dell 24" monitor:
As I tell above - "CE video capability data" block simply not present.

>Benq projector
This is not full HDMI EDID - high 128 bytes is absent.

Ok thanks, so I won't screw around with the registry. I will just leave the EnableFullRGB :-) Thanks for taking a look...
post #178 of 186
How do you use the "FakeEDID_%d_%d_%x_%x" registry key exactly? What I want to now, is what should the %d_%_d_%x_%x part point to? The rest I understand, including the EDID hexadecimal data. But it is this code after FakeEDID which I do not comprehend... I assume it has to do with the port, but how do I find out what that should be?

Thanks...
Edited by alexs3d2 - 1/28/14 at 12:35am
post #179 of 186
For those of you who prefer a little software utility over manually modifying the registry: In the latest madVR version (v0.87.4) the tool "madLevelsTweaker.exe" can now force both NVidia and Intel GPUs to PC levels (0-255). For Intel GPUs it uses the registry tweak mentioned in this thread.
post #180 of 186
Quote:
Originally Posted by madshi View Post

For those of you who prefer a little software utility over manually modifying the registry: In the latest madVR version (v0.87.4) the tool "madLevelsTweaker.exe" can now force both NVidia and Intel GPUs to PC levels (0-255). For Intel GPUs it uses the registry tweak mentioned in this thread.

Thanks Madshi!
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Theater Computers
AVS › AVS Forum › Video Components › Home Theater Computers › Theory About Intel's HDMI Quantization Range Setting (Full 0-255)