Custom Resolution Utility (CRU)

[Vikto0r]

Dear forum users.
My question is, is there any way to give the exact frequency with cru?
Example (2 pc stream setup with capture card. Passthrough .) :

-240hz gamer monitor almost 240hz cru exact using https://ibb.co/9ZKCPdq
-60hz stream pc : 59.997601hz --> exact using cru. with other options 60.000360 etc. never accurate

I want 240.000000 and 60.000000hz, is this possible?

Why?
When streaming. when recording. there is periodic choppy stutter in the recording and in the stream too. in my opinion, my guess is that the hz differences cause this.

important: note. obs 60fps, game 60 fps . no dropped frames or overload. checked

Thanks in advance:
I would be grateful if you could help me with this, I have been suffering with this for years and have already gone through a million tests and settings

[ToastyX]

(12-12-2024 11:57 AM)Vikto0r Wrote:  Dear forum users.
My question is, is there any way to give the exact frequency with cru?
Example (2 pc stream setup with capture card. Passthrough .) :

-240hz gamer monitor almost 240hz cru exact using https://ibb.co/9ZKCPdq
-60hz stream pc : 59.997601hz --> exact using cru. with other options 60.000360 etc. never accurate

I want 240.000000 and 60.000000hz, is this possible?

Why?
When streaming. when recording. there is periodic choppy stutter in the recording and in the stream too. in my opinion, my guess is that the hz differences cause this.

important: note. obs 60fps, game 60 fps . no dropped frames or overload. checked

Thanks in advance:
I would be grateful if you could help me with this, I have been suffering with this for years and have already gone through a million tests and settings

"Exact" is mathematically exact, but hardware timing and measurements may not be. That wouldn't solve your problem anyway. The monitor's refresh rate is different from the game's frame rate which is different from the recording's frame rate. Even if the monitor's refresh rate were exact, how can you guarantee the game's frame rate and the recording's frame rate are also exact? Even that's not enough because they all have to be perfectly synchronized with when the GPU has a new frame ready, not just have the same rate.

If you are using vsync, that alone can cause stutter if the game's frame rate is also capped to the monitor's refresh rate. Vsync should be used without frame rate caps since it already acts as a frame rate cap, but that might not be possible for games that only support 60 FPS. If you are using G-SYNC, that will synchronize the monitor's refresh rate to the game's frame rate, but the game might have fluctuations that would mess up the timing. That's just for synchronizing the monitor's refresh rate with the game's frame rate. The recording would also have to be perfectly synchronized to avoid stutter, and the video player would also have to be perfectly synchronized to play it smoothly. There's just too much that has to go right for this to work perfectly, and I'm not sure it's possible unless the recording software has some way to synchronize perfectly with the monitor.

If you want to reduce stutter, the best way is to not try to synchronize everything. Run your monitor at the highest refresh rate (240 Hz I assume) and avoid vsync, but you can use G-SYNC. Cap the game's frame rate to something higher than the recording's frame rate, like 90 FPS. If you want to use vsync instead, then you'd need to use a refresh rate like 90 Hz instead of using a frame rate cap. Those options wouldn't be as smooth as a perfectly synchronized recording, but that would avoid the periodic stutter you're seeing, except for games that are stuck at 60 FPS. In that case, maybe recording at 50 FPS would help.

[ToastyX]

(12-12-2024 05:49 AM)LoveTilapia Wrote:  How do people normally check for DSC?

They don't unless the monitor has a way to report if DSC is active.

[Vikto0r]

(12-12-2024 04:20 PM)ToastyX Wrote:  

(12-12-2024 11:57 AM)Vikto0r Wrote:  Dear forum users.
My question is, is there any way to give the exact frequency with cru?
Example (2 pc stream setup with capture card. Passthrough .) :

-240hz gamer monitor almost 240hz cru exact using https://ibb.co/9ZKCPdq
-60hz stream pc : 59.997601hz --> exact using cru. with other options 60.000360 etc. never accurate

I want 240.000000 and 60.000000hz, is this possible?

Why?
When streaming. when recording. there is periodic choppy stutter in the recording and in the stream too. in my opinion, my guess is that the hz differences cause this.

important: note. obs 60fps, game 60 fps . no dropped frames or overload. checked

Thanks in advance:
I would be grateful if you could help me with this, I have been suffering with this for years and have already gone through a million tests and settings

"Exact" is mathematically exact, but hardware timing and measurements may not be. That wouldn't solve your problem anyway. The monitor's refresh rate is different from the game's frame rate which is different from the recording's frame rate. Even if the monitor's refresh rate were exact, how can you guarantee the game's frame rate and the recording's frame rate are also exact? Even that's not enough because they all have to be perfectly synchronized with when the GPU has a new frame ready, not just have the same rate.

If you are using vsync, that alone can cause stutter if the game's frame rate is also capped to the monitor's refresh rate. Vsync should be used without frame rate caps since it already acts as a frame rate cap, but that might not be possible for games that only support 60 FPS. If you are using G-SYNC, that will synchronize the monitor's refresh rate to the game's frame rate, but the game might have fluctuations that would mess up the timing. That's just for synchronizing the monitor's refresh rate with the game's frame rate. The recording would also have to be perfectly synchronized to avoid stutter, and the video player would also have to be perfectly synchronized to play it smoothly. There's just too much that has to go right for this to work perfectly, and I'm not sure it's possible unless the recording software has some way to synchronize perfectly with the monitor.

If you want to reduce stutter, the best way is to not try to synchronize everything. Run your monitor at the highest refresh rate (240 Hz I assume) and avoid vsync, but you can use G-SYNC. Cap the game's frame rate to something higher than the recording's frame rate, like 90 FPS. If you want to use vsync instead, then you'd need to use a refresh rate like 90 Hz instead of using a frame rate cap. Those options wouldn't be as smooth as a perfectly synchronized recording, but that would avoid the periodic stutter you're seeing, except for games that are stuck at 60 FPS. In that case, maybe recording at 50 FPS would help.

Dear ToastyX.
Thank you for an honorable and meaningful answer. I will consider what you have written.

[LoveTilapia]

I am pretty sure those clock gens are affected by temperature as well. So they might cycle a little faster or slower after it warms up.

---

(12-12-2024 04:21 PM)ToastyX Wrote:  

(12-12-2024 05:49 AM)LoveTilapia Wrote:  How do people normally check for DSC?

They don't unless the monitor has a way to report if DSC is active.

Thanks for the help ToastyX, Damn this DSC world we live in.

[DmitriyBlade]

Only after i select "3. enable settings for selected display model" in nvidia
i was able to overclock further than my monitor default 165hz to 182hz(if i change it to 166 it starts artifacting)
If i overclock via nvidia custom resolution, my max was 174hz(if i set 175hz ask do i want to save - yes, and it won't save)

i copied settings from 165hz profile, changed only refresh rate to 182hz, seems working fine so far

Question:
1)Does messing around with Front porct/Sync width/Back porch etc gives you any latency decrease?
(or i should only use refresh rate overclock)
2)My Display cable kinda old(from previous monitor), but quite lengthy, if i order a new one, can i improve my 182hz limit further?

ps seems good for 200$ china 3440x1440 34' IPS display

[stej]

I'm trying to edit a block that's not editable with cru (greyed out).
The only solution I see is exporting a .bin dump of the edid and editing that block with an external editor.
The problem is that the edid reported by the monitor is not fixed from what I can see.
When I change certain settings on the monitor, the reported edid changes. I dumped the edid between such setting changes and verified that the binary files are different.

Am I correct to assume that if I import an edited edid with cru, it will override everything the monitor reports, essentially nullifying the monitor's ability to switch configurations?
And if so, is there a workaround for changing the specific block only and not affecting anything else?

[ToastyX]

(12-13-2024 10:40 AM)stej Wrote:  Am I correct to assume that if I import an edited edid with cru, it will override everything the monitor reports, essentially nullifying the monitor's ability to switch configurations?

That would depend on what the graphics driver considers a unique monitor. Usually each EDID would be considered a different monitor, so you can override just one of the EDIDs.

[ToastyX]

(12-13-2024 04:13 AM)DmitriyBlade Wrote:  Question:
1)Does messing around with Front porct/Sync width/Back porch etc gives you any latency decrease?
(or i should only use refresh rate overclock)
2)My Display cable kinda old(from previous monitor), but quite lengthy, if i order a new one, can i improve my 182hz limit further?

1. Latency would depend on when the frame is rendered. If you're using G-SYNC, you don't need to change the timing parameters because the vertical blanking is automatically adjusted to wait until the next frame is ready.
2. Overclocking is usually limited by the monitor. Cable would only be an issue if you're getting signal dropouts.

[stej]

(12-13-2024 02:25 PM)ToastyX Wrote:  

(12-13-2024 10:40 AM)stej Wrote:  Am I correct to assume that if I import an edited edid with cru, it will override everything the monitor reports, essentially nullifying the monitor's ability to switch configurations?

That would depend on what the graphics driver considers a unique monitor. Usually each EDID would be considered a different monitor, so you can override just one of the EDIDs.

I don't see additional monitors created in Enum\Display in the registry, so I guess not, it only updates the EDID.
Comparing the contents of the exported .bin files I see that the first part of the file, presumably the EDID base, remains constant. What changes is the extension blocks. Which explains why it's not detecting additional monitors I suppose.

So, from your reply it seems that my assumption was correct. How about workarounds? The block I want changed is always present in every reported configuration and its contents remain static.

Any ideas for overriding a couple bytes and letting everything else pass through?