Custom Resolution Utility (CRU)

[Bertie_bassett]

(05-31-2022 05:38 PM)ToastyX Wrote:  TV resolutions are CTA-861 standard resolutions intended for TVs, while detailed resolutions let you define custom timing parameters. TV resolutions are supposed to include both refresh rates, but that's up to the driver. If the driver added both, you should see both 23 Hz and 24 Hz listed in the Windows display settings. It's not possible to define both with detailed resolutions because Windows will consider both to be 24 Hz and only use one of them. Is 1920x1080 @ 24 Hz available in the Windows display settings, and is it scaled correctly? If so, the problem is on Kodi's end. I can't make a generic .bin file because I don't know what your TV supports. Do you have a copy of the TV's original EDID and the changes you made?

Hi, sorry it's taken a while to get back to you. I have been doing some more playing, and here's where I am now. I simply cannot get any video player, whether Kodi or any of MPC-HC or BE +/- madvr, JRiver, any of them, to send a 1080p video at 1080p but a 2160p video at 2160p. However, I think I've narrowed down the issue to somewhere in my Intel Iris Plus 655 drivers. This is because when I play a 1080p file in Kodi, the render info (alt-o) shows me that 'surfaces' is set to 1920x1080p. This means that is what Kodi is outputting. However, my TV only ever reports receiving 2160p. The refresh rates reported by the screen change correctly to match the file. If I go into the Kodi whitelist and only select 2160p resolutions, then play a 1080p file, the 'surfaces' info changes to 3840x2160, indicating that Kodi's player is now doing the upscaling. So Kodi is not at fault.

I am using the very latest Intel drivers (v30.0.101.1994, dated 5/25/2022) downloaded from Intel here. The driver definitely added both 23 and 24 Hz modes as they are selectable in the windows display settings, and they scale correctly when I select those modes at both 1920x1080 and 3840x2160. But 'active display resolution' never changes from 3840x2160.

1. The EDID I am currently using is attached (current.bin). It's the default EDID applied by the HDMI splitter (one of these) that sits between the NUC and the display. I use this because I need it to send HD audio to my non-HDR capable receiver while still allowing me to send HDR to the display. HDR is currently working fine.

2. The second attachment (Q80T.bin) is the EDID that my system detects when I connect my Samsung Q80T display directly to the NUC, bypassing the splitter. This should tell windows all of the input modes my TV supports, but indicates that the display does not support any DTS audio codecs. However, when I use this EDID the same problems occur - the display only reports an input of 2160p resolutions, indicating that scaling is still taking place before the signal reaches my screen.

3. I've also attached my modified EDID (Q80T_edited) where I've added in the DTS audio codecs I need and removed any 4096 resolutions. The audio is working well and the screen capabilities should be the same as the original Q80T.bin.

With both the Q80T.bin and Q80T_edited.bin EDIDs in place I get some odd screen blanking every now and then. This is the main reason why I've reverted to the current.bin file attached.

My intel graphics command center settings are shown in the attached image. Changing RGB to 444 or 442 doesn't seem to help, neither does changing 8bpc to 12bpc. Maintain Display Scaling seems to be staying put now, but it still seems to me that my GPU is scaling 1080 images to 2160 before sending them to the TV. This is what I'm trying to disable!

What am I doing wrong?