green-recorder VS wf-recorder

As the developer of Green Recorder [1], the second example referred to in this page, I have to say that it sounds my abandonment statement is taken out of context.

In order to support recording on different Wayland compositors (without having to develop tons of other middle layers by yourself), one would need to simply activate their built-in screencasting tool according the specified user settings. This took me a bit of time to figure out for GNOME, and I had to fill a bug-report to speak to one of the compositor developers to understand how to do that, as no documentation was available at all. Even so, some hidden bugs appeared (Quality wasn't too good, audio had to be recorded separately over ffmpeg, and then both audio and video had to be merged together in one file, V9 had a bug that consumes 100% of CPU on some hardware, so we had to use V8 by default... etc).

In order to go further, I had to do the same thing for KWin on Wayland, Sway and other compositors out there in the market and then integrate them into my program. I had to find some workarounds for any bugs that may occur.

Later on, some changes for ffmpeg API broke the Xorg recording (Green Recorder used ffmpeg to record on all desktop environments on Xorg), so I had to do more testing now for multiple versions of ffmpeg and on which distro do they work and don't work.

So I just gave up, as I simply didn't find any particular reason to continue doing that since the only amount of support I received on my then-opened Patreon was $20 per month at its max.

But it shouldn't be said that Wayland can not support screencasting or that it breaks screencasting. It is possible, and the previously mentioned issues are actually on the compositors' developers side, not the protocol.

1: https://github.com/mhsabbagh/green-recorder

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