Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/russelltg/wl-screenrec

High performance wlroots screen recording, featuring hardware encoding
https://github.com/russelltg/wl-screenrec

Last synced: 3 months ago
JSON representation

High performance wlroots screen recording, featuring hardware encoding

Lists

README 

        
# wl-screenrec



High performance screen recorder for wlroots Wayland. 



Uses dma-buf transfers to get surface, and uses the GPU to do both the pixel format conversion and the encoding,

meaning the raw video data never touches the CPU, leaving it free to run your applications.



Open an issue if something is not working, I'm happy to take a look.



# System Requirements



* wayland compositor supporting the following unstable protocols:

  * [`wlr-output-management-unstable-v1`](https://wayland.app/protocols/wlr-output-management-unstable-v1) 

  * [`wlr-screencopy-unstable-v1`](https://wayland.app/protocols/wlr-screencopy-unstable-v1)



   [Sway](https://swaywm.org/), [Hyprland](https://hyprland.org/), and [wayfire](https://wayfire.org/) all meet this criteria.

* [`vaapi`](https://01.org/temp-linuxgraphics/community/vaapi) encode support, consult your distribution for how to set this up. Known good configurations:

  * Intel iGPUs

  * Radeon GPUs



# Performance



(relatively unscientific) benchmark setup:

- 4kp60 display

- i9-11900H CPU/GPU

- `vkcube` running on screen, as both `wf-recorder` and `wl-screenrec` don't copy/encode frames when there is no difference



| command                                       | CPU Usage | GPU 3D Δ | GPU Video Δ |

| --------------------------------------------- | --------- | -------- | ----------- |

| `wf-recorder`                                 | ~500%     | +44%     | 0%          |

| `wf-recorder -c h264_vaapi -d /dev/dri/card0` | ~75%      | +88%     | +23%        |

| `wl-screenrec`                                | ~2.5%     | +91%     | +30%        |



Additionally, with either `wf-recorder` setup there is visible stuttering in the `vkcube` window. `wl-screenrec` does not seem to stutter at all.



However, it does come at the cost of using slightly more GPU. Those number seem stable and I hypothesize that they are statistically significant,

but still not a huge change.



# Installation



## From the AUR



```bash

paru -S wl-screenrec

# OR

paru -S wl-screenrec-git

```

Or, manually:

```

git clone https://aur.archlinux.org/wl-screenrec-git.git

cd wl-screenrec-git

makepkg -si

```



## From source using cargo



Install ffmpeg 6 or later, which is a required dependency.

ffmpeg 5 may work, but is untested (open an issue or PR if you test with ffmpeg 5

so I can update these docs on if it works or not)



```bash

cargo install wl-screenrec # stable version

# OR

cargo install --git https://github.com/russelltg/wl-screenrec # git version

```



## FreeBSD



There is currently an [upstream bug](https://github.com/zmwangx/rust-ffmpeg/pull/152) preventing

builds on FreeBSD from succeeding, but you can fix this by patching the `rust-ffmpeg` dependency:



```bash

git clone https://github.com/russelltg/wl-screenrec

cd wl-screenrec

echo '[patch.crates-io]

ffmpeg-next = { git = "https://github.com/russelltg/rust-ffmpeg", branch = "fix_freebsd_build" }' >> Cargo.toml

cargo install --path .

```



# Usage



Capture entire output:



```bash

wl-screenrec         # valid when you only have one output

wl-screenrec -o DP-1 # specify outuput

```



Capture region:



```bash

wl-screenrec -g "$(slurp)"    # use slurp

wl-screenrec -g "0,0 128x128" # manual region

```



Capture 444 video (no pixel format compression):



> NOTE: Look at `vainfo -a` to see your supported pixel formats. Support is very 

> hardware-dependent. For example, on my machine only HEVC suports 444 formats, and

> all of 8-bit RGB formats didn't work for whatever reason.



```bash

wl-screenrec --codec hevc --encode-pixfmt vuyx   # 8-bit 444

wl-screenrec --codec hevc --encode-pixfmt xrgb10 # 10-bit 444

```



Capture with audio:



```bash

wl-screenrec --audio                                                                 # default capture device

wl-screenrec --audio --audio-device alsa_output.pci-0000_00_1f.3.hdmi-stereo.monitor # capture desktop audio (example, use `pactl list short sources` to figure out what you should put here)

```



Record with history:

```bash

wl-screenrec --history 10 & # record the most recent 10 seconds into memory, not writing into the file

# ... some important event occurs

killall -USR1 wl-screenrec  # flush the most recent 10 seconds onto the file, and start appending to the file like recording normally

```



Capture to [v4l2loopback](https://github.com/umlaeute/v4l2loopback) (for Zoom, etc):



```bash

sudo modprobe v4l2loopback

v4l2-ctl --list-devices # find "Dummy video device" device. /dev/video6 in my case.

wl-screenrec --ffmpeg-muxer v4l2 -f /dev/video6

```



# All options



```text

$ wl-screenrec --help

Usage: wl-screenrec [OPTIONS]



Options:

      --no-hw

          don't use the GPU encoder, download the frames onto the CPU and use a software encoder. Ignored if `encoder` is supplied

  -f, --filename 

          filename to write to. container type is detected from extension [default: screenrecord.mp4]

  -g, --geometry 

          geometry to capture, format x,y WxH. Compatible with the output of `slurp`. Mutually exclusive with --output

  -o, --output 

          Which output to record to. Mutually exclusive with --geometry. Defaults to your only display if you only have one [default: ]

  -v, --verbose...

          add very loud logging. can be specified multiple times

      --dri-device 

          which dri device to use for vaapi. by default, this is obtained from the drm-lease-v1 protocol, if present. if not present, /dev/dri/renderD128 is guessed

      --low-power 

          [default: auto] [possible values: auto, on, off]

      --codec 

          which video codec to use. Ignored if `--ffmpeg-encoder` is supplied [default: auto] [possible values: auto, avc, hevc, vp8, vp9, av1]

      --ffmpeg-muxer 

          Which ffmpeg muxer to use. Guessed from output filename by default

      --ffmpeg-encoder 

          Use this to force a particular ffmpeg encoder. Generally, this is not necessary and the combo of --codec and --hw can get you to where you need to be

      --encode-pixfmt 

          which pixel format to encode with. not all codecs will support all pixel formats. This should be a ffmpeg pixel format string, like nv12 or x2rgb10

      --encode-resolution 

          what resolution to encode at. example: 1920x1080. Default is the resolution of the captured region. If your goal is reducing filesize, it's suggested to try --bitrate/-b first

  -b, --bitrate 

          bitrate to encode at. Unit is bytes per second, so 5 MB is 40 Mbps [default: "5 MB"]

      --history 

          run in a mode where the screen is recorded, but nothing is written to the output file until SIGUSR1 is sent to the process. Then, it writes the most recent N seconds to a file and continues recording

      --audio

          record audio with the stream. Defaults to the default audio capture device

      --audio-device 

          which audio device to record from. list devices with `pactl list short sources` [default: default]

      --audio-backend 

          which ffmpeg audio capture backend (see https://ffmpeg.org/ffmpeg-devices.html`) to use. you almost certainally want to specify --audio-device if you use this, as the values depend on the backend used [default: pulse]

      --no-damage

          copy every frame, not just unique frames. This can be helpful to get a non-variable framerate video, but is generally discouraged as it uses much more resources. Useful for testing

      --gop-size 

          GOP (group of pictures) size

  -h, --help

          Print help

  -V, --version

          Print version

```



# Known issues



- Cannot capture a region that spans more than one display. This is probably possible but quite difficult, espeicially with potential differences in refresh rate. Probably will never be supported.