Heavy Judders while playing movies on 165Hz Screen.

mpv Information

mpv v0.38.0-641-g6107112b Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on Jul 27 2024 00:04:43
libplacebo version: v7.349.0 (v7.349.0-dirty)
FFmpeg version: N-116435-g719e46f54
FFmpeg library versions:
   libavcodec      61.10.100
   libavdevice     61.2.100
   libavfilter     10.2.102
   libavformat     61.5.101
   libavutil       59.29.100
   libswresample   5.2.100
   libswscale      8.2.100

Other Information

• Windows version: Microsoft Windows [Version 10.0.22631.3958]
• GPU model, driver and version: NVIDIA GeForce RTX 3050 6GB Laptop GPU, Driver version: 32.0.15.6070
• Source of mpv:https://sourceforge.net/projects/mpv-player-windows/files
• Introduced in version: All

Reproduction Steps

I bought a new laptop with 165hz screen & while watching movies there are heavy judders especially in fast scenes, it's ruining the whole experience, i have tried various solution i could find over the internet like Gsync, Freesync, Vsync -On/Off, reducing refresh rates to 60, 48 hz, tried different versions of GPU drivers, used "video-sync=display-resample" along with intepolation also, still the issue is there.

Expected Behavior

Judder free media playback.

Actual Behavior

Heavy Judders

Log File

Log.log

Sample Files

No response

I carefully read all instruction and confirm that I did the following:

• I tested with the latest mpv version to validate that the issue is not already fixed.
• I provided all required information including system and mpv version.
• I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of --log-file=output.txt.
• I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
• I attached the full, untruncated log file.
• I attached the backtrace in the case of a crash.

Start by reviewing the attached Log.log alongside the reported mpv build, Windows version, NVIDIA GPU driver, refresh rates, and sync settings. Reproduce the judder with the same playback conditions and determine whether the log provides a specific, repeatable failure signal; done means the issue has an actionable diagnosis or a narrowly scoped fix path.