Replies: 1 comment 3 replies
|
This would be great to have indeed. But as far as I know, mpv with these settings already present in perfect frame pacing and synchronization if the compositor supports the required stuff (like Mutter). The manual has more info on why these are the case. For example, Mutter supports both the FIFO protocol and v2 of presentation time protocol, so you can disable mpv's internal vsync with But I'm hoping VK_EXT_present_timing would further improve this or be much better. Also, Mesa has VK_EXT_present_timing in Mesa since 26.1 for Wayland, and will have support for X11/XWayland with Mesa 26.2. |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
VK_EXT_present_timing was recently merged into the Vulkan 1.4.335 specification and appears to already be supported, or soon supported, by several drivers.
I'm wondering whether there are any plans to make use of this in mpv's Vulkan backend.
From the Vulkan documentation:
According to the Khronos proposal and related blog posts, VK_EXT_present_timing provides a platform-independent way for applications to specify time-based presentation, allowing the compositor/driver to schedule frame presentation more precisely.
Since mpv already relies heavily on accurate frame pacing and A/V synchronization, this extension seems potentially relevant for improving presentation timing without relying on platform-specific mechanisms.
Would this provide any practical benefit for mpv, or is the current presentation timing approach already sufficient?
All reactions