Optimal Strobe Utility Settings at 120Hz

[Chief Blur Buster]

Over time, I found these were optimal settings for Blur Busters Strobe Utility.
The Crosstalk setting changes at different refresh rates, and whether or not the Vertical Total 1350 tweak is done.
Less ghosting occurs at lower refresh rates (e.g. 100Hz instead of 120Hz).


1920x1080p 120Hz, optimized for bright & pretty clear

Similiar to LightBoost=100% or a bit brighter

1. First, do the "Vertical Total 1350" Tweak.
2. In Strobe Utility, enable "Override"
3. Set "Persistence" to 2.0ms or a bit higher
4. Set "Crosstalk" to leftmost (setting 0)


1920x1080p 120Hz, optimized for similarity to LightBoost=10%

Similiar To LightBoost=10%, including improved clarity and less brightness

1. First, do the "Vertical Total 1350" Tweak.
2. In Strobe Utility, enable "Override"
3. Set "Persistence" to 1.0ms
4. Set "Crosstalk" less than 1 tick upwards (1 position up).


1920x1080p 120Hz, optimized for clearest motion, but very dim

Sharper & Clearer Than LightBoost=10%, but dimmer

1. First, do the "Vertical Total 1350" Tweak.
2. In Strobe Utility, enable "Override"
3. Set "Persistence" to 0.5ms
4. Set "Crosstalk" to first tick (3 clicks up)

NOTE: Benefits of 0.5ms persistence is extremely hard to see. To see benefits of 0.5ms persistence, you will need to use very fast motion tests (e.g. 1920 pixels/second and faster), and it only reduces motion blur by about 1 pixel during full-screen-width-per-second motion. It is usually better to aim for brighter picture, as in LightBoost 10% vs 50% vs 100%.

[Mouzuone]

Would some settings change for a lightboost equivalent at 125Hz?

[Chief Blur Buster]

Would some settings change for a lightboost equivalent at 125Hz?

125Hz is very close to 120Hz, so the settings will be almost identical.
Maybe one notch movement to realign the "Crosstalk" (ghosting zone) slightly.

You may become unable to do the "Vertical Total 1350" trick above 120Hz, so you may have to use a lower Vertical Total such as 1300, because VT1350 at 120Hz actually uses more bandwidth than 144Hz! In addition, I just received a message from a user that Vertical Total 1500 is possible on the XL2411Z, but is not possible on the XL2720Z.

[eight]

Btw how come 144hz is dimmer than 120hz with the same persistence? Shouldn't 144x1ms strobes be brighter than 120x1ms strobes?

[Chief Blur Buster]

Btw how come 144hz is dimmer than 120hz with the same persistence? Shouldn't 144x1ms strobes be brighter than 120x1ms strobes?

Yes, that's correct. And that's what happens.

However, the VT1350 trick (not available at 144Hz) apparently widen the strobe length adjustment range significantly, so you can get a brighter image at 120Hz than at 144Hz. You have more time for a longer strobe during a longer blanking interval, before the strobe crosstalk becomes distracting.

[Falkentyne]

Chief,

There may need to be an extra step to make this work correctly at 120hz, depending on the default timings and totals being shown in CRU (it may be very possible that AMD cards are setting different total pixels/lines and porch and sync widths than Geforces.

The default AMD timings are much too high (although they work for 100 hz up to 1500 vertical total just fine).

I was wondering why I was getting massive crosstalk at 120hz even with the fixes, which (apparently) were only working at 100hz.
Here's what I found out:

1) setting vertical total to 1350 at 120hz originally was not working at ALL-the driver was using the stock settings, until I used toasty'x's pixel rate patcher (because the pixel clock was 356).
I then set it to 120hz and noticed massive screen shimmering (crosstalk was almost 100% gone though). The pixel clock being used was 356 MHz(!)

Then I noticed the timings were completely different than shown in the screenshot:

The AMD card was defaulting to these:
1920/1080
front porch 88/4
Sync width 44/5
(Back porch and blanking didn't seem to matter)
Total 2250 pixels and 1125 lines.

Changing 1125 to 1350 at 120 hz would corrupt the panel screen with these settings (356 MHz pixel clock).
However using these exact same settings at 100 hz and a 1500 vertical total (330 MHz pixel clock) was flawless with pristine crosstalk improvement.

For 120hz, you need to change the timings to match the screenshot on the 1350 tweak page:
Change front porch to 48/3
Sync width to 32/5
total to 2080/1125 (instead of 2250/1125), then change 1125->1350
and it works great.

However using 100hz and the original (AMD default) other timings with 1500 vertical total (2250 pixels) is even **BETTER**. (1600 goes out of sync; you may be able to use 1600+ if you use the lower 120hz settings as above).

Set crosstalk to leftmost or 1 notch to the right from left most and persistence to 1.0ms and enjoy

[Mouzuone]

What were the settings in CRU (or Nvidia CP) that you used for 120hz? 1500/120hz vertical total is WAY too high and just makes the monitor go out of sync at 120hz (pixel bandwidth is over 350 MHz, 330 is the driver limit unpatched) while its either 312mhz (will always work) or 330 MHz bandwith (may need the patch) at 100hz (depending on if you used 2080/1500 (for 24") or 2200/1500 for 27". You may still need a patch if it's 330.00 MHz at 100hz.

Are you sure that 1500 is actually working? Check the pixel bandwidth; if it's higher than 329 MHz, your VT's probably didn't work at all, as the driver ignored them (I'm suspicious because there should be no way you got VT 1500 for 120hz). You need to use toastyX's pixel clock patcher (on his forum) to have >330 pixel clock on AMD or Nvidia cards (there's a patcher for each one).

Is that true? Anything over 329 won't work at all? I had 125Hz at 1350, as well as 120Hz at 1500 with a flashed 2720Z and the control panel didn't complain. I felt like a had some skipping in fast scenes, so that might be it. Yet, even at 120Hz and 1350vertical you were still over 330Mhz

[Chief Blur Buster]

Is that true? Anything over 329 won't work at all? I had 125Hz at 1350, as well as 120Hz at 1500 with a flashed 2720Z and the control panel didn't complain. I felt like a had some skipping in fast scenes, so that might be it. Yet, even at 120Hz and 1350vertical you were still over 330Mhz

You can test for frame skipping at www.testufo.com/frameskipping

[Mouzuone]

I use firefox and get performance warnings all the time and messages that I should use chrome. It gives me a valid only a couple ofm seconds, before the next warning comes. Both, with 120Hz and 1350 vertical and 125 and 1350 v..
Gotta get chrome portable, I suppose.

Currently, I have set fps and Hz to 125. Persistence is set to 1ms and crosstalk to one right key stroke from the very left. NOT to the first mark. I hope that's how you meant it, but it seemed to be the best one to me, as well.
However, in-game I get a weird blurred horizontal line in the middle of the screen. I don't know if that is tearing or something else. vSync won't help, just gives me more input lag. Do you know what I mean? fps are 100% stable.

[lebowsky]

hi, tried the 1350/120hz, very nice picture and performance. my problem is, I play cs:go in 1280x960 4:3 stretched, so I need to force the stretch to fullscreen in the nvidia control panel. the dilemma, with 1350/120 I have a 4:3 screen with black bars in go and for scaling I need to choose a non-custom resolution. Any suggestions?