Post Reply
Custom Resolution Utility (CRU)
05-29-2019, 11:41 PM
Post: #4051
RE: Custom Resolution Utility (CRU)
Hi there everyone.
Recently I started having problems with Windows not recognizing correctly the 23.976Hz refresh rate.
I was always able to add both 23.976 and 24 (with CRU, obviously) and Windows recognized them correctly as 23 and 24Hz.
But few days ago, after updating GPU drivers, all custom refresh rates were wiped, so I had to add them again (IIRC, this was always the case when updating the drivers). But now, no matter whether I add 23.976 or 24, Windows recognizes both of them as 24Hz. This means I can't have both of them added at the same time, because Windows only accepts one at a time.
What do?
Find all posts by this user
Quote this message in a reply
05-30-2019, 01:26 AM
Post: #4052
RE: Custom Resolution Utility (CRU)
(05-29-2019 11:41 PM)moewchin Wrote:  I was always able to add both 23.976 and 24 (with CRU, obviously) and Windows recognized them correctly as 23 and 24Hz.
That should have never been the case. Windows will list 23.976 Hz as 24 Hz. The graphics driver might provide a 23 Hz alias for 24 Hz TV resolutions, but that's separate and unrelated to the 23.976 Hz added with CRU. Try adding a 24 Hz resolution in a TV resolutions data block in the extension block and see if that makes 23 Hz appear.
Find all posts by this user
Quote this message in a reply
05-30-2019, 09:16 AM (Last edited: 05-30-2019, 09:24 AM by chros)
Post: #4053
RE: Custom Resolution Utility (CRU)
(05-29-2019 03:24 PM)chros Wrote:  
(04-29-2019 01:18 PM)ToastyX Wrote:  
(04-28-2019 11:52 PM)wolpers0815 Wrote:  I have an issue when connecting a Geforce 1080 with my new Sony 65ZF9 with a HDMI 2.0b cable capable of 18Gbps. At 3840x2160 with 30Hz in RGB mode the Nvidia Control Panel allows me for selecting either 8 or 12 bit. What about 10 bit?

You should be able to enable 30-bit deep color (10 bpc) in the HDMI data block to get 10-bit with 24/25/30 Hz. You might be able to get UHD 50 Hz to use 10-bit with custom timing parameters, but I'm not sure if the driver will allow 10-bit for non-TV resolutions.

Thanks, I'll give it a try using 10-bit with 24/25/30 Hz and report back.

In short: it didn't give me the 10bit option, only 8bit is available (it removed the 12bit option).
Setup: MSI GTX 1060 Gaming X 6GB (driver v385.28) on Win10 LTSB 1607 + HDMI + LG B8 (PC mode)
What I did:
- unticked the 36bit in both HDMI and HDMI2.0 datablock (30bit are still ticked in both)
- restart-64.exe
- restart PC
- selected 25Hz (I have custom 23Hz)

ToastyX, have you managed to get 10bit option in "recent" nvidia drivers? (>=v385.28)
This problem is not that important: I only want to experiment with 10bit output (if it's possible) to compare the resulting banding on the B8.
And thanks for this really useful util!

(05-29-2019 11:41 PM)moewchin Wrote:  But few days ago, after updating GPU drivers

Aside what ToastyX said, try this way, it definitely works. But note, that certain GPU drivers are broken: blocking the usage of custom resolution.

Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v385.28),Win10 LTSB 1607,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED65B8(04.10.25+PC4:4:4+2160p@23/24/25/29/30/50/59/60Hz)
Find all posts by this user
Quote this message in a reply
05-30-2019, 03:38 PM (Last edited: 05-30-2019, 03:39 PM by moewchin)
Post: #4054
RE: Custom Resolution Utility (CRU)
(05-30-2019 01:26 AM)ToastyX Wrote:  
(05-29-2019 11:41 PM)moewchin Wrote:  I was always able to add both 23.976 and 24 (with CRU, obviously) and Windows recognized them correctly as 23 and 24Hz.
That should have never been the case. Windows will list 23.976 Hz as 24 Hz. The graphics driver might provide a 23 Hz alias for 24 Hz TV resolutions, but that's separate and unrelated to the 23.976 Hz added with CRU. Try adding a 24 Hz resolution in a TV resolutions data block in the extension block and see if that makes 23 Hz appear.
OK, I finally got it to work. What helped was deleting the 24Hz resolution in TV resolutions data block, then adding it back and moving it to the top of the list. I also sorted all the resolutions on the list by ascending frequency. Then I removed all detailed resolutions on the main screen. That did the trick.

Interestingly, if I add 23.976 and 24 detailed resolutions, both 23Hz and 24Hz Windows resolutions are actually 23.976. But when the detailed resolutions block is empty everything works, so whatever.
Thanks for the help.
Find all posts by this user
Quote this message in a reply
05-31-2019, 09:08 AM
Post: #4055
RE: Custom Resolution Utility (CRU)
(05-30-2019 03:38 PM)moewchin Wrote:  Interestingly, if I add 23.976 and 24 detailed resolutions, both 23Hz and 24Hz Windows resolutions are actually 23.976. But when the detailed resolutions block is empty everything works, so whatever.

Haven't you tried out the DisplayID block at the top of the Extension block instead?

Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v385.28),Win10 LTSB 1607,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED65B8(04.10.25+PC4:4:4+2160p@23/24/25/29/30/50/59/60Hz)
Find all posts by this user
Quote this message in a reply
06-01-2019, 01:28 AM
Post: #4056
RE: Custom Resolution Utility (CRU)
(05-30-2019 09:16 AM)chros Wrote:  In short: it didn't give me the 10bit option, only 8bit is available (it removed the 12bit option).
It doesn't make sense for 36-bit to work but not 30-bit. You might have to enable YCbCr 4:4:4 deep color as well; otherwise, it might only be available with RGB. If that doesn't work, it might be a driver bug. I don't have a deep color monitor to test this. Also, the HDMI specification says if it supports any deep color mode, it shall support 36-bit mode, so maybe you have to leave that enabled.
Find all posts by this user
Quote this message in a reply
06-03-2019, 11:15 AM
Post: #4057
RE: Custom Resolution Utility (CRU)
(06-01-2019 01:28 AM)ToastyX Wrote:  
(05-30-2019 09:16 AM)chros Wrote:  In short: it didn't give me the 10bit option, only 8bit is available (it removed the 12bit option).
It doesn't make sense for 36-bit to work but not 30-bit. You might have to enable YCbCr 4:4:4 deep color as well; otherwise, it might only be available with RGB. If that doesn't work, it might be a driver bug. I don't have a deep color monitor to test this. Also, the HDMI specification says if it supports any deep color mode, it shall support 36-bit mode, so maybe you have to leave that enabled.

Thanks, so you can't confirm that it works. Deep Color is supported and enabled in B8, once again:
- if 36 bits is checked: 8 bit and 12 bit
- if 36 bits is not checked: only 8 bit

Ryzen 5 2600,Asus Prime b450-Plus,16GB,MSI GTX 1060 Gaming X 6GB(v385.28),Win10 LTSB 1607,MPC-BEx64+LAV+MadVR,Yamaha RX-A870,LG OLED65B8(04.10.25+PC4:4:4+2160p@23/24/25/29/30/50/59/60Hz)
Find all posts by this user
Quote this message in a reply
06-03-2019, 08:27 PM (Last edited: 06-03-2019, 09:26 PM by Deceptive Pastry)
Post: #4058
RE: Custom Resolution Utility (CRU)
(04-27-2019 07:13 PM)ToastyX Wrote:  
(04-25-2019 06:08 PM)Deceptive Pastry Wrote:  Have a TCL S405 4k TV, laptop connected through HDMI, that I often game on. Initially when gaming in 1920x1080 or 1600x900 resolution, the TV or laptop seems to upscale and output to the native res of 4k as displayed when I hit the info button on the TV. The problem is my graphics card can only do up to 30hz at 4k, so as long as it is outputting in 4k I can't get 1080p 60hz even if that is what I have the game set to. I have solved this problem in 95% of games with CRU by deleting or lowering priority of 3840x2160 under detailed resolutions and moving 1080 to the top. This causes the image to be output at 1080p 60hz and the TV properly shows this in the info. Some rare games still give me odd issues, like I can run at 1600x900 60hz but if I set the game to 1080 it will resort to outputting 4k 30hz again. I'm hoping to better understand why this happens.

2nd issue is, sometimes I will lose audio over HDMI. I hit restart.exe, then the HDMI audio device will completely disappear from playback devices and I'm left with only "Speakers". If I unplug/replug HDMI cable to restore default TV settings the HDMI audio device will return. I have tried importing the hdmi-audio.dat extension block but I seem to be missing something there. It seems like if I simply deprioritize 3840x2160 instead of outright deleting it I can get 60hz without losing HDMI audio. But I'm not entirely sure if that is what's solving it.
The audio issue might be a driver bug. To troubleshoot both issues, I would try just the bare minimum configuration that does what you want.

Try importing this file and do NOT check the "Import complete EDID" option:

That includes 1920x1080 @ 60 Hz, 3840x2160 @ 30 Hz, and HDMI audio.

I'm back...had it working for a while. Ended up having to reset the settings, however now no matter what I do I lose HDMI audio. Initially all I did was move priority of 1080 to the top, save settings, restart driver, and was able to retain HDMI audio. Now nothing is working. It seems making ANY changes, saving, and restarting the driver results in lost audio until I re-plug cable or reset settings again.

Tried importing the bin to add the HDMI extension - no luck.

More details regarding my issue. Something very odd is going on.

I do believe it has to do with drivers. Given that it's a laptop it has dual video cards, Intel HD Graphics and a Geforce 950m for gaming. The HDMI/display info and such goes through the Intel. I have found that after restarting the driver and losing HDMI audio, if I go to device manager > Sound, video and game controllers > Intel® Display Audio, and I click Update Driver > Browse my computer > Let me pick from list, install the standard "High Definition Audio Device" instead, the device shows back up in Sound as generic Digital Audio (HDMI) and I get sound again. Ok, cool. Click restart64.exe...still there. Cool. Click restart64.exe again to double check...and it's gone again. Ok, so I go back to Sound, video and game controllers, reinstall the old Intel® Display Audio driver. Audio pops back up as 49S405 (HDMI)...sometimes. Hit restart64.exe, gone again. Reinstall generic "High Definition Audio Device", it comes back until I hit restart64.exe 1-2 more times. It seems to either only work for one restart once changing the Intel Audio drivers, or it is completely random before it disappears again. I have no idea what is going on.
Find all posts by this user
Quote this message in a reply
06-05-2019, 03:50 PM
Post: #4059
RE: Custom Resolution Utility (CRU)
(06-03-2019 08:27 PM)Deceptive Pastry Wrote:  I do believe it has to do with drivers. Given that it's a laptop it has dual video cards, Intel HD Graphics and a Geforce 950m for gaming. The HDMI/display info and such goes through the Intel. I have found that after restarting the driver and losing HDMI audio, if I go to device manager > Sound, video and game controllers > Intel® Display Audio, and I click Update Driver > Browse my computer > Let me pick from list, install the standard "High Definition Audio Device" instead, the device shows back up in Sound as generic Digital Audio (HDMI) and I get sound again. Ok, cool. Click restart64.exe...still there. Cool. Click restart64.exe again to double check...and it's gone again. Ok, so I go back to Sound, video and game controllers, reinstall the old Intel® Display Audio driver. Audio pops back up as 49S405 (HDMI)...sometimes. Hit restart64.exe, gone again. Reinstall generic "High Definition Audio Device", it comes back until I hit restart64.exe 1-2 more times. It seems to either only work for one restart once changing the Intel Audio drivers, or it is completely random before it disappears again. I have no idea what is going on.
Running restart64.exe basically does the same thing as disabling and enabling the display adapters in the Device Manager, so if doing that also affects the sound, then I can't really do anything about it. What about if you reboot instead of running restart64.exe?
Find all posts by this user
Quote this message in a reply
06-06-2019, 04:50 AM
Post: #4060
RE: Custom Resolution Utility (CRU)
(06-05-2019 03:50 PM)ToastyX Wrote:  Running restart64.exe basically does the same thing as disabling and enabling the display adapters in the Device Manager, so if doing that also affects the sound, then I can't really do anything about it. What about if you reboot instead of running restart64.exe?

Rebooting essentially sets everything back to TV defaults - no EDID overrides. If I start up a game it upscales to 4k 30hz, I get HDMI audio back, etc. Same if I unplug-replug the HDMI cable or turn the TV off then back on. After any of those actions, I need to hit the restart exe to have my CRU settings applied and set the primary detailed resolution to 1080, which is then when HDMI audio disappears. No need to go back into CRU, I just have to hit restart64.exe. Is this abnormal?
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 148 Guest(s)