|
Custom Resolution Utility (CRU)
|
|
11-01-2025, 05:32 PM
Post: #9281
|
|||
|
|||
|
RE: Custom Resolution Utility (CRU)
Hy, i have a special problem i hope you can help me.
I use CRU to make a custom rezolution for a secondary monitor what is connected to one Microsoft Surface pro 9, exactly to make refresh rate. The problem now is in whatsapp pc app when i share screen and select display 1 (surface 9 display) dont work(the other persone dont see nothing just a loading stream), if i share display2 (auxiliary monitor) work. I disconect the second monitor still dont work when i share the surface display. The default rezolution of Surface 9 is 2880x1920 120Hz, i change to a lower rezolution and works, i put a bigger rezolution what display not support and is a black screen but share screen on whatsapp works, so the problem is this rezolution what is default 2880x1920. Before use CRU works. The files reset-all dont work i delete the registry cache of the monitors, i delete the entry from device manager, i try all i know and nothing work. I test on discord works , something happens on whatsapp. I uninstall ,repair, older version all the stuff with whatsapp still dont work. If somebody help me without installing the windows i will appreciate. Thanks |
|||
|
|
11-01-2025, 10:20 PM
Post: #9282
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-01-2025 05:32 PM)lex4life Wrote: Hy, i have a special problem i hope you can help me.I honestly don't understand how that could happen. CRU doesn't do anything that should affect WhatsApp in that way. That seems like a bug in WhatsApp, but I don't understand how CRU could have triggered it, especially since you didn't edit the primary display with the problem, and the secondary display that you edited still works fine. If this were a display settings issue, then running reset-all.exe and rebooting should have resolved it. This is something you should ask WhatsApp support about. The only thing left to try is to reinstall Intel's graphics driver after using DDU: https://www.wagnardsoft.com/display-driv...taller-ddu |
|||
|
|
|
11-02-2025, 12:34 PM
Post: #9283
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-01-2025 10:20 PM)ToastyX Wrote:(11-01-2025 05:32 PM)lex4life Wrote: Hy, i have a special problem i hope you can help me.I honestly don't understand how that could happen. CRU doesn't do anything that should affect WhatsApp in that way. That seems like a bug in WhatsApp, but I don't understand how CRU could have triggered it, especially since you didn't edit the primary display with the problem, and the secondary display that you edited still works fine. If this were a display settings issue, then running reset-all.exe and rebooting should have resolved it. This is something you should ask WhatsApp support about. The only thing left to try is to reinstall Intel's graphics driver after using DDU: https://www.wagnardsoft.com/display-driv...taller-ddu Thanks, yes i think this is the last choise with DDU if still not working must to reinstall the windows. I come back with feedback if works. Have a nice day . |
|||
|
|
|
11-03-2025, 06:28 PM
Post: #9284
|
|||
|
|||
|
RE: Custom Resolution Utility (CRU)
Im playing with a TCL 34R83Q. Specs: https://www.tcl.com/eu/en/monitors/34r83q
Situation: TCL pulled a smooth brain move and only allowed 60hz 10 bit (100 hz 8 bit) at 3440x1440 with HDMI 2.1. No clue why they'd put limitations like that when DP 1.4 goes up to 170hz 8 bit (180 when overclocked). To maintain 10 bit (yes i know its FRC but it doesnt hurt), i dropped it down to 156 in CRU which works well. Id like to use the full HDMI 2.1 potential with 10 bit. I cant figure it out in CRU, though. Where should i focus to get the higher refresh rates applied? Atm, anything over 120 under the detailed section is RED, even after increasing the limits in the HDMI 2.1 block like FRL etc. Image 1: https://postimg.cc/CByth3Sd |
|||
|
|
|
11-03-2025, 10:47 PM
Post: #9285
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-03-2025 06:28 PM)b0uncyfr0 Wrote: Im playing with a TCL 34R83Q. Specs: https://www.tcl.com/eu/en/monitors/34r83qHDMI 2.x without FRL only supports up to 600 MHz pixel clock for 8 bpc and 480 MHz for 10 bpc with 4:4:4 chroma. You can't add FRL if it's not already supported because it's a totally different signaling method. EDID detailed resolutions are limited to 655.35 MHz pixel clock, so you would need to use a DisplayID extension block for higher refresh rates, but that won't get around HDMI limitations. |
|||
|
|
|
Yesterday, 05:35 AM
Post: #9286
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(11-03-2025 10:47 PM)ToastyX Wrote: HDMI 2.x without FRL only supports up to 600 MHz pixel clock for 8 bpc and 480 MHz for 10 bpc with 4:4:4 chroma. You can't add FRL if it's not already supported because it's a totally different signaling method. EDID detailed resolutions are limited to 655.35 MHz pixel clock, so you would need to use a DisplayID extension block for higher refresh rates, but that won't get around HDMI limitations. The spec page does say : HDMI in max bandwith 48G (FRL) but this doesnt seem to be the case in CRU. Why would they use HDMI 2.1 and then completely nerf it? |
|||
|
|
|
Yesterday, 04:05 PM
Post: #9287
|
|||
|
|||
RE: Custom Resolution Utility (CRU)
(Yesterday 05:35 AM)b0uncyfr0 Wrote: The spec page does say : HDMI in max bandwith 48G (FRL) but this doesnt seem to be the case in CRU.Seems like a mistake. The specs say HDMI is limited to 100 Hz. If they were using FRL, there would be no need to limit HDMI to 100 Hz. |
|||
|
|
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 151 Guest(s)