fix(linux/pipewire): try variable rate for non-KWin compositors - #5569
Merged
ReenigneArcher merged 2 commits intoAug 30, 2026
Merged
Conversation
2 tasks
psyke83
force-pushed
the
pw_mutter_variable_rate
branch
4 times, most recently
from
August 29, 2026 03:08
b18310f to
bbfcf5f
Compare
psyke83
marked this pull request as ready for review
August 29, 2026 04:11
Variable rate capture works better on mutter, but since GNOME 50 we encountered negotiation failures. It seems that if we negotiate maxFramerate with a default of variable rate but relaxed maximum value, the final negotiation phase actually lands on variable rate (after being constrained to the host refresh rate); mutter debug included: [2026-08-29 00:38:43.671]: Info: [pipewire] Framerate (from compositor): 0/1 [2026-08-29 00:38:43.671]: Info: [pipewire] Framerate (from compositor, max): 60/1 SCREEN_CAST: Video format changed to 1920x1080 (framerate: 0/1 (max: 60/1)) SCREEN_CAST: Video format changed to 1920x1080 (framerate: 0/1 (max: 0/1)) [2026-08-29 00:38:43.672]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture) Pacing does seem to be improved and Sunshine reports variable rate for the *final* negotiation phase. Upstream MR has been submitted, but doesn't seem strictly necessary: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/5278 With upstream MR applied, output is more uniform: [2026-08-29 00:35:42.248]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture) [2026-08-29 00:35:42.248]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture) [2026-08-29 00:35:42.248]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture) [2026-08-29 00:35:42.248]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture) SCREEN_CAST: Video format changed to 1920x1080 (framerate: 0/1 (max: 0/1))
ReenigneArcher
force-pushed
the
pw_mutter_variable_rate
branch
from
August 30, 2026 04:52
a571568 to
7ed7985
Compare
|
Bundle ReportBundle size has no change ✅ |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #5569 +/- ##
========================================
Coverage 33.91% 33.91%
========================================
Files 104 104
Lines 25193 25193
Branches 11145 11145
========================================
Hits 8543 8543
- Misses 13624 13793 +169
+ Partials 3026 2857 -169
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 42 files with indirect coverage changes Continue to review full report in Codecov by Harness.
|
This was referenced Sep 7, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Variable rate capture works better on mutter, but since GNOME 50
we encountered negotiation failures.
It seems that if we negotiate maxFramerate with a default of variable rate
but relaxed maximum value, the final negotiation phase actually lands on
variable rate (after being constrained to the host refresh rate); mutter
debug included:
[2026-08-29 00:38:43.671]: Info: [pipewire] Framerate (from compositor): 0/1
[2026-08-29 00:38:43.671]: Info: [pipewire] Framerate (from compositor, max): 60/1
SCREEN_CAST: Video format changed to 1920x1080 (framerate: 0/1 (max: 60/1))
SCREEN_CAST: Video format changed to 1920x1080 (framerate: 0/1 (max: 0/1))
[2026-08-29 00:38:43.672]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture)
Pacing does seem to be improved and Sunshine reports variable rate for the
final negotiation phase.
Upstream MR has been submitted, but doesn't seem strictly necessary:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/5278
With upstream MR applied, output is more uniform:
[2026-08-29 00:35:42.248]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture)
[2026-08-29 00:35:42.248]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture)
[2026-08-29 00:35:42.248]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture)
[2026-08-29 00:35:42.248]: Info: [pipewire] Framerate (from compositor): 0/1 (variable rate capture)
SCREEN_CAST: Video format changed to 1920x1080 (framerate: 0/1 (max: 0/1))
Screenshot
Issues Fixed or Closed
Roadmap Issues
Type of Change
Checklist
AI Usage
See our AI usage policy.