mpv-player / mpv-player/mpv

Multi-monitor with different refresh rates causes dropped frames.

Open
#9,686 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

down-upstream:nvidia os:linux
Dominant language
C
Stars
37k
Forks
3.5k
Avg merge
1d 10h
Merged PRs (30d)
22

Description

mpv 0.34.1
Arch
Arch Official repositories
Kwin
Nvidia 495.46

Reproduction steps

While using multiple monitors with different refresh rates, use display-resample, starting the video and going into or out of fullscreen repeats the issue.

Expected behavior

mpv will pick up the refresh rate of the monitor where the window is and have no significant amount of dropped, mistimed and delayed frames.

Actual behavior

mpv picks the wrong refresh rate, and shows a lot of mistimed/delayed and dropped frames during the first few seconds, it gets stable after some time but the estimated refresh rate continues to show the refresh rate of the other monitor.
The issue happens every time in the 144Hz monitor, but i only saw the issue in the 60Hz monitor once while testing on KDE. I was also able to replicate this issue on GNOME Wayland and Xorg, on Wayland the 60Hz monitor would have the issue more often.
This is similar or possibly identical to #9339 but on Linux.

Log file

output.txt

Sample files

Anything that I've tested caused the issue.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with display-resample on multiple monitors using different refresh rates, including fullscreen transitions under Wayland and Xorg. Review the attached output.txt and compare the reported refresh rate and frame timing on each monitor; done means the active monitor is selected and dropped, mistimed, and delayed frames no longer occur.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
desktop, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.