https://bugs.kde.org/show_bug.cgi?id=521356
--- Comment #8 from Yann Salmon <[email protected]> --- I am not sure. On the one hand, the current setting looks more like a workaround than an actual fix to me. On the other hand, I am not aware of how the responsibilities are divided between the different actors / software. Is it normal for krdpserver and/or the va library to need to be explicitly told which driver to (not) use via an env var? Isn't NVIDIA to blame for not exposing NVENC to VAAPI, or VA for not getting that fact ? Is it normal that krdpserver does not work either with KPIPEWIRE_FORCE_ENCODER=libx264 or KPIPEWIRE_FORCE_ENCODER=libx264_baseline (but maybe that would actually be another bug) ? And even if that is normal, is it normal that krdpserver "fails" so abruptly ? Shouldn't the disfunction be better handled ? My RDP client was set to negociate the image quality/transmission method with the server, and krdpserver seems to ne be doing that well. In the end, it remains that, in the same context (and distro), krdpserver and spectacle do not work out-of-the box but OBS screencast does (and it uses pipewire too). -- You are receiving this mail because: You are watching all bug changes.
