Arch Linux User Repository

Global hotkeys (shortcuts) are now supported on wayland, but only on kde plasma as only kde plasma supports this properly at the moment.

@ThatOneSeong I reverted back to using the same key for start/stop now. I'll instead look into how to make it more obvious that its recording

@ThatOneSeong Having both options as toggleable would make the ui more messy than it already is, but the bigger issue is that wayland cant really deal with that nicely. The reason why I separated start from stop is that it's not clear visually when recording is ongoing, if you started recording while in a fullscreen game. Some users have said that they have noticed later that it wasn't recording. With separate hotkeys you can press start hotkey multiple times without stopping it.

With nvidia shadowplay there is an overlay in the bottom right corner that shows that its recording and that overlay doesn't show up in the video but that isn't really possible on linux except with window capture only. I would use one hotkey for both start and stop if this could be done nicely, but im not sure how it should be done.

I'll look into it and see if I can give the option.

Would it be possible to re-add support for certain action pairs sharing a hotkey? i.e. using Ctrl+\ for both starting and stopping recording. It was part of my workflow, and when trying to force it in the config file, I get an immediate generic Failed to save video error (despite recording itself working just fine).

Global hotkeys (shortcuts) are now supported on wayland, but only on kde plasma as only kde plasma supports this properly at the moment.

@DexterHaxxor thanks, fixed

Please fix clang: error: argument unused during compilation: '-s' [-Werror,-Wunused-command-line-argument] when using Clang

Yes, I'm on AMD and both installations are running on Wayland. Playing on KDE feels smoother than Labwc. 100 FPS on Labwc feels like 30 FPS. But the recording on Labwc is smoother as you can see in the video. I'll send you all the information you asked by email.

@flxbr are both on wayland? if yes then there isn't any difference with recording on wayland compositors (recording is done by bypassing wayland compositor) so there shouldn't be any difference when it comes to this. Do you not notice any difference when playing and only notice the difference in the video itself? The frame timing of different wayland compositors can affect the jitter which you might not notice when playing if it's at high fps, until you slow it down. I would need full system info to know more (and output of sudo drm_info), reported as described here: https://git.dec05eba.com/?p=about

On labwc (wlroots compositor) the recording is smooth, but on KDE the recording is jittery. Do you know what could be causing this?

Here's a video comparing both: https://youtu.be/Z9H9afcptEE

5600X / 6800XT Arch Linux, both running the same kernel and drivers.