output drops frames that exceed 60fps (on a 240hz panel)

[krob64]

mpv Information

mpv v0.38.0-dirty Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects
 built on May 23 2024 10:29:03
libplacebo version: v6.338.2
FFmpeg version: n6.1.1
FFmpeg library versions:
   libavutil       58.29.100
   libavcodec      60.31.102
   libavformat     60.16.100
   libswscale      7.5.100
   libavfilter     9.12.100
   libswresample   4.12.100

Other Information

• Linux version: NAME="Arch Linux"
• Kernel Version: Linux archlinux 6.7.4-273-tkg-bore The big pull request of pending changes #1 SMP PREEMPT_DYNAMIC TKG Thu, 15 Feb 2024 19:11:46 +0000 x86_64 GNU/Linux
• GPU Model: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3060 Ti Lite Hash Rate] [10de:2489] (rev a1)
• Mesa/GPU Driver Version: OpenGL version string: 4.6.0 NVIDIA 550.78
• Window Manager and Version: i3 version 4.23 | no compositor
• Source mpv: pacman
• Introduced in version: n/a

Reproduction Steps

neither --no-config (& --profile-fast) nor ctrl+h fixed the issue.

step 1: grab a >60fps 1080p video (f.e. this small clip https://blurbusters.com/hfr-120fps-video-game-recording/)

step 2: use mpv to play it back. press shift+i and look at "Dropped Frames: [...] x (output). it should increase by ~60 each second.

Expected Behavior

i expected to not drop any frames when playing back a 120fps video on a 240hz panel

Actual Behavior

what happens instead is that all of the frames exceeding 60fps are being dropped. 60fps videos work just fine, no dropped frames there. never had any issues with high fps playback in the browser either, 240fps streams on twitch are working as expected.

this screenshot was taken upon hitting 5 seconds into the video.

Log File

mpv_issuelog.txt

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.