Raising refresh rate cannot eliminate sample-and-hold judder from moving content

What it is

Once refresh rate is high enough to clear the critical flicker fusion frequency, the "can I see flicker" problem is already solved — but whether motion in the displayed content looks smooth is a completely separate problem that doesn't get fixed automatically just by raising refresh rate further. Moving content can still show a choppy, jumpy look mixed with trailing blur, a phenomenon called judder (sample-and-hold judder), often just called motion blur or stutter.

This is easy to conflate with "motion looks rough because the refresh rate isn't high enough," which leads to the mistaken belief that raising refresh rate will cure it. What actually determines whether motion looks smooth is the mismatch between the display's frame-by-frame hold presentation and the eye's continuous tracking of a moving object — not how fast frames switch.

Why it happens

Most modern mainstream displays are sample-and-hold: once a frame is computed, it's held on screen unchanged for the entire refresh interval, jumping to the next frame only at the next refresh — the image is completely static within each frame, and motion shows up only as a position jump between frames. When the eye performs smooth pursuit to track a moving object, the eyeball rotates continuously at a matched speed, but the object's image on the retina goes "static for a frame, instant jump, static for another frame" in a staircase pattern — the two don't line up. The static portion within each frame gets smeared into a short blurred trail by the tracking eye, and the jump between frames adds another layer of discontinuity on top; together these two effects are the source of judder and motion blur.

Simply raising refresh rate and shortening each frame's hold time can reduce the physical distance each frame gets smeared over to some extent, easing the blur, but as long as the display remains a sample-and-hold structure — each frame's content held unchanged for a while, then jumping — this mismatch mechanism persists. Raising refresh rate just makes the judder finer-grained and less obvious, without eliminating the underlying mismatch between sample-and-hold presentation and smooth pursuit. The targeted fixes (black frame insertion, scanning backlight, presentation closer to impulse-driven display) change "how long each frame is held and how it's presented," not just "how often frames change."

Studying it

The typical paradigm is a motion clarity assessment: participants perform smooth pursuit with their eyes on a target moving at constant speed on screen (usually text or a sharp-edged graphic), and the degree of blur/trailing, or edge sharpness, is compared across different display technologies, refresh rates, and presentation methods (whether black frames are inserted, whether an impulse-driven backlight is used) — either through subjective report or objective measurement. A high-speed camera recording the actual displayed content under simulated tracking eye movement can also serve as an objective measure of the resulting blur trail. Independent variables include refresh rate, the proportion of time each frame is held (duty cycle), and content motion speed; the dependent variable is a subjective blur rating or an objectively measured edge-sharpness value.

This differs methodologically from the purely flicker-detection research covered elsewhere: flicker detection measures whether static-image light/dark alternation can be seen, while motion clarity measures whether moving content stays sharp under tracking eye movement. These are different dependent-variable systems, and a flicker-fusion experiment's design and conclusions cannot answer a motion-clarity question.

Where it stops holding

• This is only noticeable on the object actually being tracked; a static background is unaffected. Judder and trailing require the eye to be performing smooth pursuit; if a user's gaze isn't following the moving object (glimpsing an animation in the corner of the eye, say), the mismatch mechanism doesn't show up to the same degree.
• The faster the motion, the more noticeable the problem. Slowly moving content shows relatively mild trailing and judder; fast-scrolling text or a fast-panning view exposes this most readily.
• Different display technologies are affected to different degrees. Displays using impulse-driven or scanning backlights, or actively inserting black frames, meaningfully ease this problem because they change the key variable — how long each frame is held — so motion clarity between different presentation methods should not be compared using refresh rate numbers alone.
• This entry covers judder caused by the display side's presentation method. It is a related but distinct cause from the source content's own frame rate being too low (like the 3:2 pulldown mismatch common when film content's frame rate doesn't match a display's refresh rate) — the two shouldn't be treated as the same problem to fix.

Applying it

• When feedback says "motion feels choppy, there's trailing," first confirm the flicker-perception issue has already been ruled out (critical flicker fusion frequency is already exceeded); if flicker is invisible but motion still looks smeared, the problem sits in the sample-and-hold structure itself, and simply telling users or the product team to "raise the refresh rate" likely won't touch the root cause.
• For scenarios demanding high motion clarity — fast-scrolling long lists, fast-panning maps or canvases — prefer a display solution that supports black frame insertion, impulse-driven backlighting, or similar techniques, rather than comparing refresh-rate numbers alone.
• On the content side, controlling motion speed (avoiding unnecessary high-speed scrolling or panning) lowers the demand on motion clarity — a supplementary lever that doesn't depend on display-hardware improvements.
• Verification: have testers actively track fast-moving text or a graphic edge on screen with their eyes and rate edge sharpness and whether trailing is present, rather than only testing for flicker with a static image — the two measure completely different things, and passing the static test doesn't mean motion clarity also passes.

Related

• Same group: A1.08.1 Flicker above the critical frequency is perceived as steady · A1.08.2 The critical frequency shifts with brightness and visual-field position · A1.08.6 Fusion thresholds apply to static images; motion blur perception follows different rules
• Nearby: A1.14 Motion perception
• Search terms: judder · sample-and-hold · motion blur · black frame insertion