Package request: wl-screenrec
Package name
wl-screenrec
Package homepage
https://github.com/russelltg/wl-screenrec
Description
High performance wlroots screen recording, featuring hardware encoding. Better than wf-recorder.
Does the requested package meet the package requirements?
System, Compiled
Is the requested package released?
Yes
Good alternative for wf-recorder, I like it 😃
Possibly requires ffmpeg 6.0 though, which is still in progress.
building it is not possible for me, anyone had succeed?
building it is not possible for me, anyone had succeed?
Here is the draft of the template:
# Template file for 'wl-screenrec'
pkgname=wl-screenrec
version=0.1.7
revision=1
build_style=cargo
hostmakedepends="pkg-config"
makedepends="ffmpeg6-devel clang19-devel libdrm-devel"
short_desc="High performance wlroots screen recording, featuring hardware encoding"
maintainer="Yushi <[email protected]>"
license="Apache-2.0"
homepage="https://github.com/russelltg/wl-screenrec"
distfiles="https://github.com/russelltg/wl-screenrec/archive/refs/tags/v${version}.tar.gz"
checksum=1a76d1061ecb54df53297f2394ae90087d7271cd8ae9081e34566857c8a3d77e
I can build the package with the template but it shows error when I execute it. Maybe it is missing some runtime dependency:
03:35:11 [WARN] there is a known vaapi codec (h264_vaapi) for codec H264, but it's not available. Using a generic encoder...
Opening libva device from DRM device /dev/dri/renderD128
03:35:11 [ERROR] failed to create encoder(s): Failed to load vaapi device: Cannot allocate memory. This is likely *not* a bug in wl-screenrec, but an issue with your vaapi installation. Follow your distribution's instructions. If you're pretty sure you've done this correctly, create a new issue with the output of `vainfo` and if `wf-recorder -c h264_vaapi -d /dev/dri/renderD128` works.
thread 'main' panicked at src/main.rs:922:51:
enc left in intermediate state
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
The runtime dependency is indeed vaapi drivers.
I built it with mesa-vaapi for my AMD laptop and it fixed the error.
For Nvidia, it should be nvidia-vaapi-driver, but I don't have one with me to test.
Try working with that if you're still interested.