From f49ecc31c4d2a187c4c479e84fc6e6acaf5231f2 Mon Sep 17 00:00:00 2001 From: Ivan Molodetskikh Date: Sun, 3 Aug 2025 13:29:48 +0300 Subject: pw_utils: Wait for frame completion before queueing Without explicit sync, we have no way to signal the PipeWire consumer when the rendering is done. So, wait until it's done before giving it the frame. This should fix flickering screencasts on NVIDIA. --- wiki/Configuration:-Debug-Options.md | 17 ----------------- 1 file changed, 17 deletions(-) (limited to 'wiki/Configuration:-Debug-Options.md') diff --git a/wiki/Configuration:-Debug-Options.md b/wiki/Configuration:-Debug-Options.md index 299437ca..ad74dba7 100644 --- a/wiki/Configuration:-Debug-Options.md +++ b/wiki/Configuration:-Debug-Options.md @@ -21,7 +21,6 @@ debug { force-pipewire-invalid-modifier dbus-interfaces-in-non-session-instances wait-for-frame-completion-before-queueing - wait-for-frame-completion-in-pipewire emulate-zero-presentation-time disable-resize-throttling disable-transactions @@ -155,22 +154,6 @@ debug { } ``` -### `wait-for-frame-completion-in-pipewire` - -Since: 25.05 - -Wait until every screencast frame is done rendering before handing it over to PipeWire. - -Sometimes helps on NVIDIA to prevent glitched frames when screencasting. - -This debug flag will eventually be removed once we handle this properly (via explicit sync in PipeWire). - -```kdl -debug { - wait-for-frame-completion-in-pipewire -} -``` - ### `emulate-zero-presentation-time` Emulate zero (unknown) presentation time returned from DRM. -- cgit