https://bugs.kde.org/show_bug.cgi?id=526795
Austen Frazier <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Austen Frazier <[email protected]> --- Confirming on a second machine and a newer release. System: Arch Linux, Plasma 6.7.5, KPipeWire 6.7.5 and KRdp 6.7.5 (KRdp with a local backport of the virtual-monitor size fix only), kernel 7.2.9. Two GPUs: RTX 4090 (proprietary 615.78 driver, no VAAPI encoding) and the Radeon iGPU of a Ryzen 9 9950X3D (Mesa 26.2.4 radeonsi). KRdp is used with --virtual-monitor 2940x1912@2; the client is sdl-freerdp on macOS. Observed: Session rendered on the RTX 4090: KRdp logs VAAPI: current session render node "/dev/dri/renderD129" does not support H264 encoding and falls back to libx264. Dark backgrounds arrive grey and contrast is washed out, as described in this report. Same machine, same client, session moved to the Radeon (KRdp logs VAAPI radeonsi on renderD128): blacks are black. Code, 6.7.5 tarball: same cause as described above. LibX264Encoder's constructor builds scale=out_range=%1 from m_colorRange (src/libx264encoder.cpp:35-40) while it still holds the default Limited (src/encoder_p.h:121); H264VAAPIEncoder builds its graph in initialize() (src/h264vaapiencoder.cpp:100-101), after KRdp's setColorRange(Full), which is why only the VAAPI path is correct. (Disclosure: the code references were traced with an AI assistant and checked against the 6.7.5 source; the grey-vs-black observation is my own, on the same client before and after moving the session between GPUs.) -- You are receiving this mail because: You are watching all bug changes.
