From 9d7e90ec2eb08ae925341bcc650f7e075a497cec Mon Sep 17 00:00:00 2001 From: Gilles Schintgen Date: Sun, 1 Sep 2024 20:20:29 +0200 Subject: [PATCH] docs(troubleshooting): update note on AMD lowlatencyenc (Linux) (#3117) Co-authored-by: ReenigneArcher <42013603+ReenigneArcher@users.noreply.github.com> --- docs/troubleshooting.md | 29 ++++++++++++++--------------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md index 3eb72cf8..da91630d 100644 --- a/docs/troubleshooting.md +++ b/docs/troubleshooting.md @@ -143,25 +143,24 @@ often grub is used to load the kernel and set its command line.) ### AMD encoding latency issues If you notice unexpectedly high encoding latencies (e.g. in Moonlight's -performance overlay) or strong fluctuations thereof, this is due to -[missing support](https://gitlab.freedesktop.org/drm/amd/-/issues/3336) -in Mesa/libva for AMD's low latency encoder mode. This is particularly -problematic at higher resolutions (4K). - -Only the most recent development versions of mesa include support for this -low-latency mode. It will be included in Mesa-24.2. - -In order to enable it, Sunshine has to be started with a special environment -variable: +performance overlay) or strong fluctuations thereof, your system's Mesa +libraries are outdated (<24.2). This is particularly problematic at higher +resolutions (4K). +Starting with Mesa-24.2 applications can request a +[low-latency mode](https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/30039) +by running them with a special +[environment variable](https://docs.mesa3d.org/envvars.html#envvar-AMD_DEBUG): ```bash -AMD_DEBUG=lowlatencyenc sunshine +export AMD_DEBUG=lowlatencyenc ``` +Sunshine sets this variable automatically, no manual +configuration is needed. -To check whether low-latency mode is being used, one can watch the `VCLK` and -`DCLK` frequencies in `amdgpu_top`. Without this encoder tuning both clock -frequencies will fluctuate strongly, whereas with active low-latency encoding -they will stay high as long as the encoder is used. +To check whether low-latency mode is being used, one can watch the VCLK and DCLK +frequencies in amdgpu_top. Without this encoder tuning both clock frequencies +will fluctuate strongly, whereas with active low-latency encoding they will stay +high as long as the encoder is used. ### Gamescope compatibility Some users have reported stuttering issues when streaming games running within Gamescope.