https://bugs.kde.org/show_bug.cgi?id=516067
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|REOPENED |RESOLVED --- Comment #6 from Zamundaaa <[email protected]> --- This is the gap between presentations, in number of frames: > 8, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 5, 3, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 5, 3, 4, 4, 4, 5, 3, 5, 3, 5, 4, 4, 4, 3, 4, 5, 3, 4, 5, 3, 5, 4, > 4, 4, 4, 3, 5, 4, 3, 4, 5, 4, 4, 4, 4, 4, 3, 4, 5, 4, 3, 4, 5, 4, 3, 4, 5, 4, > 4, 4, 4, 4, 4, 3, 5, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 5, 3, 4, 4, 4, 4, 4, 4, 4, 4, 4, 5, 3, 4, 4, > 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, > 4, 4, 5, 3, 4, 4, 4, 4, 5, 3, 5, 4, 4, 4, 3, 5, 3, 5, 3, 5, 3 So, there are a few frames delayed by one refresh cycle in there, as well as a few frames early by one refresh cycle... but the video doesn't really stutter so much as it actually just plays at 30Hz. I did some digging, and it looks like mpv relies on the refresh counter of the presentation time protocol. The protocol unfortunately ties that refresh counter to the presentation output, which causes problems for example when switching presentation from an output to a screencast - we'd have no way to make the client differentiate between "we just skipped forward or backward by 1000 refresh cycles" and "the meaning of the value changed" - so KWin always sends zero instead (which the protocol reserves as an invalid value that clients are expected to handle). For now it's best if mpv adds a fallback for this situation, and in the long term maybe we can amend the presentation time protocol in some way to decouple it from outputs. -- You are receiving this mail because: You are watching all bug changes.
