FPS estimate when on secondary display is wrong, possibly based on the primary monitor?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Important Information
Note: May be related to?: https://github.com/mpv-player/mpv/issues/11465
When having the mpv window on the secondary screen it estimates the fps based on the primary screen:
Provide following Information:
- mpv version
mpv 0.35.0-326-ge1727553 - Windows Version:
Microsoft Windows 11 Pro, 10.0.22621, Build 22621 - Source of the mpv binary: https://github.com/shinchiro/mpv-winbuild-cmake/releases/tag/20230317
Reproduction steps
Open MPV via: >mpv --no-config -v -v --log-file=debug.txt --video-sync=display-resample --vo=gpu-next ytdl://https://www.youtube.com/watch?v=7ePaVk7TKGM
Move video from 180Hz main screen to another screen that is 60Hz.
Expected behavior
Estimate should be ~60Hz
Actual behavior
Estimate is 180Hz, taken from the wrong monitor.
Log file
https://0x0.st/s/31O7IqeOxpbLcRA8oNwyew/H-_u.txt
Sample files
I was using a youtube video as demo via ytdl inside mpv (See command up top): https://www.youtube.com/watch?v=7ePaVk7TKGM`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the provided mpv command, moving the video between the 180Hz primary display and the 60Hz secondary display, then inspect debug.txt and the linked related issue. Done means the display-sync FPS estimate follows the monitor containing the mpv window and reports approximately 60Hz on the secondary display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop-dev, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100