IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
117 stars 4 forks source link

All current available drivers for Arc A770 set RGB range incorrectly / incorrect black levels ( continuation of #801 ) #815

Closed alexander-laiman closed 3 months ago

alexander-laiman commented 4 months ago

Checklist [README]

Application [Required]

Windows

Processor / Processor Number [Required]

4790k

Graphic Card [Required]

A770

GPU Driver Version [Required]

31.0.101.5594

Other GPU Driver version

No response

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

report.txt

Description and steps to reproduce [Required]

As written prior, installing the intel arc graphics card drivers sets RGB output range on the card to be limited, with no controls for setting it to full. When the Graphics card driver is cleanly uninstalled and the computer falls back to builtin windows drivers, blacks are correctly represented in the display. Installing the drivers causes blacks to become washed out again.

This happens in my case with the PC connected directly to the display, a Samsung TV UN55fh6003 with black level controls in the menu which supports limited and full, or when its connected to the AV receiver, an integra DRX 5.2, which then passes the signal to the display.

This bug was introduced after drivers 31.0.101.4577 where it last set blacks correctly, as evidenced in this reddit post from a user having the same issue. https://www.reddit.com/r/IntelArc/comments/1cwoqv6/colors_washed_out_on_secondary_monitor/

This issue is a recreation of #801 which was closed quickly when I didnt follow up.

Device / Platform

No response

Crash dumps [Required, if applicable]

No response

Application / Windows logs

No response

EstebanIntel commented 4 months ago

Hi @alexander-laiman,

This is a known limitation for Arc A-Series GPUs, let me explain.

PC monitors and TVs work slightly different when displaying color from digital sources. When in 8-bit color mode, PC monitors are able to display the full range of colors (0 to 255), whereas TVs can only display a limited range (16 to 235).

Now, the majority of PC users use PC monitors as their display; so, having the GPU use the full range by default makes sense. However, in order to accommodate to the users who chose to use a TV as their PC display, Intel added the "Quantization Range" option to the Intel Graphis Command Center (IGCC). And, since the video interface used by TVs is HDMI, the "Quantization Range" option was made only available to HDMI outputs, more specifically, to native HDMI outputs.

The limitation comes from the Intel Arc A-Series Limited Edition cards not having a native HDMI, but rather using a PCON to convert from DP to HDMI. This results in the "Quantization Range" option not been available in IGCC for these cards. We have taken note of this limitation and will be taking it into account for future Intel Arc products.

Finally, one possible work around you might want to try is to connect you TV to the motherboard's HDMI port, instead of the Intel Arc card's HDMI port. This will cause the display functions to be managed by the iGPU, but the rendering will still be done by the Intel Arc card. Since the display functions will be handled by the iGPU, the "Quantization Range" should be avaiable in IGCC.

However, please note that the only supported hardware configurations for Intel Arc A-Series is to pair it with an 10th Gen Intel® Core™ Processors or newer or with an AMD Ryzen™ 3000 series Processors or newer (please see the full details on the supported configurations here: Intel® Arc™ A-Series Graphics – Desktop Quick Start Guide. Also, that IGCC is only supported for 6th Gen Intel® Core™ Processors or newer as described here: How to Install the Intel® Graphics Command Center From the Microsoft Store.

LadyMikea commented 4 months ago

For what is worth, I observed this: setting my monitor (LG W2442PA connected to Intel A750 via HDMI) to 60,00 Hz results in incorrect black level (looks like 16-235 RGB) but if I set refresh rate to 59,934 Hz black level is correct (0-255 RGB). I have no idea why is this, but in this particular model, this is how it works.

alexander-laiman commented 4 months ago

This might be true for old TVs but the display Im using is fully capable of displaying full range as it does with my laptop and other devices (ps5 etc). Im also able to use my NVIDIA quadro card to do output.

I have no quantization range option available in IGCC as you mentioned which lines up. Connecting to the motherboards hdmi is not a good fix, since this breaks several audio over hdmi functions that I can use through the card. Im not sure why this is a hardware limitation, when If I uninstall the new drivers and use the old ones it works fine over the exact same connection. Ill provide two images to show this.

alexander-laiman commented 4 months ago

20240705_115845 20240705_115921

Here's the display output whilst doing clean install. You can see when it uninstalls the driver's and cleans out the display shows blacks as intended, but when the driver installs it suddenly washes everything out. So the hardware IS capable of doing the correct thing. I'm not sure what this would have to do with PCON.

LadyMikea commented 4 months ago

I see. But your monitor refresh rate is the same in both situations? You could check if changing refresh rate changes something (probably not, but in my case, there is a difference).

alexander-laiman commented 4 months ago

hmm for me changing refresh in windows or adapter settings has no effect

On Fri, 5 Jul 2024, 14:11 LadyMikea, @.***> wrote:

I see. But your monitor refresh rate is the same in both situations? You could check if changing refresh rate changes something (probably not, but in my case, there is a difference).

— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815#issuecomment-2211244589, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCK6SKBYIBVR7PEOJVWMVDZK3OWJAVCNFSM6AAAAABKNOIVE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGI2DINJYHE . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815/2211244589@ github.com>

Vipitis commented 4 months ago

I experience the same thing for the past 20 months too. monitor is not a TV and is connected via HDMI. Not options for RGB range in IGCC for me either. How do I know that this is a driver issue? if I boot into safemode, run DDU, or remove the device in device manager - the windows default driver output takes over and has full range.

EstebanIntel commented 4 months ago

Hi @alexander-laiman,

I was wrong on the Quantization Range setting not been available for the HDMI output on Arc graphics cards. This setting is available, but its name was changed.

Please download and install the latest version of IGCC. Then Open IGCC, go to the "Video" tab and scroll down to find the setting called "Input Range". Then, change this setting to full or limited accordingly.

alexander-laiman commented 4 months ago

This doesn't change the output range for the card

On Tue, 9 Jul 2024, 16:08 Esteban, @.***> wrote:

Hi @alexander-laiman https://github.com/alexander-laiman,

I was wrong on the Quantization Range setting not been available for the HDMI output on Arc graphics cards. This setting is available, but its name was changed.

Please download and install the latest version of IGCC https://apps.microsoft.com/detail/9plfnlnt3g5g. Then Open IGCC, go to the "Video" tab and scroll down to find the setting called "Input Range". Then, change this setting to full or limited accordingly.

— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815#issuecomment-2218629716, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCK6SKOMWT2K3TFVSZFSTDZLQ7KRAVCNFSM6AAAAABKNOIVE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJYGYZDSNZRGY . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815/2218629716@ github.com>

Vipitis commented 4 months ago

Please download and install the latest version of IGCC. Then Open IGCC, go to the "Video" tab and scroll down to find the setting called "Input Range". Then, change this setting to full or limited accordingly.

similar result for me. I change from none to limited to full and see no difference. Meaning nothing actually applies - and I also don't get any option in the video tab to chose a connected display for example. So I don't think that feature is working.

E: seems to apply on reboot at least...

EstebanIntel commented 4 months ago

@alexander-laiman,

I just tested this with a Samsung UN55RU7300P connected to an Arc A770 via HDMI and the Input Range setting is working as intended. Can you try setting the Input Range to Limited and then restarting your system?

alexander-laiman commented 4 months ago

Awesome I just downloaded the latest driver and Intel arc control and it works as it should now out of the box! Thank you to the team for looking into it <3

On Wed, 10 Jul 2024, 19:25 Esteban, @.***> wrote:

@alexander-laiman https://github.com/alexander-laiman,

I just tested this with a Samsung UN55RU7300P connected to an Arc A770 via HDMI and the Input Range setting is working as intended. Can you try setting the Input Range to Limited and then restarting your system?

— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815#issuecomment-2221696296, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCK6SOYIH6ULW3AZVCLWIDZLW7GXAVCNFSM6AAAAABKNOIVE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRRGY4TMMRZGY . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815/2221696296@ github.com>

alexander-laiman commented 4 months ago

Oh wait nevermind it just reset to the windows 2006 driver false alarm ☠️

On Wed, 10 Jul 2024, 22:49 Alexander James L, @.***> wrote:

Awesome I just downloaded the latest driver and Intel arc control and it works as it should now out of the box! Thank you to the team for looking into it <3

On Wed, 10 Jul 2024, 19:25 Esteban, @.***> wrote:

@alexander-laiman https://github.com/alexander-laiman,

I just tested this with a Samsung UN55RU7300P connected to an Arc A770 via HDMI and the Input Range setting is working as intended. Can you try setting the Input Range to Limited and then restarting your system?

— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815#issuecomment-2221696296, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCK6SOYIH6ULW3AZVCLWIDZLW7GXAVCNFSM6AAAAABKNOIVE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRRGY4TMMRZGY . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815/2221696296@ github.com>

alexander-laiman commented 4 months ago

So updating to latest driver has enabled me to be able to select ycbr444 as output instead of RGB which is a sort of patch since black levels seem to work correctly with this. However it would be good to be able to output blacks on RGB as intended. I'll grab another monitor to test asap

On Wed, 10 Jul 2024, 22:51 Alexander James L, @.***> wrote:

Oh wait nevermind it just reset to the windows 2006 driver false alarm ☠️

On Wed, 10 Jul 2024, 22:49 Alexander James L, @.***> wrote:

Awesome I just downloaded the latest driver and Intel arc control and it works as it should now out of the box! Thank you to the team for looking into it <3

On Wed, 10 Jul 2024, 19:25 Esteban, @.***> wrote:

@alexander-laiman https://github.com/alexander-laiman,

I just tested this with a Samsung UN55RU7300P connected to an Arc A770 via HDMI and the Input Range setting is working as intended. Can you try setting the Input Range to Limited and then restarting your system?

— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815#issuecomment-2221696296, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCK6SOYIH6ULW3AZVCLWIDZLW7GXAVCNFSM6AAAAABKNOIVE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRRGY4TMMRZGY . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815/2221696296@ github.com>

EstebanIntel commented 4 months ago

Hey @alexander-laiman, any updates on your tests?

alexander-laiman commented 4 months ago

After updating some chipset and PCI drivers through CCleaner (unfortunately the Intel tool only seems to look at the most standard drivers) I am able to select two drop downs withing the Graphic command center. There are no relevant options available in Arc Control, which is disappointing given that Id assume they'd be in there. (Though maybe the ideology is similar to GeForce experience and Nvidia control panel as an analogy )

output: Only option is 8BPC_RGB

and the type RGB 422 444

If I do 8BPC and RGB, Though I would expect a full range signal, I only get the Black Low signal (16-235). If the TV is set to full range signal in, it will display what should be full black as a grey, due to the value being represented at 16 instead of 0. This is the washed out screen we've seen. To get black we can set the TV so a low range signal which maps 16-235 to full black and white but this loses out on some potential.

If I select either of the compressed formats, 422 or 444 The PC sends a full range output in that format, such that when the TV is set to receive a full signal with RGB level set to High / Normal, blacks are represented correctly.

For now I'm fine with using 444 as I'm viewing at a distance where the chroma aberrations etc aren't noticable. But would be good to fix this or at least show the user the range currently being output.

On Mon, 15 Jul 2024, 16:30 Esteban, @.***> wrote:

Hey @alexander-laiman https://github.com/alexander-laiman, any updates on your tests?

— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815#issuecomment-2229345093, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCK6SLHKRDMO5KWUOMCUTDZMQWMVAVCNFSM6AAAAABKNOIVE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRZGM2DKMBZGM . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815/2229345093@ github.com>

EstebanIntel commented 3 months ago

@alexander-laiman I'm glad the using YCbCr 4:4:4 is working for you.

As a last test, can you please try setting your configuration in IGCC as below?

EstebanIntel commented 3 months ago

Hey @alexander-laiman any chance you were able to perform the test from the last comment?

alexander-laiman commented 3 months ago

Yes I was able to test with those settings, no luck though

On Tue, Jul 23, 2024 at 12:05 PM Esteban @.***> wrote:

Hey @alexander-laiman https://github.com/alexander-laiman any chance you were able to perform the test from the last comment?

— Reply to this email directly, view it on GitHub https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815#issuecomment-2245649973, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCK6SO5QRLH7S4NNI5D3OLZNZ5NTAVCNFSM6AAAAABKNOIVE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBVGY2DSOJXGM . You are receiving this because you were mentioned.Message ID: <IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/issues/815/2245649973@ github.com>

EstebanIntel commented 3 months ago

@alexander-laiman Thanks for testing! We will take these results as feedback to improve our products. But, since YCbCr 4:4:4 is working for you, can this issue be closed?