Backlight Strobing Explained: ULMB, DyAc, Motion Clarity, and Crosstalk

A conventional LCD is normally sample-and-hold: after a frame is scanned to the panel, its image remains visible while the next refresh is prepared. When your eyes track a moving object, that persistence contributes to perceived motion blur even if the pixels transition quickly.

Backlight strobing reduces that visible persistence by keeping the LCD backlight dark for part of each refresh and flashing it during a narrower window. NVIDIA describes ULMB this way, while BenQ ZOWIE describes DyAc as a backlight-control technique intended to make moving imagery clearer. The technique changes light emission timing; it does not make the game render more unique frames.

The strobe duty cycle is the fraction of a refresh period during which the backlight is visibly on. Shortening that window can reduce persistence, but less on-time also means less emitted light unless the backlight can compensate with higher pulse brightness.

NVIDIA's original ULMB example used a 25 percent duty cycle and therefore kept the backlight off for 75 percent of the time. NVIDIA says that implementation traded brightness and sometimes refresh rate for motion clarity. Its later ULMB 2 design was created to support full-refresh-rate strobing with higher brightness on qualified displays. Those brightness and effective-motion-clarity figures are NVIDIA's certification and product claims, not independent Core Tech Tips measurements.

Strobing does not erase LCD response time. Pixels still need to transition from the previous frame to the next target value. If the backlight flashes while parts of the panel are still transitioning, old and new image information can become visible together as duplicated edges or strobe crosstalk.

The timing problem is harder because an LCD refresh is scanned progressively rather than every row changing at exactly the same instant. NVIDIA says ULMB 2 uses vertically dependent overdrive so pixel response is adjusted according to scan position before the backlight pulse. That describes NVIDIA's implementation; other strobing systems can use different panel, firmware, overdrive and backlight strategies.

NVIDIA ULMB and BenQ ZOWIE DyAc are not generic standards that every monitor implements identically. Both use controlled LCD backlight timing to improve motion clarity, but their supported displays, refresh modes, tuning and operating requirements are product-specific.

ZOWIE says DyAc and DyAc+ switch the backlight on and off at controlled points, while DyAc 2 uses a dual-backlight design plus its own circuitry and firmware. NVIDIA's ULMB 2 instead documents requirements around full-refresh-rate strobing, brightness, effective motion clarity and low crosstalk. Treat the brand name as evidence of a particular implementation, not a universal performance score.

Traditional strobe modes work most predictably when refresh timing is fixed, because the display knows when each scan and backlight pulse will occur. NVIDIA's ULMB 2 instructions explicitly require G-SYNC variable refresh rate to be disabled before ULMB 2 is enabled on supported monitors.

That limitation is not a permanent law of display engineering. NVIDIA's newer G-SYNC Pulsar implementation is specifically designed to pulse the backlight while retaining VRR behavior. The useful distinction is therefore between the exact monitor mode and implementation, not a blanket claim that all strobing is incompatible with variable refresh.

When evaluating a strobe mode, check the refresh rates at which it operates, brightness in that mode, visible crosstalk across different screen regions, overdrive artifacts, and whether VRR remains available. Also confirm whether the feature requires a firmware update, specific input mode, or particular GPU ecosystem.

A higher refresh rate can reduce sample-and-hold persistence even without strobing, while a well-tuned strobe mode can make motion look clearer at a lower physical refresh rate. Those are different mechanisms. Do not convert a vendor's effective-motion-clarity figure into an assumed panel refresh rate, response time, FPS, or end-to-end latency.

Competitive games with rapid camera movement and target tracking are the clearest use case because persistence blur can make moving detail harder to follow. A strobe mode is less compelling when its brightness reduction, flicker perception, fixed-refresh requirement, crosstalk, or mode restrictions matter more to the user than the motion-clarity gain.

The safest comparison is model-specific. Verify the monitor's supported strobe modes and then use trustworthy measurements for brightness, response behavior, crosstalk and latency rather than assuming that ULMB, DyAc or another blur-reduction label makes one display universally better.