wf-recorder VS wlroots

Try wf-recorder.

The closest thing is probably wf-recorder.

The spec is designed to be minimal and it's expected for compositors to work together and add additional features, for example here is the tool for screen recording on wlroots compositors (sway and what most wayland WM's use) https://github.com/ammen99/wf-recorder, even though most people claim wayland doesn't support screen-recording/screenshotting. We just don't have a universal tool for that that works on all compositors, pipewire however seems to be coming to fill that niche.

If you are on Wayland, wf-recorder Is a good choice .

As for screen recording, I’ve used wf-recorder (IIRC, not at PC atm) several times the past couple of weeks, works equally well.

The issue I'm encountering is described here in more detail (including images).

Wfrecorder [0] is what I use, doesn't have a fancy gui but it just works

0: https://github.com/ammen99/wf-recorder

A workaround for sharing the whole screen is to use wf-recorder [1], which supports capturing the whole screen, and feeding its output to a virtual V4L2 device using v4l2loopback [2]. Software that is able to capture from a V4L2-compatible webcam (i.e. most) can them capture from the virtual device without knowing anything about Wayland. It's not exactly the most CPU-efficient way of doing things, but if you can afford the cycles it works very well!

[1] https://github.com/ammen99/wf-recorder

[2] https://github.com/umlaeute/v4l2loopback

You want to use wf-recorder. This is in my sway config:

> set $screenrecord wf-recorder -g "$(slurp)" -f ~/screenshots/mov-$(date +"%Y-%m-%d--%H-%M-%S.mp4")

> bindsym Shift+Control+F6 exec $screenrecord

> bindsym Ctrl+Shift+BackSpace exec killall -s SIGINT wf-recorder

Hitting shift-control-f6 will spawn slurp which lets you click and drag to set the area you want to record. This will then launch wf-recorder and record the selected area, saving to ~/screenshots/mov-${date}. You can use ctrl-shift-backspace to kill the recorder and end recording.

https://github.com/ammen99/wf-recorder

https://github.com/emersion/slurp

>barrier has been unmaintained for a long time.

As if not having new features added for 2 years makes it stop working? barrier is perfectly fine on normal linux desktop installs. I actually use synergy 1.x personally which has been "unmaintained" for much, much longer. Except synergy 1.x will compile and run on anything from windows 98 to ubuntu 5 to debian 12. You can't get a waynergy or inputleap to compile on an OS more than 2 years old. And even then, as you say, it's crapshoot if the particular wayland will have libei; many like sway are actively hostile to it and never will: https://github.com/swaywm/wlroots/issues/2378

It looks like they actually patched it to filter those modes out, so presumably it worked out of the box and was considered undesirable: https://github.com/swaywm/wlroots/issues/3038

I haven't experienced any of those. The video game performance hit may be due to vsync, but I don't play games so I haven't noticed.

You can however use tinywl. It is an example Wayland compositor that can't do more than displaying one application.

Sway/wlroots has implemented this, but I can't find any discussion for KDE.

wlroots is archived on github. Is it abandoned? Just saying, that only means they moved git hosts :-D

A lot of compositors are based no the wlroots lirbary. So they are still sharing the development effort and have a common base, its just in the form of a library rather than a display server.

gamescope use wlroots