Post Reply
Custom Resolution Utility (CRU)
01-10-2024, 07:23 PM (Last edited: 01-10-2024, 07:45 PM by Artasdmc)
Post: #7901
RE: Custom Resolution Utility (CRU)
(01-10-2024 05:43 PM)ToastyX Wrote:  
(01-09-2024 07:50 PM)Artasdmc Wrote:  Hey guys, I've asked everywhere else, but I forgot that this place is the best place to ask any questions regarding resolutions and etc.

I've just snagged a used LG B7 Oled in great condition, no retention or burn in. Just a tiny amount of pixels in the corner that fade to black once it heats up, which is probably an overheating issue that I could solve by taking the shell and getting a some fans or something.

So anyways, it's HDMI 2.0 only. I'm wondering what useful I can do with it.
I want to get 1440p/120hz, but when I enabled it through Nvidia panel HDR doesn't work properly, screen is overblown, darks are gray and I think it's stuck at only 8bit rgb.

What would be the best resolutions, colour depth and format for an OLED?
And how do I even change colour depth and format in CRU?
NVIDIA control panel custom resolutions are always RGB. You can try adding 2560x1440 @ 120 Hz with CRU and see if you get a different result. Color depth and formats are defined in the HDMI data blocks, but they are not resolution-specific except for 4:2:0, so you shouldn't need to change anything related to color formats in CRU.

Thanks. Really appreciate your work and dedication to the community behind it.



I've just tried it, I've cleared all custom resolutions in Nvidia control panel using NvCRBT as I couldn't delete them for some reason. Unistalled monitor driver in manager and restarted.

Set up a custom resolution in CRU 2560x1440 @ 120Hz using automatic HDTV and automatic native HDTV and both fail. LG tv shows invalid format on screen. Any idea?

Sorry to be bothersome.
Find all posts by this user
Quote this message in a reply
01-10-2024, 08:29 PM
Post: #7902
RE: Custom Resolution Utility (CRU)
(01-10-2024 07:23 PM)Artasdmc Wrote:  I've just tried it, I've cleared all custom resolutions in Nvidia control panel using NvCRBT as I couldn't delete them for some reason. Unistalled monitor driver in manager and restarted.

Set up a custom resolution in CRU 2560x1440 @ 120Hz using automatic HDTV and automatic native HDTV and both fail. LG tv shows invalid format on screen. Any idea?
What timing parameters did you use with the NVIDIA control panel? The same timing parameters should work with CRU.
Find all posts by this user
Quote this message in a reply
01-10-2024, 09:51 PM
Post: #7903
RE: Custom Resolution Utility (CRU)
(01-10-2024 08:29 PM)ToastyX Wrote:  
(01-10-2024 07:23 PM)Artasdmc Wrote:  I've just tried it, I've cleared all custom resolutions in Nvidia control panel using NvCRBT as I couldn't delete them for some reason. Unistalled monitor driver in manager and restarted.

Set up a custom resolution in CRU 2560x1440 @ 120Hz using automatic HDTV and automatic native HDTV and both fail. LG tv shows invalid format on screen. Any idea?
What timing parameters did you use with the NVIDIA control panel? The same timing parameters should work with CRU.

I am unsure, because it was set to automatic in there as well.
Also I've tried changing it 120hz in nvidia panel again and it wasn't working. I've later realized that for some reason first I need to apply a 120hz profile. The highest one available is 1080p, so afterwards I edited resolution on that profile to 1440p and it works like it did before.

I've changed color settings to 4:2:2 8 bit, that's the only one working with HDR, at least I think it's working because it's not washed out. The rest have the washed out screen. It is the same on 1080P regular preset. HDR only works at 8 bit 4:2:2.

At native 4K/60 every single color profile and depth work fine, 4:2:2, 4:4:4, 4:2:0. No matter the depth, 8bit, 10bit, or 12bit.

How do I read timing parameters from Nvidia panel so I can apply them to CRU?
I don't think this is a cable issue as 4K60 with 4:2:0 12 bit would use up more bandwith than 4:2:2 8bit 1440/120 no?
Find all posts by this user
Quote this message in a reply
01-10-2024, 10:07 PM
Post: #7904
RE: Custom Resolution Utility (CRU)
(01-10-2024 09:51 PM)Artasdmc Wrote:  I am unsure, because it was set to automatic in there as well.
Also I've tried changing it 120hz in nvidia panel again and it wasn't working. I've later realized that for some reason first I need to apply a 120hz profile. The highest one available is 1080p, so afterwards I edited resolution on that profile to 1440p and it works like it did before.
That's not a true 2560x1440. You're scaling down to 1920x1080, which is then scaled up to 3840x2160 by the TV, so it's being scaled twice. The NVIDIA control panel shows the timing parameters when you create the custom resolution. The active pixels is what is actually sent to the display, so if the resolution at the top doesn't match the active pixels, it's being scaled by the GPU. Windows will also show you the desktop resolution vs. the active signal resolution in the advanced display settings. Based on what I've read from searching, the LG B7 doesn't support 2560x1440 @ 120 Hz, only 1920x1080 @ 120 Hz.
Find all posts by this user
Quote this message in a reply
01-10-2024, 10:11 PM
Post: #7905
RE: Custom Resolution Utility (CRU)
(01-10-2024 10:07 PM)ToastyX Wrote:  
(01-10-2024 09:51 PM)Artasdmc Wrote:  I am unsure, because it was set to automatic in there as well.
Also I've tried changing it 120hz in nvidia panel again and it wasn't working. I've later realized that for some reason first I need to apply a 120hz profile. The highest one available is 1080p, so afterwards I edited resolution on that profile to 1440p and it works like it did before.
That's not a true 2560x1440. You're scaling down to 1920x1080, which is then scaled up to 3840x2160 by the TV, so it's being scaled twice. The NVIDIA control panel shows the timing parameters when you create the custom resolution. The active pixels is what is actually sent to the display, so if the resolution at the top doesn't match the active pixels, it's being scaled by the GPU. Windows will also show you the desktop resolution vs. the active signal resolution in the advanced display settings. Based on what I've read from searching, the LG B7 doesn't support 2560x1440 @ 120 Hz, only 1920x1080 @ 120 Hz.

Aww, damn it. Thanks for clearing that up. So I'll just stick to 4k/60 and 1080/120 for other occasions. Maybe you also know why other depths and colour profiles don't work even on 1080p 120?
Find all posts by this user
Quote this message in a reply
01-14-2024, 02:33 AM
Post: #7906
RE: Custom Resolution Utility (CRU)
(01-10-2024 10:11 PM)Artasdmc Wrote:  Aww, damn it. Thanks for clearing that up. So I'll just stick to 4k/60 and 1080/120 for other occasions. Maybe you also know why other depths and colour profiles don't work even on 1080p 120?
The problem with HDR at 120 Hz is an issue specific to the LG B7. The LG C7 also has the same problem according to RTINGS.
Find all posts by this user
Quote this message in a reply
01-14-2024, 05:33 PM
Post: #7907
RE: Custom Resolution Utility (CRU)
Hi, i posted this before as separate thread but i see more people here so ill try asking, maybe someone can help me.

So i have Lenovo Legion GO Handheld, it has AMD 780m
Its 16:10 device and by default it came with x3 resolutions in windows settings and 3 resolutions in Lenovo Pop-up overlay
1600p, 1200p, 800p,

After windows update [I assume thats what happened], i now have a bunch of unnecessary 16:9 resolutions
I tried safe boot, driver cleaner > fresh driver, no help


these are the resolutions that appeared, they all 16:9:
1440p, 1080p, 1000p, 900p, 720p

I cant choose "hide unsupported resolutions" since it uses windows default driver and that option is grayed out.

Whats even stranger is that CRU in all its settings only shows single resolution 1600 x 2560 [its portrait display]
It doesn't even show the 2 others: 1200p and 800p so no idea where they coming from.

I also downloaded SRU, and chose delete all option, zero effect

What im looking for is either:
People that know where to delete resolutions in assuming windows registry [because i have a reg file thata dds 1050 resolution so i think they all hidden somewhere in the registry?]
Or help creating custom monitor.inf file with just the supported resolutions, also maybe its possible to edit the inf with monitor actual name from CRU so windows thinks its actual real driver? this way "hide unsupported resolutions" will appear
Also maybe someone know the registry location for "hide unsupported resolutions" to force this option? will be easiest solution

P.S. this display is strange, it just has 60hz and 144hz, i tried adding 120hz with CRU, it works but touch function gets disabled
Find all posts by this user
Quote this message in a reply
01-14-2024, 07:51 PM
Post: #7908
RE: Custom Resolution Utility (CRU)
(01-09-2024 07:50 PM)Artasdmc Wrote:  Hey guys, I've asked everywhere else, but I forgot that this place is the best place to ask any questions regarding resolutions and etc.

I've just snagged a used LG B7 Oled in great condition, no retention or burn in. Just a tiny amount of pixels in the corner that fade to black once it heats up, which is probably an overheating issue that I could solve by taking the shell and getting a some fans or something.

So anyways, it's HDMI 2.0 only. I'm wondering what useful I can do with it.
I want to get 1440p/120hz, but when I enabled it through Nvidia panel HDR doesn't work properly, screen is overblown, darks are gray and I think it's stuck at only 8bit rgb.

What would be the best resolutions, colour depth and format for an OLED?
And how do I even change colour depth and format in CRU?

Hi,
I been OLED "monitor" user since 2016 C6P>C9>s96B

For your model, if you want 4K + HDR you must set it to 4:2:2 + 10bit or if it doesn't work 4:2:0
If you run 8BIT and turn on HDR thats not real HDR, its dithered HDR and you just lose all of its glory, especially on OLED which is 10bit

For movies and video games, there is zero visible difference when 4:2:2/4:2:0 is enabled
The official HDR standard for movies is 10bit 4:2:0, thats how UHD blurays encoded
So it looks ok, you have nothing to worry, the only issue is if you decide to keep it for windows youll have text a bit strange, but if you manage to use 4:2:2+10bit its not that bad even in windows.

Just dont forget to enable game mode and honestly the 4:2:2 mode 60Hz 4K + HDR was great, i been gaming like that for years until C9 came out with HDMI 2.1, had no reason to upgrade to C7/C8

The 9 series is the first with official 1440p support, before it had no offical 1440p
Find all posts by this user
Quote this message in a reply
01-15-2024, 03:59 PM (Last edited: 01-15-2024, 04:15 PM by fan_of_cru)
Post: #7909
RE: Custom Resolution Utility (CRU)
Hello ToastyX,

first of all, thank you very much for your work and effort to create the CRU tool. Heart

I would like to use the latest version 1.5.2 and downloaded it from your site.

As always, I scanned all downloaded files via virustotal.com before I executed them.

By this, I discovered that some of your executables are reported as "suspicious" by some scanners at virustotal.

For example the "reset-all.exe" is flagged as "W32.AIDetectMalware" by Bkav Pro and
"Generic.Malware" by TEHTRIS.

The "CRU.exe" is flagged as "Trojan.Malware.300983.susgen" by MaxSecure.

Most probably they are false positives.

Do you know why these engines detect these potential threads within your executables?

Additionally filescan.io e.g. reports for "CRU.exe" (version 1.5.2):
Code:
Malicious:
* imports APIs commonly found in keyloggers
* imports APIs used for code injection (PowerLoader)
* imports APIs used to take screenshots

--------

Unexpected was, that the "behaviour analysis" by virustotal.com reports that "CRU.exe" connects to the following IPs:
Code:
104.86.182.43:443 (TCP)
104.86.182.8:443 (TCP)
13.107.4.50:80 (TCP)
131.253.33.203:80 (TCP)
168.62.242.76:443 (TCP)
184.25.191.235:443 (TCP)
192.168.0.1:137 (UDP)
192.168.0.40:137 (UDP)
192.168.0.53:137 (UDP)
192.168.0.85:137 (UDP)
192.229.211.108:80 (TCP)
20.22.113.133:443 (TCP)
20.62.24.77:443 (TCP)
20.69.140.28:443 (TCP)
20.80.129.13:443 (TCP)
20.96.52.198:443 (TCP)
20.99.132.105:443 (TCP)
20.99.133.109:443 (TCP)
20.99.184.37:443 (TCP)
20.99.185.48:443 (TCP)
20.99.186.246:443 (TCP)
23.209.116.25:443 (TCP)
23.209.116.9:443 (TCP)
23.216.147.62:443 (TCP)
23.216.147.64:443 (TCP)
23.216.147.76:443 (TCP)
23.216.81.152:80 (TCP)
23.40.197.184:443 (TCP)
52.154.209.174:443 (TCP)
52.184.215.140:443 (TCP)
a83f:8110:0:0:0:0:100:0:53 (UDP)
a83f:8110:0:0:0:0:2002:0:53 (UDP)
a83f:8110:0:0:100:0:1800:0:53 (UDP)
a83f:8110:0:0:1400:1400:2800:3800:53 (UDP)
a83f:8110:0:0:1b00:100:2800:0:53 (UDP)
a83f:8110:0:0:2000:0:0:0:53 (UDP)
a83f:8110:0:0:2000:0:400:0:53 (UDP)
a83f:8110:0:0:2098:5d75:dc02:0:53 (UDP)
a83f:8110:0:0:5800:0:0:0:53 (UDP)
a83f:8110:0:0:beac:bf78:cce1:d301:53 (UDP)
a83f:8110:0:0:e600:0:0:0:53 (UDP)
a83f:8110:0:200:0:0:0:0:53 (UDP)
a83f:8110:1002:0:181e:bb90:1002:0:53 (UDP)
a83f:8110:100:ae00:ae:a6:0:0:53 (UDP)
a83f:8110:101:1ff:101:1ff:101:1ff:53 (UDP)
a83f:8110:1212:12ff:1313:13ff:1414:14ff:53 (UDP)
a83f:8110:1cad:0:c0b3:0:3c77:100:53 (UDP)
a83f:8110:202:2ff:202:2ff:202:2ff:53 (UDP)
a83f:8110:2800:1800:4000:1800:1800:100:53 (UDP)
a83f:8110:3202:0:6862:eaac:fe7f:0:53 (UDP)
a83f:8110:4747:47ff:4747:47ff:4747:47ff:53 (UDP)
a83f:8110:766b:b00:2600:0:5803:3900:53 (UDP)
a83f:8110:80a:14ff:709:13ff:409:12ff:53 (UDP)
a83f:8110:8401:0:2075:2cc:8401:0:53 (UDP)
a83f:8110:89d7:ffff:e00:0:0:0:53 (UDP)
a83f:8110:8c31:da01:beac:bf78:cce1:d301:53 (UDP)
a83f:8110:9802:100:0:a007:0:800:53 (UDP)
a83f:8110:c000:0:c800:0:0:0:53 (UDP)
a83f:8110:cc03:0:0:0:cc03:0:53 (UDP)
a83f:8110:cce1:d301:1bbb:ccef:3fc:d801:53 (UDP)

And performs the following DNS Resolutions:
Code:
fp2E7A.wpc.2BE4.phicdn.net
fp2e7a.wpc.phicdn.net
prda.aadg.msidentity.com
query.prod.cms.rt.microsoft.com
www.microsoft.com

The "behaviour analysis" by virustotal.com reports that "reset-all.exe" connects to the following IPs:
Code:
13.107.4.50:80 (TCP)
131.253.33.203:80 (TCP)
192.168.0.18:137 (UDP)
192.229.211.108:80 (TCP)
20.80.129.13:443 (TCP)
20.99.132.105:443 (TCP)
20.99.133.109:443 (TCP)
20.99.184.37:443 (TCP)
20.99.185.48:443 (TCP)
20.99.186.246:443 (TCP)
23.216.147.62:443 (TCP)
23.216.147.64:443 (TCP)
23.216.147.76:443 (TCP)
23.34.172.81:443 (TCP)
23.40.197.184:443 (TCP)
a83f:8110:0:0:100:0:1800:0:53 (UDP)
a83f:8110:0:0:1b00:100:2800:0:53 (UDP)
a83f:8110:0:0:4788:21:0:0:53 (UDP)
a83f:8110:0:0:700:700:2800:4000:53 (UDP)
a83f:8110:300:0:300:0:5830:24a7:53 (UDP)
a83f:8110:3ec5:559b:c930:3c06:a2b:601:53 (UDP)
a83f:8110:407:bff:205:aff:104:9ff:53 (UDP)
a83f:8110:61be:81d8:14c4:3415:eee5:572b:53 (UDP)
a83f:8110:6300:6100:7400:6900:6f00:6e00:53 (UDP)
a83f:8110:911:18ff:a12:19ff:50d:14ff:53 (UDP)
a83f:8110:ccf4:d801:346e:2282:ccf4:d801:53 (UDP)
a83f:8110:fce1:b48:324f:e6eb:b8ad:4fe4:53 (UDP)

I can't understand why these files have to connect to (so many) internet servers.

I would have expected that there's no traffic at all.

Why is this the case and what data is beeing transmitted?

It would help me a lot to understand why there's so much network traffic in order to know if it is intended like this and to know what data is received/sent from/to my computer if I use your tool.

I hope you understand these questions. Most likely you also would scan/analyse any downloaded software before executing it.

As stated above this all are most likely false positives and there's probably a good reason why your tools contact the above mentioned IPs.

I just want to understand why this is the case.

Thank you very much! Heart
Find all posts by this user
Quote this message in a reply
01-15-2024, 05:11 PM
Post: #7910
RE: Custom Resolution Utility (CRU)
(01-15-2024 03:59 PM)fan_of_cru Wrote:  I would like to use the latest version 1.5.2 and downloaded it from your site.

As always, I scanned all downloaded files via virustotal.com before I executed them.

By this, I discovered that some of your executables are reported as "suspicious" by some scanners at virustotal.

For example the "reset-all.exe" is flagged as "W32.AIDetectMalware" by Bkav Pro and
"Generic.Malware" by TEHTRIS.

The "CRU.exe" is flagged as "Trojan.Malware.300983.susgen" by MaxSecure.

Most probably they are false positives.

Do you know why these engines detect these potential threads within your executables?
Because they are dumb. There is always some false positive by some obscure antivirus or some automatic heuristics algorithm. Even when I go through the trouble of reporting the false positive (and some of these companies are hard to contact), some new one eventually pops up a few months later, so I don't bother unless it's a major antivirus program. https://blog.nirsoft.net/2009/05/17/anti...evelopers/


(01-15-2024 03:59 PM)fan_of_cru Wrote:  I can't understand why these files have to connect to (so many) internet servers.

I would have expected that there's no traffic at all.

Why is this the case and what data is beeing transmitted?

It would help me a lot to understand why there's so much network traffic in order to know if it is intended like this and to know what data is received/sent from/to my computer if I use your tool.
None of the included executable files make any connections or transmit any data. Those are mostly Microsoft IP addresses and DNS servers. Likely they are recording all IP traffic when running the program including whatever Windows does in the background. You can try any program such as C:\Windows\notepad.exe and it will report IP traffic.
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


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