https://bugs.kde.org/show_bug.cgi?id=525619
--- Comment #3 from Conn O'Griofa <[email protected]> --- I mentioned in the relevant bug report, but to reiterate, I tested 3fad2bbcdcbd087c11a9f3b7848bc2043ccc2341 backported onto v6.7.4 and it resolved stuttering for fixed rate capture. KWin's incoming pipewire buffer rate was about 3% under the target on the 6.7 branch and earlier when fixed rate was negotiated. Testing a build against v6.7.90 tag with 3fad2bbcdcbd087c11a9f3b7848bc2043ccc2341 reverted, the incoming framerate is now erroneously doubled (~120fps for a 60/1, 60fps session). I can't really comment on smoothness as Moonlight is reporting constant network jitter (which happens when the rate exceeds the target) and so it obviously is stuttering for that reason. Do you want me to try partially reverting 3fad2bbcdcbd087c11a9f3b7848bc2043ccc2341 by leaving the precision change but reverting the frame schedule changes? I suspect that it will still exhibit the 120fps issue. Is there a later commit that further changes this? Perhaps I can try building against the commit-timing HEAD with the schedule changes manually reverted (but not the precision part)? ... Just a small update for the Sunshine side. I understand it's a pain to compile the patch I referenced just to test KWin, so I sent a PR to ensure that Sunshine handles KWin 6.8 beta versions properly for selecting fixed rate capture. The next release will include it or you can grab the artifacts from the PR runner results: https://github.com/LizardByte/Sunshine/pull/5704 Sunshine's logs will let you know what kind of rate negotiation happens. You want to see (60/1) rather than variable rate (0/1) being negotiated for maxFramerate to reproduce this issue: ``` [conn@archlinux sunshine]$ cat ~/.config/sunshine/sunshine.log | cut -b28- | grep -Ei "frame|pacing" | sort | uniq Info: [pipewire] Compositor negotiated frame rate: 0/1, max: 60/1 Info: [pipewire] Requested frame rate: 60fps Info: [pipewire] Sunshine frame pacing: disabled (event-driven capture) ``` -- You are receiving this mail because: You are watching all bug changes.
