https://bugs.kde.org/show_bug.cgi?id=476866

--- Comment #7 from Prajna Sariputra <putr...@gmail.com> ---
Okay, I just found the bit of code that decides which device to use for
hardware encoding
(https://invent.kde.org/plasma/kpipewire/-/blob/master/src/vaapiutils.cpp?ref_type=heads#L34),
KPipeWire just gets the list of DRM devices and picks the first render device
from the list, that says it supports H.264 VAAPI, which in my case is
/dev/dri/renderD128, the discrete/secondary GPU.

So, I tried adding a hack to make the code pick the second device it finds,
which is /dev/dri/renderD129, the integrated GPU, and recompiled KPipeWire (do
I also need to recompile Spectacle or anything else?). With that, Spectacle
starts noticeably quicker, and recording also starts as soon as I click the
button, even when VP9 is selected as the format, whereas before the recording
only starts like 3s after I click the button.

However, it turns out that even when using the integrated GPU for encoding the
video output is still corrupted, but it's a different sort of corrupt, with the
discrete GPU I can make nothing out of the source at all, but with the
integrated GPU I can see bits of the source. I'll file a new bug report for the
corruption with more details.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to