Custom Resolution Utility (CRU)

[MysticWizard]

Hi Everyone

I have an Intel NUC 8 Rugged Kit NUC8CCHKR (with latest drivers, HD audio enabled in BIOS) and an LG PF1500G (led projector).

What I would like is to send 5.1 audio to my analog 5.1 amplifier (I have an ali express audio extractor).

What is happening is that the EDID of my PF1500 is read by the intel chip and it decides to only enable stereo.



I followed the following guide https://www.intel.com/content/www/us/en/...l-nuc.html
Also tried the internal options of Custom Resolution Utility and the suggestions in this start post but in all cases when I load the modified EDID the sound option changes to OFF and I can't select any (also in sound options the intel sound card is completely gone). I have not touched the video settings, they work fine so I assumed I did not need to modify anything there.

I tried the direct "restart", reboot, different configurations, audio only, audio + speaker layout etc, nothing works, it just doesn't allow these 5.1 selection options to be installed

Perhaps I am skipping something important, any help would be appreciated.

[ToastyX]

(08-31-2022 02:09 PM)MysticWizard Wrote:  I followed the following guide https://www.intel.com/content/www/us/en/...l-nuc.html

That guide can't possibly work because it's missing the HDMI data block. You need to make sure the extension block has an HDMI data block.

The easiest thing you can do is try importing this file using CRU: https://www.monitortests.com/download/da...-audio.dat

If you get no sound with that, then there's a problem with the driver.

[MysticWizard]

(09-01-2022 05:29 AM)ToastyX Wrote:  

(08-31-2022 02:09 PM)MysticWizard Wrote:  I followed the following guide https://www.intel.com/content/www/us/en/...l-nuc.html

That guide can't possibly work because it's missing the HDMI data block. You need to make sure the extension block has an HDMI data block.

The easiest thing you can do is try importing this file using CRU: https://www.monitortests.com/download/da...-audio.dat

If you get no sound with that, then there's a problem with the driver.

Thank you for your time, I think I tried this one but I will try it again just to make sure.

[aelius]

Hello!

I'm having trouble adding 4K resolutions to an HDMI dummy plug I use for remote access.

Am I doing something wrong? Hopefully the attached picture has all the information.

Thank you!

[ToastyX]

(09-01-2022 03:30 PM)aelius Wrote:  I'm having trouble adding 4K resolutions to an HDMI dummy plug I use for remote access.

Am I doing something wrong? Hopefully the attached picture has all the information.

Dummy plugs are still bound by pixel clock limitations. Dummy plugs are usually HDMI 1.4 (340 MHz limit) or DisplayPort 1.0/1.1 HBR (360 MHz 8 bpc/480 MHz 6 bpc).

[ChristianSm1th]

I have 3 x 4K TV’s which I use in my racing simulator. I am able to run them all at native resolution, 120hz, 10bit colour depth, VRR on 2 monitors (my 3080ti only has 2 x 2.1hdmi ports), with the monitors setup individually it all works perfectly. One of the sims I drive requires you to run full screen and not windowed to enable hdr. If I try and enable nvidia surround, I am able to run at 11520x2160 120hz vrr, but nvidia control panel just will not allow me to set 10bpc (always defaults to 8bpc) and so I can’t enable hdr. I have even tried reducing the resolution to 7680 x 1440 but it behaves the same way, defaulting to 8bpc and not allowing me to select 10bpc. Any ideas?

[Dreamic]

I don't think it's a fault of your program but something dumb Nvidia is doing and I think should be added to the Editing VRR Range section, not sure if there's been discussion about this.

In order to lower my VRR/LFC Range from 80 to 30, changing it is not enough. I must also change the Device ID to something with a lower VRR Range, like DELA179 (Dell/Alienware AW2721D 1-240Hz). Mine is SAM105C (Samsung Odyssey G7 80-240Hz).
This is the only way to go below 80Hz VRR. Reset Device ID to SAM105C and it will no longer go down to 30Hz~.
Also the Nvidia database is wrong about this display being 60-240Hz, it's 80-240Hz.
Everything is as up to date as it could be, monitor firmware included.

I don't think everyone will figure this out, why their 40fps in GSync Pendulum is 80Hz instead of 40Hz or 70fps is 140Hz, it's because of Device ID, LFC doubling isn't changed unless Device ID is to a correct one.
And we know LFC on certain displays, I think I've heard mainly VA, results in a brightness shift/flicker, as Hz jumps from 75Hz to 150Hz etc when you drop to 75fps, 85fps will be back at 85Hz. This is how you fix/mitigate this.

[ToastyX]

(09-02-2022 02:12 AM)Dreamic Wrote:  In order to lower my VRR/LFC Range from 80 to 30, changing it is not enough. I must also change the Device ID to something with a lower VRR Range, like DELA179 (Dell/Alienware AW2721D 1-240Hz). Mine is SAM105C (Samsung Odyssey G7 80-240Hz).
This is the only way to go below 80Hz VRR. Reset Device ID to SAM105C and it will no longer go down to 30Hz~.
Also the Nvidia database is wrong about this display being 60-240Hz, it's 80-240Hz.
Everything is as up to date as it could be, monitor firmware included.

That means NVIDIA must have ranges hard-coded in the driver for some monitors, possibly to work around issues like flickering. Does the ID need to be a monitor with VRR, or can it be any other random ID?

[ToastyX]

(09-01-2022 06:27 PM)ChristianSm1th Wrote:  I have 3 x 4K TV’s which I use in my racing simulator. I am able to run them all at native resolution, 120hz, 10bit colour depth, VRR on 2 monitors (my 3080ti only has 2 x 2.1hdmi ports), with the monitors setup individually it all works perfectly. One of the sims I drive requires you to run full screen and not windowed to enable hdr. If I try and enable nvidia surround, I am able to run at 11520x2160 120hz vrr, but nvidia control panel just will not allow me to set 10bpc (always defaults to 8bpc) and so I can’t enable hdr. I have even tried reducing the resolution to 7680 x 1440 but it behaves the same way, defaulting to 8bpc and not allowing me to select 10bpc. Any ideas?

You'll have to ask NVIDIA about that. Either the color format is different in some way, like RGB vs. YCbCr or 4:4:4 vs. 4:2:2, or there is some limitation with Surround when the ports don't all match.

[aelius]

(09-02-2022 02:12 AM)Dreamic Wrote:  I don't think it's a fault of your program but something dumb Nvidia is doing and I think should be added to the Editing VRR Range section, not sure if there's been discussion about this.

In order to lower my VRR/LFC Range from 80 to 30, changing it is not enough. I must also change the Device ID to something with a lower VRR Range, like DELA179 (Dell/Alienware AW2721D 1-240Hz). Mine is SAM105C (Samsung Odyssey G7 80-240Hz).
This is the only way to go below 80Hz VRR. Reset Device ID to SAM105C and it will no longer go down to 30Hz~.
Also the Nvidia database is wrong about this display being 60-240Hz, it's 80-240Hz.
Everything is as up to date as it could be, monitor firmware included.

I don't think everyone will figure this out, why their 40fps in GSync Pendulum is 80Hz instead of 40Hz or 70fps is 140Hz, it's because of Device ID, LFC doubling isn't changed unless Device ID is to a correct one.
And we know LFC on certain displays, I think I've heard mainly VA, results in a brightness shift/flicker, as Hz jumps from 75Hz to 150Hz etc when you drop to 75fps, 85fps will be back at 85Hz. This is how you fix/mitigate this.

Increasing the variable refresh range to dip down into 30Hz is a really bad idea, because the pixel response time and input lag will skyrocket, and if you ever dip below 30Hz the flicker will be way WORSE than before. There's a reason stock LFC kicks on as high as 80Hz.

A better approach is to shrink the variable refresh range. Flicker becomes harder to notice in the higher Hz, so you can leverage your 240Hz of headroom to make the range 120Hz-240Hz. Be sure to make it exactly 1/2 of the actual max Hz (239.something). You can go even smaller, if you like, but you'll create a gap in the coverage. A range of 150Hz-240Hz won't be able to engage variable refresh from 121fps-150fps, for example.

fwiw, flicker should only ever occur if you've got poor frame pacing, so the easiest fix is always to investigate why the game is running poorly. Many games are just unfixable though