or Connect
AVS › AVS Forum › Video Components › Home Theater Computers › Intel Integrated HD Graphics Black Level Setting
New Posts  All Forums:Forum Nav:

Intel Integrated HD Graphics Black Level Setting - Page 3

post #61 of 98
MFusick,

On the Intel HD Control panel, select Video instead of Display. The input range can be adjusted here. Does that help?
post #62 of 98
Quote:
Originally Posted by slosvt View Post

MFusick,

On the Intel HD Control panel, select Video instead of Display. The input range can be adjusted here. Does that help?

Nope.



It's like Intel sees my Samsung LCD as a Digital TV and sends it limited anyways. It lists it as a digital TV and it's not. How can I fix that ?
post #63 of 98
Quote:
Originally Posted by Mfusick View Post

Fingers crossed for this....

I posted about the custom resolution workaround a few days ago in my thread:
http://www.avsforum.com/t/1477460/theory-about-intels-hdmi-quantization-range-setting-full-0-255#post_23433647

Unfortunately, I think that only works up to driver 2509 (that's the one I'm using on my Sandy). That driver is too old for Ivy or Haswell. Newer drivers I tried, forced limited range on HDMI connected displays, even with custom resolutions. The only hope is if Intel pays attention to that EDID flag I mentioned in my thread.
post #64 of 98
I have a LG PC monitor with DVI, HDMI and VGA in. HDMI IN is mostly the same as LG TV's HDMI IN with "HIGH" (full-range) and "LOW" (limited-range) BLACK LEVELs. Intel iGPU always sends:

- Full-range RGB to DVI IN
- Limited-range RGB to HDMI IN

When using HDMI IN, therefore "LOW" must be selected, otherwise black areas are washed out. (It doesn't matter which output port of the motherboard I use, HDMI or DVI, at least for ASRock.)
post #65 of 98
Quote:
Originally Posted by renethx View Post

I have a LG PC monitor with DVI, HDMI and VGA in. HDMI IN is mostly the same as LG TV's HDMI IN with "HIGH" (full-range) and "LOW" (limited-range) BLACK LEVELs. Intel iGPU always sends:

- Full-range RGB to DVI IN
- Limited-range RGB to HDMI IN

When using HDMI IN, therefore "LOW" must be selected, otherwise black areas are washed out. (It doesn't matter which output port of the motherboard I use, HDMI or DVI, at least for ASRock.)

Yes! This is exactly what I have found. I'm going to use a GPU.
post #66 of 98
Thread Starter 
I started this post about two years ago and I can't believe it is still an issue. Who writes these drivers?
post #67 of 98
Quote:
Originally Posted by Mfusick View Post

Yes! This is exactly what I have found. I'm going to use a GPU.

That's what I was forced to do. Got a passive Asus GT 430, best 70 bucks I spent on my HTPC. I wasted countless nights trying to get Intel's graphics to work, haven't wasted another minute on it since.
post #68 of 98
Quote:
Originally Posted by bryansj View Post

I started this post about two years ago and I can't believe it is still an issue. Who writes these drivers?

I'm coming from a radeon GPU so I've never experienced this yet. Lol.
post #69 of 98
And it appears I can not fix it.. so I guess I'll put my GPU back in.
post #70 of 98
Or you can just use DVI port like I did on my LCD monitor. There is zero advantage of using HDMI port anyway for a PC monitor unless you paid $$ to get speakers on the screen.
post #71 of 98
Quote:
Originally Posted by Foxbat121 View Post

Or you can just use DVI port like I did on my LCD monitor. There is zero advantage of using HDMI port anyway for a PC monitor unless you paid $$ to get speakers on the screen.

You missed the part where I have dual monitors and already using the DVI on my 26" Samsung. This is a secondary monitor. I actually run dual 23" flanking my 26" so I need a GPU anyways. I miss my third monitor.

I did not think I would miss my Radeon card as much as I do.
post #72 of 98
Quote:
Originally Posted by Mfusick View Post

You missed the part where I have dual monitors and already using the DVI on my 26" Samsung. This is a secondary monitor. I actually run dual 23" flanking my 26" so I need a GPU anyways. I miss my third monitor.

I did not think I would miss my Radeon card as much as I do.

According to renethx posted above, it doesn't matter which port on your motherboard uses. So, theoretically, you can use a HDMI to DVI cable connect from the HDMI port of your mobo to your LCD monitor's DVI port. As long as you are using DVI port on the monitor, Intel IGP should output full range just fine.
post #73 of 98
Quote:
Originally Posted by bryansj View Post

I started this post about two years ago and I can't believe it is still an issue. Who writes these drivers?

The drivers are doing the right thing based on official HDMI specs. (see the thread I linked above). What people want is a working override/hack like we have for Nvidia/ATI to overrule the HDMI spec. For some reason Intel refuses to provide this. The fact that this issue has persisted for so many years makes it clear it's not a bug - it's a policy decision on their part. I'm still trying to figure out what the purpose of the quantization-range control panel option was.
post #74 of 98
My speculation: it is done so to minimize the unnecessary support costs. For majority of users, they only connect HDMI to a TV and Intel's choice is the right one so that they can view their desktop in correct mode (all consumer TVs defaults to limited range).
post #75 of 98
Well I figured out how to fix my black level to 0-255 I am happy to report. It was actually easy.
post #76 of 98
Quote:
Originally Posted by Mfusick View Post

Well I figured out how to fix my black level to 0-255 I am happy to report. It was actually easy.

I'm not sure that installing a dedicated GPU card counts as a fix. It's more like avoiding the problem. wink.gif
post #77 of 98
I'm just happier with a GPU
post #78 of 98
what about the 3165 drivers? They are supposed to fix this.
post #79 of 98
No, it does not fix it.
post #80 of 98
Assume this is never going to be fixed, and that I don't want to install a dedicated GFX card, what is the best way of calibrating my system please for limited range RGB? I can't use any of the standard test patterns as they all rely on being able to see BTB and WTW?
post #81 of 98
I thought I read somewhere that people were connecting the TV via DVI/analog stereo and a receiver via HDMI.
The idea would be to use analog stereo when watching TV/recorded shows/'not great sound', and then switch audio to hdmi when you need 'great sound' to go through the receiver. Video remains DVI with full range.
I think I'll try that, dunno if it would work though...

...
tried it, didn't work. my tv doesn' know how to accept audio on a different input than dvi/hdmi.
The pc side did do as expected though.
So if your tv has a 'real' dvi in and, when using that, can accept some audio on some other input, then this should work.

You still have to switch audio outs on the PC when you want to bitstream audio over hdmi to a receiver though. So there some hassle involved either way.
Edited by Robin Mitra - 7/26/13 at 5:09pm
post #82 of 98
I'm trying to convince intel to correct this problem.
This is the thread:

http://communities.intel.com/message/204055#204055

I was able to reprogram my Samsung LCD EDID eprom and i can confirm that intel driver respect the quantization bit in the EDID.
I managed to modify the edid eprom of mi TV, specifically changed the Quantization Range Selectable Bit from 0 to 1 and corrected the checksum
This was done in ubuntu using i2ctools entering service menu of samsung tv enabling edid overwrite.
Then booted into windows 7, and the magic was done, the combo for selecting default,limited or full range appeared in Display/Monitor-Tv Setting
Change to full and finnally the blacks where not washed

So the intel driver is respecting that bit.
The thing is that reprograming the EPROM is dificult and TV specific.

The problem left is that when connecting through my denon avr the EDID bit changes to 0 and again limited range.
post #83 of 98
Subscribing.... :popcorn:
post #84 of 98
any news about issue?
post #85 of 98
Quote:
Originally Posted by Robertos View Post

any news about issue?

There is some recent developments in the 0-255 thread yeah...
post #86 of 98
Does this issue affect the latest Haswell IGPs? What if I just want to connect my Panasonic plasma HDTV?
post #87 of 98
The HDMI is effected on all intel igpu including Haswell - so yes. It is.
post #88 of 98
But if all you want is connect to your HDTV, there is nothing you need to do or fix. It works as advised out of box. That's why Intel made the driver this way in the first place. The particular problem only affect those who uses a PC monitor that only support full-range RGB or wish to use their TV in full-range RGB mode.
post #89 of 98
Quote:
Originally Posted by Foxbat121 View Post

But if all you want is connect to your HDTV, there is nothing you need to do or fix. It works as advised out of box. That's why Intel made the driver this way in the first place. The particular problem only affect those who uses a PC monitor that only support full-range RGB or wish to use their TV in full-range RGB mode.

YES.

For me I have HDMI only (or VGA) on one of my cheap extra monitors on my desktop. My Asrock Extreme 4 mobo has Display Port, HDMI, DVI, and VGA. VGA sucks for high resolutions (I run 1200x1920 on 26" ) and I only have 1 display port but none available on the monitors. Since I run 3 monitors I am ok running a Display port to DVI or Display port to HDMI cable for one- and running a DVI to DVI for another. But VGA sucks... and HDMI looks terrible with washed out blacks.


I ended up just using a GPU card (for other reasons too) and that seems to work for me. But using HDMI for a PC monitor (many have this only) will expose the problem clearly. Only new machines and displays have display port so if you are using an older monitor for your second monitor and you are already using DVI for your main display- you get stuck with HDMI and the stupid Intel iGPU problem of 16-235.
post #90 of 98
It seems that I don't have this problem, but if I'm missing out on some quality, I would really like to fix it.

I have a first generation HD Graphics (Core i3 530), and I have two settings for RGB in the Intel driver: Limited, Full. Even if I change it to full, setting reverts to limited before a reboot, and no visible change is made when changing settings.

I believe I have full output because I can clearly see the difference between levels 0-15 in the lagom black level test

I have 3 questions:

Is the problem mentioned in the thread related to crushing of BTB and WTW (i.e.: 0-15 all look the same) or conversion from 0-255 to 16-235 (introducing banding)?

Is displaying levels 0 - 15 as distinct shades in lagom test sufficient evidence of full RGB output through HDMI?

Wouldn't using a DVI-to-HDMI adapter work as a makeshift solution for those that don't need audio? (that is, intel:dvi - > tv, monitor:hdmi?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Home Theater Computers
AVS › AVS Forum › Video Components › Home Theater Computers › Intel Integrated HD Graphics Black Level Setting