Native Gnome recorder (Ctrl+Alt+Shift+R) records only 30 seconds and exposes no user interface to change record duration, select the screen area or target format. Needless to say it doesn’t allow to edit the screencast to drop unnecessary frames.
byzanz - simply doesn’t work on Wayland.
➜ ~ byzanz-record
usage: byzanz-record [OPTIONS] filename
➜ ~ byzanz-record /tmp/xxx
Given area is not inside desktop.
wf-recorder should work on Wayland, but on Fedora it does not.
➜ ~ wf-recorder
compositor doesn't support wlr-screencopy-unstable-v1
simplescreenrecorder honestly tells that it doesn’t work.
So is there anything that works out of the box with the following features?
Sure—would you like to set up a wiki page or a quick doc on this please?
(I personally prefer that folks go to Ask Fedora and search/ask questions because that way it becomes a self maintaining, self curated source of information. With wikis/docs, someone has to regulary go through them to ensure that they’re all up to date.)
There should be a limit of going into rabbit holes to shave yaks at which one needs to stop, or he will have nothing to eat. So unfortunately, I can only contribute a small rant about Ask Fedora as a source of information.
What are the chances that I could discover Kooha after finding two closed answers with not such option? StackOverflow at least allows to add new and edit answers, which is necessary to make a source of information self-curated or self-maintaining, but not enough. For that to be enough, there should be a gameplay, like points, popularity or something. Editing a wiki page on the internet that even original authors doesn’t seem to care about much is not inspiring. Or maybe they care, but there is no way to get in touch with them. The ideal workflow is a magazine article with some initial research, which gets comments for a while and then converted to “quick doc” that is updated and discussed as new people jump in. I guess that wiki page has thousands of hits every month, but 0 engagement for the function that is very critical to any development and getting feedback about software wrongdoings.
Well, I understand all the opportunities. Just finding excuses not to do this, because the problem is already solved. What is not solved is editing the resulting .gif, for which I had to usegifsicle (size optimization) + gifcurry (trimming). Next time I will try losslesscut.
It sounds more fun to record a video with review of available tools and their UI/UX, and problems encountered, but doing this alone is not very exciting.